Auto-create Ocean Booking and Shipping Containers on Transport Order creation
Ocean Bookings often have to be created by hand after the Material Order (MO) already carries the recommended Port of Loading (POL), Port of Discharge (POD) and recommended Shipping Container.
As customer you can now let Control Tower create the Ocean Booking (OB) and shipping containers automatically when a Transport Order is created, so the TO can move on without a separate booking step.
How To Use
How To Use
Open Transport Order Form settings.
Enable Auto create Ocean Booking and/or Enable Auto-create Shipping Containers
Set a default Booking Type in the same settings. Booking Type is taken from TO Form settings, not from the MO.
Link Material Orders with recommended POL/POD and or shipping containers together to create a TO.
The Rule
The OB is created when recommended POL and POD are present and the same across all MOs on the TO, and Booking Type can be resolved from settings.
If POL/POD is missing or differs across MOs, or Booking Type is not set, the TO is still created and no Ocean Booking is added.
With the setting off, Ocean Booking stays manual.
Shipping Containers are created based on the given amount in the Material Orders.
Default Order contact on Transport Orders
In default the Order Contact of the Transport Order is the user who created the order or tendered the order via Spot (Best Carrier). This is shared to carriers too to make them aware whom to contact in case of questions.
In some cases there are standard users to be contacted. This can be set up now in Divisions Master Data per Division. If this has been set up this user will be shown as Order contact for all orders created of that division.
Carriers will see the Name of the user, Email Address and Phone number when given.
How To Use
How To Use
Open Master Data --> Division and enter the default Order contact by choosing the user from Accounts Master Data
Create or open a Transport Order. The Order contact is filled from that default and can be sent to Carrier Portal / carrier applications.
Force Finish Enhancement for not started Transport Orders - Ready for Pickup
Force Finish used to apply only once a Transport Order was at least In transit. When collect never arrives, the TO never reaches that status, so Force Finish cannot close it for downstream processes such as Ready for billing. As customer you can now opt in so Force Finish also considers orders that are Ready for pickup in the Transport Order Settings.
For more details please have a look at the Transport Order Status documentation.
Improvements
The package milestone API
/v1/transportOrders/{transportOrderCode}/packages/{packageIdentifier}/packageMilestonenow accepts the same extra fields as the package-level milestone API: reason code collect/deliver, original carrier status, standard carrier status, and carrier status data.Transsmart mapping can override the shipment reference with the Transport Order’s package identifier when a single package identifier is present (
$SinglePackageIdentifierCode). Configure this per division and carrier in the Transsmart mapping table; other mappings stay unchanged.