Cubing Operation with Order Detail OBLPN Type
Generally, Oracle Transport Management (OTM) plans to have multiple order details in a single planned parcel shipment number or a load from different order headers, if the orders have the same ship to destination. Currently, the OBLPN type information is available at the Order header level in the system and as per the Order Header’s OBLPN type, all corresponding order details acquires the same OBLPN type, irrespective of the item size. When cubing the order details, the system utilizes the Order Header’s OBLPN type and cubing with varying OBLPN types for order details is not supported.
To provide flexibility of having the OBLPN type at the order detail level and perform cubing based on different OBLPN types, following changes to the UIs are enhanced:
- You can view the Outbound LPN Type in the following UIs.
- “LPN Type” column in the Order Header (OrderHdrView) > Order Detail screen.
- “Dtl OB LPN Type” column in the OB Orders (OBOrdersView_FW) UI (flattened view).
- “LPN Type” column in the Input Interfaces (InputInterfaceView) > Stage Record button > Order Detail screen.
NOTE: If the order detail status is “Created”, you can edit the LPN type on the Order Detail screen.
- A new selection field “Order Dtl OB LPN Type” is added to the Dynamic wave search selection criteria (Wave Template > Wave template searches > Dynamic Wave > Selection Criteria). This allows filtering order details based on LPN type during wave execution and allocation. The corresponding wave run matches the order detail OBLPN type as per the criteria and allocates the details accordingly.
- To facilitate filtering and creating tasks based on the Order Detail OBLPN type, a new column “Order Dtl OB LPN Type” is added in the Task Creation Template (TaskCreationView) > Details > Selection Criteria and Cubing Rules (CubingRuleView) > Details > Selection Criteria.
On running a wave template, while performing cubing (only in Cubing Mode-1 to Use Predetermined OBLPN Type), the system now considers the LPN type from the configured templates or UIs in the following sequence:
- Wave Template
- Order Detail screen
- Order Header UI
- Item UI
PLANNED OB LOAD INTERFACE CHANGES
To provide flexibility in sending OBLPN types for order details, a new field ob_lpn_type is added in the order detail section of Planned OB Load input interface (XML format).
ORDER INTERFACE CHANGES
To accommodate the specification of OBLPN types for individual order detail, a new field ob_lpn_type is added to the order detail section of all existing interface formats for the Order Interface.
NOTE: On entering an invalid LPN type to update or send, the system alerts you with an error message “Invalid LPN Type”.
On successful execution of the Planned Parcel Shipment or Planned OB Load interface, the system updates the LPN type field (at the order detail) for the corresponding orders/order details in the order list.
Steps to Enable
You don't need to do anything to enable this feature.