ASN Splitting

Overview

ASN splitting is required when an inbound Transfer Order booking is directly supplying goods to one or more outbound Sales Orders. In other words, certain Sales Orders have been prioritised by the client (ROOM) to be allocated goods directly from an inbound Transfer Order.

Operationally this means that when the warehouse receives all the goods in the inbound Transfer Order, instead of putting them all away in the warehouse, they must separately allocate goods to the correct outbound Sales Orders, and place those goods in a “cross-dock” area ready for fulfilment, without the need to put all goods away and then pick & pack to those sales orders.

To instruct the warehouse, the inbound Transfer Order needs to be split into multiple ASNs are follows:

• One ASN for each Sales Order that has been allocated to this Transfer Order, each containing the goods required by the individual Sales Order, and containing the linked inbound ASN booking reference to indicate the cross-dock instruction

• One ASN for the remaining goods (i.e. all SKUs / quantities left over after all the linked Sales Orders have been processed) - these are the goods not needed for cross-dock and so will be put away.

Please note that any inbound Transfer Order that has no linked Sales Orders, will be treated as one ASN where all goods will be put away.

Processing

When the user clicks the button to ‘Send ASN’ for an inbound Transfer Order, the following processing must be done:

1. LINKED SALES ORDERS: Determine all the Sales Order Bookings stored in the system (with Booking. Booking Reason = SALES ORDER) that are linked to this Transfer Order (via the “allocate goods from” link in domain model)

2. GOODS CHECK: Check that the Goods within the Transfer Order can fulfil all the linked Sales Orders. So calculate the total quantity by SKU across all the linked Sales Orders; each of those SKUs must exist within the Transfer Order’s Goods, and the total quantity by SKU across all the linked Sales Orders must be less than or equal to the quantity of the corresponding SKUs in the Transfer Order

3. IF GOODS CHECK FAILS: Set the following:

   1. Booking. Is WMS Success = FALSE

   2. Booking. WMS Error Message = “Not enough goods in Transfer Order to fulfil linked Sales Orders”

   3. (NB this will need remediation outside the system, and requiring updates from ROOM to either the Transfer Order or the linked Sales Orders, or both, before ‘Send ASN’ can be re-attempted)

4. IF THE GOODS CHECK PASSES: proceed with below

5. STORAGE PREP OF SALES ORDER STATUS: For each linked Sales Order, check if an instance of “WMS ASN Split Status” against this Transfer Order booking already exists with ASN Split Ref = the linked Sales Order’s Booking Ref. If it exists, do nothing at this stage. If it does not exist, create a new instance of “WMS ASN Split Status” against this Transfer Order, with Is Success = null, and ASN Split Ref = the linked Sales Order’s Booking Ref. See below and https://bigdigit.atlassian.net/wiki/spaces/SMH/pages/3274768397 page.

6. STORAGE PREP OF TRANSFER ORDER STATUS: For the main Transfer Order, check if an instance of “WMS ASN Split Status” against this Transfer Order booking already exists with ASN Split Ref = this Transfer Order’s Booking Ref. If it exists, do nothing at this stage. If it does not exist, create a new instance of “WMS ASN Split Status” against this Transfer Order, with Is Success = null, and ASN Split Ref = this Transfer Order’s Booking Ref. See below and https://bigdigit.atlassian.net/wiki/spaces/SMH/pages/3274768397 page.

   Open

   

7. SEND CROSS DOCK ASNS: For each linked Sales Order:

   • if the corresponding instance of WMS ASN Split Status has Is Success = null or FALSE, invoke WMS 'Load Receipts’ API call below for scenario NEW / CROSS DOCK

   • If the corresponding instance of WMS ASN Split Status has Is Success = TRUE, invoke WMS 'Load Receipts’ API call below for scenario UPDATE / CROSS DOCK

8. SEND RESIDUAL ASN: For the main Transfer Order:

   • if the corresponding instance of WMS ASN Split Status has Is Success = null or FALSE, invoke WMS 'Load Receipts’ API call below for scenario NEW / ASN

   • If the corresponding instance of WMS ASN Split Status has Is Success = TRUE, invoke WMS 'Load Receipts’ API call below for scenario UPDATE / ASN

9. STORE ASN STATUS: Store the result of each WMS ‘Load Receipts’ API call above into the corresponding instance of WMS ASN Split Status:

   • If API call returns success, set WMS ASN Split Status. Is Success = TRUE and set WMS ASN Split Status. WMS Error Message to null

   • If API call returns failure, set WMS ASN Split Status. Is Success = FALSE and set WMS ASN Split Status. WMS Error Message to the returned error message from the API call

10. STORE OVERALL STATUS: Process the overall Transfer Order Booking as follows:

    1. If ALL WMS ASN Split Status instances were successful:

       • Set Booking. Is WMS Success to TRUE

       • Clear the value of Booking. WMS Error Message to null

       • Set Booking. Status to ASN SENT

    2. If one or more WMS ASN Split Status instances were unsuccessful:

       • Set Booking. Is WMS Success to FALSE

       • Set the value of Booking. WMS Error Message to “one or more ASNs could not be transmitted to the warehouse”

       • Do not transition the Booking. Status (it remains in status CREATED)

    3. All this information, including the individual WMS ASN Split Status. WMS Error Message values, must be handed to the front-end API for display on the user’s UI.

Load Receipts API call (Scenario parameters)

The following fields represent the WMS ‘Load Receipts’ API call to send either or a NEW or UPDATE for either a CROSS DOCK or a normal ASN, as described above:

Load Receipts Line Items

The following fields must be populated per Load Receipts Line Item. These must each correspond to the separate instances of goods within either the linked Sales Order (CROSS DOCK scenario) or the residual goods in the ASN after all linked sales order goods have been taken out (ASN scenario):