Versions Compared

Old Version 1

changes.mady.by.user Steven Bennett

Saved on

compared with

New Version 2

changes.mady.by.user Steven Bennett

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

...

Clearly for phase 1 we are not supporting anything regarding this but we will need to use the principles of the fully-electronic signalling and flow to allow manual signals from operators in earlier phases.

Receive & Putaway Task

Transfer Order Cancellation

Depending on Workflow status, e.g. if the ASN has already been sent, then an ASN cancellation will need to be sent. See 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 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)

  • Task Status: CLIENT CANCELLED

  • update display so that the only action the operator can do next is to Cancel the booking.

When Operator Cancels the booking:

  • Task Status = CANCELLED

  • update display so that the only action the operator can do next is to ‘close’ (dismiss) the booking.

  • Task Status: CLIENT AMENDED

  • update display so that the operator can see what has changed, during the workflow planning process

ASN PENDING

(Transfer Order only)

  • Task Status: ASN PENDING - CLIENT CANCELLED

  • update display so that the only action the operator can do next is to Cancel the booking.

When Operator Cancels the booking:

  • Task Status = CANCELLED

  • update display so that the only action the operator can do next is to ‘close’ (dismiss) the booking.

  • Task Status: ASN PENDING - CLIENT AMENDED

  • update display so that the operator can see what has changed and must select to re-plan

When Operator selects to re-plan:

  • Task Status = REPLANNING

  • allow operator to make changes to the task & workflow prior to confirming the new plan

ASN SENT

  • Task Status: ASN SENT - CLIENT CANCELLED

  • update display so that the only action the operator can do next is to Cancel the booking.

When Operator Cancels the booking:

  • Send an ASN Cancellation message to the Warehouse

  • Task Status = CANCELLED

  • update display so that the only action the operator can do next is to ‘close’ (dismiss) the booking

  • Task Status: ASN SENT - CLIENT AMENDED

  • update display so that the operator can see what has changed and must select to re-plan

When Operator selects to re-plan:

  • Send an ASN Cancellation message to the Warehouse

  • Task Status = REPLANNING

  • allow operator to make changes to the task & workflow prior to confirming the new 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.

Sales Order Cancellation

Out

...