Service lists are, unlike the orders, stateless. All operations performed on these lists are performed internally, therefore no integration settings are needed.
Except mentioned lists management is very similar to working with orders.
Unlike service of items by external vendors, items with internal service vendors are added to service list directly when service of an item is requested. This allows to speed up the service process, when items can be picked for service right after they are returned for service without need to wait for scheduled script to run or need to create service list manually.
Service of by internal vendors is illustrated on following flow:
Request service of item
- Request of service is invoked by returning of item for service by user or automatically by system, when automatic service rules are set for serialized item (if serialized item is picked in production at this time, it is added to the list in moment when it is returned)
- When request is made, item is directly added to service list for respective vendor and device. If list does not exist, it is automatically created
Item is added to the list directly on SFI allowing an operator to proceed with service flow right after items has been returned for service
Pick items for service
- Pick for service can occur directly after service of item has been requested
Restock items
- Since item has been picked for service, it can be restocked back to system
- Picked items can be marked as scrapped on both AP and SFI
Service completed Since item is restocked or scrapped, it is removed from the list. List remains in the system and will be reused next time when service of some item is requested