Transportation Split Creation

Transportation split allows you to load a single order detail to multiple loads. This trigger may come from OTM based on their loading capacity.

You can perform transportation split via Planned Load Interface.

To perform the transportation split for an order detail, do the following:

1. Open the Planned OB Load Interface .xml file.
2. Enter the Order details to split.

   Based on the planned_qty, the system splits the order detail. If you skip the planned_qty entry, the system plans the load for the complete order detail quantity. Also, you can enter multiple order details to assign the load.

   Note: If multiple details are added, the system identifies and filters the order details in the following sequence to uniquely identify an order detail (to be interfaced in the Planned OB Load interface file).

   • order_nbr + order_seq_nbr
   • erp_fulfillment_line_ref
   • 4 part key
   • ship_request_line
3. Enter a Load Number (External Planned load) to assign for the order detail.
4. Enter the “CREATE” action code at the load level.
5. Save the file.
6. Navigate to the Input Interfaces UI.
7. Select Planned OB Load from the drop-down list.
8. Click Upload and choose the saved Planned OB Load Interface .xml file.
9. Click Upload.

   You can observe the uploaded file under the Files tab.

   

10. Click Run Interface to run the Planned OB Load interface file.

    The system displays a pop-up message “Interface completed”. If any execution fails, the system displays an error message.

    You can check the processed records under the Stage Record tab.

Note: During Transportation Split, the only reference to find the new Order details created from the source order detail is from the Order detail reference number field. The Order Detail Original Sequence Number field is available (in all file formats) to be shared via the WOA output interface (WAVE PICK INFO), SLS Output Interface, OBLPN Shipping info Output interface, and Pallet Shipping info Output interface.

Points for Consideration:

• The system displays an error message in the following conditions:
  • If the Planned Load Quantity > Order Detail Quantity.
  • If the Planned Load Quantity > (Order Detail Quantity - Shipped Quantity).
  • If Order Detail does not exist.
  • If the Planned Quantity is 0.
  • If the Order Detail has any allocated Quantity. No pending allocations should be present for the Order Detail.
• If you leave “qty_uom_code” as blank, by default, the system considers the Item Primary UOM as UOM Code.
• As you are splitting the Order Detail, every time the system creates a new sequence number. So, the unique identifier here is the 4-part key (erp_source_hdr_ref + erp_source_line_ref + erp_source_shipment_ref + erp_fulfillment_line_ref).

For example, consider an order ORD-01 requires 100 quantities of SKU-1.

Order Before Planning:

Order Number	SKU	Ordered Quantity	External Planned Load Number
ORD-01	SKU-1	100

If you plan LOAD-1 and LOAD-2 with 50 and 20 quantities respectively via Planned OB Load Interface, the system splits the 100 quantities of ORD-01 order detail and updates the order details as follows.

Order Number	SKU	Ordered Quantity	External Planned Load Number
ORD-01	SKU-1	30
ORD-01	SKU-1	50	LOAD-1
ORD-01	SKU-1	20	LOAD-2