Support Backordered Sales Order Line Split or Update via Planned Load Interface
4 Part Key (erp_source_hdr_ref + erp_source_line_ref + erp_source_shipment_ref +erp_fulfillment_line_ref) links orders in Order Management to multiple systems. Each fulfillment order line is treated as a separate order in WMS.
Generally, the combination of 4 Part Key is supposed to be unique for each order line. But, certain scenarios create multiple order lines with same 4 Part Key. So, WMS-OTM integration supports 4 Part Key duplication for multiple order lines.
Following are scenarios where Fusion Shipping creates a new order line with a different Ship Request line but the same 4 Part Key.
- When Order Management increases the back order (created due to shorting) quantity, Fusion Shipping creates a new order line with a different ship request line but the same 4 Part Key.
- When Fusion Shipping splits the order coming from Order Management, the WMS receives two Sales Orders with the same 4 Part Key.
WMS-OTM integration happens based on the 4 Part key. So, to plan the external load, the Planned Load Interface supports handling of the same 4 Part Key for multiple order details. For more details on how to update an externally planned load quantity or order details for an order detail, refer to Update/Delete an Externally Planned Order Detail.
If multiple eligible orders or lines are available with the same 4 Part Key, while planning the load, the system compares and sequences the orders based on the following criteria. So that the system fulfills and ships the orders with the earlier required ship date and higher ordered quantity.
- Ascending sequence of the required ship date of the order.
- Descending order of the required quantity (Ordered Quantity).
- Planned Quantity should be less than the required quantity (summed up value) of all eligible orders or order line. If you plan more than the required quantity, the received planned load interface fails.
- If you decrease the planned quantity of a load (spread across multiple eligible orders), the system unassigns the load in the reverse order of the assignment. The system sorts the orders in the descending order of the required ship date and in case of a tie, uses the ascending order of the required quantity.
Example:
Consider the following orders are created with the same 4 Part Key.
| Order ID | Sequence | SKU | Ordered Quantity | External Load | 4 Part Key | Required Ship Date |
|---|---|---|---|---|---|---|
| 123 | 1 | ABC | 20 | - | 1.1.2.1 | 06/10/2024 |
| 124 | 1 | ABC | 7 | - | 1.1.2.1 | 06/10/2024 |
Assume that you have planned an external load “Load-1” with 22 units (4 Part Key is 1.1.2.1). For planning the load, the system uses the following criteria.
- The system checks for the ascending sequence of the required ship date. Here, the required ship date is the same for both orders. So, the system goes for the next criteria.
- The system checks for the descending sequence of the ordered quantity. Here, the ordered quantity for Order ID “123” is more. So, the system fulfills the Order ID “123” first.
Post-planning of external load “Load-01”, the system updates the orders as follows.
| Order ID | Sequence | SKU | Ordered Quantity | External Load | 4 Part Key | Required Ship Date |
|---|---|---|---|---|---|---|
| 123 | 1 | ABC | 20 | Load-1 | 1.1.2.1 | 06/10/2024 |
| 124 | 1 | ABC | 5 | - | 1.1.2.1 | 06/10/2024 |
| 124 | 2 | ABC | 2 | Load-1 | 1.1.2.1 | 06/10/2024 |