Background
Client Orders may be cancelled or amended at any time, but this will mean the system needs to perform certain actions to ‘unwind’ previously-completed actions in respect of that booking.
...
See https://bigdigit.atlassian.net/wiki/spaces/SMH/pages/3251601441/Standard+Tasks+within+a+Workflow#Receive-%26-Put-Away task status flow. The following table shows the ideal processing that would need to occur depending on the possible statuses of this task when a Client ASN or Inbound Client TRANSFER ORDER is Cancelled or Amended:
Task Status | On Client Booking API Cancellation | On Client Booking API Amendment |
---|---|---|
CREATED REPLANNING (task has yet to be confirmed planned) |
When Operator Cancels the booking:
|
|
ASN PENDING (Transfer Order only) |
When Operator Cancels the booking:
|
When Operator selects to re-plan:
|
ASN SENT |
When Operator Cancels the booking:
|
When Operator selects to re-plan:
|
GOODS RECEIVED GOODS PUTAWAY | These scenarios are extremely unlikely and will probably be a client error. It should probably be flagged with an error message / alert condition for the SEKO operator to call up the client and ask what is going on. |
Transport Task
See https://bigdigit.atlassian.net/wiki/spaces/SMH/pages/3251601441/Standard+Tasks+within+a+Workflow#Transport. The following table shows the ideal processing that would need to occur depending on the possible statuses of this task when a Client ASN or Inbound Client TRANSFER ORDER or outbound Client SALES ORDER is Cancelled or Amended:
Task Status | On Client Booking API Cancellation | On Client Booking API Amendment |
---|---|---|
CREATED REPLANNING (task has yet to be confirmed planned) |
When Operator Cancels the booking:
|
|
CARRIER INSTRUCTED |
When Operator Cancels the booking:
|
When Operator selects to re-plan: |
CARRIER ACCEPTED | ||
IN TRANSIT | ||
DELIVERED |
Sales Order Cancellation
Out
...