Status Types

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.

OTM Status button on shipment header screen

For example, if you want to track the tender status of a shipment, you can review shipment status ‘SECURE RESOURCES’ and its values at each stage in the tender lifecycle. When a shipment is originally created, it might have a status like ‘SECURE RESOURCES_NOT STARTED’. Once tendered to a carrier, this status changes to ‘SECURE RESOURCES_TENDERED’. Once the carrier accepts the tender, the status changes to ‘SECURE RESOURCES_ACCEPTED’, and so on. These status values give users clear information about what actions are required next.

Status values are of two types: Internal Statuses and External Statuses.

Internal statuses like ‘SECURE RESOURCES’ on the Shipment are standard OTM application statuses maintained by OTM product code. Custom SQL DML statements on such internal status type values should be avoided to prevent conflicts with the standard OTM code flow.

If you want to add new status types, you can create external statuses based on client-specific requirements. To create an external status, follow the steps below:

Configuration and Administration Data > Power Data > General > Status Types > New
  • Status Type ID: Enter a qualifier or name — this appears when you click the 'Status' button
  • Object Type: Enter the object this status applies to, for example 'Shipment'
  • Status Values: Use the naming convention of Status Type ID followed by an underscore and the status value. Add all possible values and mark one as 'Initial Value' — this will be the default when the transaction is created. You can update these values via SQL DML through Agents based on standard or custom events.

Questions & Discussion

Have a question about this topic? Post it below using your GitHub account. Comments are visible to everyone and help other OTM consultants with the same question.