Versions Compared

Old Version 3

changes.mady.by.user Steven Bennett (Unlicensed)

Saved on

compared with

New Version 4

changes.mady.by.user Steven Bennett (Unlicensed)

Saved on

Key

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

Background

...

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:

Current Task Status

On Client Booking API Cancellation

On Client Booking API Amendment

CREATED

REPLANNING

(task has yet to be confirmed as 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 whole workflow

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 whole workflow

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

Then when planning has been completed/ confirmed:

  • regenerate the ASN.

  • Compare it the previously-sent ASN. If they are the same, do nothing.

  • If they are different:

    • Send an ASN Cancellation message to the Warehouse

    • Send the new ASN to the Warehouse

GOODS RECEIVED

GOODS PUTAWAY

(ASN or Transfer Order only)

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 any booking is Cancelled or Amended but it has a workflow which includes any Transport task:

Task Status

On Client Booking API Cancellation

On Client Booking API Amendment

CREATED

REPLANNING

(task has yet to be confirmed as 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

CARRIER INSTRUCTED

  • Task Status : CARRIED → CARRIER INSTRUCTED - , CLIENT CANCELLED

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

When Operator Cancels the booking:

  • Recalculate the Carrier Consolidated Instruction Consolidation across all bookings, based on the removal of this booking. If the previously issued instruction has changed, send an Instruction Amendment to that carrierTask Status =

    • send an Instruction Amendment to that carrier for each Instruction that has changed

    • send an Instruction Cancellation to that carrier for each Instruction that was previously sent but no longer exists

  • Task Status → CANCELLED

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

  • Task Status → CARRIER INSTRUCTED, CLIENT AMENDED

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

When Operator selects to re-plan:

  • Task Status = REPLANNING

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

Then when planning has been completed/ confirmed:

  • Recalculate the Carrier Instruction Consolidation across all bookings, based on the amendment to this task.

    • send an Instruction Amendment to that carrier for each Instruction that has changed

    • send an Instruction Cancellation to that carrier for each Instruction that was previously sent but no longer exists

    • send a new Carrier Instruction for each new consolidated instruction that now exists

CARRIER ACCEPTED

  • Task Status → CARRIER ACCEPTED, CLIENT CANCELLED

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

When Operator Cancels the booking:

  • Recalculate the Carrier Instruction Consolidation across all bookings, based on the removal of this booking.

    • send an Instruction Amendment to that carrier for each Instruction that has changed

    • send an Instruction Cancellation to that carrier for each Instruction that was previously sent but no longer exists

  • 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 - → CARRIER ACCEPTED, CLIENT AMENDED

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

When Operator selects to re-plan:CARRIER ACCEPTED

  • Task Status = REPLANNING

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

Then when planning has been completed/ confirmed:

  • Recalculate the Carrier Instruction Consolidation across all bookings, based on the amendment to this task.

    • send an Instruction Amendment to that carrier for each Instruction that has changed

    • send an Instruction Cancellation to that carrier for each Instruction that was previously sent but no longer exists

    • send a new Carrier Instruction for each new consolidated instruction that now exists

IN TRANSIT

DELIVERED

These scenarios are extremely unlikely and will probably be a client error. It should 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

...