GET STARTED
DOCUMENTS
APPS
API
INTEGRATION
GALLERY
Transport Order Extensions

A Transport Order is the smallest shippable quantity which can fit into a single container/transport equipment configured by a Shipper Org to best fit their planning needs. Shippable Quantity or the "Ready to Ship" represents a request for transportation that includes goods picked up from one location (a Shipping Site) at one time and can contain lines going to different Final Destinations.

Transport Order extracts shipment specific information from the Ready to Ship. All the extracted data (i.e. carrier, B/L, Port of Load, Port of Discharge) will be stored with the Transport Order itinerary after it is planned on a specific Transport Plan.

Ready To Ship can be associated with multiple Transport Orders, but on the contrary a Transport Order can NEVER be associated with more than one Ready To Ship.

A Transport Order can be aligned with one or more Transport Plan.

Explanation of Extensible Transport Order Events

On Create

The onCreate extension point will fire once per object insert. It will be only on the first save.

On Save

The onSave extension point will fire on every Save.

NOTE: Users can update the reference fields. Fields mapped from the downstream objects cannot be updated.
Roles and Abilities of Transport Order Extensions
Events Roles Query Modify Modify Others
On Create Consolidator, Customer Yes Yes Yes
On Save Consolidator, Customer Yes Yes Yes
Query Fields

The following fields can be used in your OQL to filter TransportOrderShipment(s):

  • transportOrderNumber
  • transportOrderUid
  • poNumber
  • shippingOrderNumber
  • packageBookingNumber