OTM Order Management Data Structure

Purchase Order

PO record will have the basic details like source location, destination location, INCO terms, Item number, Qty etc. Note that PO might not have exact weight/volume details that might be required for planning orders. Usually POs are created in the ERP systems well ahead of time and sent to OTM.

PO tables:

OB_ORDER_BASE - PO Header
OB_REFNUM - PO Header Reference number details
OB_REMARK - PO Header remarks
OB_ORDER_BASE_STATUS - PO Header status values
OB_INVOLVED_PARTY - PO involved party details
OB_LINE - PO Line
OB_LINE_REFNUM - PO Line reference numbers
OB_LINE_REMARK - PO Line level remarks
OB_LINE_STATUS - PO Line level status values

01 - Domain, Items, Locations, and Equipment

Note: These posts are numbered to cover a typical end to end transaction flow that happens in OTM at a very high level.

01 - Domain, Items, Locations, and Equipment

02 - Itinerary

03 - Service Provider and Rates

04 - Business Numbers, Planning Parameter

05 - Bulk Plan

06 - Tender process

07 - Invoicing

08 - Voucher Allocation

Below is a typical OTM end to end flow in it’s most simple/vanilla usage. Readers can explore more on each of the below topics and use this as starting point to understand basic OTM configurations using OTM Help documentation.