Saved Queries in OTM help to query specific records in a screen or add conditions to custom logic while creating an Agent or similar configuration. They can be reused across multiple OTM features including recurring processes and business monitors.
OTM provides the flexibility to associate custom attributes — also called refnums — to every transaction object such as Order Base, Order Release, and Shipment. Developers can use these refnums to store client-specific values like source system …
OTM provides attribute columns (Char, Number, Date, and Currency) on most major transaction tables such as ORDER_RELEASE and SHIPMENT to store custom data alongside standard fields. Flex Fields are definitions applied to these attribute columns that …
In OTM, transaction objects like Order Release and Shipment have a ‘Status’ button on the header screen that shows values describing the current state of that object in the transaction lifecycle.
For example, if you want to track the tender …
Business Number Rules control how OTM generates IDs for business objects such as Order Bases, Order Releases, Shipments, and Invoices. OTM provides default XID sequences for all objects, but you can create custom rules when business requirements call for a …
Truckload (TL) carrier contracts are typically priced on a per-mile basis — the freight cost for a shipment is calculated by multiplying the agreed rate per mile by the distance between the origin and destination. To do this, OTM needs to know the distance …
LTL (Less-than-Truckload) rate pricing works differently from TL. Rather than a flat per-mile charge, LTL rates are class-based — the freight cost depends on the shipment’s weight, the distance, and the NMFC freight class of the goods being shipped. …
Rate Distance in OTM is the calculated distance between a shipment’s origin and destination. OTM needs this distance to cost TL shipments on per-mile rate contracts. There are two ways to provide this distance: