Equipment Hierarchy in OTM

The below image shows the Equipment Hierarchy in OTM

Capacity

Location Capacity:

• Location capacity allows you to define different types of constraints for a particular location.
• When the Check Location Capacity parameter is set to TRUE, location capacity constraints are honored.
• A location is assumed to have unlimited capacity unless it is imposed by capacity constraints.
• While a capacity calendar is closely related to the business calendar, they should not be combined. When creating a capacity calendar, keep in mind the business calendar of the location.
• The relationship between the capacity calendar and a location is established in the location manager roles tab by attaching a location capacity group to the location.

Capacity Limits:

Operational Planning > Capacity Management > Capacity Limits

Capacity Limits can be used to manage service provider inventory of equipment by date range and determine a service provider's available capacity for accepting a shipment for transport.

Capacity Group ID: Capacity Groups allow you to identify and define groups of rate offerings from the same service provider.

Equipment Type ID: OTM measures capacity limits against equipment types for service providers that have available capacity.

To use capacity functionality, you must create an equipment group in shipments with only one equipment type in that group designated for capacity, and then select the same equipment type when you create a capacity limit

Lane ID:Select a Lane ID for this capacity limit.

OTM Integration

Inbound Data Methods

• HTTP

1. WMServlet is the default servlet used when sending the Transmission http://hostname/GC3/glog.integration.servlet.WMServlet 
2. Large Transmission Servlet
3. Transformer Servlet(XSL Files)
4. DirLoad Servlet(The DirLoadServlet does not raise events (like shipment - created for ActualShipment) so automation agents cannot be triggered)

• Send Via Web Interface to Application Tier
• Oracle Advanced Queuing
• Manually Upload XML
• Direct XML Insert into transmission table(pkg/proc name --> pkg_integration_util. insert_transmission).

XML documents being sent inbound to Oracle Transportation Management are not required to specify the namespace in the XML. OTM will automatically generate XID based on BN generators in OTM

Data Queues:

The inbound data queue events reside in the Q_INTEGRATION_IN Data Queue table. 

The outbound data queue events reside in the Q_INTEGRATION_OUT Data Queue table.

By default the PUBLIC queues are inactive. To activate the queues, login as DBA.ADMIN and edit the Data Queue records via the Data Queue Manager (under Business Process Automation à Integration menu). 

Transactions:

You can send many transactions in or out of Oracle Transportation Management in one transmission

but to separate the transactions, every transaction must be wrapped in a GLogXMLElement.

A Transmission Body element wraps one or more GLogXMLElement elements in a Transmission

Transmission Status:

• STAGED: Indicates that the Transmission is initially stored in the transmission tables, and is awaiting some pre-preprocessing steps such as sequencing of the Transactions for processing.
• STAGING: Indicates that the Transmission has been staged and is waiting on a condition to be released for processing. Additional transactions can be added to it prior to processing.
• FRESH: Indicates that the Transmission is waiting to complete processing. The individual transactions may still be processing.
• ERROR: Indicates that the Transmission had completed processing and there were errors in the processing.
• PROCESSED: Indicates that the Transmission successfully completed processing.
• REDO: Indicates that the Transmission is waiting for the REDO logic to initiate re-processing.
• MESSAGE: Indicates that the Transmission is a Message

Blank Out Certain Fields: To delete (null out) values from certain fields in a record (without deleting the whole record), you can specify the (~) character in the element.

Integration Saved Queries:

• Arg Values: The queries are written as SQL statements that contain references to the information in the incoming XML transmission 
• XPath Reference: The queries can also be written using XPath expressions to search for values from specific elements in the XML

Transaction Code  DR (Delete Reference)  will only delete reference between objects and not the object.

Transaction Code RC (Replace Child)  will update the parent element and delete and replaces the child elements.

Processing Codes for TransOrder XML

• NOPLN: Instructs OTM not to plan shipments
• PLN: Instructs OTM to plan shipments from OR assuming transorder setup to create order release already exists

Outbound XML Profiles:  Out XML Profiles are used to exclude portions of outbound XML with a high degree of control.

OTM can automatically change text to upper case when processing the inbound XML by setting the below property to true.

glog.integration.enableCaseChange=true

CutOff and Recovery Times

Cut-off Time: The time before which Deliveries need to be brought to the origin airport prior to a flight.

Recovery Time: Certain amount of time that the delivery must wait at the destination before it is ready.

• Both of them can be applied at rate service, service provider and location level
• If there are multiple Cut-off Recovery Time records that apply to a particular shipment, OTM looks first at the rate service, then the service provider, and finally the location.
• The times are also listed as wait time for the associated shipment stop

Buy Shipment Actions

Append Shipment: If the append-to shipment has handling shipments or secondary charges, or is in a shipment group, you will not be able to append the shipment

• Shipment1 - last stop is a drop-off
• Shipment1 last stop and Shipment2  first stop must be the same location
• Shipment1 must not be tendered
• Shipment2 must not be in-transit
• Shipment1 and Shipment2 should have only one freight s_equipment

Divert Shipment: is used to change destination location for a shipment.

Split Shipment: When splitting a shipment, you have the option of splitting to a direct shipment or a parallel shipment.

Direct: 

Parallel: takes on the characteristics of the original shipment

Console: It places the shipment on a new consolidation shipment

A new shipment, when split, does not go through a replanning process but takes on the characteristics of the original shipment; for example, same start and end time; same source and destination location, same rate offering, same rate service, same equipment, same preceding and succeeding shipments

Approve For Execution Action:

• Select this option when you do not want the shipment tendered automatically.
• To approve a shipment for execution and tender it automatically, select Secure Resources Action
• You can execute shipments that have the status value SECURE_RESOURCES_NOT STARTED.
• When you approve a shipment for execution, OTM changes the status to REVIEW_EXECUTE.

Commitment Allocaiton

Commitment allocations are percentage commitments to your carriers.

Commitment allocations are a lane-level percentages assigned at Rate Offering/Service Provider level. If you want assign service provider A with 30% of Shipments and Service Provider B with 70% of shipments for a particular lane, then set the allocation percentage for that service provider A to be 30% and service provider B to 70%.

If you want to set-up percentage allocations to repeat on weekly/monthly/quarterly/annually, then select the option while creating commitment allocation.

Commitment allocation is considered by the planning engine if the plan shipments with carrier commitment parameter is TRUE

Note: When each of two carriers has an unfulfilled commitment count, but only one has an unfulfilled allocation percentage commitment, the one with the unfulfilled percentage commitment takes priority.
 
Note: Allocation by rate offering is supported for setup, tracking, and service provider. Allocation by rate offering is not supported for route selection or container optimization.
 
Assign allocation group if you want to be able to define different commitment allocations on the same lane

Note: The parameter APPLY ALLOCATION GROUP ON PRIMARY LEG ONLY impacts this. The parameter determines whether the allocation group from the order will be matched to the allocation group on the commitment allocation for all shipments on the itinerary path or only the shipment on the primary leg

Order Release Actions for Shipment Creation

Bulk Plan:

Bulk planning is the consolidation of two or more orders into one or more shipments
Use this action when you want Oracle Transportation Management to determine the optimal shipment plan for multiple order releases at one time. Oracle Transportation Management builds direct or multi-stop shipments with the least cost.
Oracle Transportation Management does not automatically split orders to maximize equipment capacity, but tries to put as many whole orders as possible on a piece of equipment

When you initiate the bulk plan action, Oracle Transportation Management asks you to specify a parameter set that determines the parameter settings that are used to process the bulk plan. The default parameter set configured for the domain in Domain Settings appears if a default was configured

The bulk planner first bundles orders that have the same source and destination and then consolidates the remaining orders into multi-stop shipments, if possible. The remaining orders that cannot be bundled or consolidated are built into direct shipments

Show Routing Options:

Use this action when you want to create a shipment (buy or sell), and want to review and assign an itinerary from a valid list generated by OTM

Show Network Routing Options:

This action considers both itineraries and routing networks, and uses network routing to determine what possible routes are available

Show Network Routing Options - Ocean:

This action focuses on ocean shipments with the primary leg being the ocean leg. Instead of giving a list of possible routes, it shows the vessel options enabling you to pick the best option for you based on the most important leg.

Build Buy Shipment on Primary Leg:

The order will be scheduled on a main leg of a valid itinerary. Order movements are created for all the legs on the itinerary. Only the main leg order movement is scheduled to a shipment; either consol, ground schedule, or ordinary shipments


If the order release you are working with already belongs to a shipment, it is removed from that shipment and resent through the planning logic. Potentially, it can be put onto a new shipment

The order release status value is set to PLANNING_PLANNED - FINAL after a shipment is successfully created