Creating additional Order Release Ship Units by agent DSU
Summary:
OTM Cloud 26A: Creating additional Order Release Ship Units by agent DSU works, but ship units do not behave correctly due to Order Configuration
Content (please ensure you mask any confidential information):
We are working on Oracle Transportation Management Cloud 26A.
Our business case is container transport. One Order Release may represent multiple physical containers, for example: 3X20 RF
Business-wise, we need to capture container number and seal number per physical container. We originally considered storing this data on shipment/equipment, but this is not safe for us because our Hold/Edit process may unassign/delete the Buy Shipment and re-plan it. Therefore, we want the stable execution object to be the Order Release Ship Unit, not the Buy Shipment.