CTMS - User contributions [en-gb]

Interface - CTMS XML EDI Order Flow Guide

2026-03-06T11:31:35Z

Anw: Added appendices for XSD sections and core import fields

{{Doc_Title
| System = Calidus TMS
| Title = Interface - CTMS XML EDI Order Flow Guide
| Reference = INTERFACE
| Version = 3.05
| Date = 6th March 2026
| Sysver = 12.48
| Client = Aptean
}}

=Overview=
== Introduction ==
{{:TripOrder Interface XML}}

[[Category:Documents]][[Category:C-TMS Training Guides]]
[[Category:Interface Guides]]

TripOrder Interface XML

2026-03-06T11:30:24Z

Anw: Minor formatting change

This document is designed to give a brief overview of integration methods into and out of the Aptean TMS - Calidus Edition (CTMS) for transport orders.

The transport orders can be created in CTMS from external systems using XML files based on a standard XSD file format for CTMS called 'TripOrder'.

The following sections will describe some of the sections that are available in the XSD file to create and amend transport orders.

The same XSD file format is used for files being sent by CTMS to external systems to provided information about the transport orders in CTMS and how they have been, or will be, transported between depots and sites.

= XML Inbound Order File Structure =
== EDI Maintenance ==
The XML files for CTMS will be received into a directory structure and processed as may be specified in the 'EDI Maintenance' screen.

Multiple EDI flows may be active to process XML files from different source systems with different filename formats as required.

There are various EDI parameters that can be set to provide different levels of validation of the data that is extracted from the file.

There are also EDI parameters that can be used to set default values for when the data is not able to be provided in the file.

For example, the order time windows can be recalculated and the hazardous data can be defaulted.

=== Webservice API Imports ===
This is controlled via the EDI Maintenance screen. See the section [[TripOrder Interface XML#EDI Trip Order XML Webservices Configuration|EDI Trip Order XML Webservices Configuration]] below for details.

== TripOrder File ==
<OBS_XML>
<EVENT>
<EVENT_HEADER>
<EVENT_DETAIL>

The overall file structure consists of two complex type elements - the file header information and then the details. Each element must only exist once per file.

The different sections within <OBS_XML> can occur differently, the data in bold type is included in the text. {{Note}} Not all of the sections and elements that are available in the XSD file format are listed, just the most common use cases:

<OBS_XML> 1.1 <EVENT>
<EVENT> 1.1 <EVENT_HEADER>
<EVENT_HEADER> 1.1 <ALL ELEMENTS>
<EVENT> 0.00 <EVENT_DETAIL>
<EVENT_DETAIL> 1.1 <TRIP_HEADER>
<TRIP_HEADER> 1.1 <TRIP_IDENTIFIER>
<TRIP_HEADER> 0.1 <TRIP_TRANSACTION_DATE>
<TRIP_HEADER> 0.1 <TRIP_ID>
<EVENT_DETAIL> 0.1 <TRIP_DETAIL>
<EVENT_DETAIL> 0.1 <STOPS>
<STOPS> 1.00 <STOP>
<STOP> 1.1 <STOP_HEADER>
<STOP_HEADER> 1.1 <STOP_IDENTIFIER>
<STOP_HEADER> 0.1 <STOP_ID>
<STOP_HEADER> 0.1 <STOP_SEQ>
<STOP> 0.1 <STOP_DETAIL>
<STOP> 0.1 <ORDERS>
<ORDERS> 1.1 <ORDER>
<ORDER> 1.1 <ORDER_HEADER>
<ORDER_HEADER> 1.1 <ORDER_TRANSACTION_DATE>
<ORDER_HEADER> 0.1 <ORDER_TYPE>
<ORDER_HEADER> 0.1 <WMS_WAREHOUSE>
<ORDER_HEADER> 0.1 <WMS_OWNER>
<ORDER_HEADER> 0.1 <SO_REF>
<ORDER_HEADER> 0.1 <TMS_REF>
<ORDER_HEADER> 0.1 <PO_REF>
<ORDER_HEADER> 0.1 <BOOK_REF>
<ORDER_HEADER> 0.1 <BOOK_DATE>
<ORDER_HEADER> 0.1 <SPECIAL_INSTR>
<ORDER_HEADER> 0.1 <ORDER_COMMENTS>
<ORDER_HEADER> 0.1 <ORDER_HEADER_TMS>
<ORDER_HEADER_TMS> 1.1 <EARLY_AVAIL_DATE>
<ORDER_HEADER_TMS> 1.1 <LATE_AVAIL_DATE>
<ORDER_HEADER_TMS> 1.1 <EARLY_DEL_DATE>
<ORDER_HEADER_TMS> 1.1 <LATE_DEL_DATE>
<ORDER_HEADER_TMS> 0.1 <TMS_GROUP_NAME>
<ORDER_HEADER_TMS> 0.1 <TMS_DELIVERY_TYPE>
<ORDER_HEADER_TMS> 0.1 <TMS_COST_CENTRE>
<ORDER_HEADER_TMS> 0.1 <HAULIER>
<ORDER_HEADER_TMS> 0.1 <TRANSPORT_MODE>
<ORDER_HEADER> 0.1 <ORDER_HEADER_ADDRESSES>
<ORDER_HEADER_ADDRESSES> 1.00 <ORDER_HEADER_ADDRESS>
<ORDER_HEADER_ADDRESS> 1.1 <ADDRESS_TYPE>
<ORDER_HEADER_ADDRESS> 1.1 <ADDRESS_ID>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_NAME>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LINE1>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LINE2>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LINE3>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_TOWN>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_COUNTY>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_COUNTRY_CODE>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_POSTCODE>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LOC_TYPE>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_CUST_GROUP>
<ORDER_HEADER_ADDRESS> 0.1 <OH_ADDRESS_CONTACTS>
<OH_ADDRESS_CONTACTS> 1.00 <OH_ADDRESS_CONTACT>
<OH_ADDRESS_CONTACT> 0.1 <ALL ELEMENTS>
<ORDER_HEADER> 0.1 <CUSTOMER_ID>
<ORDER_HEADER> 0.1 <CUSTOMER_NAME>
<ORDER> 0.1 <ORDER_SUB_REFS>
<ORDER_SUB_REFS> 1.1 <ORDER_SUB_REF>
<ORDER_SUB_REF> 1.1 <SUB_REF_IDENTIFIER>
<ORDER_SUB_REF> 1.1 <SUB_REFERENCE>
<ORDER> 0.1 <ORDER_DETAILS>
<ORDER_DETAILS> 1.1 <ORDER_DETAIL>
<ORDER_DETAIL> 1.1 <DETAIL_TYPE>
<ORDER_DETAIL> 0.1 <DETAIL_ID>
<ORDER_DETAIL> 0.1 <PRODUCT_TYPE>
<ORDER_DETAIL> 0.1 <PRODUCT_TYPE_DESC>
<ORDER_DETAIL> 0.1 <DU_TYPE>
<ORDER_DETAIL> 1.1 <ITEM_IDENTIFIER>
<ORDER_DETAIL> 0.1 <ITEM_DESCRIPTION>
<ORDER_DETAIL> 0.1 <PALLET_ID>
<ORDER_DETAIL> 0.1 <ITEM_AKA_CODE>
<ORDER_DETAIL> 0.1 <ITEM_FACTOR>
<ORDER_DETAIL> 0.1 <LIFTS>
<ORDER_DETAIL> 0.1 <RPE_QTY>
<ORDER_DETAIL> 0.1 <WEIGHT>
<ORDER_DETAIL> 0.1 <VOLUME>
<ORDER_DETAIL> 0.1 <ORDERED>
<ORDER_DETAIL> 0.1 <TO_DELIVER>
<ORDER_DETAIL> 0.1 <DELIVERED>
<ORDER_DETAIL> 0.1 <PLANNED_CASES>
<ORDER_DETAIL> 0.1 <LENGTH>
<ORDER_DETAIL> 0.1 <WIDTH>
<ORDER_DETAIL> 0.1 <HEIGHT>
<ORDER_DETAIL> 0.1 <COMMODITY_ID>
<ORDER_DETAIL> 0.1 <CLASS_ID>
<ORDER> 0.1 <ORDER_HAZARDOUS_DETAILS>
<ORDER_HAZARDOUS_DETAILS> 1.00 <ORDER_HAZARDOUS_DETAIL>
<ORDER_HAZARDOUS_DETAIL> 0.1 <ALL ELEMENTS>

The XML items have the following definitions in the XSD file format:

{| class="wikitable apt-searchable" border="1" id="triporderxml"
|- bgcolor="silver"
!Item !!Type !!Size !!Restriction !!CTMS Mandatory*
|-
|EVENT_PROCESSED ||STRING ||1 ||E,N,Y ||Y
|-
|EVENT_SOURCE_TYPE ||STRING ||4 ||New Value ||Y
|-
|EVENT_SOURCE_NAME ||STRING ||10 || ||Y
|-
|EVENT_DATE ||DATETIME || || ||Y
|-
|EVENT_TYPE ||STRING ||3 || ||Y
|-
|EVENT_ACTION ||STRING ||1 ||A,C,D ||Y
|-
|TRIP_IDENTIFIER ||STRING ||1 ||O,T ||Y
|-
|TRIP_TRANSACTION_DATE ||DATETIME || || ||
|-
|TRIP_ID ||STRING ||12 || ||
|-
|STOP_IDENTIFIER ||STRING ||1 ||O,S ||Y
|-
|STOP_ID ||STRING ||51 || ||
|-
|STOP_SEQ ||INTEGER ||6 || ||
|-
|ORDER_TRANSACTION_DATE ||DATETIME || || ||Y
|-
|ORDER_TYPE ||STRING ||1 || ||
|-
|WMS_WAREHOUSE ||STRING ||3 || ||
|-
|WMS_OWNER ||STRING ||12 || ||Y
|-
|SO_REF ||STRING ||20 || ||Y
|-
|TMS_REF ||STRING ||20 || ||
|-
|PO_REF ||STRING ||20 || ||
|-
|BOOK_REF ||STRING ||20 || ||
|-
|BOOK_DATE ||DATETIME || || ||
|-
|SPECIAL_INSTR ||STRING ||2000 || ||
|-
|ORDER_COMMENTS ||STRING ||2000 || ||
|-
|EARLY_AVAIL_DATE ||DATETIME || || ||Y
|-
|LATE_AVAIL_DATE ||DATETIME || || ||Y
|-
|EARLY_DEL_DATE ||DATETIME || || ||Y
|-
|LATE_DEL_DATE ||DATETIME || || ||Y
|-
|TMS_GROUP_NAME ||STRING ||12 || ||
|-
|TMS_DELIVERY_TYPE ||STRING ||35 || ||
|-
|TMS_COST_CENTRE ||STRING ||12 || ||Y
|-
|HAULIER ||STRING ||12 || ||
|-
|TRANSPORT_MODE ||STRING ||30 || ||
|-
|ADDRESS_TYPE ||STRING ||3 || ||Y
|-
|ADDRESS_ID ||STRING ||25 || ||Y
|-
|ADDRESS_NAME ||STRING ||50 || ||
|-
|ADDRESS_LINE1 ||STRING ||50 || ||
|-
|ADDRESS_LINE2 ||STRING ||50 || ||
|-
|ADDRESS_LINE3 ||STRING ||50 || ||
|-
|ADDRESS_TOWN ||STRING ||50 || ||
|-
|ADDRESS_COUNTY ||STRING ||50 || ||
|-
|ADDRESS_COUNTRY_CODE ||STRING ||3 || ||
|-
|ADDRESS_POSTCODE ||STRING ||9 || ||
|-
|ADDRESS_LOC_TYPE ||STRING ||12 || ||
|-
|ADDRESS_CUST_GROUP ||STRING ||12 || ||
|-
|ADDRESS_CONTACT_TYPE ||STRING ||1 ||L,O ||
|-
|ADDRESS_CONTACT_FORENAME ||STRING ||50 || ||
|-
|ADDRESS_CONTACT_SURNAME ||STRING ||50 || ||
|-
|ADDRESS_CONTACT_NUMBER ||STRING ||50 || ||
|-
|ADDRESS_EMAIL ||STRING ||100 || ||
|-
|ADDRESS_CONTACT_JOB ||STRING ||50 || ||
|-
|CUSTOMER_ID ||STRING ||12 || ||
|-
|CUSTOMER_NAME ||STRING ||50 || ||
|-
|SUB_REF_IDENTIFIER ||STRING ||50 || ||Y
|-
|SUB_REFERENCE ||STRING ||512 || ||Y
|-
|DETAIL_TYPE ||STRING ||1 ||D,S ||Y
|-
|DETAIL_ID ||STRING ||30 || ||
|-
|PRODUCT_TYPE ||STRING ||12 || ||
|-
|PRODUCT_TYPE_DESC ||STRING ||50 || ||Y
|-
|DU_TYPE ||STRING ||12 || ||
|-
|ITEM_IDENTIFIER ||STRING ||20 || ||Y
|-
|ITEM_DESCRIPTION ||STRING ||122 || ||
|-
|PALLET_ID ||STRING ||100 || ||
|-
|ITEM_AKA_CODE ||STRING ||30 || ||
|-
|ITEM_FACTOR ||STRING ||12 || ||
|-
|LIFTS ||DECIMAL ||8,2 || ||
|-
|RPE_QTY ||DECIMAL ||10,2 || ||
|-
|WEIGHT ||DECIMAL ||10,2 || ||
|-
|VOLUME ||DECIMAL ||15,5 || ||
|-
|ORDERED ||DECIMAL ||28,4 || ||
|-
|TO_DELIVER ||DECIMAL ||28,4 || ||
|-
|DELIVERED ||DECIMAL ||28,4 || ||
|-
|PLANNED_CASES ||INTEGER ||8 || ||
|-
|LENGTH ||DECIMAL ||10,2 || ||
|-
|WIDTH ||DECIMAL ||10,2 || ||
|-
|HEIGHT ||DECIMAL ||10,2 || ||
|-
|COMMODITY_ID ||STRING ||256 || ||
|-
|CLASS_ID ||STRING ||256 || ||
|-
|UN_NUMBER ||STRING ||50 || ||Y
|-
|HAZARDOUS_QTY ||DECIMAL ||28,4 || ||Y
|-
|HAZARDOUS ||STRING ||1 ||N,Y ||Y
|-
|HAZARDOUS_DESCRIPTION ||STRING ||40 || ||Y
|}

*The mandatory flag for CTMS is only valid if the optional section has been provided in the file.

Note that an item quantity must be provided as 'ORDERED' or 'TO_DELIVER' depending which item is being used (as set by an EDI parameter).

=== Event Header <EVENT_HEADER> ===
<EVENT_HEADER>
<EVENT_PROCESSED>N</EVENT_PROCESSED>
<EVENT_SOURCE_TYPE>SAGE</EVENT_SOURCE_TYPE>
<EVENT_SOURCE_NAME>SAGE</EVENT_SOURCE_NAME>
<EVENT_DATE>2015-05-31T12:52:13</EVENT_DATE>
<EVENT_TYPE>ORD</EVENT_TYPE>
<EVENT_ACTION>C</EVENT_ACTION>
</EVENT_HEADER>

The header section describes the fact that an event has occurred. Each event must generally create a new file and this complex type element must not repeat within the file.

Each of the simple type elements outlined above is mandatorily required.

The <EVENT_PROCESSED> is expected to have a value of 'N'.

The <EVENT_SOURCE_TYPE> must be setup as a recognised source system within CTMS, within the [[System Configuration]] screen, [[System Configuration#Sources|Sources]] tab.

Although a number of <EVENT_TYPE> values can be received it is the 'ORD' event type which represents a transport order to be created or amended in CTMS, the <EVENT_ACTION> value of 'C' (for 'C'reate) will ensure a new order is generated, an event action value of 'A' (for 'A'mend) will update an order, and an event action value of 'D' (for 'D'elete) will delete an order.

Validation will exist to check that the transport order can be created, amended or deleted as directed.

The <EVENT_DATE> simple element must be in the format 'YYYY-MM-DDTHH:MI:SS'

=== Event Detail <EVENT_DETAIL> ===
<EVENT_DETAIL>
<TRIP_HEADER>
<STOPS>
<STOP>
<STOP_HEADER>
<ORDERS>
<ORDER>
<ORDER_HEADER>
<ORDER_DETAILS>
<ORDER_HAZARDOUS_DETAILS>
</ORDER>

The event detail section consists of complex type elements representing the 'Trip' - a CTMS planned transport movement representing a vehicle with one or more transport orders to one or more location.

The trip can have several 'stops' (a geographical location visited) against which one or more 'orders' can be handled for loading or unloading the vehicle at each stop.

Therefore, the <STOPS> and <ORDERS> may contain multiple stops and transport orders that exist on the trip.

=== Trip Header <TRIP_HEADER> ===
<TRIP_HEADER>
<TRIP_IDENTIFIER>O</TRIP_IDENTIFIER>
</TRIP_HEADER>

The 'ORD' event type does not require trip header information, although this complex type is mandatory in the file, it is exempted by denoting the <TRIP_IDENTIFIER> with 'O' to represent that the file contains order data only.

The order data received is denoted as an 'unplanned' order, that is it has not been built into a vehicle movement and routed through one or more load and unload activities. This planning activity is handled within CTMS.

=== Stops <STOPS> ===
<STOPS>
<STOP>
<STOP_HEADER>
<STOP_IDENTIFIER>O</STOP_IDENTIFIER>
</STOP_HEADER>

The ORD event type does not require any trip stop information and although the complex type is mandatory it is exempted by denoting the <STOP_IDENTIFIER> with 'O' to indicate that the file contains order data only.

=== Orders <ORDERS> ===
<ORDER>
<ORDER_HEADER> ... </ORDER_HEADER> [1]
<ORDER_SUB_REFS> ... </ORDER_SUB_REFS> [0..1]
<ORDER_DETAILS> ... </ORDER_DETAILS> [0..1]
<ORDER_HAZARDOUS_DETAILS> ... </ORDER_HAZARDOUS_DETAILS> [0..1]
</ORDER>
The orders complex type contains the core information that constitutes a transport order request in CTMS, that is, a unique instruction to collect and deliver a number of goods items of a particular type between two points at requested times.

The <ORDER> element can repeat to represent multiple orders within the same file; however it is recommended best practice when using the ORD event type to receive one per individual XML file.

The structure is made up of complex elements representing the higher level order header information which is none repeating and the lower level order details complex type element which may repeat.

The <ORDER_HEADER> complex type is mandatory and must occur once and only once.

The <ORDER_HEADER> complex type is optional.

The <ORDER_DETAILS> complex type is mandatory for transport orders and can repeat but must occur at least once.

The <ORDER_HAZARDOUS_DETAILS> complex type is optional.

=== Order Header <ORDER_HEADER> ===
<ORDER_HEADER>

<ORDER_HEADER>
<ORDER_TRANSACTION_DATE> ... </ORDER_TRANSACTION_DATE> [1]
<ORDER_TYPE> ... </ORDER_TYPE> [0..1]
<WMS_WAREHOUSE> ... </WMS_WAREHOUSE> [0..1]
<WMS_OWNER> ... </WMS_OWNER> [0..1]
<SO_REF> ... </SO_REF> [0..1]
<TMS_REF> ... </TMS_REF> [0..1]
<PO_REF> ... </PO_REF> [0..1]
<BOOK_REF> ... </BOOK_REF> [0..1]
<BOOK_DATE> ... </BOOK_DATE> [0..1]
<SPECIAL_INSTR> ... </SPECIAL_INSTR> [0..1]
<ORDER_COMMENTS> ... </ORDER_COMMENTS> [0..1]
<ORDER_HEADER_TMS> ... </ORDER_HEADER_TMS> [0..1]
<ORDER_HEADER_ADDRESSES> ... </ORDER_HEADER_ADDRESSES> [0..1]
<CUSTOMER_ID> ... </CUSTOMER_ID> [0..1]
<CUSTOMER_NAME> ... </CUSTOMER_NAME> [0..1]
<ORDER_STATUS> ... </ORDER_STATUS> [0..1]
</ORDER_HEADER>

The order header structure represents the high level simple single attributes of the order which exist in isolation, such as references and who the transport order is being conducted on behalf of.

The <ORDER_TRANSACTION_DATE> simple element is mandatory and must be in the format 'YYYY-MM-DDTHH:MI:SS'

The <ORDER_TYPE> simple type element is mandatory and must be received with a value of 'O'.

The <WMS_OWNER> simple type element indicates the customer and must match the customer IDs setup on CTMS, this is a mandatory field.

The <SPECIAL_INSTR> simple type element captures any additional information that is presented to the driver on his hand held delivery device at that may be relevant to the transport planning.

=== Order Header TMS <ORDER_HEADER_TMS> ===
<ORDER_HEADER_TMS>
<EARLY_AVAIL_DATE>2015-05-24T17:00:00</EARLY_AVAIL_DATE>
<TMS_GROUP_NAME>OBS</TMS_GROUP_NAME>
<TMS_DELIVERY_TYPE>Standard</TMS_DELIVERY_TYPE>
<TMS_COST_CENTRE>OBS</TMS_COST_CENTRE>
<TRANSPORT_MODE>ROAD</TRANSPORT_MODE>

The order header TMS section contains additional information relevant to the order and is simply an extension to the main order header complex type.

Most of the simple type elements in the section are optional.

The <TMS_DELIVERY_TYPE> is used to receive the service level: this value must be populated and is validated against CTMS master data

The <EARLY_AVAIL_DATE> simple type element is mandatory and will be used to calculate forward the collection/loading date/time window and also the approximate delivery date/time window. It must be in the format 'YYYY-MM-DDTHH:MI:SS'.

The other 3 dates for the order may be omitted because they can be calculated from the early available date that is provided and the delivery type (i.e. service level) of the order, however, the configuration in CTMS (TBC) will determine the required level of data.

All elements in this section are validated against CTMS master data and therefore must match CTMS configuration.

The accepted values in the <TRANSPORT_MODE> simple type element are:
* AIR
* ROAD

This will be validated and the order file rejected if the value does not match.

The <TOTAL_PRICE> element is optional and defines the TOTAL price of the order. If provided and populated, the value must be a valid decimal value, or an error will be raised. If not provided or null, the value will be set to 0.

=== Order Header Addresses <ORDER_HEADER_ADDRESSES> ===
<ORDER_HEADER_ADDRESSES>
<ORDER_HEADER_ADDRESS>
<ORDER_HEADER_ADDRESS>
<OH_ADDRESS_CONTACTS>

An <ORDER_HEADER_ADDRESSES> complex type element must always exist once per order.

It must include two instances of the <ORDER_HEADER_ADDRESS> complex type element, one for the loading/pickup location (i.e. 'DEP' address type) and one for the unloading/drop-off location (i.e. 'DEL' address type).

=== Order Header Addresses <ORDER_HEADER_ADDRESS> ===
<ORDER_HEADER_ADDRESS>
<ADDRESS_TYPE>DEP</ADDRESS_TYPE>
<ADDRESS_ID>OBS</ADDRESS_ID>
<ADDRESS_NAME>OBS Logistics</ADDRESS_NAME>
<ADDRESS_LINE1>Southern Gateway</ADDRESS_LINE1>
<ADDRESS_LINE2>Speke Boulevard</ADDRESS_LINE2>
<ADDRESS_LINE3></ADDRESS_LINE3>
<ADDRESS_TOWN>Liverpool</ADDRESS_TOWN>
<ADDRESS_COUNTY>Merseyside</ADDRESS_COUNTY>
<ADDRESS_COUNTRY_CODE>GB</ADDRESS_COUNTRY_CODE>
<ADDRESS_POSTCODE>L24 9HZ</ADDRESS_POSTCODE>
<ADDRESS_CUST_GROUP>OBS</ADDRESS_CUST_GROUP>
<OH_ADDRESS_CONTACTS>

The <ORDER_HEADER_ADDRESS> complex type element includes the address attributes for either the initial point of collection/loading or the final point of delivery/unloading.

The <ADDRESS_TYPE> simple type element is mandatory and must be either:
* 'DEP' - Indicates that the address represents the initial 'DEP'arture location of the order.
* 'DEL' - Indicates that the address represents the final 'DEL'ivery location of the order.

The <ADDRESS_TOWN> item and <ADDRESS_POSTCODE> elements will not be validated and will be accepted regardless of data content.

The <ADDRESS_ID> item is mandatory and can be sent as a unique account identifier for the sender/recipient or it can be sent with the word 'UNKNOWN' which will allow CTMS to generate this unique address identifier where necessary.

The system will initially cross check the received Address Name and Address Postcode in the order file to see if any locations exist for that address name and postcode (to narrow down the number of records to validate), if so it will identify against all other address attributes (Address lines, town/suburb, county/state, country code) to see if there is an existing EXACT match.

If an existing EXACT address match is found the existing CTMS location code will be used against the received order - as the address detail matches all attributes. If any difference is found a new location is generated with the data received, generating a new location ID in the following format:

* Characters 1 to 8: Characters 1 to 8 from <ADDRESS_NAME>
* Character 9: '-'
* Characters 10 to 12: Sequence number 001 to 999

The location ID generated will be a maximum of 12 characters, for example:

<ADDRESS_ID>UNKNOWN<ADDRESS_ID>
<ADDRESS_NAME>OBS Logistics</ADDRESS_NAME>
<ADDRESS_POSTCODE>L24 9HZ</ADDRESS_POSTCODE>

Would create location code 'OBS Logi-001'.

Also note that new addresses for existing locations can be provided for each order and new locations can be created for the specific address that may be provided.

Once a location is created it will not be updated via the order upload process, any amendments can be carried out manually or via the import of a 'CSV' file.

New locations will only be created for the address details provided.

=== Order Header Address Contact <OH_ADDRESS_CONTACT> ===
<OH_ADDRESS_CONTACT>
<ADDRESS_CONTACT_TYPE>O</ADDRESS_CONTACT_TYPE>
<ADDRESS_CONTACT_FORENAME>Yard Manager</ADDRESS_CONTACT_FORENAME>
<ADDRESS_CONTACT_SURNAME></ADDRESS_CONTACT_SURNAME>
<ADDRESS_CONTACT_NUMBER>0151 123 5678</ADDRESS_CONTACT_NUMBER>
<ADDRESS_EMAIL>yardmanager@obs.com</ADDRESS_EMAIL>

For each address an optional <OH_ADDRESS_CONTACT> complex type element can be received. This element must only occur once for within a <OH_ADDRESS_CONTACT>.

The <ADDRESS_CONTACT_TYPE> simple type element is mandatory where the <OH_ADDRESS_CONTACT> is used and indicates if the contact information is to be permanently associated to the address master data (value 'L') or whether it is only related to that particular address for the instance of that particular order (value 'O'). For this implementation 'O'rder type contacts should always be received.

If there is no contact information for the loading location then this element is not required for the "DEP" address type.

The other simple type elements are optional.

=== Order Sub-references <ORDER_SUB_REFS> ===
<ORDER_DETAILS>
<ORDER_SUB_REFS>
<ORDER_SUB_REF> <ORDER_SUB_REF>
<SUB_REF_IDENTIFIER> ... </SUB_REF_IDENTIFIER> [1]
<SUB_REF_IDENTIFIER> ... </SUB_REFERENCE> [1]
</ORDER_SUB_REF>
</ORDER_SUB_REFS>
<ORDER_DETAIL>
This <ORDER_SUB_REFS> section is optional, and allows you to store additional references for an order.

The section must include at least one instance of the <ORDER_SUB_REF> complex type element.

The <SUB_REF_IDENTIFIER> simple type must match up to a configured order sub-reference type. These are maintained by your system administrator in the CTMS [[Imports]] screen, on the [[Imports#Decodes|Decodes]] tab, type "XML_REFERENCE". Include the CODE here, not the NAME.

The <SUB_REF_IDENTIFIER> simple type is the value you want to store against that reference. The value can be anything at all, but to 512 characters long. These values are not validated.

You can add as many order sub references as you need for the order.

{{Note|
* If system parameter USE_XML_ORDER_SUB_REFS is set to "Y", sub references will be automatically generated from lane comments that begin with ORDER_REFS:", followed by a comma-delimited list of sub reference names and values. Otherwise this section will contain the order sub references for this order.
* A sub reference of TRIP_TYPE may be automatically generated based on EDI parameter INC_TRIP_TYPE being set. In this case, the value may be set to
** COL - if the from location is the load location of the trip stop and the load location type is not RDC
** TRUNK - if the from location is the load location and the order to location is not the unload location
** XDOCK_DEL - if the order to location is equal to the unload location, and there are onward trips.
** DIRECT_DEL - if the order to location is equal to the unload location, and there are no onward trips.
* If the sub-ref name DELIVERY_METHOD is present, the value will be translated for the carrier.
}}Several static sub-references are supported.

The following will automatically store data as order information, for contact purposes:

* SMS_ADDRESS_1
* SMS_ADDRESS_2
* SMS_ADDRESS_3
* SMS_ADDRESS_4
* EMAIL_ADDRESS

Depending on which values you provide here, the order will be stamped with contact preferences:

* E - Email only.
* S - SMS Only
* B - Both

{{Note}}SMS sending from CTMS is supported at additional transaction cost per message.

The reference ORDER_WMS_STATUS may be used to update a source system status against the trip. Values are:

* OPEN STAGED
* IN PROGRESS STAGED
* CLOSED STAGED
* OPEN
* IN PROGRESS
* CLOSED

=== Order Detail <ORDER_DETAIL> ===
<ORDER_DETAIL>
<DETAIL_TYPE>S</DETAIL_TYPE>
<PRODUCT_TYPE_DESC>CANTEEN</PRODUCT_TYPE_DESC>
<DU_TYPE>20x9</DU_TYPE>
<ITEM_IDENTIFIER>ABC004783</ITEM_IDENTIFIER>
<ITEM_DESCRIPTION>CARTON</ITEM_DESCRIPTION>
<ITEM_AKA_CODE>10*20*30</ITEM_AKA_CODE>
<LIFTS>1</LIFTS>
<WEIGHT>5.37</WEIGHT>
<ORDERED>1</ORDERED>
<TO_DELIVER>1</TO_DELIVER>
<LENGTH>10</LENGTH>
<WIDTH>20</WIDTH>
<HEIGHT>30</HEIGHT>
<COMMODITY_ID>DG</COMMODITY_ID>
<CLASS_ID>2.1</CLASS_ID>
</ORDER_DETAIL>

The <ORDER_DETAIL> complex element is mandatory and can repeat but must occur at least once to form a valid CTMS order.

The order details will be used to generate both the individual dispatch box/carton detail (per unique barcode) and also the higher level summary order detail line level.

The <DETAIL_TYPE> simple element is mandatory and must be received as either:
* 'D' - Represents a CTMS order detail line - summary level of the total of unique package types.
* 'S' - Represents a CTMS order detail item - the lowest level entry for each individual carton/box.

Note that the DU types (i.e. for the order lines) and its items, just the DU types (if items are not being recorded) or just the items may be provided.

If just items are provided then the DU types and thus the order lines may be generated automatically for the order based on the types of items that have been provided.

The <PRODUCT_TYPE_DESC> simple element is mandatory and will be validated against CTMS master data to ensure it is a recognised value. An unrecognised or blank value will cause the order upload to fail with applicable validation message recorded.

The <DU_TYPE> simple element is optional and will be validated against CTMS master data to ensure it is a recognised value. An unrecognised will cause the order upload to fail with applicable validation message recorded.

The <ITEM_IDENTIFIER> simple element is mandatory and will not be validated although it must be a maximum of 15 alphanumeric characters.

The <ITEM_DESCRIPTION> and <ITEM_AKA_CODE simple type elements are an optional freetext tags and can be used as required.

One of the <ORDERED> and <TO_DELIVER> simple type elements will be mandatory and must be received with a numeric integer value. This represents the number of items reflected by the <ORDER_DETAIL> segment received

As this is at individual carton/box level then this is expected to always be 1 for this implementation.

The <WEIGHT>, <HEIGHT>, <WIDTH>, <LENGTH> simple type elements are optional.

{{Note|* The weight provided is a TOTAL weight of the item or line, not a UNIT weight.
* The height, width and length will be used by CTMS to calculate the carton/box level volume for each order item as per existing standard processing logic.}}

The <COMMODITY_ID> simple type element is optional and will be validated against CTMS master data to ensure it is a recognised value. An unrecognised value will cause the order upload to fail with applicable validation message recorded.

The <CLASS_ID> simple type element is optional but must be received when a <COMMODITY_ID> element is provided which has a 'Dangerous' flag setting of 'Y' (in CTMS master data setup). The value will be validated against CTMS master data to ensure it is a recognised value. An unrecognised will cause the order upload to fail with applicable validation message recorded.

The <ITEM_PRICE> element is optional and defines the TOTAL price of the item. This applies only to Item detail type lines. If provided and populated, the value must be a valid decimal value, or an error will be raised. If not provided or null, the value will be set to 0.

=== Order Hazardous Details ===
<ORDER_HAZARDOUS_DETAILS>
<ORDER_HAZARDOUS_DETAIL>

The <ORDER_HAZARDOUS_DETAILS> complex type element is optional and can be provided if required.

If this element is used then one or more <ORDER_HAZARDOUS_DETAIL> complex type elements is mandatorily required.

=== Order Hazardous Detail ===
<ORDER_HAZARDOUS_DETAIL>
<UN_NUMBER>1089</UN_NUMBER>
<HAZARDOUS_QTY>1</HAZARDOUS_QTY>
<HAZARDOUS>Y</HAZARDOUS>
<HAZARDOUS_DESCRIPTION>CARBONYL SULFIDE</HAZARDOUS_DESCRIPTION>
</ORDER_HAZARDOUS_DETAIL>

The <ORDER_HAZARDOUS_DETAIL> complex type element and all its simple type elements are mandatory. The elements are not validated against CTMS master data and will be stored as received.

= XML Outbound Order File Structure =
CTMS may provide updates to a customer’s source system, including how the order has been scheduled for delivery, when a vehicle is en-route and delivery details including successful delivery and reasons for a short delivery. The same TripOrder XSD will be used to generate the Trip file.

==EDI Maintenance ==
The XML files from CTMS will be generated and placed into a directory structure and processed as may be specified in the 'EDI Maintenance' screen.

Multiple EDI flows may be active to process XML files at different stages of processing.

There are various EDI parameters that can be set to provide different levels of validation to generate the files.

The trip/order outbound flows can generate standard flows via a webservice push to an endpoint, or can be sent out to the filesystem for FTP - See [[TripOrder Interface XML#Filesystem Server Requirements|Filesystem Server Requirements]] below. This depends on the EDI processes generated.

Further, more bespoke EDI exports can be generated - these still use the same TripOrder XML export structure, but are more focussed on different processes, such as tracking summary messages - these are not covered in this guide.

=== Filesystem Server Requirements ===
CTMS will push files to the OUT sub folder within the customer folder. From this folder CTMS will FTP the file across to the customer system. The customer must provide CTMS with the IP, PORT, Username , Password and Directory name. The customer will provide CTMS with access to the directory.<center>
[[File:TripOrderXML-EDI-FTP.png]]
</center>

=== Webservice API Export ===
Like Filesystem exports, this is controlled via the EDI Maintenance screen. See the section [[TripOrder Interface XML#EDI Trip Order XML Webservices Configuration|EDI Trip Order XML Webservices Configuration]] below for details.

== TripOrder File ==
<OBS_XML>
<EVENT>
<EVENT_HEADER>
<EVENT_DETAIL>

The same XSD file format is used for files from CTMS as per files into CTMS.

These files may contain more data in each section than are required in the inbound order files.

For example, an outbound file may contain data about the trip, its stops, each order on each stop and the DU types and/or items on each order.

Export depends on the events that are being exported, controlled by EDI Parameters on the API EDI process:
* API_ARR
* API_COL
* API_DEL
* API_DEP
* API_ORD
* API_TRP

Additional EDI parameters are also present (described in detail in the following sections):
*INCLUDE_CDATA_TAG - affects variable text data entry from the execution level - should it be wrapped to prevent interface errors?
* SEND_AND_FORGET - affects the basic interface - should the message be sent with no expectation of explicit acknowledgement back from the destination?
*PRINT_STOP_PID
*PRINT_ROUTE_CODE
*INCLUDE_ORDER_STATUS
*SEND_DEL_TYPE_CODE
*EXPORT_SERVICES
*INC_TRIP_TYPE
*INC_TRIP_ACTION
*INC_PACKED_TO_DEL
*INCLUDE_SAP_LINE_NOS
*INCLUDE_REASON_CODES
*INCLUDE_NON_CON_CODES
* INCLUDE_TRACK_REF
*INCLUDE_ITEM_DELIVER
*INCLUDE_REASON_TYPE

Export may also include debrief-level information, depending on the type of event, and where the order is up to.

The Export will be of Trip Type if related to a trip, and Order type (similar to the above) for Order-type events.

Trip type events:
*TRP - any changes to or creation of a trip.
* ARR - Arrival at any stop.
*DEP - departure at any stop.

Order type events:
*ORD - any changes to or creation of an order.
*CAN - if an order is cancelled.
*COL - if an order is collected.
*DEL - if an order is delivered.

In general, trip-type events include everything that an Order-type event would include, but with the following additions:
*TRIP_DETAIL
*STOP_DETAIL
*STOP_SIGNATURE (if LOTS_INC_STOP_SIGNATURE = "Y")
*ORDER_HEADER_TMS

As an indication of what may change, please see the below sections.

===TRIP_DETAIL===
<pre>
<HAULIER> ... </HAULIER> [0..1]
<HAULIER_NAME> ... </HAULIER_NAME> [0..1]
<HAULIER_TYPE> ... </HAULIER_TYPE> [0..1]
<TRACKING> ... </TRACKING> [1]
<TRIP_SCHEDULE> ... </TRIP_SCHEDULE> [0..1]
<DRIVER> ... </DRIVER> [0..1]
<DRIVER_NAME> ... </DRIVER_NAME> [0..1]
<DRIVER_CONTACT> ... </DRIVER_CONTACT> [0..1]
<TRACTOR> ... </TRACTOR> [0..1]
<TRACTOR_LAT> ... </TRACTOR_LAT> [0..1]
<TRACTOR_LON> ... </TRACTOR_LON> [0..1]
<COST_CENTRE> ... </COST_CENTRE> [0..1]
<TRIP_STATUS> ... </TRIP_STATUS> [0..1]
<TRIP_REF> ... </TRIP_REF> [0..1]
<TRIP_TRAILER_ID> ... </TRIP_TRAILER_ID> [0..1]
<TRIP_TRAILER_TYPE> ... </TRIP_TRAILER_TYPE> [0..1]
<TRIP_DISTANCE> ... </TRIP_DISTANCE> [0..1]
<FUEL_DRAWN> ... </FUEL_DRAWN> [0..1]
<OWNING_DEPOT> ... </OWNING_DEPOT> [0..1]
<CONTAINER_NO> ... </CONTAINER_NO> [0..1]
<SEAL_NO> ... </SEAL_NO> [0..1]
<EFX_NUMBER> ... </EFX_NUMBER> [0..1]
<START_ODOMETER> ... </START_ODOMETER> [0..1]
<END_ODOMETER> ... </END_ODOMETER> [0..1]
<ACTUAL_TRIP_DISTANCE> ... </ACTUAL_TRIP_DISTANCE> [0..1]
<ROUTE_CODE> ... </ROUTE_CODE> [0..1]
<COST_PER_TONNE> ... </COST_PER_TONNE> [0..1]
<COST> ... </COST> [0..1]
<COST_REASON> ... </COST_REASON> [0..1]
<AUDIT_ID> ... </AUDIT_ID> [0..1]
<TRIP_SUB_REFS> ... </TRIP_SUB_REFS> [0..1]
</pre>

{{Note|
* Carrier will be modified if the carrier type is 3PL. This will be exported in the HAULIER tag.
* TRACKING tag will only be populated from trips that are tracked through Microlise.
* The information sent to MICROLISE is extremely limited in this section.
* ROUTE_CODE will only be populated if the EDI parameter PRINT_ROUTE_CODE is populated or the TRIP_ORDER_XSD_VERS system parameter is "2.5". If the system parameter INCL_ROUTE_CODE is set, then this will be instead populated with the Baxter route code.
* AUDIT_ID is a unique ID appended to the message for external tracking purposes.
}}

===TRIP_SUB_REF===
<pre>
<TRIP_SUB_REF>
<SUB_REF_IDENTIFIER> ... </SUB_REF_IDENTIFIER> [1]
<SUB_REFERENCE> ... </SUB_REFERENCE> [1]
</TRIP_SUB_REF>
</pre>

{{Note|
* If system parameter INC_TRIP_ACTION is "Y", a trip sub reference will be generated based on the action of the event.
}}

===STOP_DETAIL===
<pre>
<STOP_REF> ... </STOP_REF> [0..1]
<STOP_TYPE> ... </STOP_TYPE> [0..1]
<STOP_LOCATION_TYPE> ... </STOP_LOCATION_TYPE> [0..1]
<STOP_LOCATION_ID> ... </STOP_LOCATION_ID> [0..1]
<STOP_LOCATION_NAME> ... </STOP_LOCATION_NAME> [0..1]
<STOP_ADDR_LINE1> ... </STOP_ADDR_LINE1> [0..1]
<STOP_ADDR_LINE2> ... </STOP_ADDR_LINE2> [0..1]
<STOP_ADDR_LINE3> ... </STOP_ADDR_LINE3> [0..1]
<STOP_TOWN> ... </STOP_TOWN> [0..1]
<STOP_COUNTY> ... </STOP_COUNTY> [0..1]
<STOP_COUNTRY_CODE> ... </STOP_COUNTRY_CODE> [0..1]
<STOP_POSTCODE> ... </STOP_POSTCODE> [0..1]
<STOP_CONTACT_NAME> ... </STOP_CONTACT_NAME> [0..1]
<STOP_CONTACT_PHONE> ... </STOP_CONTACT_PHONE> [0..1]
<STOP_BREAK_DURATION> ... </STOP_BREAK_DURATION> [0..1]
<STOP_PREV_DIST> ... </STOP_PREV_DIST> [0..1]
<STOP_ACTUAL_PREV_DIST> ... </STOP_ACTUAL_PREV_DIST> [0..1]
<STOP_TRAILER_ID> ... </STOP_TRAILER_ID> [0..1]
<STOP_LAT> ... </STOP_LAT> [0..1]
<STOP_LON> ... </STOP_LON> [0..1]
<STOP_PLANNED_ARRIVAL_DATE> ... </STOP_PLANNED_ARRIVAL_DATE> [0..1]
<STOP_PLANNED_DEPARTURE_DATE> ... </STOP_PLANNED_DEPARTURE_DATE> [0..1]
<STOP_ETA_DATE> ... </STOP_ETA_DATE> [0..1]
<STOP_ETA_AT_DATE> ... </STOP_ETA_AT_DATE> [0..1]
<STOP_EARLIEST_BOOKED_DATE> ... </STOP_EARLIEST_BOOKED_DATE> [0..1]
<STOP_ACTUAL_ARRIVAL_DATE> ... </STOP_ACTUAL_ARRIVAL_DATE> [0..1]
<STOP_ACTUAL_DEPARTURE_DATE> ... </STOP_ACTUAL_DEPARTURE_DATE> [0..1]
<STOP_ODO_READING> ... </STOP_ODO_READING> [0..1]
<STOP_FUEL> ... </STOP_FUEL> [0..1]
<STOP_EMAIL> ... </STOP_EMAIL> [0..1]
<STOP_BARCODE> ... </STOP_BARCODE> [0..1]
<STOP_PID> ... </STOP_PID> [0..1]
<STOP_COUNTRY_NAME> ... </STOP_COUNTRY_NAME> [0..1]
<WAREHOUSE_LOAD> ... </WAREHOUSE_LOAD> [0..1]
</pre>

{{Note|
* Dates are in XML DateTime format.
* ETA and ACTUAL Dates will be populated from execution-based systems.
* STOP_PID will only be populated for LOTS and CIM flows in one format, or if EDI parameter PRINT_STOP_PID is set to "Y" in a different format. This second format should not be enabled for LOTS interfaces.
}}

=== STOP_SIGNATURE===
This section will only be generated if system parameter LOTS_INC_STOP_SIGNATURE is set to "Y".

<pre>
<STOP_SIGNATURE>
<SIGNATURE> ... </SIGNATURE> [0..1]
<SIGNED_BY> ... </SIGNED_BY> [0..1]
</STOP_SIGNATURE>
</pre>

===ORDER_HEADER===
<pre>
<ORDER_TRANSACTION_DATE> ... </ORDER_TRANSACTION_DATE> [1]
<ORDER_TYPE> ... </ORDER_TYPE> [0..1]
<WMS_WAREHOUSE> ... </WMS_WAREHOUSE> [0..1]
<WMS_OWNER> ... </WMS_OWNER> [0..1]
<SO_REF> ... </SO_REF> [0..1]
<ORIG_SO_REF> ... </ORIG_SO_REF> [0..1]
<TMS_REF> ... </TMS_REF> [0..1]
<PO_REF> ... </PO_REF> [0..1]
<BOOK_REF> ... </BOOK_REF> [0..1]
<BOOK_DATE> ... </BOOK_DATE> [0..1]
<SPECIAL_INSTR> ... </SPECIAL_INSTR> [0..1]
<ORDER_COMMENTS> ... </ORDER_COMMENTS> [0..1]
<ORDER_HEADER_TMS> ... </ORDER_HEADER_TMS> [0..1]
<ORDER_HEADER_ADDRESSES> ... </ORDER_HEADER_ADDRESSES> [0..1]
<ORDER_HEADER_CONFIRM> ... </ORDER_HEADER_CONFIRM> [0..1]
<CUSTOMER_ID> ... </CUSTOMER_ID> [0..1]
<CUSTOMER_NAME> ... </CUSTOMER_NAME> [0..1]
<ORDER_STATUS> ... </ORDER_STATUS> [0..1]
<DESTINATION_ORDER> ... </DESTINATION_ORDER> [0..1]
<DESTINATION_DRIVER> ... </DESTINATION_DRIVER> [0..1]
<DESTINATION_VEHICLE> ... </DESTINATION_VEHICLE> [0..1]
<ORDER_SERVICES> ... </ORDER_SERVICES> [0..1]
</pre>

{{Note|
* SO_REF will be populated with the External reference of the order. This may be modified to remove any rebooking suffix if system parameter ORD_RBO_PREFIX is set to "Y"
* ORDER_STATUS will only be included if the EDI parameter INCLUDE_ORDER_STATUS is set to "Y". Further, if system parameter INCLUDE_FAILED_ORDERS is set to "Y" and the order status is FAILED, this will be changed to CANCELLED instead.
* DESTINATION_ORDER, DESTINATION_DRIVER and DESTINATION_VEHICLE will only be present if order sub references exist of those names.
}}

===ORDER_HEADER_TMS ===
<pre>
<ORDER_HEADER_TMS>
<SHIPMENT_ID> ... </SHIPMENT_ID> [0..1]
<TMS_ORDER_SCHEDULE> ... </TMS_ORDER_SCHEDULE> [0..1]
<TMS_HAULAGE_ACTIVITY> ... </TMS_HAULAGE_ACTIVITY> [0..1]
<TMS_HAULAGE_TYPE> ... </TMS_HAULAGE_TYPE> [0..1]
<EARLY_AVAIL_DATE> ... </EARLY_AVAIL_DATE> [1]
<LATE_AVAIL_DATE> ... </LATE_AVAIL_DATE> [1]
<EARLY_DEL_DATE> ... </EARLY_DEL_DATE> [1]
<LATE_DEL_DATE> ... </LATE_DEL_DATE> [1]
<TMS_GROUP_NAME> ... </TMS_GROUP_NAME> [0..1]
<TMS_DELIVERY_TYPE> ... </TMS_DELIVERY_TYPE> [0..1]
<TMS_COST_CENTRE> ... </TMS_COST_CENTRE> [0..1]
<SD_TEMP_COMBO> ... </SD_TEMP_COMBO> [0..1]
<SD_POD_BY> ... </SD_POD_BY> [0..1]
<KEY_CODE> ... </KEY_CODE> [0..1]
<REVENUE> ... </REVENUE> [0..1]
<COST> ... </COST> [0..1]
<COST_PER_TONNE> ... </COST_PER_TONNE> [0..1]
<HAULIER> ... </HAULIER> [0..1]
<TRAILER_TYPE> ... </TRAILER_TYPE> [0..1]
<ROUTE_CODE> ... </ROUTE_CODE> [0..1]
<EFX_NUMBER> ... </EFX_NUMBER> [0..1]
<TRANSPORT_MODE> ... </TRANSPORT_MODE> [0..1]
<TRANSPORT_STATUS> ... </TRANSPORT_STATUS> [0..1]
<RPE_QTY> ... </RPE_QTY> [0..1]
<ACTUAL_RPE_QTY> ... </ACTUAL_RPE_QTY> [0..1]
<WEIGHT> ... </WEIGHT> [0..1]
<ACTUAL_WEIGHT> ... </ACTUAL_WEIGHT> [0..1]
<VOLUME> ... </VOLUME> [0..1]
<ACTUAL_VOLUME> ... </ACTUAL_VOLUME> [0..1]
<FOOTPRINT> ... </FOOTPRINT> [0..1]
<ACTUAL_FOOTPRINT> ... </ACTUAL_FOOTPRINT> [0..1]
<TOTAL_PRICE> ... </TOTAL_PRICE> [0..1]
</ORDER_HEADER_TMS>
</pre>

{{Note|
* TMS_DELIVERY_TYPE is set to the full delivery type if the EDI parameter SEND_DEL_TYPE_CODE is set to "Y". Otherwise the short code associated to the delivery type is sent.
}}

===ORDER_SERVICES===
This section is only populated if the EDI parameter EXPORT_SERVICES is set to "Y", or if this is set to "C" and the event is "CAN" or "DEL".

<pre>
<ORDER_SERVICE>
<SERVICE_ID> ... </SERVICE_ID> [1]
<SERVICE_NAME> ... </SERVICE_NAME> [1]
<SERVICE_QTY> ... </SERVICE_QTY> [1]
<SERVICE_VALUE> ... </SERVICE_VALUE> [1]
</ORDER_SERVICE>
</pre>

=== ORDER_DETAIL===
The details sent in this section are subject to configuration:
* Order Lines are sent if LOTS_SEND_LINE_ITEMS = "Y", or the value is "N" and there are no order items.
* Order Items are sent if LOTS_SEND_LINE_ITEMS = "Y", or the value is "N" and there are order items.

<pre>
<ORDER_DETAIL>
<DETAIL_TYPE> ... </DETAIL_TYPE> [1]
<DETAIL_ID> ... </DETAIL_ID> [0..1]
<PRODUCT_TYPE> ... </PRODUCT_TYPE> [0..1]
<PRODUCT_TYPE_DESC> ... </PRODUCT_TYPE_DESC> [0..1]
<DU_TYPE> ... </DU_TYPE> [0..1]
<ITEM_IDENTIFIER> ... </ITEM_IDENTIFIER> [1]
<ITEM_DESCRIPTION> ... </ITEM_DESCRIPTION> [0..1]
<PALLET_ID> ... </PALLET_ID> [0..1]
<ITEM_AKA_CODE> ... </ITEM_AKA_CODE> [0..1]
<ITEM_FACTOR> ... </ITEM_FACTOR> [0..1]
<LIFTS> ... </LIFTS> [0..1]
<STACK> ... </STACK> [0..1]
<RPE_QTY> ... </RPE_QTY> [0..1]
<ACTUAL_RPE_QTY> ... </ACTUAL_RPE_QTY> [0..1]
<WEIGHT> ... </WEIGHT> [0..1]
<ACTUAL_WEIGHT> ... </ACTUAL_WEIGHT> [0..1]
<VOLUME> ... </VOLUME> [0..1]
<ACTUAL_VOLUME> ... </ACTUAL_VOLUME> [0..1]
<FOOTPRINT> ... </FOOTPRINT> [0..1]
<ACTUAL_FOOTPRINT> ... </ACTUAL_FOOTPRINT> [0..1]
<ORDERED> ... </ORDERED> [0..1]
<PACKED> ... </PACKED> [0..1]
<TO_DELIVER> ... </TO_DELIVER> [0..1]
<DELIVERED> ... </DELIVERED> [0..1]
<SAP_LINE_NO> ... </SAP_LINE_NO> [0..1]
<SHIPMENT_DETAIL> ... </SHIPMENT_DETAIL> [0..1]
<REASON_CODES> ... </REASON_CODES> [0..1]
<DIM_WEIGHT> ... </DIM_WEIGHT> [0..1]
<ACTUAL_DIM_WEIGHT> ... </ACTUAL_DIM_WEIGHT> [0..1]
<TRACKING_REFS> ... </TRACKING_REFS> [0..1]
<DU_DESCRIPTION> ... </DU_DESCRIPTION> [0..1]
<DU_CATEGORY> ... </DU_CATEGORY> [0..1]
<PLANNED_CASES> ... </PLANNED_CASES> [0..1]
<ACTUAL_CASES> ... </ACTUAL_CASES> [0..1]
<SCAN_TYPE> ... </SCAN_TYPE> [0..1]
<LENGTH> ... </LENGTH> [0..1]
<WIDTH> ... </WIDTH> [0..1]
<HEIGHT> ... </HEIGHT> [0..1]
<COMMODITY_ID> ... </COMMODITY_ID> [0..1]
<CLASS_ID> ... </CLASS_ID> [0..1]
<WMS_LOCATION> ... </WMS_LOCATION> [0..1]
<LONG_DESCRIPTION> ... </LONG_DESCRIPTION> [0..1]
<ORDER_DETAIL_TYRE> ... </ORDER_DETAIL_TYRE> [0..1]
<ITEM_PRICE> ... </ITEM_PRICE> [0..1]
</ORDER_DETAIL>
</pre>

{{Note|
* DETAIL_TYPE will be "D" if generated from Order Lines, and "S" if generated from Order Items.
* For D lines
** ITEM_IDENTIFIER will be the DU Type
** ITEM_DESCRIPTION will the DU Type description for "D" lines
** RPE_QTY will include Despatched and Packed REP if the EDI Parameter INC_PACKED_TO_DEL is set to "Y", other wise this will just be the Actual RPE and RPE qty.
** PACKED will be populated if the order has been packed.
** TO_DELIVER will be populated if the order has been collected.
** DELIVERED will be present and populated if the order has been delivered to its final destination.
** SAP_LINE_NO will only be present and populated if the EDI Parameter INCLUDE_SAP_LINE_NOS is "Y" and there is a SAP line number against the order line.
** REASON_CODES will be included if there are non-conformity reason codes against the order line for the API interface.
** REASON_CODES will be included for other flows if EDI Parameters INCLUDE_REASON_CODES and INCLUDE_NON_CON_CODES are set. {{Warning}} These should NOT be set against the API process.
** TRACKING_REFS will be included if the EDI Parameter INCLUDE_TRACK_REF is set to "Y".
* For S lines
** ITEM_IDENTIFIER will be the Item Identifier, unless the customer has specified that an alternative item identifier is used and one is provided against the item. If system parameter USE_PALLET_ID_XML is set to "Y", then the Pallet ID of the item record will be used instead.
** PALLET_ID will only be populated if system parameter SEND_PALLET_ID_XML is set to "Y".
** ORDERED will only be present and populated if the value is not null.
** TO_DELIVER will only be present and populated if the value is null i.e. the order item has been collected.
** DELIVERED will only be present and populated if the value is not null i.e. the order item has been delivered and EDI parameter INCLUDE_ITEM_DELIVER is set to "Y", or this is sent through the API.
** SAP_LINE_NO will only be present and populated if the EDI Parameter INCLUDE_SAP_LINE_NOS is "Y" and there is a SAP line number against the order line.
** REASON_CODES will be included if there are non-conformity reason codes against the order line for the API interface.
** REASON_CODES will be included for other flows if EDI Parameters INCLUDE_REASON_CODES and INCLUDE_NON_CON_CODES are set. {{Warning}} These should NOT be set against the API process.
}}

===TRACKING_REFS===
TRACKING_REFS will be included if the EDI Parameter INCLUDE_TRACK_REF is set to "Y".

<pre>
<TRACKING_REF>
<UNIT_TRACKING_REF> ... </UNIT_TRACKING_REF> [1]
<UNIT_TRACKING_NO> ... </UNIT_TRACKING_NO> [1]
</TRACKING_REF>
</pre>

===ORDER_DETAIL_TYRE===
For TYRE-based systems

<pre>
<ORDER_DETAIL_TYRE>
<WPX_PRODUCT_ID> ... </WPX_PRODUCT_ID> [1]
<POSITION> ... </POSITION> [1]
<LOCATION> ... </LOCATION> [1]
<PRICE> ... </PRICE> [1]
<CUSTOMER_VEHICLE> ... </CUSTOMER_VEHICLE> [1]
<AUTHORITY_CODE> ... </AUTHORITY_CODE> [1]
<WORK_TYPE> ... </WORK_TYPE> [1]
<PRESSURE> ... </PRESSURE> [1]
<TREAD_DEPTH> ... </TREAD_DEPTH> [1]
<CASING> ... </CASING> [1]
<CASING_DESTINATION> ... </CASING_DESTINATION> [1]
<NEW_REMOULD> ... </NEW_REMOULD> [1]
<REGROOVED> ... </REGROOVED> [1]
<TYRE_SERIAL_NO> ... </TYRE_SERIAL_NO> [1]
<REMOVAL_REASON> ... </REMOVAL_REASON> [1]
<WORK_TYPES> ... </WORK_TYPES> [1]
<SERVICES_SUPPLIED> ... </SERVICES_SUPPLIED> [1]
<BARCODE> ... </BARCODE> [1]
<TORQUE> ... </TORQUE> [1]
</ORDER_DETAIL_TYRE>
</pre>

=== ORDER_REASON_CODE ===
<pre>
<ORDER_REASON_CODE>
<RC_TYPE> ... </RC_TYPE> [1]
<RC_CODE> ... </RC_CODE> [1]
<RC_DESCRIPTION> ... </RC_DESCRIPTION> [1]
<RC_COMMENT> ... </RC_COMMENT> [0..1]
</ORDER_REASON_CODE>
</pre>

{{Note|
* For reason codes included for Order Item non-conformities, RC_TYPE will only be included if EDI parameter INCLUDE_REASON_TYPE is set to "Y", and will always then be "NONC"
}}

===ORDER_HEADER_TYRE===
For TYRE-based systems

<pre>
<ORDER_HEADER_TYRE>
<CUSTOMER_VEHICLE> ... </CUSTOMER_VEHICLE> [0..1]
<AUTHORITY_CODE> ... </AUTHORITY_CODE> [0..1]
</ORDER_HEADER_TYRE>
</pre>

=== ORDER_VEHICLE===
For TYRE-based systems

<pre>
<ORDER_VEHICLE> - for TYRE-based systems only
<VEHICLE_ID> ... </VEHICLE_ID> [1]
<MAKE> ... </MAKE> [1]
<MODEL> ... </MODEL> [1]
<ODO> ... </ODO> [1]
<DESCRIPTION> ... </DESCRIPTION> [1]
<LAST_INSPECTION_DATE> ... </LAST_INSPECTION_DATE> [1]
<VEHICLE_CONFIG_ID> ... </VEHICLE_CONFIG_ID> [1]
<VEHICLE_CONFIG> ... </VEHICLE_CONFIG> [1]
<EPOD_SERVICE_ID> ... </EPOD_SERVICE_ID> [0..1]
</ORDER_VEHICLE>
</pre>

== EDI Trip Order XML Webservices Configuration ==
{{:EDI Trip Order XML Webservices Configuration}}

==System Parameters affecting XML Production==
System parameters affecting content in TripOrder XML

{| class="wikitable apt-searchable" border="1" id="systemparams"
|- bgcolor="silver"
!Parameter!!Description!!Level
|-
|CUST_UPDATE_ORDER_LINES||Update Orders|| CUSTOMER
|-
|EPOD_SIGNATURE_STORAGE||Store signature received from C-ePOD ||COST_CENTRE
|-
|IMP_OVERRIDE_SOURCE_REF||Set source system and control additional functionality in ORD_LINE_ITM CSV order import||SYSTEM
|-
| INCL_ROUTE_CODE||Include Baxter Route code and delivery method||COST_CENTRE
|-
|INCLUDE_FAILED_ORDERS||Include Failed Orders as CANCELLED for API||COST_CENTRE
|-
|LOTS_ADD_DEBRIEF||LOTS Additional Debrief Details||COST_CENTRE
|-
|LOTS_DEL_CUST_SIGNATORY ||Controls if DEL messages for LOTS require an actual signatory - Y to hold messages.||COST_CENTRE
|-
|LOTS_INC_ORDER_HEADER_CONFIRM ||Includes the ORDER_HEADER_CONFIRM section in the DEL file for LOTS. ||SYSTEM - only LOTS, DEL event
|-
|LOTS_INC_STOP_SIGNATURE|| Indicates if the STOP_SIGNATURE section will be displayed in the DEL outbound files to LOTS.||SYSTEM - only for LOTSC
|-
|LOTS_INC_STOP_TYPE_DESC||Include STOP-TYPE_DESC tag in XML||SYSTEM - ONLY FOR LOTS process
|-
|LOTS_SEND_WHEN_VEHICLE_SCANNED||List of LOTS message types that will be held until a vehicle scan is received for the order.||COST_CENTRE
|-
|MIC_ADD_STOP_BARCODE|| Include new tag STOP_BARCODE on Microlise outbound xml||SYSTEM - only for process MIC
|-
| OMS_FOOTPRINT_FOR_VOLUME ||Will the footprint of the order line be include in the VOLUME item for the outbound XML file for the despatch units instead of the cubic volume (Y/N)?||COST_CENTRE
|-
|ORD_NO_DEL_FOR_FAILS||Controls if DEL messages are generated for FAILED orders - Y to prevent, C to send as CAN|| COST_CENTRE
|-
|ORD_RBO_PREFIX||Is the rebook prefix stripped for LOTS? ||SYSTEM
|-
|ORD_TEMPERATURE_COMBO||Use Temperature Combo to determine if the customer reference should be highlighted.||COST_CENTRE
|-
|SEND_LINE_ITEM_TO_LOTS ||Send Line Item To LOTS. Y - send both Order Line (D) and Item (S) records. N - Checks for Items and, if there are any, sends Item (S) records, else Order Line (D) records.||SYSTEM
|-
|SEND_PALLET_ID_XML|| Send Pallet ID tag in xml||COST_CENTRE
|-
| STOP_PID||LOTS - is STOP_PID included in the extract ||SYSTEM - only for LOTS/CIM
|-
|TIME_ZONE_ACTIVE||Time Zone Active||SYSTEM
|-
| TMS_OTBOUND_SO_REF||Controls the outbound format for SO_REF in LOTSC||CUSTOMER
|-
|TRIP_ORDER_XSD_VERS||Version of TRIP XSD being used.||SYSTEM
|-
|TRM_DESP_FOR_DEL||Maintain the Actual Despatched Quantity for a Delivery Trip in Trip Debrief (Y/N).||COST_CENTRE
|-
|UNI_LOCATION||Location for Unilever||SYSTEM
|-
|USE_ORDER_ADDRESSEE||Will the addressee name be used for the order? (Y/N)||COST_CENTRE
|-
| USE_PALLET_ID_XML||Use Pallet ID instead of item identifier in XML Outbound files||COST_CENTRE
|-
|USE_XML_ORDER_SUB_REFS||Print order sub refs on outbound XML||COST_CENTRE
|}

= APPENDIX: XSD SECTIONS =
{| class="wikitable apt-searchable"
!Parent
!Cardinality
!Child
!Description of Child
|-
|OBS_XML
|1
|EVENT
|Event message containing header, detail, and optional tracking.
|-
|EVENT
|1
|EVENT_HEADER
|Message event header containing metadata about the event.
|-
|EVENT
|0..*
|EVENT_DETAIL
|Business payload containing trip, stops, and tasks.
|-
|EVENT
|0..1
|EVENT_TRACKING
|Tracking information for the event.
|-
|EVENT_TRACKING
|1..*
|MILESTONE
|Individual tracking milestone with status, dates, and locations.
|-
|EVENT_DETAIL
|1
|TRIP_HEADER
|Message control and trip identifier.
|-
|EVENT_DETAIL
|0..1
|TRIP_DETAIL
|Principal operational details of the trip.
|-
|EVENT_DETAIL
|0..1
|STOPS
|Detail of stops on the trip.
|-
|EVENT_DETAIL
|0..1
|TRIP_TASKS
|Tasks for the given trip.
|-
|TRIP_TASKS
|1..*
|TRIP_TASK
|Individual task performed during the trip.
|-
|STOPS
|1..*
|STOP
|Details of a single stop on the trip.
|-
|STOP
|1
|STOP_HEADER
|Message control and stop identifier.
|-
|STOP
|0..1
|STOP_DETAIL
|Operational and location details of the stop.
|-
|STOP
|0..1
|STOP_SIGNATURE
|Signature captured after stop completion.
|-
|STOP
|0..1
|ORDERS
|Orders associated with the stop.
|-
|STOP
|0..1
|STOP_REASON_CODES
|Stop-level discrepancy or exception reasons.
|-
|STOP
|0..1
|STOP_TASKS
|Tasks performed at stop level.
|-
|STOP_DETAIL
|0..1
|STOP_SUB_REFS
|Stop-level sub-references.
|-
|STOP_SUB_REFS
|1..*
|STOP_SUB_REF
|A single stop sub-reference.
|-
|STOP_REASON_CODES
|1..*
|STOP_REASON_CODE
|Individual stop reason code.
|-
|STOP_TASKS
|1..*
|STOP_TASK
|Individual task performed at the stop.
|-
|ORDERS
|1..*
|ORDER
|Order for collection, delivery, or direct movement.
|-
|ORDER
|1
|ORDER_HEADER
|Header information describing an order.
|-
|ORDER
|0..1
|ORDER_SUB_REFS
|Repeating sub-order references.
|-
|ORDER
|0..1
|ORDER_SIGNATURE
|Order-level proof-of-delivery signature.
|-
|ORDER
|0..1
|ORDER_DETAILS
|Line-level detail information for the order.
|-
|ORDER
|0..1
|ORDER_HEADER_TYRE
|Tyre service–specific order information.
|-
|ORDER
|0..1
|ORDER_TASKS
|Tasks associated with the order.
|-
|ORDER
|0..1
|ORDER_HAZARDOUS_DETAILS
|Hazardous goods details for the order.
|-
|ORDER
|0..1
|ORDER_REASON_CODES
|Order-level discrepancy or exception reasons.
|-
|ORDER
|0..1
|ORDER_SERVICES
|Services supplied for the order.
|-
|ORDER
|0..1
|ORDER_VEHICLES
|Vehicles associated with tyre-service orders.
|-
|ORDER_HEADER
|1
|ORDER_TRANSACTION_DATE
|Transaction date and time of the order.
|-
|ORDER_HEADER
|0..1
|ORDER_HEADER_TMS
|Transport Management System details of the order.
|-
|ORDER_HEADER
|0..1
|ORDER_HEADER_ADDRESSES
|Addresses associated with the order.
|-
|ORDER_HEADER
|0..1
|ORDER_HEADER_CONFIRM
|LOTS confirmed delivery information.
|-
|ORDER_HEADER_ADDRESSES
|1..*
|ORDER_HEADER_ADDRESS
|Address information for collection, delivery, or invoice.
|-
|ORDER_HEADER_ADDRESS
|0..1
|OH_ADDRESS_DATE_TIMES
|Planned and actual date/time windows for the address.
|-
|ORDER_HEADER_ADDRESS
|0..1
|OH_ADDRESS_CONTACTS
|Contacts associated with the address.
|-
|ORDER_HEADER_ADDRESS
|0..1
|OH_ADDRESS_TRAILERS
|Trailer constraints for the address.
|-
|ORDER_HEADER_ADDRESS
|0..1
|OH_ADDRESS_REFERENCES
|Reference identifiers associated with the address.
|-
|OH_ADDRESS_CONTACTS
|1..*
|OH_ADDRESS_CONTACT
|Individual address contact details.
|-
|OH_ADDRESS_REFERENCES
|1..*
|OH_ADDRESS_REFERENCE
|Single address reference entry.
|-
|OH_ADDRESS_TRAILERS
|0..*
|OH_ADDRESS_TRAILER
|Trailer type constraint for an address.
|-
|ORDER_SUB_REFS
|1..*
|ORDER_SUB_REF
|Individual sub-order reference.
|-
|ORDER_DETAILS
|1..*
|ORDER_DETAIL
|Individual order line, despatch unit, or stock item.
|-
|ORDER_DETAIL
|0..1
|TRACKING_REFS
|Tracking references for despatch units.
|-
|TRACKING_REFS
|1..*
|TRACKING_REF
|Individual tracking reference and number.
|-
|ORDER_HAZARDOUS_DETAILS
|1..*
|ORDER_HAZARDOUS_DETAIL
|Hazardous material details for an order line.
|-
|ORDER_REASON_CODES
|1..*
|ORDER_REASON_CODE
|Individual order reason code.
|-
|ORDER_TASKS
|1..*
|ORDER_TASK
|Individual task performed at order level.
|-
|ORDER_VEHICLES
|0..*
|ORDER_VEHICLE
|Vehicle details for tyre-service orders.
|-
|TRIP_DETAIL
|0..1
|TRIP_SUB_REFS
|Trip-level sub-references.
|-
|TRIP_SUB_REFS
|1..*
|TRIP_SUB_REF
|Individual trip sub-reference.
|}

= APPENDIX: Core Import XSD Elements =
{| class="wikitable apt-searchable"
!Item
!Type
!Size
!Restriction
!CTMS Mandatory*
!Maximum Length
|-
|EVENT_PROCESSED
|STRING
|1
|E,N,Y
|Y
|1
|-
|EVENT_SOURCE_TYPE
|STRING
|4
|New Value
|Y
|4
|-
|EVENT_SOURCE_NAME
|STRING
|10
|
|Y
|10
|-
|EVENT_DATE
|DATETIME
|
|
|Y
|
|-
|EVENT_TYPE
|STRING
|3
|
|Y
|3
|-
|EVENT_ACTION
|STRING
|1
|A,C,D
|Y
|1
|-
|TRIP_IDENTIFIER
|STRING
|1
|O,T
|Y
|1
|-
|TRIP_TRANSACTION_DATE
|DATETIME
|
|
|
|
|-
|TRIP_ID
|STRING
|12
|
|
|12
|-
|STOP_IDENTIFIER
|STRING
|1
|O,S
|Y
|1
|-
|STOP_ID
|STRING
|51
|—
|N
|51
|-
|STOP_SEQ
|INTEGER
|—
|< 999999
|N
|—
|-
|ORDER_TRANSACTION_DATE
|DATETIME
|—
|xs:dateTime
|Y
|—
|-
|ORDER_TYPE
|STRING
|10
|—
|N
|10
|-
|WMS_WAREHOUSE
|STRING
|3
|—
|N
|3
|-
|WMS_OWNER
|STRING
|12
|—
|N
|12
|-
|SO_REF
|STRING
|20
|—
|N
|'''16'''
|-
|TMS_REF
|STRING
|20
|—
|N
|20
|-
|PO_REF
|STRING
|20
|—
|N
|20
|-
|BOOK_REF
|STRING
|20
|—
|N
|20
|-
|BOOK_DATE
|DATETIME
|—
|xs:dateTime
|N
|—
|-
|SPECIAL_INSTR
|STRING
|2000
|—
|N
|2000
|-
|ORDER_COMMENTS
|STRING
|2000
|—
|N
|2000
|-
|EARLY_AVAIL_DATE
|DATETIME
|—
|xs:dateTime
|Y
|—
|-
|LATE_AVAIL_DATE
|DATETIME
|—
|xs:dateTime
|Y
|—
|-
|EARLY_DEL_DATE
|DATETIME
|—
|xs:dateTime
|Y
|—
|-
|LATE_DEL_DATE
|DATETIME
|—
|xs:dateTime
|Y
|—
|-
|TMS_GROUP_NAME
|STRING
|12
|—
|N
|12
|-
|TMS_DELIVERY_TYPE
|STRING
|35
|—
|N
|35
|-
|TMS_COST_CENTRE
|STRING
|12
|—
|N
|12
|-
|HAULIER
|STRING
|12
|—
|N
|12
|-
|TRANSPORT_MODE
|STRING
|30
|—
|N
|30
|-
|ADDRESS_TYPE
|STRING
|3
|DEP,DEL,INV
|Y
|3
|-
|ADDRESS_ID
|STRING
|25
|—
|Y
|25
|-
|ADDRESS_NAME
|STRING
|50
|—
|N
|50
|-
|ADDRESS_LINE1
|STRING
|50
|—
|N
|50
|-
|ADDRESS_LINE2
|STRING
|50
|—
|N
|50
|-
|ADDRESS_LINE3
|STRING
|50
|—
|N
|50
|-
|ADDRESS_TOWN
|STRING
|50
|—
|N
|50
|-
|ADDRESS_COUNTY
|STRING
|50
|—
|N
|50
|-
|ADDRESS_COUNTRY_CODE
|STRING
|3
|—
|N
|3
|-
|ADDRESS_POSTCODE
|STRING
|9
|—
|N
|9
|-
|CUSTOMER_ID
|STRING
|12
|—
|N
|12
|-
|CUSTOMER_NAME
|STRING
|50
|—
|N
|50
|-
|SUB_REF_IDENTIFIER
|STRING
|50
|—
|Y
|50
|-
|SUB_REFERENCE
|STRING
|1000
|—
|Y
|1000
|-
|DETAIL_TYPE
|STRING
|1
|S,D,C
|Y
|1
|-
|DETAIL_ID
|STRING
|30
|—
|N
|30
|-
|PRODUCT_TYPE
|STRING
|12
|—
|N
|12
|-
|PRODUCT_TYPE_DESC
|STRING
|50
|—
|N
|50
|-
|DU_TYPE
|STRING
|12
|—
|N
|12
|-
|ITEM_IDENTIFIER
|STRING
|20
|—
|Y
|'''15'''
|-
|ITEM_DESCRIPTION
|STRING
|122
|—
|N
|122
|-
|PALLET_ID
|STRING
|100
|—
|N
|100
|-
|ITEM_AKA_CODE
|STRING
|30
|—
|N
|30
|-
|ITEM_FACTOR
|STRING
|12
|—
|N
|12
|-
|LIFTS
|DECIMAL
|8,2
|—
|N
|—
|-
|RPE_QTY
|DECIMAL
|10,2
|—
|N
|—
|-
|WEIGHT
|DECIMAL
|10,2
|—
|N
|—
|-
|VOLUME
|DECIMAL
|15,5
|—
|N
|—
|-
|ORDERED
|DECIMAL
|28,4
|—
|N
|—
|-
|TO_DELIVER
|DECIMAL
|28,4
|—
|N
|—
|-
|DELIVERED
|DECIMAL
|28,4
|—
|N
|—
|-
|PLANNED_CASES
|INTEGER
|—
|< 99999999
|N
|—
|-
|LENGTH
|DECIMAL
|10,2
|—
|N
|—
|-
|WIDTH
|DECIMAL
|10,2
|—
|N
|—
|-
|HEIGHT
|DECIMAL
|10,2
|—
|N
|—
|-
|COMMODITY_ID
|STRING
|256
|—
|N
|256
|-
|CLASS_ID
|STRING
|256
|—
|N
|256
|-
|UN_NUMBER
|STRING
|50
|—
|N
|50
|-
|HAZARDOUS
|STRING
|1
|Y,N
|N
|1
|-
|HAZARDOUS_QTY
|DECIMAL
|28,4
|—
|N
|—
|-
|HAZARDOUS_DESCRIPTION
|STRING
|40
|—
|N
|40
|}
<nowiki>*</nowiki>The mandatory flag for CTMS is only valid if the optional section has been provided in the file.

Note that an item quantity must be provided as ‘ORDERED’ or ‘TO_DELIVER’ depending which item is being used (as set by an EDI parameter).

TripOrder Interface XML

2026-03-06T11:29:05Z

Anw: Added appendices showing sections and core import fields

This document is designed to give a brief overview of integration methods into and out of the Aptean TMS - Calidus Edition (CTMS) for transport orders.

The transport orders can be created in CTMS from external systems using XML files based on a standard XSD file format for CTMS called 'TripOrder'.

The following sections will describe some of the sections that are available in the XSD file to create and amend transport orders.

The same XSD file format is used for files being sent by CTMS to external systems to provided information about the transport orders in CTMS and how they have been, or will be, transported between depots and sites.

= XML Inbound Order File Structure =
== EDI Maintenance ==
The XML files for CTMS will be received into a directory structure and processed as may be specified in the 'EDI Maintenance' screen.

Multiple EDI flows may be active to process XML files from different source systems with different filename formats as required.

There are various EDI parameters that can be set to provide different levels of validation of the data that is extracted from the file.

There are also EDI parameters that can be used to set default values for when the data is not able to be provided in the file.

For example, the order time windows can be recalculated and the hazardous data can be defaulted.

=== Webservice API Imports ===
This is controlled via the EDI Maintenance screen. See the section [[TripOrder Interface XML#EDI Trip Order XML Webservices Configuration|EDI Trip Order XML Webservices Configuration]] below for details.

== TripOrder File ==
<OBS_XML>
<EVENT>
<EVENT_HEADER>
<EVENT_DETAIL>

The overall file structure consists of two complex type elements - the file header information and then the details. Each element must only exist once per file.

The different sections within <OBS_XML> can occur differently, the data in bold type is included in the text. {{Note}} Not all of the sections and elements that are available in the XSD file format are listed, just the most common use cases:

<OBS_XML> 1.1 <EVENT>
<EVENT> 1.1 <EVENT_HEADER>
<EVENT_HEADER> 1.1 <ALL ELEMENTS>
<EVENT> 0.00 <EVENT_DETAIL>
<EVENT_DETAIL> 1.1 <TRIP_HEADER>
<TRIP_HEADER> 1.1 <TRIP_IDENTIFIER>
<TRIP_HEADER> 0.1 <TRIP_TRANSACTION_DATE>
<TRIP_HEADER> 0.1 <TRIP_ID>
<EVENT_DETAIL> 0.1 <TRIP_DETAIL>
<EVENT_DETAIL> 0.1 <STOPS>
<STOPS> 1.00 <STOP>
<STOP> 1.1 <STOP_HEADER>
<STOP_HEADER> 1.1 <STOP_IDENTIFIER>
<STOP_HEADER> 0.1 <STOP_ID>
<STOP_HEADER> 0.1 <STOP_SEQ>
<STOP> 0.1 <STOP_DETAIL>
<STOP> 0.1 <ORDERS>
<ORDERS> 1.1 <ORDER>
<ORDER> 1.1 <ORDER_HEADER>
<ORDER_HEADER> 1.1 <ORDER_TRANSACTION_DATE>
<ORDER_HEADER> 0.1 <ORDER_TYPE>
<ORDER_HEADER> 0.1 <WMS_WAREHOUSE>
<ORDER_HEADER> 0.1 <WMS_OWNER>
<ORDER_HEADER> 0.1 <SO_REF>
<ORDER_HEADER> 0.1 <TMS_REF>
<ORDER_HEADER> 0.1 <PO_REF>
<ORDER_HEADER> 0.1 <BOOK_REF>
<ORDER_HEADER> 0.1 <BOOK_DATE>
<ORDER_HEADER> 0.1 <SPECIAL_INSTR>
<ORDER_HEADER> 0.1 <ORDER_COMMENTS>
<ORDER_HEADER> 0.1 <ORDER_HEADER_TMS>
<ORDER_HEADER_TMS> 1.1 <EARLY_AVAIL_DATE>
<ORDER_HEADER_TMS> 1.1 <LATE_AVAIL_DATE>
<ORDER_HEADER_TMS> 1.1 <EARLY_DEL_DATE>
<ORDER_HEADER_TMS> 1.1 <LATE_DEL_DATE>
<ORDER_HEADER_TMS> 0.1 <TMS_GROUP_NAME>
<ORDER_HEADER_TMS> 0.1 <TMS_DELIVERY_TYPE>
<ORDER_HEADER_TMS> 0.1 <TMS_COST_CENTRE>
<ORDER_HEADER_TMS> 0.1 <HAULIER>
<ORDER_HEADER_TMS> 0.1 <TRANSPORT_MODE>
<ORDER_HEADER> 0.1 <ORDER_HEADER_ADDRESSES>
<ORDER_HEADER_ADDRESSES> 1.00 <ORDER_HEADER_ADDRESS>
<ORDER_HEADER_ADDRESS> 1.1 <ADDRESS_TYPE>
<ORDER_HEADER_ADDRESS> 1.1 <ADDRESS_ID>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_NAME>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LINE1>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LINE2>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LINE3>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_TOWN>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_COUNTY>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_COUNTRY_CODE>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_POSTCODE>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LOC_TYPE>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_CUST_GROUP>
<ORDER_HEADER_ADDRESS> 0.1 <OH_ADDRESS_CONTACTS>
<OH_ADDRESS_CONTACTS> 1.00 <OH_ADDRESS_CONTACT>
<OH_ADDRESS_CONTACT> 0.1 <ALL ELEMENTS>
<ORDER_HEADER> 0.1 <CUSTOMER_ID>
<ORDER_HEADER> 0.1 <CUSTOMER_NAME>
<ORDER> 0.1 <ORDER_SUB_REFS>
<ORDER_SUB_REFS> 1.1 <ORDER_SUB_REF>
<ORDER_SUB_REF> 1.1 <SUB_REF_IDENTIFIER>
<ORDER_SUB_REF> 1.1 <SUB_REFERENCE>
<ORDER> 0.1 <ORDER_DETAILS>
<ORDER_DETAILS> 1.1 <ORDER_DETAIL>
<ORDER_DETAIL> 1.1 <DETAIL_TYPE>
<ORDER_DETAIL> 0.1 <DETAIL_ID>
<ORDER_DETAIL> 0.1 <PRODUCT_TYPE>
<ORDER_DETAIL> 0.1 <PRODUCT_TYPE_DESC>
<ORDER_DETAIL> 0.1 <DU_TYPE>
<ORDER_DETAIL> 1.1 <ITEM_IDENTIFIER>
<ORDER_DETAIL> 0.1 <ITEM_DESCRIPTION>
<ORDER_DETAIL> 0.1 <PALLET_ID>
<ORDER_DETAIL> 0.1 <ITEM_AKA_CODE>
<ORDER_DETAIL> 0.1 <ITEM_FACTOR>
<ORDER_DETAIL> 0.1 <LIFTS>
<ORDER_DETAIL> 0.1 <RPE_QTY>
<ORDER_DETAIL> 0.1 <WEIGHT>
<ORDER_DETAIL> 0.1 <VOLUME>
<ORDER_DETAIL> 0.1 <ORDERED>
<ORDER_DETAIL> 0.1 <TO_DELIVER>
<ORDER_DETAIL> 0.1 <DELIVERED>
<ORDER_DETAIL> 0.1 <PLANNED_CASES>
<ORDER_DETAIL> 0.1 <LENGTH>
<ORDER_DETAIL> 0.1 <WIDTH>
<ORDER_DETAIL> 0.1 <HEIGHT>
<ORDER_DETAIL> 0.1 <COMMODITY_ID>
<ORDER_DETAIL> 0.1 <CLASS_ID>
<ORDER> 0.1 <ORDER_HAZARDOUS_DETAILS>
<ORDER_HAZARDOUS_DETAILS> 1.00 <ORDER_HAZARDOUS_DETAIL>
<ORDER_HAZARDOUS_DETAIL> 0.1 <ALL ELEMENTS>

The XML items have the following definitions in the XSD file format:

{| class="wikitable apt-searchable" border="1" id="triporderxml"
|- bgcolor="silver"
!Item !!Type !!Size !!Restriction !!CTMS Mandatory*
|-
|EVENT_PROCESSED ||STRING ||1 ||E,N,Y ||Y
|-
|EVENT_SOURCE_TYPE ||STRING ||4 ||New Value ||Y
|-
|EVENT_SOURCE_NAME ||STRING ||10 || ||Y
|-
|EVENT_DATE ||DATETIME || || ||Y
|-
|EVENT_TYPE ||STRING ||3 || ||Y
|-
|EVENT_ACTION ||STRING ||1 ||A,C,D ||Y
|-
|TRIP_IDENTIFIER ||STRING ||1 ||O,T ||Y
|-
|TRIP_TRANSACTION_DATE ||DATETIME || || ||
|-
|TRIP_ID ||STRING ||12 || ||
|-
|STOP_IDENTIFIER ||STRING ||1 ||O,S ||Y
|-
|STOP_ID ||STRING ||51 || ||
|-
|STOP_SEQ ||INTEGER ||6 || ||
|-
|ORDER_TRANSACTION_DATE ||DATETIME || || ||Y
|-
|ORDER_TYPE ||STRING ||1 || ||
|-
|WMS_WAREHOUSE ||STRING ||3 || ||
|-
|WMS_OWNER ||STRING ||12 || ||Y
|-
|SO_REF ||STRING ||20 || ||Y
|-
|TMS_REF ||STRING ||20 || ||
|-
|PO_REF ||STRING ||20 || ||
|-
|BOOK_REF ||STRING ||20 || ||
|-
|BOOK_DATE ||DATETIME || || ||
|-
|SPECIAL_INSTR ||STRING ||2000 || ||
|-
|ORDER_COMMENTS ||STRING ||2000 || ||
|-
|EARLY_AVAIL_DATE ||DATETIME || || ||Y
|-
|LATE_AVAIL_DATE ||DATETIME || || ||Y
|-
|EARLY_DEL_DATE ||DATETIME || || ||Y
|-
|LATE_DEL_DATE ||DATETIME || || ||Y
|-
|TMS_GROUP_NAME ||STRING ||12 || ||
|-
|TMS_DELIVERY_TYPE ||STRING ||35 || ||
|-
|TMS_COST_CENTRE ||STRING ||12 || ||Y
|-
|HAULIER ||STRING ||12 || ||
|-
|TRANSPORT_MODE ||STRING ||30 || ||
|-
|ADDRESS_TYPE ||STRING ||3 || ||Y
|-
|ADDRESS_ID ||STRING ||25 || ||Y
|-
|ADDRESS_NAME ||STRING ||50 || ||
|-
|ADDRESS_LINE1 ||STRING ||50 || ||
|-
|ADDRESS_LINE2 ||STRING ||50 || ||
|-
|ADDRESS_LINE3 ||STRING ||50 || ||
|-
|ADDRESS_TOWN ||STRING ||50 || ||
|-
|ADDRESS_COUNTY ||STRING ||50 || ||
|-
|ADDRESS_COUNTRY_CODE ||STRING ||3 || ||
|-
|ADDRESS_POSTCODE ||STRING ||9 || ||
|-
|ADDRESS_LOC_TYPE ||STRING ||12 || ||
|-
|ADDRESS_CUST_GROUP ||STRING ||12 || ||
|-
|ADDRESS_CONTACT_TYPE ||STRING ||1 ||L,O ||
|-
|ADDRESS_CONTACT_FORENAME ||STRING ||50 || ||
|-
|ADDRESS_CONTACT_SURNAME ||STRING ||50 || ||
|-
|ADDRESS_CONTACT_NUMBER ||STRING ||50 || ||
|-
|ADDRESS_EMAIL ||STRING ||100 || ||
|-
|ADDRESS_CONTACT_JOB ||STRING ||50 || ||
|-
|CUSTOMER_ID ||STRING ||12 || ||
|-
|CUSTOMER_NAME ||STRING ||50 || ||
|-
|SUB_REF_IDENTIFIER ||STRING ||50 || ||Y
|-
|SUB_REFERENCE ||STRING ||512 || ||Y
|-
|DETAIL_TYPE ||STRING ||1 ||D,S ||Y
|-
|DETAIL_ID ||STRING ||30 || ||
|-
|PRODUCT_TYPE ||STRING ||12 || ||
|-
|PRODUCT_TYPE_DESC ||STRING ||50 || ||Y
|-
|DU_TYPE ||STRING ||12 || ||
|-
|ITEM_IDENTIFIER ||STRING ||20 || ||Y
|-
|ITEM_DESCRIPTION ||STRING ||122 || ||
|-
|PALLET_ID ||STRING ||100 || ||
|-
|ITEM_AKA_CODE ||STRING ||30 || ||
|-
|ITEM_FACTOR ||STRING ||12 || ||
|-
|LIFTS ||DECIMAL ||8,2 || ||
|-
|RPE_QTY ||DECIMAL ||10,2 || ||
|-
|WEIGHT ||DECIMAL ||10,2 || ||
|-
|VOLUME ||DECIMAL ||15,5 || ||
|-
|ORDERED ||DECIMAL ||28,4 || ||
|-
|TO_DELIVER ||DECIMAL ||28,4 || ||
|-
|DELIVERED ||DECIMAL ||28,4 || ||
|-
|PLANNED_CASES ||INTEGER ||8 || ||
|-
|LENGTH ||DECIMAL ||10,2 || ||
|-
|WIDTH ||DECIMAL ||10,2 || ||
|-
|HEIGHT ||DECIMAL ||10,2 || ||
|-
|COMMODITY_ID ||STRING ||256 || ||
|-
|CLASS_ID ||STRING ||256 || ||
|-
|UN_NUMBER ||STRING ||50 || ||Y
|-
|HAZARDOUS_QTY ||DECIMAL ||28,4 || ||Y
|-
|HAZARDOUS ||STRING ||1 ||N,Y ||Y
|-
|HAZARDOUS_DESCRIPTION ||STRING ||40 || ||Y
|}

*The mandatory flag for CTMS is only valid if the optional section has been provided in the file.

Note that an item quantity must be provided as 'ORDERED' or 'TO_DELIVER' depending which item is being used (as set by an EDI parameter).

=== Event Header <EVENT_HEADER> ===
<EVENT_HEADER>
<EVENT_PROCESSED>N</EVENT_PROCESSED>
<EVENT_SOURCE_TYPE>SAGE</EVENT_SOURCE_TYPE>
<EVENT_SOURCE_NAME>SAGE</EVENT_SOURCE_NAME>
<EVENT_DATE>2015-05-31T12:52:13</EVENT_DATE>
<EVENT_TYPE>ORD</EVENT_TYPE>
<EVENT_ACTION>C</EVENT_ACTION>
</EVENT_HEADER>

The header section describes the fact that an event has occurred. Each event must generally create a new file and this complex type element must not repeat within the file.

Each of the simple type elements outlined above is mandatorily required.

The <EVENT_PROCESSED> is expected to have a value of 'N'.

The <EVENT_SOURCE_TYPE> must be setup as a recognised source system within CTMS, within the [[System Configuration]] screen, [[System Configuration#Sources|Sources]] tab.

Although a number of <EVENT_TYPE> values can be received it is the 'ORD' event type which represents a transport order to be created or amended in CTMS, the <EVENT_ACTION> value of 'C' (for 'C'reate) will ensure a new order is generated, an event action value of 'A' (for 'A'mend) will update an order, and an event action value of 'D' (for 'D'elete) will delete an order.

Validation will exist to check that the transport order can be created, amended or deleted as directed.

The <EVENT_DATE> simple element must be in the format 'YYYY-MM-DDTHH:MI:SS'

=== Event Detail <EVENT_DETAIL> ===
<EVENT_DETAIL>
<TRIP_HEADER>
<STOPS>
<STOP>
<STOP_HEADER>
<ORDERS>
<ORDER>
<ORDER_HEADER>
<ORDER_DETAILS>
<ORDER_HAZARDOUS_DETAILS>
</ORDER>

The event detail section consists of complex type elements representing the 'Trip' - a CTMS planned transport movement representing a vehicle with one or more transport orders to one or more location.

The trip can have several 'stops' (a geographical location visited) against which one or more 'orders' can be handled for loading or unloading the vehicle at each stop.

Therefore, the <STOPS> and <ORDERS> may contain multiple stops and transport orders that exist on the trip.

=== Trip Header <TRIP_HEADER> ===
<TRIP_HEADER>
<TRIP_IDENTIFIER>O</TRIP_IDENTIFIER>
</TRIP_HEADER>

The 'ORD' event type does not require trip header information, although this complex type is mandatory in the file, it is exempted by denoting the <TRIP_IDENTIFIER> with 'O' to represent that the file contains order data only.

The order data received is denoted as an 'unplanned' order, that is it has not been built into a vehicle movement and routed through one or more load and unload activities. This planning activity is handled within CTMS.

=== Stops <STOPS> ===
<STOPS>
<STOP>
<STOP_HEADER>
<STOP_IDENTIFIER>O</STOP_IDENTIFIER>
</STOP_HEADER>

The ORD event type does not require any trip stop information and although the complex type is mandatory it is exempted by denoting the <STOP_IDENTIFIER> with 'O' to indicate that the file contains order data only.

=== Orders <ORDERS> ===
<ORDER>
<ORDER_HEADER> ... </ORDER_HEADER> [1]
<ORDER_SUB_REFS> ... </ORDER_SUB_REFS> [0..1]
<ORDER_DETAILS> ... </ORDER_DETAILS> [0..1]
<ORDER_HAZARDOUS_DETAILS> ... </ORDER_HAZARDOUS_DETAILS> [0..1]
</ORDER>
The orders complex type contains the core information that constitutes a transport order request in CTMS, that is, a unique instruction to collect and deliver a number of goods items of a particular type between two points at requested times.

The <ORDER> element can repeat to represent multiple orders within the same file; however it is recommended best practice when using the ORD event type to receive one per individual XML file.

The structure is made up of complex elements representing the higher level order header information which is none repeating and the lower level order details complex type element which may repeat.

The <ORDER_HEADER> complex type is mandatory and must occur once and only once.

The <ORDER_HEADER> complex type is optional.

The <ORDER_DETAILS> complex type is mandatory for transport orders and can repeat but must occur at least once.

The <ORDER_HAZARDOUS_DETAILS> complex type is optional.

=== Order Header <ORDER_HEADER> ===
<ORDER_HEADER>

<ORDER_HEADER>
<ORDER_TRANSACTION_DATE> ... </ORDER_TRANSACTION_DATE> [1]
<ORDER_TYPE> ... </ORDER_TYPE> [0..1]
<WMS_WAREHOUSE> ... </WMS_WAREHOUSE> [0..1]
<WMS_OWNER> ... </WMS_OWNER> [0..1]
<SO_REF> ... </SO_REF> [0..1]
<TMS_REF> ... </TMS_REF> [0..1]
<PO_REF> ... </PO_REF> [0..1]
<BOOK_REF> ... </BOOK_REF> [0..1]
<BOOK_DATE> ... </BOOK_DATE> [0..1]
<SPECIAL_INSTR> ... </SPECIAL_INSTR> [0..1]
<ORDER_COMMENTS> ... </ORDER_COMMENTS> [0..1]
<ORDER_HEADER_TMS> ... </ORDER_HEADER_TMS> [0..1]
<ORDER_HEADER_ADDRESSES> ... </ORDER_HEADER_ADDRESSES> [0..1]
<CUSTOMER_ID> ... </CUSTOMER_ID> [0..1]
<CUSTOMER_NAME> ... </CUSTOMER_NAME> [0..1]
<ORDER_STATUS> ... </ORDER_STATUS> [0..1]
</ORDER_HEADER>

The order header structure represents the high level simple single attributes of the order which exist in isolation, such as references and who the transport order is being conducted on behalf of.

The <ORDER_TRANSACTION_DATE> simple element is mandatory and must be in the format 'YYYY-MM-DDTHH:MI:SS'

The <ORDER_TYPE> simple type element is mandatory and must be received with a value of 'O'.

The <WMS_OWNER> simple type element indicates the customer and must match the customer IDs setup on CTMS, this is a mandatory field.

The <SPECIAL_INSTR> simple type element captures any additional information that is presented to the driver on his hand held delivery device at that may be relevant to the transport planning.

=== Order Header TMS <ORDER_HEADER_TMS> ===
<ORDER_HEADER_TMS>
<EARLY_AVAIL_DATE>2015-05-24T17:00:00</EARLY_AVAIL_DATE>
<TMS_GROUP_NAME>OBS</TMS_GROUP_NAME>
<TMS_DELIVERY_TYPE>Standard</TMS_DELIVERY_TYPE>
<TMS_COST_CENTRE>OBS</TMS_COST_CENTRE>
<TRANSPORT_MODE>ROAD</TRANSPORT_MODE>

The order header TMS section contains additional information relevant to the order and is simply an extension to the main order header complex type.

Most of the simple type elements in the section are optional.

The <TMS_DELIVERY_TYPE> is used to receive the service level: this value must be populated and is validated against CTMS master data

The <EARLY_AVAIL_DATE> simple type element is mandatory and will be used to calculate forward the collection/loading date/time window and also the approximate delivery date/time window. It must be in the format 'YYYY-MM-DDTHH:MI:SS'.

The other 3 dates for the order may be omitted because they can be calculated from the early available date that is provided and the delivery type (i.e. service level) of the order, however, the configuration in CTMS (TBC) will determine the required level of data.

All elements in this section are validated against CTMS master data and therefore must match CTMS configuration.

The accepted values in the <TRANSPORT_MODE> simple type element are:
* AIR
* ROAD

This will be validated and the order file rejected if the value does not match.

The <TOTAL_PRICE> element is optional and defines the TOTAL price of the order. If provided and populated, the value must be a valid decimal value, or an error will be raised. If not provided or null, the value will be set to 0.

=== Order Header Addresses <ORDER_HEADER_ADDRESSES> ===
<ORDER_HEADER_ADDRESSES>
<ORDER_HEADER_ADDRESS>
<ORDER_HEADER_ADDRESS>
<OH_ADDRESS_CONTACTS>

An <ORDER_HEADER_ADDRESSES> complex type element must always exist once per order.

It must include two instances of the <ORDER_HEADER_ADDRESS> complex type element, one for the loading/pickup location (i.e. 'DEP' address type) and one for the unloading/drop-off location (i.e. 'DEL' address type).

=== Order Header Addresses <ORDER_HEADER_ADDRESS> ===
<ORDER_HEADER_ADDRESS>
<ADDRESS_TYPE>DEP</ADDRESS_TYPE>
<ADDRESS_ID>OBS</ADDRESS_ID>
<ADDRESS_NAME>OBS Logistics</ADDRESS_NAME>
<ADDRESS_LINE1>Southern Gateway</ADDRESS_LINE1>
<ADDRESS_LINE2>Speke Boulevard</ADDRESS_LINE2>
<ADDRESS_LINE3></ADDRESS_LINE3>
<ADDRESS_TOWN>Liverpool</ADDRESS_TOWN>
<ADDRESS_COUNTY>Merseyside</ADDRESS_COUNTY>
<ADDRESS_COUNTRY_CODE>GB</ADDRESS_COUNTRY_CODE>
<ADDRESS_POSTCODE>L24 9HZ</ADDRESS_POSTCODE>
<ADDRESS_CUST_GROUP>OBS</ADDRESS_CUST_GROUP>
<OH_ADDRESS_CONTACTS>

The <ORDER_HEADER_ADDRESS> complex type element includes the address attributes for either the initial point of collection/loading or the final point of delivery/unloading.

The <ADDRESS_TYPE> simple type element is mandatory and must be either:
* 'DEP' - Indicates that the address represents the initial 'DEP'arture location of the order.
* 'DEL' - Indicates that the address represents the final 'DEL'ivery location of the order.

The <ADDRESS_TOWN> item and <ADDRESS_POSTCODE> elements will not be validated and will be accepted regardless of data content.

The <ADDRESS_ID> item is mandatory and can be sent as a unique account identifier for the sender/recipient or it can be sent with the word 'UNKNOWN' which will allow CTMS to generate this unique address identifier where necessary.

The system will initially cross check the received Address Name and Address Postcode in the order file to see if any locations exist for that address name and postcode (to narrow down the number of records to validate), if so it will identify against all other address attributes (Address lines, town/suburb, county/state, country code) to see if there is an existing EXACT match.

If an existing EXACT address match is found the existing CTMS location code will be used against the received order - as the address detail matches all attributes. If any difference is found a new location is generated with the data received, generating a new location ID in the following format:

* Characters 1 to 8: Characters 1 to 8 from <ADDRESS_NAME>
* Character 9: '-'
* Characters 10 to 12: Sequence number 001 to 999

The location ID generated will be a maximum of 12 characters, for example:

<ADDRESS_ID>UNKNOWN<ADDRESS_ID>
<ADDRESS_NAME>OBS Logistics</ADDRESS_NAME>
<ADDRESS_POSTCODE>L24 9HZ</ADDRESS_POSTCODE>

Would create location code 'OBS Logi-001'.

Also note that new addresses for existing locations can be provided for each order and new locations can be created for the specific address that may be provided.

Once a location is created it will not be updated via the order upload process, any amendments can be carried out manually or via the import of a 'CSV' file.

New locations will only be created for the address details provided.

=== Order Header Address Contact <OH_ADDRESS_CONTACT> ===
<OH_ADDRESS_CONTACT>
<ADDRESS_CONTACT_TYPE>O</ADDRESS_CONTACT_TYPE>
<ADDRESS_CONTACT_FORENAME>Yard Manager</ADDRESS_CONTACT_FORENAME>
<ADDRESS_CONTACT_SURNAME></ADDRESS_CONTACT_SURNAME>
<ADDRESS_CONTACT_NUMBER>0151 123 5678</ADDRESS_CONTACT_NUMBER>
<ADDRESS_EMAIL>yardmanager@obs.com</ADDRESS_EMAIL>

For each address an optional <OH_ADDRESS_CONTACT> complex type element can be received. This element must only occur once for within a <OH_ADDRESS_CONTACT>.

The <ADDRESS_CONTACT_TYPE> simple type element is mandatory where the <OH_ADDRESS_CONTACT> is used and indicates if the contact information is to be permanently associated to the address master data (value 'L') or whether it is only related to that particular address for the instance of that particular order (value 'O'). For this implementation 'O'rder type contacts should always be received.

If there is no contact information for the loading location then this element is not required for the "DEP" address type.

The other simple type elements are optional.

=== Order Sub-references <ORDER_SUB_REFS> ===
<ORDER_DETAILS>
<ORDER_SUB_REFS>
<ORDER_SUB_REF> <ORDER_SUB_REF>
<SUB_REF_IDENTIFIER> ... </SUB_REF_IDENTIFIER> [1]
<SUB_REF_IDENTIFIER> ... </SUB_REFERENCE> [1]
</ORDER_SUB_REF>
</ORDER_SUB_REFS>
<ORDER_DETAIL>
This <ORDER_SUB_REFS> section is optional, and allows you to store additional references for an order.

The section must include at least one instance of the <ORDER_SUB_REF> complex type element.

The <SUB_REF_IDENTIFIER> simple type must match up to a configured order sub-reference type. These are maintained by your system administrator in the CTMS [[Imports]] screen, on the [[Imports#Decodes|Decodes]] tab, type "XML_REFERENCE". Include the CODE here, not the NAME.

The <SUB_REF_IDENTIFIER> simple type is the value you want to store against that reference. The value can be anything at all, but to 512 characters long. These values are not validated.

You can add as many order sub references as you need for the order.

{{Note|
* If system parameter USE_XML_ORDER_SUB_REFS is set to "Y", sub references will be automatically generated from lane comments that begin with ORDER_REFS:", followed by a comma-delimited list of sub reference names and values. Otherwise this section will contain the order sub references for this order.
* A sub reference of TRIP_TYPE may be automatically generated based on EDI parameter INC_TRIP_TYPE being set. In this case, the value may be set to
** COL - if the from location is the load location of the trip stop and the load location type is not RDC
** TRUNK - if the from location is the load location and the order to location is not the unload location
** XDOCK_DEL - if the order to location is equal to the unload location, and there are onward trips.
** DIRECT_DEL - if the order to location is equal to the unload location, and there are no onward trips.
* If the sub-ref name DELIVERY_METHOD is present, the value will be translated for the carrier.
}}Several static sub-references are supported.

The following will automatically store data as order information, for contact purposes:

* SMS_ADDRESS_1
* SMS_ADDRESS_2
* SMS_ADDRESS_3
* SMS_ADDRESS_4
* EMAIL_ADDRESS

Depending on which values you provide here, the order will be stamped with contact preferences:

* E - Email only.
* S - SMS Only
* B - Both

{{Note}}SMS sending from CTMS is supported at additional transaction cost per message.

The reference ORDER_WMS_STATUS may be used to update a source system status against the trip. Values are:

* OPEN STAGED
* IN PROGRESS STAGED
* CLOSED STAGED
* OPEN
* IN PROGRESS
* CLOSED

=== Order Detail <ORDER_DETAIL> ===
<ORDER_DETAIL>
<DETAIL_TYPE>S</DETAIL_TYPE>
<PRODUCT_TYPE_DESC>CANTEEN</PRODUCT_TYPE_DESC>
<DU_TYPE>20x9</DU_TYPE>
<ITEM_IDENTIFIER>ABC004783</ITEM_IDENTIFIER>
<ITEM_DESCRIPTION>CARTON</ITEM_DESCRIPTION>
<ITEM_AKA_CODE>10*20*30</ITEM_AKA_CODE>
<LIFTS>1</LIFTS>
<WEIGHT>5.37</WEIGHT>
<ORDERED>1</ORDERED>
<TO_DELIVER>1</TO_DELIVER>
<LENGTH>10</LENGTH>
<WIDTH>20</WIDTH>
<HEIGHT>30</HEIGHT>
<COMMODITY_ID>DG</COMMODITY_ID>
<CLASS_ID>2.1</CLASS_ID>
</ORDER_DETAIL>

The <ORDER_DETAIL> complex element is mandatory and can repeat but must occur at least once to form a valid CTMS order.

The order details will be used to generate both the individual dispatch box/carton detail (per unique barcode) and also the higher level summary order detail line level.

The <DETAIL_TYPE> simple element is mandatory and must be received as either:
* 'D' - Represents a CTMS order detail line - summary level of the total of unique package types.
* 'S' - Represents a CTMS order detail item - the lowest level entry for each individual carton/box.

Note that the DU types (i.e. for the order lines) and its items, just the DU types (if items are not being recorded) or just the items may be provided.

If just items are provided then the DU types and thus the order lines may be generated automatically for the order based on the types of items that have been provided.

The <PRODUCT_TYPE_DESC> simple element is mandatory and will be validated against CTMS master data to ensure it is a recognised value. An unrecognised or blank value will cause the order upload to fail with applicable validation message recorded.

The <DU_TYPE> simple element is optional and will be validated against CTMS master data to ensure it is a recognised value. An unrecognised will cause the order upload to fail with applicable validation message recorded.

The <ITEM_IDENTIFIER> simple element is mandatory and will not be validated although it must be a maximum of 15 alphanumeric characters.

The <ITEM_DESCRIPTION> and <ITEM_AKA_CODE simple type elements are an optional freetext tags and can be used as required.

One of the <ORDERED> and <TO_DELIVER> simple type elements will be mandatory and must be received with a numeric integer value. This represents the number of items reflected by the <ORDER_DETAIL> segment received

As this is at individual carton/box level then this is expected to always be 1 for this implementation.

The <WEIGHT>, <HEIGHT>, <WIDTH>, <LENGTH> simple type elements are optional.

{{Note|* The weight provided is a TOTAL weight of the item or line, not a UNIT weight.
* The height, width and length will be used by CTMS to calculate the carton/box level volume for each order item as per existing standard processing logic.}}

The <COMMODITY_ID> simple type element is optional and will be validated against CTMS master data to ensure it is a recognised value. An unrecognised value will cause the order upload to fail with applicable validation message recorded.

The <CLASS_ID> simple type element is optional but must be received when a <COMMODITY_ID> element is provided which has a 'Dangerous' flag setting of 'Y' (in CTMS master data setup). The value will be validated against CTMS master data to ensure it is a recognised value. An unrecognised will cause the order upload to fail with applicable validation message recorded.

The <ITEM_PRICE> element is optional and defines the TOTAL price of the item. This applies only to Item detail type lines. If provided and populated, the value must be a valid decimal value, or an error will be raised. If not provided or null, the value will be set to 0.

=== Order Hazardous Details ===
<ORDER_HAZARDOUS_DETAILS>
<ORDER_HAZARDOUS_DETAIL>

The <ORDER_HAZARDOUS_DETAILS> complex type element is optional and can be provided if required.

If this element is used then one or more <ORDER_HAZARDOUS_DETAIL> complex type elements is mandatorily required.

=== Order Hazardous Detail ===
<ORDER_HAZARDOUS_DETAIL>
<UN_NUMBER>1089</UN_NUMBER>
<HAZARDOUS_QTY>1</HAZARDOUS_QTY>
<HAZARDOUS>Y</HAZARDOUS>
<HAZARDOUS_DESCRIPTION>CARBONYL SULFIDE</HAZARDOUS_DESCRIPTION>
</ORDER_HAZARDOUS_DETAIL>

The <ORDER_HAZARDOUS_DETAIL> complex type element and all its simple type elements are mandatory. The elements are not validated against CTMS master data and will be stored as received.

= XML Outbound Order File Structure =
CTMS may provide updates to a customer’s source system, including how the order has been scheduled for delivery, when a vehicle is en-route and delivery details including successful delivery and reasons for a short delivery. The same TripOrder XSD will be used to generate the Trip file.

==EDI Maintenance ==
The XML files from CTMS will be generated and placed into a directory structure and processed as may be specified in the 'EDI Maintenance' screen.

Multiple EDI flows may be active to process XML files at different stages of processing.

There are various EDI parameters that can be set to provide different levels of validation to generate the files.

The trip/order outbound flows can generate standard flows via a webservice push to an endpoint, or can be sent out to the filesystem for FTP - See [[TripOrder Interface XML#Filesystem Server Requirements|Filesystem Server Requirements]] below. This depends on the EDI processes generated.

Further, more bespoke EDI exports can be generated - these still use the same TripOrder XML export structure, but are more focussed on different processes, such as tracking summary messages - these are not covered in this guide.

=== Filesystem Server Requirements ===
CTMS will push files to the OUT sub folder within the customer folder. From this folder CTMS will FTP the file across to the customer system. The customer must provide CTMS with the IP, PORT, Username , Password and Directory name. The customer will provide CTMS with access to the directory.<center>
[[File:TripOrderXML-EDI-FTP.png]]
</center>

=== Webservice API Export ===
Like Filesystem exports, this is controlled via the EDI Maintenance screen. See the section [[TripOrder Interface XML#EDI Trip Order XML Webservices Configuration|EDI Trip Order XML Webservices Configuration]] below for details.

== TripOrder File ==
<OBS_XML>
<EVENT>
<EVENT_HEADER>
<EVENT_DETAIL>

The same XSD file format is used for files from CTMS as per files into CTMS.

These files may contain more data in each section than are required in the inbound order files.

For example, an outbound file may contain data about the trip, its stops, each order on each stop and the DU types and/or items on each order.

Export depends on the events that are being exported, controlled by EDI Parameters on the API EDI process:
* API_ARR
* API_COL
* API_DEL
* API_DEP
* API_ORD
* API_TRP

Additional EDI parameters are also present (described in detail in the following sections):
*INCLUDE_CDATA_TAG - affects variable text data entry from the execution level - should it be wrapped to prevent interface errors?
* SEND_AND_FORGET - affects the basic interface - should the message be sent with no expectation of explicit acknowledgement back from the destination?
*PRINT_STOP_PID
*PRINT_ROUTE_CODE
*INCLUDE_ORDER_STATUS
*SEND_DEL_TYPE_CODE
*EXPORT_SERVICES
*INC_TRIP_TYPE
*INC_TRIP_ACTION
*INC_PACKED_TO_DEL
*INCLUDE_SAP_LINE_NOS
*INCLUDE_REASON_CODES
*INCLUDE_NON_CON_CODES
* INCLUDE_TRACK_REF
*INCLUDE_ITEM_DELIVER
*INCLUDE_REASON_TYPE

Export may also include debrief-level information, depending on the type of event, and where the order is up to.

The Export will be of Trip Type if related to a trip, and Order type (similar to the above) for Order-type events.

Trip type events:
*TRP - any changes to or creation of a trip.
* ARR - Arrival at any stop.
*DEP - departure at any stop.

Order type events:
*ORD - any changes to or creation of an order.
*CAN - if an order is cancelled.
*COL - if an order is collected.
*DEL - if an order is delivered.

In general, trip-type events include everything that an Order-type event would include, but with the following additions:
*TRIP_DETAIL
*STOP_DETAIL
*STOP_SIGNATURE (if LOTS_INC_STOP_SIGNATURE = "Y")
*ORDER_HEADER_TMS

As an indication of what may change, please see the below sections.

===TRIP_DETAIL===
<pre>
<HAULIER> ... </HAULIER> [0..1]
<HAULIER_NAME> ... </HAULIER_NAME> [0..1]
<HAULIER_TYPE> ... </HAULIER_TYPE> [0..1]
<TRACKING> ... </TRACKING> [1]
<TRIP_SCHEDULE> ... </TRIP_SCHEDULE> [0..1]
<DRIVER> ... </DRIVER> [0..1]
<DRIVER_NAME> ... </DRIVER_NAME> [0..1]
<DRIVER_CONTACT> ... </DRIVER_CONTACT> [0..1]
<TRACTOR> ... </TRACTOR> [0..1]
<TRACTOR_LAT> ... </TRACTOR_LAT> [0..1]
<TRACTOR_LON> ... </TRACTOR_LON> [0..1]
<COST_CENTRE> ... </COST_CENTRE> [0..1]
<TRIP_STATUS> ... </TRIP_STATUS> [0..1]
<TRIP_REF> ... </TRIP_REF> [0..1]
<TRIP_TRAILER_ID> ... </TRIP_TRAILER_ID> [0..1]
<TRIP_TRAILER_TYPE> ... </TRIP_TRAILER_TYPE> [0..1]
<TRIP_DISTANCE> ... </TRIP_DISTANCE> [0..1]
<FUEL_DRAWN> ... </FUEL_DRAWN> [0..1]
<OWNING_DEPOT> ... </OWNING_DEPOT> [0..1]
<CONTAINER_NO> ... </CONTAINER_NO> [0..1]
<SEAL_NO> ... </SEAL_NO> [0..1]
<EFX_NUMBER> ... </EFX_NUMBER> [0..1]
<START_ODOMETER> ... </START_ODOMETER> [0..1]
<END_ODOMETER> ... </END_ODOMETER> [0..1]
<ACTUAL_TRIP_DISTANCE> ... </ACTUAL_TRIP_DISTANCE> [0..1]
<ROUTE_CODE> ... </ROUTE_CODE> [0..1]
<COST_PER_TONNE> ... </COST_PER_TONNE> [0..1]
<COST> ... </COST> [0..1]
<COST_REASON> ... </COST_REASON> [0..1]
<AUDIT_ID> ... </AUDIT_ID> [0..1]
<TRIP_SUB_REFS> ... </TRIP_SUB_REFS> [0..1]
</pre>

{{Note|
* Carrier will be modified if the carrier type is 3PL. This will be exported in the HAULIER tag.
* TRACKING tag will only be populated from trips that are tracked through Microlise.
* The information sent to MICROLISE is extremely limited in this section.
* ROUTE_CODE will only be populated if the EDI parameter PRINT_ROUTE_CODE is populated or the TRIP_ORDER_XSD_VERS system parameter is "2.5". If the system parameter INCL_ROUTE_CODE is set, then this will be instead populated with the Baxter route code.
* AUDIT_ID is a unique ID appended to the message for external tracking purposes.
}}

===TRIP_SUB_REF===
<pre>
<TRIP_SUB_REF>
<SUB_REF_IDENTIFIER> ... </SUB_REF_IDENTIFIER> [1]
<SUB_REFERENCE> ... </SUB_REFERENCE> [1]
</TRIP_SUB_REF>
</pre>

{{Note|
* If system parameter INC_TRIP_ACTION is "Y", a trip sub reference will be generated based on the action of the event.
}}

===STOP_DETAIL===
<pre>
<STOP_REF> ... </STOP_REF> [0..1]
<STOP_TYPE> ... </STOP_TYPE> [0..1]
<STOP_LOCATION_TYPE> ... </STOP_LOCATION_TYPE> [0..1]
<STOP_LOCATION_ID> ... </STOP_LOCATION_ID> [0..1]
<STOP_LOCATION_NAME> ... </STOP_LOCATION_NAME> [0..1]
<STOP_ADDR_LINE1> ... </STOP_ADDR_LINE1> [0..1]
<STOP_ADDR_LINE2> ... </STOP_ADDR_LINE2> [0..1]
<STOP_ADDR_LINE3> ... </STOP_ADDR_LINE3> [0..1]
<STOP_TOWN> ... </STOP_TOWN> [0..1]
<STOP_COUNTY> ... </STOP_COUNTY> [0..1]
<STOP_COUNTRY_CODE> ... </STOP_COUNTRY_CODE> [0..1]
<STOP_POSTCODE> ... </STOP_POSTCODE> [0..1]
<STOP_CONTACT_NAME> ... </STOP_CONTACT_NAME> [0..1]
<STOP_CONTACT_PHONE> ... </STOP_CONTACT_PHONE> [0..1]
<STOP_BREAK_DURATION> ... </STOP_BREAK_DURATION> [0..1]
<STOP_PREV_DIST> ... </STOP_PREV_DIST> [0..1]
<STOP_ACTUAL_PREV_DIST> ... </STOP_ACTUAL_PREV_DIST> [0..1]
<STOP_TRAILER_ID> ... </STOP_TRAILER_ID> [0..1]
<STOP_LAT> ... </STOP_LAT> [0..1]
<STOP_LON> ... </STOP_LON> [0..1]
<STOP_PLANNED_ARRIVAL_DATE> ... </STOP_PLANNED_ARRIVAL_DATE> [0..1]
<STOP_PLANNED_DEPARTURE_DATE> ... </STOP_PLANNED_DEPARTURE_DATE> [0..1]
<STOP_ETA_DATE> ... </STOP_ETA_DATE> [0..1]
<STOP_ETA_AT_DATE> ... </STOP_ETA_AT_DATE> [0..1]
<STOP_EARLIEST_BOOKED_DATE> ... </STOP_EARLIEST_BOOKED_DATE> [0..1]
<STOP_ACTUAL_ARRIVAL_DATE> ... </STOP_ACTUAL_ARRIVAL_DATE> [0..1]
<STOP_ACTUAL_DEPARTURE_DATE> ... </STOP_ACTUAL_DEPARTURE_DATE> [0..1]
<STOP_ODO_READING> ... </STOP_ODO_READING> [0..1]
<STOP_FUEL> ... </STOP_FUEL> [0..1]
<STOP_EMAIL> ... </STOP_EMAIL> [0..1]
<STOP_BARCODE> ... </STOP_BARCODE> [0..1]
<STOP_PID> ... </STOP_PID> [0..1]
<STOP_COUNTRY_NAME> ... </STOP_COUNTRY_NAME> [0..1]
<WAREHOUSE_LOAD> ... </WAREHOUSE_LOAD> [0..1]
</pre>

{{Note|
* Dates are in XML DateTime format.
* ETA and ACTUAL Dates will be populated from execution-based systems.
* STOP_PID will only be populated for LOTS and CIM flows in one format, or if EDI parameter PRINT_STOP_PID is set to "Y" in a different format. This second format should not be enabled for LOTS interfaces.
}}

=== STOP_SIGNATURE===
This section will only be generated if system parameter LOTS_INC_STOP_SIGNATURE is set to "Y".

<pre>
<STOP_SIGNATURE>
<SIGNATURE> ... </SIGNATURE> [0..1]
<SIGNED_BY> ... </SIGNED_BY> [0..1]
</STOP_SIGNATURE>
</pre>

===ORDER_HEADER===
<pre>
<ORDER_TRANSACTION_DATE> ... </ORDER_TRANSACTION_DATE> [1]
<ORDER_TYPE> ... </ORDER_TYPE> [0..1]
<WMS_WAREHOUSE> ... </WMS_WAREHOUSE> [0..1]
<WMS_OWNER> ... </WMS_OWNER> [0..1]
<SO_REF> ... </SO_REF> [0..1]
<ORIG_SO_REF> ... </ORIG_SO_REF> [0..1]
<TMS_REF> ... </TMS_REF> [0..1]
<PO_REF> ... </PO_REF> [0..1]
<BOOK_REF> ... </BOOK_REF> [0..1]
<BOOK_DATE> ... </BOOK_DATE> [0..1]
<SPECIAL_INSTR> ... </SPECIAL_INSTR> [0..1]
<ORDER_COMMENTS> ... </ORDER_COMMENTS> [0..1]
<ORDER_HEADER_TMS> ... </ORDER_HEADER_TMS> [0..1]
<ORDER_HEADER_ADDRESSES> ... </ORDER_HEADER_ADDRESSES> [0..1]
<ORDER_HEADER_CONFIRM> ... </ORDER_HEADER_CONFIRM> [0..1]
<CUSTOMER_ID> ... </CUSTOMER_ID> [0..1]
<CUSTOMER_NAME> ... </CUSTOMER_NAME> [0..1]
<ORDER_STATUS> ... </ORDER_STATUS> [0..1]
<DESTINATION_ORDER> ... </DESTINATION_ORDER> [0..1]
<DESTINATION_DRIVER> ... </DESTINATION_DRIVER> [0..1]
<DESTINATION_VEHICLE> ... </DESTINATION_VEHICLE> [0..1]
<ORDER_SERVICES> ... </ORDER_SERVICES> [0..1]
</pre>

{{Note|
* SO_REF will be populated with the External reference of the order. This may be modified to remove any rebooking suffix if system parameter ORD_RBO_PREFIX is set to "Y"
* ORDER_STATUS will only be included if the EDI parameter INCLUDE_ORDER_STATUS is set to "Y". Further, if system parameter INCLUDE_FAILED_ORDERS is set to "Y" and the order status is FAILED, this will be changed to CANCELLED instead.
* DESTINATION_ORDER, DESTINATION_DRIVER and DESTINATION_VEHICLE will only be present if order sub references exist of those names.
}}

===ORDER_HEADER_TMS ===
<pre>
<ORDER_HEADER_TMS>
<SHIPMENT_ID> ... </SHIPMENT_ID> [0..1]
<TMS_ORDER_SCHEDULE> ... </TMS_ORDER_SCHEDULE> [0..1]
<TMS_HAULAGE_ACTIVITY> ... </TMS_HAULAGE_ACTIVITY> [0..1]
<TMS_HAULAGE_TYPE> ... </TMS_HAULAGE_TYPE> [0..1]
<EARLY_AVAIL_DATE> ... </EARLY_AVAIL_DATE> [1]
<LATE_AVAIL_DATE> ... </LATE_AVAIL_DATE> [1]
<EARLY_DEL_DATE> ... </EARLY_DEL_DATE> [1]
<LATE_DEL_DATE> ... </LATE_DEL_DATE> [1]
<TMS_GROUP_NAME> ... </TMS_GROUP_NAME> [0..1]
<TMS_DELIVERY_TYPE> ... </TMS_DELIVERY_TYPE> [0..1]
<TMS_COST_CENTRE> ... </TMS_COST_CENTRE> [0..1]
<SD_TEMP_COMBO> ... </SD_TEMP_COMBO> [0..1]
<SD_POD_BY> ... </SD_POD_BY> [0..1]
<KEY_CODE> ... </KEY_CODE> [0..1]
<REVENUE> ... </REVENUE> [0..1]
<COST> ... </COST> [0..1]
<COST_PER_TONNE> ... </COST_PER_TONNE> [0..1]
<HAULIER> ... </HAULIER> [0..1]
<TRAILER_TYPE> ... </TRAILER_TYPE> [0..1]
<ROUTE_CODE> ... </ROUTE_CODE> [0..1]
<EFX_NUMBER> ... </EFX_NUMBER> [0..1]
<TRANSPORT_MODE> ... </TRANSPORT_MODE> [0..1]
<TRANSPORT_STATUS> ... </TRANSPORT_STATUS> [0..1]
<RPE_QTY> ... </RPE_QTY> [0..1]
<ACTUAL_RPE_QTY> ... </ACTUAL_RPE_QTY> [0..1]
<WEIGHT> ... </WEIGHT> [0..1]
<ACTUAL_WEIGHT> ... </ACTUAL_WEIGHT> [0..1]
<VOLUME> ... </VOLUME> [0..1]
<ACTUAL_VOLUME> ... </ACTUAL_VOLUME> [0..1]
<FOOTPRINT> ... </FOOTPRINT> [0..1]
<ACTUAL_FOOTPRINT> ... </ACTUAL_FOOTPRINT> [0..1]
<TOTAL_PRICE> ... </TOTAL_PRICE> [0..1]
</ORDER_HEADER_TMS>
</pre>

{{Note|
* TMS_DELIVERY_TYPE is set to the full delivery type if the EDI parameter SEND_DEL_TYPE_CODE is set to "Y". Otherwise the short code associated to the delivery type is sent.
}}

===ORDER_SERVICES===
This section is only populated if the EDI parameter EXPORT_SERVICES is set to "Y", or if this is set to "C" and the event is "CAN" or "DEL".

<pre>
<ORDER_SERVICE>
<SERVICE_ID> ... </SERVICE_ID> [1]
<SERVICE_NAME> ... </SERVICE_NAME> [1]
<SERVICE_QTY> ... </SERVICE_QTY> [1]
<SERVICE_VALUE> ... </SERVICE_VALUE> [1]
</ORDER_SERVICE>
</pre>

=== ORDER_DETAIL===
The details sent in this section are subject to configuration:
* Order Lines are sent if LOTS_SEND_LINE_ITEMS = "Y", or the value is "N" and there are no order items.
* Order Items are sent if LOTS_SEND_LINE_ITEMS = "Y", or the value is "N" and there are order items.

<pre>
<ORDER_DETAIL>
<DETAIL_TYPE> ... </DETAIL_TYPE> [1]
<DETAIL_ID> ... </DETAIL_ID> [0..1]
<PRODUCT_TYPE> ... </PRODUCT_TYPE> [0..1]
<PRODUCT_TYPE_DESC> ... </PRODUCT_TYPE_DESC> [0..1]
<DU_TYPE> ... </DU_TYPE> [0..1]
<ITEM_IDENTIFIER> ... </ITEM_IDENTIFIER> [1]
<ITEM_DESCRIPTION> ... </ITEM_DESCRIPTION> [0..1]
<PALLET_ID> ... </PALLET_ID> [0..1]
<ITEM_AKA_CODE> ... </ITEM_AKA_CODE> [0..1]
<ITEM_FACTOR> ... </ITEM_FACTOR> [0..1]
<LIFTS> ... </LIFTS> [0..1]
<STACK> ... </STACK> [0..1]
<RPE_QTY> ... </RPE_QTY> [0..1]
<ACTUAL_RPE_QTY> ... </ACTUAL_RPE_QTY> [0..1]
<WEIGHT> ... </WEIGHT> [0..1]
<ACTUAL_WEIGHT> ... </ACTUAL_WEIGHT> [0..1]
<VOLUME> ... </VOLUME> [0..1]
<ACTUAL_VOLUME> ... </ACTUAL_VOLUME> [0..1]
<FOOTPRINT> ... </FOOTPRINT> [0..1]
<ACTUAL_FOOTPRINT> ... </ACTUAL_FOOTPRINT> [0..1]
<ORDERED> ... </ORDERED> [0..1]
<PACKED> ... </PACKED> [0..1]
<TO_DELIVER> ... </TO_DELIVER> [0..1]
<DELIVERED> ... </DELIVERED> [0..1]
<SAP_LINE_NO> ... </SAP_LINE_NO> [0..1]
<SHIPMENT_DETAIL> ... </SHIPMENT_DETAIL> [0..1]
<REASON_CODES> ... </REASON_CODES> [0..1]
<DIM_WEIGHT> ... </DIM_WEIGHT> [0..1]
<ACTUAL_DIM_WEIGHT> ... </ACTUAL_DIM_WEIGHT> [0..1]
<TRACKING_REFS> ... </TRACKING_REFS> [0..1]
<DU_DESCRIPTION> ... </DU_DESCRIPTION> [0..1]
<DU_CATEGORY> ... </DU_CATEGORY> [0..1]
<PLANNED_CASES> ... </PLANNED_CASES> [0..1]
<ACTUAL_CASES> ... </ACTUAL_CASES> [0..1]
<SCAN_TYPE> ... </SCAN_TYPE> [0..1]
<LENGTH> ... </LENGTH> [0..1]
<WIDTH> ... </WIDTH> [0..1]
<HEIGHT> ... </HEIGHT> [0..1]
<COMMODITY_ID> ... </COMMODITY_ID> [0..1]
<CLASS_ID> ... </CLASS_ID> [0..1]
<WMS_LOCATION> ... </WMS_LOCATION> [0..1]
<LONG_DESCRIPTION> ... </LONG_DESCRIPTION> [0..1]
<ORDER_DETAIL_TYRE> ... </ORDER_DETAIL_TYRE> [0..1]
<ITEM_PRICE> ... </ITEM_PRICE> [0..1]
</ORDER_DETAIL>
</pre>

{{Note|
* DETAIL_TYPE will be "D" if generated from Order Lines, and "S" if generated from Order Items.
* For D lines
** ITEM_IDENTIFIER will be the DU Type
** ITEM_DESCRIPTION will the DU Type description for "D" lines
** RPE_QTY will include Despatched and Packed REP if the EDI Parameter INC_PACKED_TO_DEL is set to "Y", other wise this will just be the Actual RPE and RPE qty.
** PACKED will be populated if the order has been packed.
** TO_DELIVER will be populated if the order has been collected.
** DELIVERED will be present and populated if the order has been delivered to its final destination.
** SAP_LINE_NO will only be present and populated if the EDI Parameter INCLUDE_SAP_LINE_NOS is "Y" and there is a SAP line number against the order line.
** REASON_CODES will be included if there are non-conformity reason codes against the order line for the API interface.
** REASON_CODES will be included for other flows if EDI Parameters INCLUDE_REASON_CODES and INCLUDE_NON_CON_CODES are set. {{Warning}} These should NOT be set against the API process.
** TRACKING_REFS will be included if the EDI Parameter INCLUDE_TRACK_REF is set to "Y".
* For S lines
** ITEM_IDENTIFIER will be the Item Identifier, unless the customer has specified that an alternative item identifier is used and one is provided against the item. If system parameter USE_PALLET_ID_XML is set to "Y", then the Pallet ID of the item record will be used instead.
** PALLET_ID will only be populated if system parameter SEND_PALLET_ID_XML is set to "Y".
** ORDERED will only be present and populated if the value is not null.
** TO_DELIVER will only be present and populated if the value is null i.e. the order item has been collected.
** DELIVERED will only be present and populated if the value is not null i.e. the order item has been delivered and EDI parameter INCLUDE_ITEM_DELIVER is set to "Y", or this is sent through the API.
** SAP_LINE_NO will only be present and populated if the EDI Parameter INCLUDE_SAP_LINE_NOS is "Y" and there is a SAP line number against the order line.
** REASON_CODES will be included if there are non-conformity reason codes against the order line for the API interface.
** REASON_CODES will be included for other flows if EDI Parameters INCLUDE_REASON_CODES and INCLUDE_NON_CON_CODES are set. {{Warning}} These should NOT be set against the API process.
}}

===TRACKING_REFS===
TRACKING_REFS will be included if the EDI Parameter INCLUDE_TRACK_REF is set to "Y".

<pre>
<TRACKING_REF>
<UNIT_TRACKING_REF> ... </UNIT_TRACKING_REF> [1]
<UNIT_TRACKING_NO> ... </UNIT_TRACKING_NO> [1]
</TRACKING_REF>
</pre>

===ORDER_DETAIL_TYRE===
For TYRE-based systems

<pre>
<ORDER_DETAIL_TYRE>
<WPX_PRODUCT_ID> ... </WPX_PRODUCT_ID> [1]
<POSITION> ... </POSITION> [1]
<LOCATION> ... </LOCATION> [1]
<PRICE> ... </PRICE> [1]
<CUSTOMER_VEHICLE> ... </CUSTOMER_VEHICLE> [1]
<AUTHORITY_CODE> ... </AUTHORITY_CODE> [1]
<WORK_TYPE> ... </WORK_TYPE> [1]
<PRESSURE> ... </PRESSURE> [1]
<TREAD_DEPTH> ... </TREAD_DEPTH> [1]
<CASING> ... </CASING> [1]
<CASING_DESTINATION> ... </CASING_DESTINATION> [1]
<NEW_REMOULD> ... </NEW_REMOULD> [1]
<REGROOVED> ... </REGROOVED> [1]
<TYRE_SERIAL_NO> ... </TYRE_SERIAL_NO> [1]
<REMOVAL_REASON> ... </REMOVAL_REASON> [1]
<WORK_TYPES> ... </WORK_TYPES> [1]
<SERVICES_SUPPLIED> ... </SERVICES_SUPPLIED> [1]
<BARCODE> ... </BARCODE> [1]
<TORQUE> ... </TORQUE> [1]
</ORDER_DETAIL_TYRE>
</pre>

=== ORDER_REASON_CODE ===
<pre>
<ORDER_REASON_CODE>
<RC_TYPE> ... </RC_TYPE> [1]
<RC_CODE> ... </RC_CODE> [1]
<RC_DESCRIPTION> ... </RC_DESCRIPTION> [1]
<RC_COMMENT> ... </RC_COMMENT> [0..1]
</ORDER_REASON_CODE>
</pre>

{{Note|
* For reason codes included for Order Item non-conformities, RC_TYPE will only be included if EDI parameter INCLUDE_REASON_TYPE is set to "Y", and will always then be "NONC"
}}

===ORDER_HEADER_TYRE===
For TYRE-based systems

<pre>
<ORDER_HEADER_TYRE>
<CUSTOMER_VEHICLE> ... </CUSTOMER_VEHICLE> [0..1]
<AUTHORITY_CODE> ... </AUTHORITY_CODE> [0..1]
</ORDER_HEADER_TYRE>
</pre>

=== ORDER_VEHICLE===
For TYRE-based systems

<pre>
<ORDER_VEHICLE> - for TYRE-based systems only
<VEHICLE_ID> ... </VEHICLE_ID> [1]
<MAKE> ... </MAKE> [1]
<MODEL> ... </MODEL> [1]
<ODO> ... </ODO> [1]
<DESCRIPTION> ... </DESCRIPTION> [1]
<LAST_INSPECTION_DATE> ... </LAST_INSPECTION_DATE> [1]
<VEHICLE_CONFIG_ID> ... </VEHICLE_CONFIG_ID> [1]
<VEHICLE_CONFIG> ... </VEHICLE_CONFIG> [1]
<EPOD_SERVICE_ID> ... </EPOD_SERVICE_ID> [0..1]
</ORDER_VEHICLE>
</pre>

== EDI Trip Order XML Webservices Configuration ==
{{:EDI Trip Order XML Webservices Configuration}}

==System Parameters affecting XML Production==
System parameters affecting content in TripOrder XML

{| class="wikitable apt-searchable" border="1" id="systemparams"
|- bgcolor="silver"
!Parameter!!Description!!Level
|-
|CUST_UPDATE_ORDER_LINES||Update Orders|| CUSTOMER
|-
|EPOD_SIGNATURE_STORAGE||Store signature received from C-ePOD ||COST_CENTRE
|-
|IMP_OVERRIDE_SOURCE_REF||Set source system and control additional functionality in ORD_LINE_ITM CSV order import||SYSTEM
|-
| INCL_ROUTE_CODE||Include Baxter Route code and delivery method||COST_CENTRE
|-
|INCLUDE_FAILED_ORDERS||Include Failed Orders as CANCELLED for API||COST_CENTRE
|-
|LOTS_ADD_DEBRIEF||LOTS Additional Debrief Details||COST_CENTRE
|-
|LOTS_DEL_CUST_SIGNATORY ||Controls if DEL messages for LOTS require an actual signatory - Y to hold messages.||COST_CENTRE
|-
|LOTS_INC_ORDER_HEADER_CONFIRM ||Includes the ORDER_HEADER_CONFIRM section in the DEL file for LOTS. ||SYSTEM - only LOTS, DEL event
|-
|LOTS_INC_STOP_SIGNATURE|| Indicates if the STOP_SIGNATURE section will be displayed in the DEL outbound files to LOTS.||SYSTEM - only for LOTSC
|-
|LOTS_INC_STOP_TYPE_DESC||Include STOP-TYPE_DESC tag in XML||SYSTEM - ONLY FOR LOTS process
|-
|LOTS_SEND_WHEN_VEHICLE_SCANNED||List of LOTS message types that will be held until a vehicle scan is received for the order.||COST_CENTRE
|-
|MIC_ADD_STOP_BARCODE|| Include new tag STOP_BARCODE on Microlise outbound xml||SYSTEM - only for process MIC
|-
| OMS_FOOTPRINT_FOR_VOLUME ||Will the footprint of the order line be include in the VOLUME item for the outbound XML file for the despatch units instead of the cubic volume (Y/N)?||COST_CENTRE
|-
|ORD_NO_DEL_FOR_FAILS||Controls if DEL messages are generated for FAILED orders - Y to prevent, C to send as CAN|| COST_CENTRE
|-
|ORD_RBO_PREFIX||Is the rebook prefix stripped for LOTS? ||SYSTEM
|-
|ORD_TEMPERATURE_COMBO||Use Temperature Combo to determine if the customer reference should be highlighted.||COST_CENTRE
|-
|SEND_LINE_ITEM_TO_LOTS ||Send Line Item To LOTS. Y - send both Order Line (D) and Item (S) records. N - Checks for Items and, if there are any, sends Item (S) records, else Order Line (D) records.||SYSTEM
|-
|SEND_PALLET_ID_XML|| Send Pallet ID tag in xml||COST_CENTRE
|-
| STOP_PID||LOTS - is STOP_PID included in the extract ||SYSTEM - only for LOTS/CIM
|-
|TIME_ZONE_ACTIVE||Time Zone Active||SYSTEM
|-
| TMS_OTBOUND_SO_REF||Controls the outbound format for SO_REF in LOTSC||CUSTOMER
|-
|TRIP_ORDER_XSD_VERS||Version of TRIP XSD being used.||SYSTEM
|-
|TRM_DESP_FOR_DEL||Maintain the Actual Despatched Quantity for a Delivery Trip in Trip Debrief (Y/N).||COST_CENTRE
|-
|UNI_LOCATION||Location for Unilever||SYSTEM
|-
|USE_ORDER_ADDRESSEE||Will the addressee name be used for the order? (Y/N)||COST_CENTRE
|-
| USE_PALLET_ID_XML||Use Pallet ID instead of item identifier in XML Outbound files||COST_CENTRE
|-
|USE_XML_ORDER_SUB_REFS||Print order sub refs on outbound XML||COST_CENTRE
|}

= APPENDIX: XSD SECTIONS =
{| class="wikitable"
!Parent
!Cardinality
!Child
!Description of Child
|-
|OBS_XML
|1
|EVENT
|Event message containing header, detail, and optional tracking.
|-
|EVENT
|1
|EVENT_HEADER
|Message event header containing metadata about the event.
|-
|EVENT
|0..*
|EVENT_DETAIL
|Business payload containing trip, stops, and tasks.
|-
|EVENT
|0..1
|EVENT_TRACKING
|Tracking information for the event.
|-
|EVENT_TRACKING
|1..*
|MILESTONE
|Individual tracking milestone with status, dates, and locations.
|-
|EVENT_DETAIL
|1
|TRIP_HEADER
|Message control and trip identifier.
|-
|EVENT_DETAIL
|0..1
|TRIP_DETAIL
|Principal operational details of the trip.
|-
|EVENT_DETAIL
|0..1
|STOPS
|Detail of stops on the trip.
|-
|EVENT_DETAIL
|0..1
|TRIP_TASKS
|Tasks for the given trip.
|-
|TRIP_TASKS
|1..*
|TRIP_TASK
|Individual task performed during the trip.
|-
|STOPS
|1..*
|STOP
|Details of a single stop on the trip.
|-
|STOP
|1
|STOP_HEADER
|Message control and stop identifier.
|-
|STOP
|0..1
|STOP_DETAIL
|Operational and location details of the stop.
|-
|STOP
|0..1
|STOP_SIGNATURE
|Signature captured after stop completion.
|-
|STOP
|0..1
|ORDERS
|Orders associated with the stop.
|-
|STOP
|0..1
|STOP_REASON_CODES
|Stop-level discrepancy or exception reasons.
|-
|STOP
|0..1
|STOP_TASKS
|Tasks performed at stop level.
|-
|STOP_DETAIL
|0..1
|STOP_SUB_REFS
|Stop-level sub-references.
|-
|STOP_SUB_REFS
|1..*
|STOP_SUB_REF
|A single stop sub-reference.
|-
|STOP_REASON_CODES
|1..*
|STOP_REASON_CODE
|Individual stop reason code.
|-
|STOP_TASKS
|1..*
|STOP_TASK
|Individual task performed at the stop.
|-
|ORDERS
|1..*
|ORDER
|Order for collection, delivery, or direct movement.
|-
|ORDER
|1
|ORDER_HEADER
|Header information describing an order.
|-
|ORDER
|0..1
|ORDER_SUB_REFS
|Repeating sub-order references.
|-
|ORDER
|0..1
|ORDER_SIGNATURE
|Order-level proof-of-delivery signature.
|-
|ORDER
|0..1
|ORDER_DETAILS
|Line-level detail information for the order.
|-
|ORDER
|0..1
|ORDER_HEADER_TYRE
|Tyre service–specific order information.
|-
|ORDER
|0..1
|ORDER_TASKS
|Tasks associated with the order.
|-
|ORDER
|0..1
|ORDER_HAZARDOUS_DETAILS
|Hazardous goods details for the order.
|-
|ORDER
|0..1
|ORDER_REASON_CODES
|Order-level discrepancy or exception reasons.
|-
|ORDER
|0..1
|ORDER_SERVICES
|Services supplied for the order.
|-
|ORDER
|0..1
|ORDER_VEHICLES
|Vehicles associated with tyre-service orders.
|-
|ORDER_HEADER
|1
|ORDER_TRANSACTION_DATE
|Transaction date and time of the order.
|-
|ORDER_HEADER
|0..1
|ORDER_HEADER_TMS
|Transport Management System details of the order.
|-
|ORDER_HEADER
|0..1
|ORDER_HEADER_ADDRESSES
|Addresses associated with the order.
|-
|ORDER_HEADER
|0..1
|ORDER_HEADER_CONFIRM
|LOTS confirmed delivery information.
|-
|ORDER_HEADER_ADDRESSES
|1..*
|ORDER_HEADER_ADDRESS
|Address information for collection, delivery, or invoice.
|-
|ORDER_HEADER_ADDRESS
|0..1
|OH_ADDRESS_DATE_TIMES
|Planned and actual date/time windows for the address.
|-
|ORDER_HEADER_ADDRESS
|0..1
|OH_ADDRESS_CONTACTS
|Contacts associated with the address.
|-
|ORDER_HEADER_ADDRESS
|0..1
|OH_ADDRESS_TRAILERS
|Trailer constraints for the address.
|-
|ORDER_HEADER_ADDRESS
|0..1
|OH_ADDRESS_REFERENCES
|Reference identifiers associated with the address.
|-
|OH_ADDRESS_CONTACTS
|1..*
|OH_ADDRESS_CONTACT
|Individual address contact details.
|-
|OH_ADDRESS_REFERENCES
|1..*
|OH_ADDRESS_REFERENCE
|Single address reference entry.
|-
|OH_ADDRESS_TRAILERS
|0..*
|OH_ADDRESS_TRAILER
|Trailer type constraint for an address.
|-
|ORDER_SUB_REFS
|1..*
|ORDER_SUB_REF
|Individual sub-order reference.
|-
|ORDER_DETAILS
|1..*
|ORDER_DETAIL
|Individual order line, despatch unit, or stock item.
|-
|ORDER_DETAIL
|0..1
|TRACKING_REFS
|Tracking references for despatch units.
|-
|TRACKING_REFS
|1..*
|TRACKING_REF
|Individual tracking reference and number.
|-
|ORDER_HAZARDOUS_DETAILS
|1..*
|ORDER_HAZARDOUS_DETAIL
|Hazardous material details for an order line.
|-
|ORDER_REASON_CODES
|1..*
|ORDER_REASON_CODE
|Individual order reason code.
|-
|ORDER_TASKS
|1..*
|ORDER_TASK
|Individual task performed at order level.
|-
|ORDER_VEHICLES
|0..*
|ORDER_VEHICLE
|Vehicle details for tyre-service orders.
|-
|TRIP_DETAIL
|0..1
|TRIP_SUB_REFS
|Trip-level sub-references.
|-
|TRIP_SUB_REFS
|1..*
|TRIP_SUB_REF
|Individual trip sub-reference.
|}

= APPENDIX: Core Import XSD Elements =
{| class="wikitable"
!Item
!Type
!Size
!Restriction
!CTMS Mandatory*
!Maximum Length
|-
|EVENT_PROCESSED
|STRING
|1
|E,N,Y
|Y
|1
|-
|EVENT_SOURCE_TYPE
|STRING
|4
|New Value
|Y
|4
|-
|EVENT_SOURCE_NAME
|STRING
|10
|
|Y
|10
|-
|EVENT_DATE
|DATETIME
|
|
|Y
|
|-
|EVENT_TYPE
|STRING
|3
|
|Y
|3
|-
|EVENT_ACTION
|STRING
|1
|A,C,D
|Y
|1
|-
|TRIP_IDENTIFIER
|STRING
|1
|O,T
|Y
|1
|-
|TRIP_TRANSACTION_DATE
|DATETIME
|
|
|
|
|-
|TRIP_ID
|STRING
|12
|
|
|12
|-
|STOP_IDENTIFIER
|STRING
|1
|O,S
|Y
|1
|-
|STOP_ID
|STRING
|51
|—
|N
|51
|-
|STOP_SEQ
|INTEGER
|—
|< 999999
|N
|—
|-
|ORDER_TRANSACTION_DATE
|DATETIME
|—
|xs:dateTime
|Y
|—
|-
|ORDER_TYPE
|STRING
|10
|—
|N
|10
|-
|WMS_WAREHOUSE
|STRING
|3
|—
|N
|3
|-
|WMS_OWNER
|STRING
|12
|—
|N
|12
|-
|SO_REF
|STRING
|20
|—
|N
|'''16'''
|-
|TMS_REF
|STRING
|20
|—
|N
|20
|-
|PO_REF
|STRING
|20
|—
|N
|20
|-
|BOOK_REF
|STRING
|20
|—
|N
|20
|-
|BOOK_DATE
|DATETIME
|—
|xs:dateTime
|N
|—
|-
|SPECIAL_INSTR
|STRING
|2000
|—
|N
|2000
|-
|ORDER_COMMENTS
|STRING
|2000
|—
|N
|2000
|-
|EARLY_AVAIL_DATE
|DATETIME
|—
|xs:dateTime
|Y
|—
|-
|LATE_AVAIL_DATE
|DATETIME
|—
|xs:dateTime
|Y
|—
|-
|EARLY_DEL_DATE
|DATETIME
|—
|xs:dateTime
|Y
|—
|-
|LATE_DEL_DATE
|DATETIME
|—
|xs:dateTime
|Y
|—
|-
|TMS_GROUP_NAME
|STRING
|12
|—
|N
|12
|-
|TMS_DELIVERY_TYPE
|STRING
|35
|—
|N
|35
|-
|TMS_COST_CENTRE
|STRING
|12
|—
|N
|12
|-
|HAULIER
|STRING
|12
|—
|N
|12
|-
|TRANSPORT_MODE
|STRING
|30
|—
|N
|30
|-
|ADDRESS_TYPE
|STRING
|3
|DEP,DEL,INV
|Y
|3
|-
|ADDRESS_ID
|STRING
|25
|—
|Y
|25
|-
|ADDRESS_NAME
|STRING
|50
|—
|N
|50
|-
|ADDRESS_LINE1
|STRING
|50
|—
|N
|50
|-
|ADDRESS_LINE2
|STRING
|50
|—
|N
|50
|-
|ADDRESS_LINE3
|STRING
|50
|—
|N
|50
|-
|ADDRESS_TOWN
|STRING
|50
|—
|N
|50
|-
|ADDRESS_COUNTY
|STRING
|50
|—
|N
|50
|-
|ADDRESS_COUNTRY_CODE
|STRING
|3
|—
|N
|3
|-
|ADDRESS_POSTCODE
|STRING
|9
|—
|N
|9
|-
|CUSTOMER_ID
|STRING
|12
|—
|N
|12
|-
|CUSTOMER_NAME
|STRING
|50
|—
|N
|50
|-
|SUB_REF_IDENTIFIER
|STRING
|50
|—
|Y
|50
|-
|SUB_REFERENCE
|STRING
|1000
|—
|Y
|1000
|-
|DETAIL_TYPE
|STRING
|1
|S,D,C
|Y
|1
|-
|DETAIL_ID
|STRING
|30
|—
|N
|30
|-
|PRODUCT_TYPE
|STRING
|12
|—
|N
|12
|-
|PRODUCT_TYPE_DESC
|STRING
|50
|—
|N
|50
|-
|DU_TYPE
|STRING
|12
|—
|N
|12
|-
|ITEM_IDENTIFIER
|STRING
|20
|—
|Y
|'''15'''
|-
|ITEM_DESCRIPTION
|STRING
|122
|—
|N
|122
|-
|PALLET_ID
|STRING
|100
|—
|N
|100
|-
|ITEM_AKA_CODE
|STRING
|30
|—
|N
|30
|-
|ITEM_FACTOR
|STRING
|12
|—
|N
|12
|-
|LIFTS
|DECIMAL
|8,2
|—
|N
|—
|-
|RPE_QTY
|DECIMAL
|10,2
|—
|N
|—
|-
|WEIGHT
|DECIMAL
|10,2
|—
|N
|—
|-
|VOLUME
|DECIMAL
|15,5
|—
|N
|—
|-
|ORDERED
|DECIMAL
|28,4
|—
|N
|—
|-
|TO_DELIVER
|DECIMAL
|28,4
|—
|N
|—
|-
|DELIVERED
|DECIMAL
|28,4
|—
|N
|—
|-
|PLANNED_CASES
|INTEGER
|—
|< 99999999
|N
|—
|-
|LENGTH
|DECIMAL
|10,2
|—
|N
|—
|-
|WIDTH
|DECIMAL
|10,2
|—
|N
|—
|-
|HEIGHT
|DECIMAL
|10,2
|—
|N
|—
|-
|COMMODITY_ID
|STRING
|256
|—
|N
|256
|-
|CLASS_ID
|STRING
|256
|—
|N
|256
|-
|UN_NUMBER
|STRING
|50
|—
|N
|50
|-
|HAZARDOUS
|STRING
|1
|Y,N
|N
|1
|-
|HAZARDOUS_QTY
|DECIMAL
|28,4
|—
|N
|—
|-
|HAZARDOUS_DESCRIPTION
|STRING
|40
|—
|N
|40
|}
<nowiki>*</nowiki>The mandatory flag for CTMS is only valid if the optional section has been provided in the file.

Note that an item quantity must be provided as ‘ORDERED’ or ‘TO_DELIVER’ depending which item is being used (as set by an EDI parameter).

Interface - CTMS XML EDI Order Flow Guide

2026-03-06T09:42:58Z

Anw: Added Webservice API EDI Processes

{{Doc_Title
| System = Calidus TMS
| Title = Interface - CTMS XML EDI Order Flow Guide
| Reference = INTERFACE
| Version = 3.04
| Date = 6th March 2026
| Sysver = 12.48
| Client = Aptean
}}

=Overview=
== Introduction ==
{{:TripOrder Interface XML}}

[[Category:Documents]][[Category:C-TMS Training Guides]]
[[Category:Interface Guides]]

TripOrder Interface XML

2026-03-06T09:25:23Z

Anw: Added Webservice API EDI processes

EDI Maintenance

2026-03-06T09:22:08Z

Anw: Added Webservice API EDI processes

The EDI interface screen is accessed from the Interface menu.

== General Functionality ==
The EDI interface screen allows users to control the following activities on the system
* Outbound Flows
* Inbound Flows
* Database Jobs
* Database Processes
* Report and Extract generation
* ORS Report generation

Controllable settings include setting the time, frequency, type of process, outbound file names and folders, outbound emails, data parameters and ftp settings.

The following buttons are available:
* '''New''' Button - Clears any data currently in any of the fields to allow the user to enter a new process flow.
* '''Delete''' Button - Deletes the Process flow.
* '''Params''' Button - A number of Parameters / Triggers Can be entered. These control various rules about the business that are out of scope of the Standard xml schemer. These are normally set by by your implementation team in the first instance.
* '''Output''' Button - This screen is for Outbound flows only and contains Destination IP Address and security usernames and passwords.

To create a new EDI process, select the '''New''' button on the screen.

<center>[[Image:edi_maint_1.png|800px]]</center>

The following Information may be entered when creating a new EDI process
{| class="wikitable" border="1"
|- bgcolor="silver"
!Field !! Description
|-
|''Process Name''|| This should indicate the nature of the job so it may be identified in the screen. Required.
|-
|''Filename Format''|| This indicates how any files created or required by the process are names, for outbound files, the system will add the system date and time to ensure a unique filename is always generated. Required.
|-
|''Customer''|| Enter the Customer required using the Drop Down List. Optional.
|-
|''Cost Centre Code''|| The cost centre code may be used when the process is checking parameter values and may be matched to orders or trips to identify if the process should be running. Required.
|-
|''Location''
|The location may be used to specify selection of data from a particular location code. A lookup is provided.
|-
|''Direction''|| The direction is defined as outbound or inbound. This will indicate if the process in bringing data into C-TMS or sending data out of C-TMS. Required.
|-
|''Flow Type''|| This indicates the type of process, there are several different options discussed later. Required.
|-
|''Frequency Type''
|Frequency type indicates how often the process is run, are regular interval or specific time. Required.
|-
|''Process Time''
|Only available if selecting ''Frequency Type'' of ''Specific Time''. The time at which the process is to run.
|-
|''(Day Selection)''
|Only available if selecting ''Frequency Type'' of ''Specific Time''. Check ''All Days'', or check the days on which you want the process to run.
|-
|''Interval Length''
|Only available if selecting ''Frequency Type'' of ''Regular Interval''. Interval length indicates the regular interval. Enter the number , and then the unit (''Seconds, Minutes, Hours, Days, Monthly''). Required.
|-
|''Interval Length''|| Interval length indicates the regular interval. Required.
|-
|''Send DEL Message''|| If this box is checked then this can create an ARR message when the actual arrive times are fully entered
|-
|''Send ARR Message''|| If this box is checked then this can create a DEL message when the order to deliver quantities are fully entered
|-
|''Delivery Folder''|| When the file has been created this is the directory that the file will sit in until it has been picked up
|-
|''Archive Folder'' || When the file has been picked up by the relevant source successfully the file gets moved to this directory
|-
|''Failures folder'' || The directory of any files that failed to upload
|-
|''Acknowledgment Folder'' || The directory for an acknowledgment message to sent to
|-
|''Send ACK?'' || The box is checked if the Acknowledgment of an inbound flow is requested. The Acknowledgment will then been sent to folder to be picked up by the relevant source
|}

The screen also displays the following information about the flow:
{| class="wikitable" border="1"
|- bgcolor="silver"
!Field !! Description
|-
|''Process Time''|| This option is only visible if the Frequency Type has been set to ‘Specific Time’. The user can simply enter the time that the flow should be run. Also the checkboxes can be flagged for the required days of the week
|-
|''Status''|| This is not an editable field and tells the user if the Flow is running or has been stopped
|-
|''Last Run Date''|| This tells the user the Date and time the process last ran
|-
|''Next Run Date''|| This is the date and time the flow is due to run next
|-
|'''Start''' / '''Stop''' Buttons || Stops and starts the process flow. Please note that only the user that started the process can stop it
|}

The flow types available to select are listed below:
* EXPORT - Run an Export process.
* FORD_EDI_IN - bespoke EDI process
* MILE_XML
* MILK_ROUND - generation of milk rounds
* ORD_COLL_XML
* ORD_OR3
* ORD_XML
* ORD_XML_OUT
* ORS - run an ORS report
* PLUTO_ACTUALS
* POD_XML
* PROCESS - trigger a process
* PULSE_ORDERS - bespoke EDI process
* REPORT - run a report
* SCN
* SESSION_XML - import sessions
* STS_XML
* TRACK_IMPORT
* TRIP_ORD_XML
* TRIP_XML
* UNISON_FLAT - Legacy WMS flat-file import process

For running specific extracts and processes, PROCESS should be used.

For automatically running reports, use the REPORTS type.

For automatically running extracts, use the REPORTS type.

For automatically running exports created through ORS, use the ORS type.

If a frequency type of Specific time is selected, the following information is displayed on screen. Users are required to specify a process time and the days of the week the job will run.

<center>[[Image:edi_maint_3.png|800px]]</center>

=== Parameters ===
In addition to the EDI header, users may be required to specify additional outputs and job parameters. There are several job parameters which will control how jobs are run and the data they process. If a parameter is required for a job, users will be informed by the developer to set up the parameter and the value they should set it to.

<center>[[Image:edi_maint_4.png|800px]]</center>

=== Output ===
Output applied to a process may be different, depending upon the type of process. If a PROCESS type is selected, users are able to define FTP information. If a REPORT type is selected, users may define email addresses for report output.

Users will always be instructed how to set up the jobs but may use the screen to control when the job runs.

== Examples ==

=== Creating an Inbound Order EDI Flow ===
* Enter the Process Name e.g. INB_ORDERS
* Enter the Filename Format e.g. INB_ORD
* Enter the Customer from the list available
* Enter the Cost Centre from the list available
* Enter "Inbound" from the Direction field
* Click on the button next to the Flow Type field to populate a list of values and select ORD_XML
* Enter the required Frequency type and interval length. For example, a set Regular Interval could be chosen and an interval length of 15 minutes.
* Enter a Delivery folder directory path
* Enter an Archive Folder directory path
* Enter a Failures Folder directory path

When everything is set-up click the '''Start''' Button to run the process.

=== Creating an Outbound EDI Flow ===
* Enter the Process Name e.g. OUT_TRIPS
* Enter the Filename Format e.g. OUT_TRP
* Enter the Customer from the list available
* Enter the Cost Centre from the list available
* Enter "Outbound" from the Direction field
* Click on the button next to the Flow Type field to populate a list of values and select TRIP_XML
* Enter the required Frequency type and interval length. In the example screenshot below, Regular Interval has been chosen and an interval length of 15 minutes
* Enter a Delivery folder directory path
* Enter an Archive Folder directory path
* Enter a Failures Folder directory Path

You may also click the Output button - this shows a screen that allows you to enter the access details to allow C-TMS permission to FTP a file to another system.
* Destination IP - The IP Address of recipient Server
* FTP Port - The Port Number of recipient server
* FTP Username - Login ID for recipient server
* FTP Password - Password for above login ID
* FTP Directory - Delivery Directory for recipient server

{{Note}} An Outbound file can be collected from the Aptean Server or delivered by FTP.

=== Creating Scheduled Reports/Extracts ===
{{:EDI - Report/Extract Scheduling}}

=== Creating Processes ===
In general, creating specific EDI processes follows the same procedure as the above. The MIS/BI Reporting extract process is an example of a process.

There are many processes, mostly for a very specific reason or bespoke processes. A list of processes follows. Note that this list if evolving and may not be complete:
{| class="wikitable apt-searchable" border="1"
!'''Process'''
!'''Notes'''
|-
|ACC.GENERATE_WAREHOUSE_CHARGES
|
|-
|ASSET.REMOVE_DELETED_ASSETS
|
|-
|DP_3PL_SCHED.DEPOT_SWEEP
|The Depot Sweep process, used in conjunction with the fixed drop scheduling engine
|-
|DP_BMW_EDI_IN.PROCESS_FILES
|
|-
|DP_BMW_EDI_OUT.SEND_CLAIMS
|
|-
|DP_BNL_EDI_IN.P_PROCESS_FILES
|
|-
|DP_BNL_EDI_OUT.P_PROCESS_PLAN
|
|-
|DP_BWSC.PROCESS_FILES
|
|-
|DP_CSV4.TOKAIRO_CUST_EXPORT
|
|-
|DP_CSV6.TIMI_EXTRACT
|A bespoke tracking extract.
|-
|DP_CSV_DUN.STORE_PVA
|
|-
|DP_CSV_POD.P_PROCESS_CSV_POD
|
|-
|DP_DRIVER_SCHEDULING.ADD_SCANNED_ORDERS_TO_TRIP
|
|-
|DP_EPOD_WEBSERVICE.epod_locked_job
|A helper process for any locked jobs, used in conjunction with Calidus ePOD .
|-
|DP_EPOD_WEB_SERVICE.get_vehicle_info
|A helper process, used in conjunction with Calidus ePOD .
|-
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|The Trip/Order XML Outbound process. This should be named "API_EVENTS"
|-
|DP_FINANCE.D365_EXPORT
|
|-
|DP_FINANCE.D365_EXTRACT
|
|-
|DP_FIXED_IMPORT.P_PROCESS_FILES
|
|-
|DP_IMP.P_PROCESS_CIPD
|
|-
|DP_INT_XML_CARPOD.PROCESS_CARPOD_IN
|A process for importing Carrier POD files.
|-
|DP_LFE_POD.PROCESS_FILES
|
|-
|DP_LOGINEXT.PROCESS_OUTBOUND
|A process for exporting trips and orders to 3rd party carriers using the LogiNext system.
|-
|DP_LOGIX_NHSBT.OUTBOUND_PROCESS
|
|-
|DP_MIS.PR_CREATE_ALL_EXTRACTS
|An MIS/BI extract process
|-
|DP_MIS.PR_CREATE_ALL_EXTRACTS_DAILY
|An MIS/BI extract process
|-
|DP_MIS.PR_CREATE_ALL_EXTRACTS_DATES
|An MIS/BI extract process
|-
|DP_NOKIA_LOC_PLAT.FIND_SIMILAR_SUBURBS
|A help process for Nokia Maps extracts
|-
|DP_PAR_API.READ_PARAGON_IN
|A Paragon API process
|-
|DP_PAR_API_STP.P_UNSCHEDULE
|A Paragon API process
|-
|DP_PAR_API_STP.get_paragon
|A Paragon API process
|-
|DP_PAR_API_STP.get_paragon_route
|A Paragon API process
|-
|DP_PAR_API_STP.process_paragon
|A Paragon API process
|-
|DP_REPORTS.DAY_BEFORE_MSG
|A Reports process
|-
|DP_REPORTS.PROCESS_CLICK_OUTBOUND
|A Reports process
|-
|DP_REPORTS.P_PROCESS_ORD_CONF
|A Reports process
|-
|DP_REPORTS.P_PROCESS_PRE_DEL
|A Reports process
|-
|DP_REPORTS.P_PROCESS_URGENT
|A Reports process
|-
|DP_REPORTS.P_RUN_DAILY_STORE_ASN_REPORT
|A Reports process
|-
|DP_REPORTS.P_RUN_STORE_REPORT
|A Reports process
|-
|DP_REPORTS.SEND_CALLBACK_EMAIL
|A Reports process
|-
|DP_REPORTS.SEND_DEL_EMAIL
|A Reports process
|-
|DP_REPORTS.SEND_NON_CONFORM_EMAIL
|A Reports process
|-
|DP_REPORTS.p_run_manifest_report
|A Reports process
|-
|DP_RICO.RECEIVE_REPORT_STATUS
|
|-
|DP_SCHEDULING_NHSBT.p_nhsbt_schedule
|A bespoke scheduling process, used with the NHS scheduling engine.
|-
|DP_SHIPMENT.CLOSE_SHIPMENTS
|
|-
|DP_SHIPMENT.RUN_CONSOLIDATION
|
|-
|DP_TESLA_EDI_IN.IMPORT_ORDERS
|A bespoke import process
|-
|DP_TOMTOM.GET_GEOFENCE
|Part of the WEBFLEET interface
|-
|DP_TOMTOM.GET_MESSAGES
|Part of the WEBFLEET interface
|-
|DP_TOMTOM.SEND_ORDERS
|Part of the WEBFLEET interface
|-
|DP_TOMTOM.resend_stop(2029828,'A','911GT2')
|Part of the WEBFLEET interface - a helper/support process.
|-
|DP_TOY_EDI_IN.P_PROCESS_FILES
|A bespoke import process
|-
|FIXED.Gen_Fixed_Schedule
|Part of the Fixed Schedule process
|-
|GEO.PROCESS_NEW_LOCATIONS
|
|-
|HKP.Delete_interface_records('HUK')
|
|-
|INT_XML_MIC.PROCESS_XML_OUTBOUND_MIC
|The Microlise scanning interface
|-
|INT_XML_OUT2.PROCESS_XML_DESP_CONF
|The Microlise scanning interface
|-
|INT_XML_OUT2.PROCESS_XML_MANIFEST
|The Microlise scanning interface
|-
|INV.GENERATE_ALL_INVOICES
|Invoice generation
|-
|INV.PROCESS_CARGOWISE
|Bespoke Invoice Generation
|-
|ORS.UPDATE_ORDER_STATS
|
|-
|ORS.UPDATE_ORDER_STATS_all
|
|-
|TRIP.BUF_DEL_INVALID
|Bespoke process
|-
|TRM.P_AUTO_COMPLETE
|
|-
|TRM.fn_load_trunks
|
|-
|int_msg.process_msg_header_int_file
|
|-
|int_msg.process_pod_int_file
|
|-
|int_xml_in.process_lift_update
|
|-
|int_xml_in.process_on_hold
|
|-
|process_xml_outbound_LOTS_ORDC
|
|}
Each process can be scheduled through this EDI screen.

In most cases, they also use parameters to determine the functionality of the process itself.

A list of applicable parameters is shown here: [[EDI Process Parameters]].

Further to this, Report Values may need to be set for each process, to determine which data is being affected by the process..

A list of applicable report values is shown here: [[EDI Process Report Values]].

=== EDI Trip Order XML Webservices Configuration ===
{{:EDI Trip Order XML Webservices Configuration}}

EDI Trip Order XML Webservices Configuration

2026-03-06T09:20:29Z

Anw: Initial Creation

There are inbound and outbound processes that may be used – both must be created through the EDI Maintenance screen.

=== Inbound - API ===
<center>
[[File:EDI-Inbound API.png]]
</center>
{| class="wikitable"
!'''Field'''
!'''Description'''
!'''Value'''
|-
|''Process Name''
|This should indicate the nature of the job so it may be identified in the screen. Required.
|API
|-
|''Filename Format''
|This indicates how any files created or required by the process are names, for outbound files, the system will add the system date and time to ensure a unique filename is always generated. Required.
|''*.*''
|-
|''Customer''
|Enter the Customer required using the Drop Down List. Optional.
|N/A
|-
|''Cost Centre Code''
|The cost centre code may be used when the process is checking parameter values and may be matched to orders or trips to identify if the process should be running. Required.
|N/A
|-
|''Direction''
|The direction is defined as outbound or inbound. This will indicate if the process in bringing data into C-TMS or sending data out of C-TMS. Required.
|Inbound
|-
|''Flow Type''
|This indicates the type of process, there are several different options discussed later. Required.
|''ORD_XML''
|-
|''Frequency Type''
|Frequency type indicates how often the process is run, are regular interval or specific time. Required.
|''Regular Interval''
|-
|''Process Time''
|Only available if selecting ''Frequency Type'' of ''Specific Time''. The time at which the process is to run.
|N/A
|-
|''(Day Selection)''
|Only available if selecting ''Frequency Type'' of ''Specific Time''. Check ''All Days'', or check the days on which you want the process to run.
|N/A
|-
|''Interval Length''
|Only available if selecting ''Frequency Type'' of ''Regular Interval''. Interval length indicates the regular interval. Enter the number , and then the unit (''Seconds, Minutes, Hours, Days, Monthly''). Required.
|1 Days
|-
|''Send DEL Message''
|If this box is checked then this can create an ARR message when the actual arrive times are fully entered
|Unchecked
|-
|''Send ARR Message''
|If this box is checked then this can create a DEL message when the order to deliver quantities are fully entered
|Unchecked
|-
|''Delivery Folder''
|When the file has been created this is the directory that the file will sit in until it has been picked up
|N/A
|-
|''Archive Folder''
|When the file has been picked up by the relevant source successfully the file gets moved to this directory
|N/A
|-
|''Failures folder''
|The directory of any files that failed to upload
|N/A
|-
|''Acknowledgment Folder''
|The directory for an acknowledgment message to sent to
|N/A
|-
|''Send ACK?''
|The box is checked if the Acknowledgment of an inbound flow is requested. The Acknowledgment will then been sent to folder to be picked up by the relevant source
|Unchecked
|}

Parameters must then be entered for the process through the '''Params''' button:
{| class="wikitable"
!Parameter Name
!Description
!Values
|-
|ALLOW_INVALID_ORDER
|
|
|-
|AMEND_SCHEDULED
|
|
|-
|API_CARRIER_PACKED
|
|
|-
|AUDIT_STATUS
|
|
|-
|AUDIT_WS
|
|
|-
|AUTO_GENERATE_LINES
|
|
|-
|CREATE_UNKNOWN_CUST
|
|
|-
|CREATE_UNKNOWN_LOCS
|
|
|-
|CREATE_UNKNOWN_ORDER
|
|
|-
|CUST_CURRENCY
|
|
|-
|CUST_EPOD_ENABLED
|
|
|-
|CUST_GROUP_CUSTOMER
|
|
|-
|CUST_LOTS_ID
|
|
|-
|CUST_LOTS_SEND_ORD
|
|
|-
|CUST_REV_CHARGE_TYPE
|
|
|-
|CUST_TYPE
|
|
|-
|DEFAULT_COLLECTION
|
|
|-
|DEFAULT_COST_CENTRE
|
|
|-
|DELETE_LINES
|
|
|-
|DFLT_CUST_CURRENCY
|
|
|-
|LOCATION_EXT_REF
|
|
|-
|LOC_DEPOT
|
|
|-
|LOC_FLEXIPOD
|
|
|-
|LOC_LOADING_RATE
|
|
|-
|LOC_UNLOADING_RATE
|
|
|-
|MAIN_ADDRESS_TYPE
|
|
|-
|MATCH_FULL_LOC
|
|
|-
|MOD_ORD_ACTION_VALUE
|
|
|-
|NO_UPDATE_DEPOT_ADDR
|
|
|-
|ORDER_VEHICLE
|
|
|-
|ORD_ADD_REFS
|
|
|-
|ORD_INVOICED
|
|
|-
|PARAGON_API
|
|
|-
|ROUTE_DELIVERY
|
|
|-
|RUN_NUMBER_VALID
|
|
|-
|UNSCHED_NEW_DATA
|
|
|-
|UPDATE_CANCELLED
|
|
|-
|UPDATE_EXISTING_LOCS
|
|
|-
|UPDATE_PARAGON_ID
|
|
|-
|USE_RUN_DEPOT
|
|
|-
|USE_VARIANT_ADDRESS
|
|
|}

=== Outbound – API_EVENTS ===
<center>[[File:EDI-Outbound-API EVENTS.png]]</center>
{| class="wikitable"
!'''Field'''
!'''Description'''
!'''Value'''
|-
|''Process Name''
|This should indicate the nature of the job so it may be identified in the screen. Required.
|API_EVENTS
|-
|''Filename Format''
|This indicates how any files created or required by the process are names, for outbound files, the system will add the system date and time to ensure a unique filename is always generated. Required.
|''*.XML''
|-
|''Customer''
|Enter the Customer required using the Drop Down List. Optional.
|N/A
|-
|''Cost Centre Code''
|The cost centre code may be used when the process is checking parameter values and may be matched to orders or trips to identify if the process should be running. Required.
|N/A
|-
|''Direction''
|The direction is defined as outbound or inbound. This will indicate if the process in bringing data into C-TMS or sending data out of C-TMS. Required.
|Outbound
|-
|''Flow Type''
|This indicates the type of process, there are several different options discussed later. Required.
|''PROCESS''
|-
|''Frequency Type''
|Frequency type indicates how often the process is run, are regular interval or specific time. Required.
|Regular Interval
|-
|''Process Time''
|Only available if selecting ''Frequency Type'' of ''Specific Time''. The time at which the process is to run.
|N/A
|-
|''(Day Selection)''
|Only available if selecting ''Frequency Type'' of ''Specific Time''. Check ''All Days'', or check the days on which you want the process to run.
|N/A
|-
|''Interval Length''
|Only available if selecting ''Frequency Type'' of ''Regular Interval''. Interval length indicates the regular interval. Enter the number , and then the unit (''Seconds, Minutes, Hours, Days, Monthly''). Required.
|1 Minutes
|-
|''Send DEL Message''
|If this box is checked then this can create an ARR message when the actual arrive times are fully entered
|Unchecked
|-
|''Send ARR Message''
|If this box is checked then this can create a DEL message when the order to deliver quantities are fully entered
|Unchecked
|-
|''Delivery Folder''
|When the file has been created this is the directory that the file will sit in until it has been picked up
|N/A
|-
|''Archive Folder''
|When the file has been picked up by the relevant source successfully the file gets moved to this directory
|N/A
|-
|''Failures folder''
|The directory of any files that failed to upload
|N/A
|-
|''Acknowledgment Folder''
|The directory for an acknowledgment message to sent to
|N/A
|-
|''Send ACK?''
|The box is checked if the Acknowledgment of an inbound flow is requested. The Acknowledgment will then been sent to folder to be picked up by the relevant source
|Unchecked
|}

Report Values must then be entered for the process through the '''Params''' button:

{| class="wikitable"
!'''Title'''
!'''Name'''
!'''Value'''
|-
|Package
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|-
|Process
|p_process_name
|API_EVENTS
|}

Parameters must also be entered:
{| class="wikitable"
!'''Parameter Name'''
!'''Description'''
!'''Values'''
|-
|API_ARR
|
|
|-
|API_CAN
|
|
|-
|API_COL
|
|
|-
|API_DEL
|
|
|-
|API_DEP
|
|
|-
|API_INC_CANCELLED
|
|
|-
|API_ORD
|
|
|-
|API_TRP
|
|
|-
|API_USE_WS_ELUCID
|
|
|-
|AUDIT_METHOD
|
|
|-
|AUDIT_STATUS
|
|
|-
|DEL_ALL_ACT_QTY
|
|
|-
|EXPORT_SERVICES
|
|
|-
|EXPORT_TYRE
|
|
|-
|INCLUDE_CDATA_TAG
|
|
|-
|INCLUDE_ORDER_STATUS
|
|
|-
|INC_ORD_ITEM_EVENTS
|
|
|-
|PRINT_ROUTE_CODE
|
|
|-
|SEND_AND_FORGET
|
|
|}

File:EDI-Outbound-API EVENTS.png

2026-03-06T09:18:33Z

Anw:

Outbound API - API_EVENTS

File:EDI-Inbound API.png

2026-03-06T09:17:41Z

Anw:

Inbound API

EDI Process Parameters

2026-03-06T09:10:16Z

Anw: Added API

This page shows all parameters that can be created against each EDI process type.

{{Note}} This list is evolving constantly is is provided for general reference - please consult your Aptean implementation team for more details if required.

{{Note}} Where the flow type is PROCESS, the parameters apply ONLY to the defined process name shown.

{| class="wikitable apt-searchable" border="1"
!Flow Type
!Process Name
!Parameter Name
!Direction
|-
|CSV_IMPORT
|
|flow_name
|I
|-
|EXPORT
|
|EXTERNAL_SYSTEM
|O
|-
|EXPORT
|
|TIMI_EXTRACT
|O
|-
|EXPORT
|
|test20
|O
|-
|EXPORT
|
|test23
|O
|-
|EXPORT
|
|test24
|O
|-
|MIC_RESOURCES
|
|DRIVER_FORMAT
|I
|-
|MILE_XML
|
|ACTIONED_BY
|O
|-
|MILE_XML
|
|EVENT_ACTION
|O
|-
|MILE_XML
|
|EXTERNAL_SYSTEM
|O
|-
|MILE_XML
|
|EXTERNAL_SYSTEM
|
|-
|MILE_XML
|
|FROM_LOC_TYPE
|O
|-
|MILE_XML
|
|INCLUDE_ITEM_DELIVER
|O
|-
|MILE_XML
|
|INCLUDE_REASON_CODES
|O
|-
|MILE_XML
|
|INCLUDE_SAP_LINE_NOS
|O
|-
|MILE_XML
|
|MILESTONE_COMMENT
|O
|-
|MILE_XML
|
|MILESTONE_STATUS
|O
|-
|MILE_XML
|
|ORDER_LOC
|O
|-
|MILE_XML
|
|PREV_STATUS
|O
|-
|MILE_XML
|
|TO_LOC_TYPE
|O
|-
|ORD_COLL_XML
|
|INCLUDE_CARTON_NO
|O
|-
|ORD_COLL_XML
|
|INCLUDE_ITEM_DELIVER
|O
|-
|ORD_COLL_XML
|
|INCLUDE_REASON_CODES
|O
|-
|ORD_COLL_XML
|
|INCLUDE_SIGNATURE
|O
|-
|ORD_COLL_XML
|
|INCLUDE_TRACK_REF
|O
|-
|ORD_COLL_XML
|
|ORDER_SOURCE_SYSTEM
|O
|-
|ORD_XML
|
|4000
|I
|-
|ORD_XML
|
|ADD_CONTACTS
|I
|-
|ORD_XML
|
|ADD_HOLIDAY_ADDR
|I
|-
|ORD_XML
|
|ALLOW_DEPOT_PRINTER
|I
|-
|ORD_XML
|
|ALLOW_INCREMENT_PACK
|I
|-
|ORD_XML
|API
|ALLOW_INVALID_ORDER
|I
|-
|ORD_XML
|
|ALLOW_REBOOK
|I
|-
|ORD_XML
|API
|AMEND_SCHEDULED
|I
|-
|ORD_XML
|
|API_CARRIER_PACKED
|I
|-
|ORD_XML
|
|AUDIT_METHOD
|I
|-
|ORD_XML
|
|AUDIT_SCAN
|I
|-
|ORD_XML
|API
|AUDIT_STATUS
|I
|-
|ORD_XML
|API
|AUDIT_WS
|I
|-
|ORD_XML
|
|AUTOPLAN_METHOD
|I
|-
|ORD_XML
|API
|AUTO_GENERATE_LINES
|I
|-
|ORD_XML
|
|CALC_FROM_SCHED_RULE
|I
|-
|ORD_XML
|
|CALC_ORD_DU_QTY
|I
|-
|ORD_XML
|
|CHILD_LOCATIONS
|I
|-
|ORD_XML
|
|COLLECTION
|I
|-
|ORD_XML
|
|COMBINE_ORDER_ITEMS
|I
|-
|ORD_XML
|
|CON_ADD_DEL_TYPE
|I
|-
|ORD_XML
|
|CREATE_FREE_ADDRESS
|I
|-
|ORD_XML
|API
|CREATE_UNKNOWN_CUST
|I
|-
|ORD_XML
|
|CREATE_UNKNOWN_LOC
|I
|-
|ORD_XML
|API
|CREATE_UNKNOWN_LOCS
|I
|-
|ORD_XML
|API
|CREATE_UNKNOWN_ORDER
|I
|-
|ORD_XML
|
|CREATE_UNKNOWN_PRD
|I
|-
|ORD_XML
|
|CREATE_UNKNWON_LOCS
|I
|-
|ORD_XML
|API
|CUST_CURRENCY
|I
|-
|ORD_XML
|API
|CUST_EPOD_ENABLED
|I
|-
|ORD_XML
|API
|CUST_GROUP_CUSTOMER
|I
|-
|ORD_XML
|API
|CUST_LOTS_ID
|I
|-
|ORD_XML
|API
|CUST_LOTS_SEND_ORD
|I
|-
|ORD_XML
|API
|CUST_REV_CHARGE_TYPE
|I
|-
|ORD_XML
|API
|CUST_TYPE
|I
|-
|ORD_XML
|
|DECODE_ADDRESS_CHARS
|I
|-
|ORD_XML
|
|DEFAULT_ADD_CUST_GRP
|I
|-
|ORD_XML
|API
|DEFAULT_COLLECTION
|I
|-
|ORD_XML
|API
|DEFAULT_COST_CENTRE
|I
|-
|ORD_XML
|
|DEFAULT_DU_QTY
|I
|-
|ORD_XML
|
|DEFAULT_GROUP_NAME
|I
|-
|ORD_XML
|
|DEFAULT_UN_DESC
|I
|-
|ORD_XML
|
|DEFAULT_UN_NUMBER
|I
|-
|ORD_XML
|
|DEFAULT_UN_QTY
|I
|-
|ORD_XML
|API
|DELETE_LINES
|I
|-
|ORD_XML
|API
|DFLT_CUST_CURRENCY
|I
|-
|ORD_XML
|
|DFLT_CUST_GRP_LOC
|I
|-
|ORD_XML
|
|DFLT_DG_CLASS
|I
|-
|ORD_XML
|
|DFLT_DU_QTY
|I
|-
|ORD_XML
|
|DFLT_DU_TYPE
|I
|-
|ORD_XML
|
|DFLT_PACK_CUSTOMER
|I
|-
|ORD_XML
|
|DFLT_PARCEL_PACK_DU
|I
|-
|ORD_XML
|
|DFLT_PROD_TYPE_DESC
|I
|-
|ORD_XML
|
|DUP_SHIPMENTS_ALLOW
|I
|-
|ORD_XML
|
|EXC_CUST_MASTER
|I
|-
|ORD_XML
|
|GROUP_NAME
|I
|-
|ORD_XML
|
|IGNORE_MISSING_PROD
|I
|-
|ORD_XML
|
|INSPECT_DATE_FROM
|I
|-
|ORD_XML
|
|INSPECT_PERIOD_TYPE
|I
|-
|ORD_XML
|
|INSPECT_PERIOD_VALUE
|I
|-
|ORD_XML
|
|ITEMS_FROM_LINE
|I
|-
|ORD_XML
|
|ITEM_AKA_VOLUME
|I
|-
|ORD_XML
|
|LIMIT_ADDRESS_MATCH
|I
|-
|ORD_XML
|
|LOCATION_DECODE_MAP
|I
|-
|ORD_XML
|API
|LOCATION_EXT_REF
|I
|-
|ORD_XML
|API
|LOC_DEPOT
|I
|-
|ORD_XML
|API
|LOC_FLEXIPOD
|I
|-
|ORD_XML
|API
|LOC_LOADING_RATE
|I
|-
|ORD_XML
|API
|LOC_UNLOADING_RATE
|I
|-
|ORD_XML
|
|MAINTAIN_SCHEDULES
|I
|-
|ORD_XML
|API
|MAIN_ADDRESS_TYPE
|I
|-
|ORD_XML
|API
|MATCH_FULL_LOC
|I
|-
|ORD_XML
|
|MATCH_MASTER_LOC
|I
|-
|ORD_XML
|
|MISSING_ITEMS_DU
|I
|-
|ORD_XML
|API
|MOD_ORD_ACTION_VALUE
|I
|-
|ORD_XML
|
|NO_DATES_LOCS
|I
|-
|ORD_XML
|API
|NO_UPDATE_DEPOT_ADDR
|I
|-
|ORD_XML
|
|NULL_DATES
|I
|-
|ORD_XML
|
|OMIT_DU_DESP_QTY
|I
|-
|ORD_XML
|
|OMIT_NEW_ORDER
|I
|-
|ORD_XML
|
|OMS_SOURCE_SYSTEM
|I
|-
|ORD_XML
|
|ORDER_SOURCE_SYSTEM
|I
|-
|ORD_XML
|API
|ORDER_VEHICLE
|I
|-
|ORD_XML
|API
|ORD_ADD_REFS
|I
|-
|ORD_XML
|API
|ORD_INVOICED
|I
|-
|ORD_XML
|
|OUTBOUND
|I
|-
|ORD_XML
|
|OUTBOUND_DEL
|I
|-
|ORD_XML
|
|OWNING_DEPOT
|I
|-
|ORD_XML
|
|PACK_NEW_ORD
|I
|-
|ORD_XML
|
|PACK_NEW_ORDER
|I
|-
|ORD_XML
|API
|PARAGON_API
|I
|-
|ORD_XML
|
|PREVENT_MOD_SCHED
|I
|-
|ORD_XML
|
|PREVENT_REPACK
|I
|-
|ORD_XML
|
|PRINT_LABELS
|I
|-
|ORD_XML
|
|RECALC_DISTANCE
|I
|-
|ORD_XML
|
|RECALC_TRIP_SCHED
|I
|-
|ORD_XML
|
|REPLACE_ORDER_LINES
|I
|-
|ORD_XML
|
|REPROCESS
|I
|-
|ORD_XML
|
|RETAIN_REFS
|I
|-
|ORD_XML
|API
|ROUTE_DELIVERY
|I
|-
|ORD_XML
|API
|RUN_NUMBER_VALID
|I
|-
|ORD_XML
|
|SEND_ACK_FAIL_UPD
|I
|-
|ORD_XML
|
|SEND_ACK_FAIL_UPDATE
|I
|-
|ORD_XML
|
|SEND_CON_ADD
|I
|-
|ORD_XML
|
|SET_DEL_WIN_FROM_RUL
|I
|-
|ORD_XML
|
|SET_SCHED_GROUP
|I
|-
|ORD_XML
|
|SET_SCHED_GRP
|I
|-
|ORD_XML
|
|SHIPMENT_ACTUALS
|I
|-
|ORD_XML
|
|SPLIT_PROD_CODE
|I
|-
|ORD_XML
|
|STORE_ITEMS_DU_TYPE
|I
|-
|ORD_XML
|
|STORE_ITEM_DU_TYPE
|I
|-
|ORD_XML
|
|STORE_SHIPPING_LPN
|I
|-
|ORD_XML
|
|TRACK_ITEMS
|I
|-
|ORD_XML
|
|TRM_WMS_UPDATES
|I
|-
|ORD_XML
|API
|UNSCHED_NEW_DATA
|I
|-
|ORD_XML
|
|UNSCHED_SHIPMENTS
|I
|-
|ORD_XML
|API
|UPDATE_CANCELLED
|I
|-
|ORD_XML
|
|UPDATE_CUST_GROUP
|I
|-
|ORD_XML
|API
|UPDATE_EXISTING_LOCS
|I
|-
|ORD_XML
|
|UPDATE_INVALID_ORDER
|I
|-
|ORD_XML
|
|UPDATE_LOC_NAME
|I
|-
|ORD_XML
|
|UPDATE_PACKED
|I
|-
|ORD_XML
|API
|UPDATE_PARAGON_ID
|I
|-
|ORD_XML
|
|UPDATE_TO_DELIVER
|I
|-
|ORD_XML
|
|UPD_CUST_DATES
|I
|-
|ORD_XML
|
|UPD_CUST_ENABLE_EPOD
|I
|-
|ORD_XML
|
|USE_HAZARDOUS
|I
|-
|ORD_XML
|
|USE_HAZARD_DEFAULT
|I
|-
|ORD_XML
|
|USE_HAZARD_DEFUALT
|I
|-
|ORD_XML
|
|USE_ITEMISED_PACKING
|I
|-
|ORD_XML
|
|USE_LOC_RESTRICT
|I
|-
|ORD_XML
|
|USE_LOC_TYPE
|I
|-
|ORD_XML
|
|USE_ORDERED
|I
|-
|ORD_XML
|
|USE_PROD_TYPE_DFLT
|I
|-
|ORD_XML
|API
|USE_RUN_DEPOT
|I
|-
|ORD_XML
|API
|USE_VARIANT_ADDRESS
|I
|-
|ORD_XML
|
|VALDATE_SO_REF
|I
|-
|ORD_XML
|
|VALIDATE_COMM_CLASS
|I
|-
|ORD_XML
|
|VALIDATE_DIMENSIONS
|I
|-
|ORD_XML
|
|VALIDATE_DU_TYPE
|I
|-
|ORD_XML
|
|VALIDATE_MASTER_LOC
|I
|-
|ORD_XML
|
|VALIDATE_SO_REF
|I
|-
|ORD_XML
|
|VALIDATE_TRANS_MODE
|I
|-
|ORD_XML
|
|VOLUME_BASED_DU_QTY
|I
|-
|ORD_XML
|
|WEIGHT_BASED_DU_QTY
|I
|-
|ORD_XML_OUT
|
|ALLOW_MULTI_CUSTOMER
|O
|-
|ORD_XML_OUT
|
|INCLUDE_ORDER_STATUS
|O
|-
|ORD_XML_OUT
|
|INCLUDE_TRACKING
|O
|-
|ORD_XML_OUT
|
|INC_COPIED_ORDERS
|O
|-
|ORD_XML_OUT
|
|ORD_COUNTRY
|O
|-
|ORD_XML_OUT
|
|PACK_EVENT
|O
|-
|ORD_XML_OUT
|
|PREVENT_RESEND_ORDER
|O
|-
|ORD_XML_OUT
|
|SEND_EVENT_TRACKING
|O
|-
|ORD_XML_OUT
|
|SEND_HEADER_ITEMS
|O
|-
|ORD_XML_OUT
|
|SEND_HEADER_UPDATES
|O
|-
|ORD_XML_OUT
|
|SEND_LINE_ITEMS
|O
|-
|ORD_XML_OUT
|
|SEND_SUB_REFERENCES
|O
|-
|ORS
|
|audit_process
|O
|-
|PLUTO_ACTUALS
|
|PRINT_ROUTE_CODE
|O
|-
|PLUTO_ACTUALS
|
|PRINT_STOP_PID
|O
|-
|POD_XML
|
|NON_CONFORM_ERR
|O
|-
|PROCESS
|
|COL_EVENT
|O
|-
|PROCESS
|
|COL_EVENT
|I
|-
|PROCESS
|
|COPY_LOTS
|I
|-
|PROCESS
|
|COPY_LOTS
|O
|-
|PROCESS
|
|DEL_EVENT
|O
|-
|PROCESS
|
|DEL_EVENT
|I
|-
|PROCESS
|
|DFLT_PROD_TYPE_DESC
|O
|-
|PROCESS
|
|ORD_EVENT
|O
|-
|PROCESS
|
|ORD_EVENT
|I
|-
|PROCESS
|
|VLD_EVENT
|O
|-
|PROCESS
|
|VUI_EVENT
|O
|-
|PROCESS
|DP_BNL_EDI_IN.P_PROCESS_FILES
|DEFAULT_DEL_TYPE
|I
|-
|PROCESS
|DP_BNL_EDI_IN.P_PROCESS_FILES
|DEFAULT_GROUP_NAME
|I
|-
|PROCESS
|DP_BNL_EDI_IN.P_PROCESS_FILES
|DEFAULT_PROD_TYPE_ID
|I
|-
|PROCESS
|DP_BNL_EDI_IN.P_PROCESS_FILES
|DEFAULT_SRCE_SYSTEM
|I
|-
|PROCESS
|DP_BNL_EDI_IN.P_PROCESS_FILES
|DELIMITER
|I
|-
|PROCESS
|DP_BNL_EDI_IN.P_PROCESS_FILES
|EARLY_AVAILABLE_TIME
|I
|-
|PROCESS
|DP_BNL_EDI_IN.P_PROCESS_FILES
|LATE_AVAILABLE_TIME
|I
|-
|PROCESS
|DP_BNL_EDI_IN.P_PROCESS_FILES
|USE_DIMENSIONS
|I
|-
|PROCESS
|DP_BNL_EDI_OUT.P_PROCESS_PLAN
|DELIMITER
|O
|-
|PROCESS
|DP_BNL_EDI_OUT.P_PROCESS_PLAN
|FROM_LOC_TYPE
|O
|-
|PROCESS
|DP_BNL_EDI_OUT.P_PROCESS_PLAN
|INCLUDE_MANUAL_ORDER
|O
|-
|PROCESS
|DP_BNL_EDI_OUT.P_PROCESS_PLAN
|ORDER_SOURCE_SYSTEM
|O
|-
|PROCESS
|DP_BNL_EDI_OUT.P_PROCESS_PLAN
|TO_LOC_TYPE
|O
|-
|PROCESS
|DP_BWSC.PROCESS_FILES
|COMMENT
|I
|-
|PROCESS
|DP_BWSC.PROCESS_FILES
|REASON_CODE
|I
|-
|PROCESS
|DP_CSV6.TIMI_EXTRACT
|i_account
|I
|-
|PROCESS
|DP_CSV6.TIMI_EXTRACT
|i_cost_centre
|I
|-
|PROCESS
|DP_CSV6.TIMI_EXTRACT
|i_customer
|I
|-
|PROCESS
|DP_CSV_POD.P_PROCESS_CSV_POD
|CHECK_STOP_TIMES
|O
|-
|PROCESS
|DP_CSV_POD.P_PROCESS_CSV_POD
|SUCCESS_REASON_CODE
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|API_ARR
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|API_CAN
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|API_COL
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|API_DEL
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|API_DEP
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|API_INC_CANCELLED
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|API_ORD
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|API_TRP
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|API_USE_WS_ELUCID
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|AUDIT_METHOD
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|AUDIT_STATUS
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|DEL_ALL_ACT_QTY
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|EXPORT_SERVICES
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|EXPORT_TYRE
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|INCLUDE_CDATA_TAG
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|INCLUDE_ORDER_STATUS
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|INC_ORD_ITEM_EVENTS
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|PRINT_ROUTE_CODE
|O
|-
|PROCESS
|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
|SEND_AND_FORGET
|O
|-
|PROCESS
|DP_FIXED_IMPORT.P_PROCESS_FILES
|IMPORT_FORMAT
|I
|-
|PROCESS
|DP_FIXED_IMPORT.P_PROCESS_FILES
|SERVICE_LEVEL
|I
|-
|PROCESS
|DP_IMP.P_PROCESS_CIPD
|PREVENT_REPACK
|I
|-
|PROCESS
|DP_LFE_POD.PROCESS_FILES
|CARRIER
|I
|-
|PROCESS
|DP_LFE_POD.PROCESS_FILES
|MANIFEST_READY_TIME
|I
|-
|PROCESS
|DP_PAR_API_STP.get_paragon
|DEPOT
|I
|-
|PROCESS
|DP_PAR_API_STP.get_paragon
|PAR_SCHEDULES
|I
|-
|PROCESS
|DP_PAR_API_STP.get_paragon_route
|DEPOT_KEY
|I
|-
|PROCESS
|DP_PAR_API_STP.process_paragon
|USE_RUN_DEPOT
|O
|-
|PROCESS
|DP_REPORTS.PROCESS_CLICK_OUTBOUND
|STOP_TIMES_DEBRIEF
|O
|-
|PROCESS
|DP_REPORTS.PROCESS_CLICK_OUTBOUND
|SUPPRESS_ASSETS
|O
|-
|PROCESS
|DP_REPORTS.SEND_DEL_EMAIL
|RADIAL_ONLY
|O
|-
|PROCESS
|DP_RICO.RECEIVE_REPORT_STATUS
|p_process_name
|I
|-
|PROCESS
|DP_RICO.RECEIVE_REPORT_STATUS
|pr_process_name
|I
|-
|PROCESS
|DP_TESLA_EDI_IN.IMPORT_ORDERS
|ALLOW_REUSABLE_ASSET
|I
|-
|PROCESS
|DP_TESLA_EDI_IN.IMPORT_ORDERS
|DEFAULT_DU
|I
|-
|PROCESS
|DP_TESLA_EDI_IN.IMPORT_ORDERS
|DEFAULT_PROD
|I
|-
|PROCESS
|DP_TOMTOM.GET_GEOFENCE
|TOM_EVENT_LAST_RUN
|I
|-
|PROCESS
|DP_TOY_EDI_IN.P_PROCESS_FILES
|DEFAULT_PROD_TYPE_ID
|I
|-
|PROCESS
|DP_TOY_EDI_IN.P_PROCESS_FILES
|PROCESS_TYPE
|I
|-
|PROCESS
|INT_XML_OUT2.PROCESS_XML_DESP_CONF
|OUTBASE_INDICATOR
|O
|-
|PROCESS
|INT_XML_OUT2.PROCESS_XML_MANIFEST
|EXCLUDE_UNPACKD_LINE
|O
|-
|PROCESS
|INT_XML_OUT2.PROCESS_XML_MANIFEST
|INC_PACKED_TO_DEL
|O
|-
|PROCESS
|INT_XML_OUT2.PROCESS_XML_MANIFEST
|PROCESS_INTERVAL
|O
|-
|PROCESS
|TRM.P_AUTO_COMPLETE
|SCHED_MINUS
|O
|-
|PROCESS
|TRM.P_AUTO_COMPLETE
|SCHED_PLUS
|O
|-
|PULSE_ORDERS
|
|SET_TIMES_BMV
|I
|-
|SCN
|
|SEND_REUSABLE_ASSET
|I
|-
|SMA_XML
|INT_XML_SMA.PROCESS_XML_OUTBOUND_SMA
|SMA_SEND_ADD_REF
|O
|-
|SMA_XML
|INT_XML_SMA.PROCESS_XML_OUTBOUND_SMA
|SMA_SEND_COST
|O
|-
|SMA_XML
|INT_XML_SMA.PROCESS_XML_OUTBOUND_SMA
|SMA_SEND_ORD_CON
|O
|-
|SMA_XML
|INT_XML_SMA.PROCESS_XML_OUTBOUND_SMA
|SMA_SEND_ORD_REF
|O
|-
|STS_XML
|
|INCLUDE_33
|O
|-
|STS_XML
|
|INCLUDE_CONTENTS
|O
|-
|STS_XML
|
|INCLUDE_DETAILS
|O
|-
|STS_XML
|
|INCLUDE_ITEM_DELIVER
|O
|-
|STS_XML
|
|INCLUDE_LINES
|O
|-
|STS_XML
|
|MSG_TYPE
|O
|-
|TRIP_ORD_XML
|
|PRINT_ROUTE_CODE
|O
|-
|TRIP_ORD_XML
|
|PRINT_STOP_PID
|O
|-
|TRIP_XML
|
|ALLOW_MULTI_CUSTOMER
|O
|-
|TRIP_XML
|
|ARR message
|O
|-
|TRIP_XML
|
|ARR_MESSAGE
|O
|-
|TRIP_XML
|
|ARR_ORDER_DEBRIEF
|O
|-
|TRIP_XML
|
|A_VAM
|O
|-
|TRIP_XML
|
|BASE_DEPOT
|O
|-
|TRIP_XML
|
|CHECK_STOP_TIMES
|O
|-
|TRIP_XML
|
|DEL message
|O
|-
|TRIP_XML
|
|DEL_MESSAGE
|O
|-
|TRIP_XML
|
|DEL_ORDER_DEBRIEF
|I
|-
|TRIP_XML
|
|DEL_ORDER_DEBRIEF
|O
|-
|TRIP_XML
|
|DESPATCH_RECEIVED
|O
|-
|TRIP_XML
|
|EVENT_ACTION
|O
|-
|TRIP_XML
|
|EXCLUDE_UNPACKD_LINE
|O
|-
|TRIP_XML
|
|EXCLUDE_UNPACKD_LINE
|I
|-
|TRIP_XML
|
|EXC_ORD_SRCE_SYSTEM
|O
|-
|TRIP_XML
|
|INCLUDE_CARTON_NO
|O
|-
|TRIP_XML
|
|INCLUDE_CARTON_NO
|I
|-
|TRIP_XML
|
|INCLUDE_ITEM_DELIVER
|O
|-
|TRIP_XML
|
|INCLUDE_NONCON_CODES
|O
|-
|TRIP_XML
|
|INCLUDE_ORDER_STATUS
|O
|-
|TRIP_XML
|
|INCLUDE_REASON_CODES
|O
|-
|TRIP_XML
|
|INCLUDE_REASON_TYPE
|O
|-
|TRIP_XML
|
|INCLUDE_SAP_LINE_NOS
|O
|-
|TRIP_XML
|
|INCLUDE_SIGNATURE
|O
|-
|TRIP_XML
|
|INCLUDE_TRACK_REF
|I
|-
|TRIP_XML
|
|INCLUDE_TRACK_REF
|O
|-
|TRIP_XML
|
|INC_DIRECT_ORDERS
|O
|-
|TRIP_XML
|
|INC_ORDER_CHILD_ADDR
|O
|-
|TRIP_XML
|
|INC_TRACKING
|O
|-
|TRIP_XML
|
|INC_TRIP_ACTION
|O
|-
|TRIP_XML
|
|INC_TRIP_TYPE
|O
|-
|TRIP_XML
|
|INC_XDOCK_ORDERS
|O
|-
|TRIP_XML
|
|OFDC_EVENT
|O
|-
|TRIP_XML
|
|ORDER_SIGNATURES
|O
|-
|TRIP_XML
|
|ORDER_SOURCE_SYSTEM
|O
|-
|TRIP_XML
|
|OUTBASE_INDICATOR
|O
|-
|TRIP_XML
|
|PACK_EVENT
|O
|-
|TRIP_XML
|
|PLANNED_CARRIER
|O
|-
|TRIP_XML
|
|POCPOD_ONLY
|O
|-
|TRIP_XML
|
|PODS_POCS
|O
|-
|TRIP_XML
|
|PREVENT_RESEND_ORDER
|O
|-
|TRIP_XML
|
|PREVENT_RESEND_TRIP
|O
|-
|TRIP_XML
|
|PRINT_ORD_SECTION
|O
|-
|TRIP_XML
|
|RADIAL_ONLY
|O
|-
|TRIP_XML
|
|SEND_ALL_ORDERS
|O
|-
|TRIP_XML
|
|SEND_DU_TYPE
|O
|-
|TRIP_XML
|
|SEND_HEADER_ITEMS
|O
|-
|TRIP_XML
|
|SEND_HEADER_UPDATES
|O
|-
|TRIP_XML
|
|SEND_LINE_ITEMS
|O
|-
|TRIP_XML
|
|SEND_REUSABLE_ASSET
|O
|-
|TRIP_XML
|
|SEND_WAREHOUSE_LOAD
|O
|-
|TRIP_XML
|
|SO_DEL_DATE_CHANGE
|O
|-
|TRIP_XML
|
|STATUS
|O
|-
|TRIP_XML
|
|TRIP_COUNTRY
|O
|-
|TRIP_XML
|
|TRIP_TYPE
|O
|-
|TRIP_XML
|
|UNLOAD_ONLY
|O
|-
|TRIP_XML
|
|USE_DELIVERY_LEG
|O
|-
|TRIP_XML
|
|VAMMY
|O
|-
|TRIP_XML
|
|XDOCK_ONLY
|O
|-
|TRIP_XML
|
|XML_INCL_RESOURCE
|O
|-
|TRP_XML
|
|ALLOW_MULTI_CUSTOMER
|O
|-
|TRP_XML
|
|ARR message
|O
|-
|TRP_XML
|
|DEL message
|O
|-
|TRP_XML
|
|INCLUDE_ITEM_DELIVER
|O
|-
|TRP_XML
|
|INCLUDE_REASON_CODE
|O
|-
|TRP_XML
|
|INCLUDE_SAP_LINE_NOS
|O
|-
|TRP_XML
|
|PRINT_ORD_SECTION
|O
|-
|TRP_XML
|
|SO_DEL_DATE_CHANGE
|O
|}

EDI Maintenance

2026-03-06T08:56:56Z

Anw: /* Creating Processes */ Updated

File:TripOrderXML-EDI-FTP.png

2026-03-06T08:40:23Z

Anw:

TripOrderXML EDI FTP settings

Main Page

2025-12-19T11:38:01Z

Anw: Minor correction

<div style="text-align: center;">[[Image:Calidus-TMS.png]]</div>

<center><font size="5">Welcome to the ''CALIDUS'' TMS Assist help pages.</font></center>

Here you will find all kinds of guides, from simple to advanced, from user guides to technical implementation guides, all to provide as much information on how to get the best out of your ''CALIDUS'' TMS implementation.

Assuming you are now up and running with your system, why not try to find something you didn't know? Try clicking the 'Did You Know' link below.

<center><font size="5">[[Did You Know]]</font></center>

That's how Assist works - help broken down into bite-sized chunks, designed to help you make the most of your system. If you're familiar with the web and familiar with Wiki, you're going to find it easy to get around in Assist.

If you're coming here as a new user without a clear idea of how ''CALIDUS'' TMS works or what it does, you should start with the overview and glossary of terms - that will give you enough information so that you're clear on what we're achieving with this application. You'll find them first in the list below [[#C-TMS Key Functionality|here]].

If you're more comfortable with documents rather than web pages, we've got you covered.

Every page here can be downloaded as a PDF (including this one) by clicking the ''Print as PDF'' or ''Download as PDF'' link in the toolbar, typically on the left of your browser window, or on the tabs at the top right of the window. That will give you the PDF of just that page, but if you want something more formal, see the heading below called [[#Documents|Documents]] - downloading those as PDFs will give you the formal Aptean document. On this page, we've also provided direct links to those document versions - click the {{DocLink|Main Page}} link next to the page.

As you can see, some of the guides are multi-page, so we organise those into categories of pages. Where those pages form a guide themselves (like the C-TMS Key Functionality), you can use that ''Download as PDF'' or ''Print as PDF'' link again from the category to get all the pages in one handy guide.

We keep these pages up to date based on the latest available version of ''CALIDUS'' TMS - if you see something you like here, but aren't sure whether your version supports it, why not give our team a call? We can advise you on the steps you need to take to upgrade your system to the latest and greatest.

We're constantly updating the system, and that means that we're constantly updating the documentation too. One of the great things about Wiki pages is that the history is kept, so you can click the ''View History'' link (usually at the top of the page) to see all previous versions of the help page. So, although all the guides are the latest version, you can still access the older pages for reference.

The same is true of any of the pictures that we've uploaded in these guides - click on them and you can see the whole history of that picture. You can download them as well, if you like.

Of course, we also keep PDF copies of the previous version of the documentation when we've finished it, so we can always provide them to you. We've generated them from these Assist pages just like you can - because it's that easy to use.

Below you'll find links to all of the guides in this Assist system.

=== [[:Category:Documents|Documents]] ===
----

All formal documents can be accessed by clicking the title above. Below are some important general documents:

* [[Aptean Routing and Scheduling Overview]] {{DocLink|Aptean Routing and Scheduling Overview}}
* [[:Category:C-TMS_User_Guide|CTMS User Guide]] {{DocLink|Category:C-TMS_User_Guide}}
* [[:Category:C-TMS Key Functionality|C-TMS Key Functionality]] {{DocLink|Category:C-TMS Key Functionality}}
* [[:Category:C-TMS Modules|C-TMS Modules]] {{DocLink|Category:C-TMS Modules}}
* [[:Category:C-TMS Admin|C-TMS Administration Modules]] {{DocLink|Category:C-TMS Admin}}

=== Getting Started ===
----

[[Initial Setup]] - a guide on setting up C-TMS for a new contract.

[[:Category:C-TMS_User_Guide|CTMS User Guide]] {{DocLink|Category:C-TMS_User_Guide}}

[[:Category:FAQ]]

=== [[:Category:C-TMS Key Functionality|C-TMS Key Functionality]] ===
----
All documents can be accessed by clicking the title above. Below are some links:

* [[Overview]]
* [[Glossary]]
* [[Schedules]]
* [[Orders]]
* [[New Order]]
* [[Trip Manipulation]]
* [[Planning]]
* [[External Map Applications]]
* [[Browserless Application Installer]]

=== [[:Category:C-TMS Modules|C-TMS Modules]] ===
----
All documents can be accessed by clicking the title above. Below are some links:

* [[:Category:Order Management|Order Management]] {{DocLink|Category:Order Management}}
* [[:Category:Trip Management|Trip Management]] {{DocLink|Category:Trip Management}}
* [[:Category:Accounts|Accounting]] {{DocLink|Category:Accounts}}
* [[:Category:Maintenance|Maintenance]] {{DocLink|Category:Maintenance}}
* [[:Category:Reports|Reports]] {{DocLink|Category:Reports}}

=== [[:Category: C-TMS Training Guides|C-TMS Training Guides]]===
----
All documents can be accessed by clicking the title above, where the documents are grouped by area, as well as full compiled guides. Below are some links to stand-alone guides:

* [[Finance Guide]]
* [[BI Data Extract Guide]]

=== [[:Category:C-TMS Admin|C-TMS Administration Modules]] ===
----
All documents can be accessed by clicking the title above. Below are some links:

* [[Interfaces]]
* [[Audit Log]]
* [[Message Monitoring]]
* [[File Interfaces]]
* [[Administration - Access Control]]
* [[Administration - Fixed Schedules]]
* [[Administration - Lock Monitor]]
* [[System]]

=== [[Program Listing|C-TMS Programs]] ===
----

You can find a list of all forms in CTMS by clicking the title above or here: [[Program Listing|Program Listing]].

=== [[:Category:Training|Training]] ===
----
This category contains all documents pertaining to the initial training sessions.

All documents can be accessed by clicking the title above.


=== Connected Systems ===
----

* [{{SERVER}}/calidus-assist/EPOD/ EPOD]
* [{{SERVER}}/calidus-assist/MCS/ MCS]
* [{{SERVER}}/calidus-assist/WCS/ WCS]
* [{{SERVER}}/calidus-assist/Portal/ Portal]
* [{{SERVER}}/calidus-assist/CTLTMS/ CTL]

=== [[:Category:Incomplete|Incomplete]] ===
----
Several screens are in the process of being updated or created at any time. We tag those screens so that we can easily identify them. Click the section title to see a list of those screens that are in the process of being documented.

The following pages have not yet been created:
* [[AGREEMENTS]]
* [[BUS_TYPE]]
* [[CONFIG_MESSAGE]]
* [[DELIVERY]]
* [[INVENTORY_MAN]]
* [[ISOTRAK]]
* [[LOAD_INT]]
* [[LOGIX_INT]]
* [[MILK_ROUND_MAINT]]
* [[PAR_INT]]
* [[PTV_CONFIG]]
* [[PURCH_ORD]]
* [[SAP_MAINT]]
* [[SAVING]]
* [[SERVICE_CHARGES]]
* [[SESSION]]
* [[SHIP_ORD]]
* [[TRIPSUM_JRL]]
* [[TRIP_MSG_HOLDS]]

<div style="display:none;" class="apt-user-show">
=== Creating new documents and pages ===
----
You must be logged in to be able to create new pages in Assist.

<inputbox>
type=create
buttonlabel=Create a new Document
preload=DocTemplate
break=no
placeholder=Enter Document to Create e.g. Orders - Order Guide
</inputbox>

<inputbox>
type=create
buttonlabel=Create a new Page
preload=PageTemplate
break=no
placeholder=Enter Page to Create e.g. PTV_CONFIG
</inputbox>
</div>

FAQ

2025-12-02T15:45:27Z

Anw: Added retain planning region FAQ

CTMS Frequently Asked Questions

== How can I select what can be seen on screens? ==
* [[Layout Configuration]]

== What criteria can I use to find orders? ==
* [[New_Order#Order_Search]]

== What do the order statuses mean? ==
* [[Overview_-_Order_Import_and_Handling]]

== How can I Rebook an Order? ==
* [[New_Order#Re-booking_Orders]]
* [[Trip_Debrief#Rebook_Process]]

== How can I add additional References to an Order? ==
* [[New_Order#Add_Details_Tab]]

== How can I see the Revenue generated against an order? ==
* [[New_Order#Finance_Tab]]
* [[New_Order#Order_Search]]

== How can I see the trips on which an order is scheduled? ==
* [[New_Order#Trip_Detail_Tab]]
* [[Trip Overview (Waterfall)]]

== How do I manually create a new trip? ==
* [[Planning#Create_New_Trip]]

== How do I assign resources to a trip? ==
* [[Planning#Assign Resources]]
* [[Trip Overview (Waterfall)]]
* [[Trip Overview (Waterfall)#Allocate_Resources]]

== How do I put an order onto a trip that has already been created? ==
* [[Planning#Apply to Trip/Apply to Stop]]

== How do I check that everything is OK on a trip? ==
* [[Planning#Revalidate Trip]]

== How do I force the system to manually recalculate distances and times? ==
* [[Planning#Recalculate Distance and Time]]

== How do I set or reset a trip status? ==
* [[Overview_-_Order_Import_and_Handling]]
* [[Planning#Set Trip Status]]
* [[Trip Overview (Waterfall)#Set_Trip_Status]]

== How do I manipulate a trip? ==
* [[Planning#Manipulating a Trip]]

== How to I change the order of stops on a trip? ==
* [[Planning#Manoeuvre Stops]]
* [[Planning#Move Stop]]

== How do I merge trips together? ==
* [[Planning#Merge Trip]]

== How do I split a trip into smaller trips? ==
* [[Planning#Split Trip]]

== How do I delete a trip I don't want anymore? ==
* [[Planning#Delete Trip]]

== How do I add a stop to a trip? ==
* [[Planning#Insert Stop]]
* [[Planning#Append Stop]]

== How do I over-ride the calculated stop times? ==
* [[Planning#Over-riding Stop Times]]
* [[Planning#Wait_Times]]

== How do I remove orders from a trip? ==
* [[Planning#Removing Order(s)]]
* [[Planning#Delete Stop]]
* [[Planning#Unschedule Orders]]

== How do I change order details when the order is already on a trip? ==
* [[Planning#Change Order Details (whilst on a trip)]]
* [[Planning#Amending Order Values]]

== How do I transfer orders from 1 trip to another? ==
* [[Planning#Transfer Order(s)]]

== How do I move an unscheduled order to a new schedule? ==
* [[Planning#Move to Schedule]]
* [[Planning#Carry Forward]]

== How do I manually cross-dock an order between depots? ==
* [[Planning#Creating Trips via Crossdocks]]

== How do I Pass a Depot Trip to Another Depot or Carrier? ==
* [[Planning#Pass a Depot Trip to Another Depot or Carrier]]

== How do I change a driver on a trip? ==
* [[Planning#Change a Driver on a Trip]]
* [[Trip_Overview_(Waterfall)#Allocate_Resources]]

== Why is my time and distance zero between trip stops? ==
This is controlled by the Network table. This should be automatically calculated by your system based on the GPS co-ordinates of the location, which themselves should be automatically calculated.

* Find your locations of the two adjacent stops.
* In the Network screen, enter your first location in the criteria and find. Then check whether there is an entry for the second location

* If there is no entry between those locations, that is why no distance and time.

That may be because of the Location GPS co-ordinates:

* Go to the location screen.
* Find the locations in sequence.
* Check that the locations have a GPS co-ordinate against them.
* If they do, then check whether they are the exact same co-ordinate - if they are, change one.

If they have GPS co-ordinates, then this may be to do with the trailer on the trip,

* You can check this by removing the trailer and trailer type from the trips.
* Alternatively, check the trailer type in the Resources screen.
* If the drive time modifier (DT Mod) is 0, this should be changed to 1 (normal drive time), or a positive value that will be used to modify the drive time (less than 1 = faster, greater than 1 = slower).

Reference:

* [[System Parameters List]] - HERE Maps parameters.

* [[Network]]
* [[Resources]] screen, [[Trailer Types]] tab.
* [[Locations]], main tab

== How do I set up a new user? ==
* [[Access Control / User Maintenance#Creating a New User]]

== How do I edit a user? ==
* [[Access Control / User Maintenance#Editing a New User]]

== How do I change a user password? ==
* [[Access Control / User Maintenance#Change User Password]]

== How do I assign screens or functions to a user? ==
* [[Access Control / User Maintenance#Editing a Group]]
* [[Access Control / User Maintenance#Group Maintenance – Accessible Functionality]]
* [[Access Control / User Maintenance#Users and Groups]]
* [[Access Control / User Maintenance#Adding a User to Group]]

== I'm getting an import error about checksum ==
An error along the lines of the following is displayed when you try to upload an import file:
"A file with checksum value xxxxxx has previously been loaded."

This is a protective part of the import process - a unique checksum is generated from the filename and content, and is compared to any previous uploads, to prevent repeated uploads of the same data, which may cause problems to import processes and duplicated data.

If you are sure that the data is correct and want to import anyway, you can change the filename being uploaded or append and extra content column (e.g. ,1) to the end of one of the import lines - this will change the checksum and the file will then upload.

== How can I update or fix the planning region of a location? ==
If you have changed your postal/planning region setup, you may need to update your locations.

* Find the location in the ''Locations'' form.
* Click '''Update''' - this should update your location from the planning/post region mapping.
* Click '''Save''' to save the change.

If you want to fix the location to a particular planning region outside of the mapping, that's possible too. It’s just a checkbox against the locations.

* Find the location in the ''Locations'' form.
* Change the ''Planning Reg'' value to what you want – you can use a lookup.
* Click the ''Special'' tab.
* Check the “''Retain Planning Region''” box.
* Click '''Save'''.

You can do several locations in sequence that way – the ''Special'' tab will stay focussed as you move between locations.

See here for details of the Locations form:

[[Locations#Special|https://calidusassist.adcservices.apteancloud.com/calidus-assist/MTS/index.php/Locations#Special]]

<noinclude>
[[Category:FAQ]]
</noinclude>

Locations

2025-12-02T15:44:58Z

Anw: Updated retain planning region

Locations are used to maintain the details related to a specific location such as their Address information, Contacts and Constraints. Location Maintenance form can be accessed from Maintenance Menu as shown below:

[[Image:loc_1.png]]

The Locations module assists in the creation, maintenance and retrieval of C-TMS data pertaining to how each location functions. The Locations data determines to a small degree how the orders are created in the Bookings form.

A Default Loading and Unloading rate controlled by 2 system parameters (GEO_DEFAULT_LOAD_RATE and GEO_DEFAULT_UNLOAD_RATE) is populated when a location is created.

The Locations data can be viewed, created, edited and maintained through the following Locations form.

[[Image:loc_2.png]]

==Query existing Locations:==

To query for a Location, enter the ID of the location with a '%' as shown and click on the query button. This will provide the details of the Location queried. An example is shown below.

[[Image:loc_3.png]]

You can traverse through the relevant tabs to get details of them. '''Note the tabs will be discussed later in the document'''

[[Image:loc_4.png]]

You can also query using a lookup against the location ID. press the button indicated by the red square below to get a list of locations:

[[Image:loc_query_lookup.png|800px]]

Choose your location and press the '''OK''' button. The data for the chosen location is displayed.

==Creation of a new Location:==
The Address tab provides the facility to define and maintain Depots. As well as the address, the depot can be defined as a Branch or RDC. The longitudes and latitudes of the depot are entered along with open and close times - if required.

To create a new Location, click on the '''New Location''' button and enter the Location ID, Location Type and the Location Name as shown below.

[[Image:loc_5.png]]

When creating a new location, you may assign a time zone, which will be used to set transaction times at the location. You may also assign a customer client code which allows you to select a subset of locations in order entry.

The Location ID should identify the location uniquely. The Location Type can hold one of the types set up in the system, typically from the below:
* BRANCH - if the location is a delivery point.
* RDC - if the location is a depot/distribution centre.
* SUPPLIER - if the location is a vendor/supplier location.

Types are maintained in the system, so you can have many others, such as:
* CROSSDOCK
* HOSPITAL
* SESSION - if the location is a session location.
* SWAP - if the location is a SWAP location (PARK, LAYBY etc.)
* TEAMBASE - if the location is a session teambase location.
* AIRPORT - if the location is an airport

==Address==
This tab contains the address of the location.

[[Image:loc_6.png]]

In the address tab, enter the address details and the most important fields in this tab are the Postal Code, Town and Country (ISO Code). The 'Postal Reg' and the 'Planning Reg' will be populated by the system based on the postal code.

The Lat and Long fields will be populated by the [[External Map Applications]] used to geocode locations, once the location is used in an Order. This can also be manually entered here. The location needs to be required upon first entry to display the latitude and longitude values.

The Loading Rate and Unloading Rate specify the time required to load and unload a truck in the given location. This will be described in the Resources section of the training.

The Paragon id can contain up to 40 characters no additional validation is performed.

The Ext Ref can contain up to 50 characters and must be unique to the location. If a duplicate value is entered an error will be raised and the changes will not be saved.

UNL Location is related to emissions reporting. The code will be automatically created for you when the location is created, from the country code and the first 3 characters of the Town. This is used in the Carbon Emissions extract only.

You can click the '''Show on Map''' button to open a new tab in your browser to show the position of the location on a map.

Once you have entered the required information, click on the '''Save''' button to save the changes that you have made.

To delete the location, use the '''Delete''' button - you will be prompted for confirmation before it is deleted, and the system will not allow you to delete a location where that location has been used on orders.

==Special==
Additional data such as Alternative Collection/Delivery Location can be attached to a location or comments can be added.

[[Image:loc_7.png|800x800px]]

The following fields are available

* ''Comments'' - Location comments are for reference - these are used in some interfaces to electronic POD systems (such as Aptean Proof of Delivery (FleXipod) and are used as location instructions.
* ''Default SC Hanging''
* ''Default SC Boxed''
* ''Alternative Collection Loc''
* ''Alternative Delivery Loc''
* ''Alternative Code''
* ''Default Du Type'' - A default DU type can be added against the location which can be used to automatically assign to orders generated for collection from this location.
* ''Collecting Depot''
* ''Default Despatch Lane''
* ''Tracking System'' - a drop-down list of ''ISOTRAK, MICROLISE, TOMTOM''.
* ''Parent Location''
* ''Default Label Printer''
* ''Hub Location''
* ''RF Cross-dock'' (Checkbox) - this controls whether the location is used for item scanning through CALIDUS WCS.
* ''Early Stop Window'' (Checkbox)
* Fixed Lat Longs (Checkbox)
* ''Email Trip Manifest'' (Checkbox)
* ''Exclusive Drop'' (Checkbox)
* ''Allow DG Pallets'' (Checkbox) - whether the location allows dangerous goods.
* ''Create Empties'' (Checkbox)
* ''WCS Item to Asset'' (Checkbox) - whether goods scanned at this depot through CALIDUS WCS may be added to assets.
* ''Master Location'' (Checkbox)
* ''MIX MOVE'' (Checkbox)
* ''Retain Planning Region'' (Checkbox) - see notes below.
* ''Flexipod'' (Checkbox) - controls whether this depot (RDC) location is using Aptean POD (APOD or FleXipod) for execution of trips, if configured at depot level.

{{Note}} The system will always automatically default to the planning region associated with the postal region of the address.

If you have changed your postal/planning region setup, you may need to update your locations that already exist.

* Find the location in the ''Locations'' form.
* Click '''Update''' - this should update your location from the planning/post region mapping.
* Click '''Save''' to save the change.

If you want to fix the location to a particular planning region outside of the mapping, that's possible too. It’s just a checkbox against the locations.

* Find the location in the ''Locations'' form.
* Change the ''Planning Reg'' value to what you want – you can use a lookup.
* Click the ''Special'' tab.
* Check the “''Retain Planning Region''” box.
* Click '''Save'''.

==Slots==
Collection and Delivery [[Slot]]s are maintained for each location. Each [[Slot]] details the collection and delivery windows on a particular day that the collection or delivery of goods from one location to another should be scheduled. [[Slot]]s can be configured to use a specific Trailer Type and accept specific [[Product Types]]. [[Slot]]s are filled by the [[Create Transport Instructions]] process invoked from the [[Bookings]] form.

[[Image:loc_8.png]]

The slots are relative to a particular day of the week and cover a specified collection and delivery time window. It is these windows that are propagated onto the generated order.

===Manual Slot Manipulation===
Provides the facility to manually add, edit, delete and inactivate Slots. Only Slots in a Status of Active are displayed by default in the Slots tab as only Active Slots are considered by the system in the [[Create Transport Instructions]]'s process. A function to view Inactive Slots is included. An inactive slot gets ignored during the Create TI's process.

This also provides the facility to add, edit and delete Product Types and a Trailer Type from a Slot.

===Slot Import===
Slots can be imported into C-MTS Host via an inbound interface. In the case of Sainsbury's Supermarkets this is the VAST interface that runs nightly. This interface process inactivates all Slots in the system then either reactivates any Slots that exist in both the system and the new interface file or creates any new Slots. The Slot Import functionality on the Slots tab simply allows this import process to be invoked manually if required.

===Multiple Slot Deletion===
This function allows Inactive Slots to be removed from the system if they have not been activated for a user specified period of time. This ensures a manageable number of entries are displayed in the Slots tab if the option to display Inactive Slots is selected.

===Dynamic Day Offsets===
All Slots have collection and delivery windows and apply to a particular day. Slot windows are held with actual times, e.g. 10:00 - 11:00, and day offset. The use of day offset minimizes user maintenance as the actual date a Slot is used is not stored, it is implied by the day offset e.g. on Friday 12th July 2002, a Slot stored with a delivery window of 0 23:30 to 1 00:30 will be interpreted as 12th July 23:30 - 13th July 00:30 i.e. the day offset is used to decrement or increment the actual date on which the Slot is being used.

===Slot Trailers===
Each Slot can be configured with a specific Trailer Type. This allows a Slot to be configured to use, for example, a more maneuverable Trailer if access is restricted.

===Slot Products===
Slots can be configured to accept one or more Product Types. When Orders are created in Slots by the Create Transport Instructions process, the process is constrained to only fill Slots with permissible Product Types. If a Product Type is not compatible with a Slot it cannot be assigned to the Slot.

Each Product Type in a Slot has a Priority. If the Priority is one then the Product Type will always be assigned to the Slot. However, if the Priority is two, the Product Type will only be assigned to the Slot if it is topping up the Slot i.e. the Slot already contains some Priority one Product Type.

Slot Product Types can also be designated as Advance Only so that only Advance Orders for the appropriate Product Type are assigned to the Slot

==Constraints==
This tab allows for constraints to be set up against a location.

Constraints can be added to a location, which are taken into account when orders are created. If a constraint is added to a location, then the constraint name, day, start time, end time and value are required. For example if a constraint MAX_TRLR_LENGTH with a value of 33 exists for a location, then, it indicates that trailers over the length of 33 cannot be used on a particular day, for the location in question.

To create constraints for the location, click on the '''New''' button and enter the details as shown. The Constraint Type specifies the constraint in a specific location such as only an 11 ft truck is allowed on Mondays between 10:00 to 17:00 hours. Once the details are entered, click on the '''OK''' button to save it.

[[Image:loc_9.png]]

==Trailer Types==
The Trailer Types tab specifies the trailers that are compatible with the location.

To create a new record click the '''New''' button.

For the example here, this location can handle only 45ft curtain side trailers, i.e. when the 'Include' option is selected then only those trailer mentioned in the list are compatible with the location.

When the 'Exclude' option is selected then, excluding those trailer all other trailers are compatible with the location.

[[Image:loc_10.png]]

{{Note}} A location may only use one trailer type or many.

==Contacts==
This tab allows for the details of the contacts for the location to be maintained.

Type in the contract details into the empty fields. Please ensure that you click on the '''Save''' button to save all the changes that you have made.

[[Image:loc_11.png]]

Once contacts are in the system, users can use this screen to set a default value for Email Tracking, Email Service Report and Send Text.
* Email Tracking – This contact’s email will be used when sending a tracking link for the Portal TTM system.
* Email Service Report – This contact’s email will be used when sending the completed work report from the EPOD system.
* Send Text – This contact’s phone number will be used when sending a text from the EPOD system.

The Email Tracking, Email Service Report and Send Text check boxes will show how they are set up within CTMS.

This information is assessed when sending data to EPOD and TTM on the created jobs.

==Roles==
A single location could behave as multiple location types, so that, for example, a [[Crossdock]] could also be a depot. This functionality is not currently used by any automated part of the system and is for reference only.

[[Image:loc_12.png]]

==DU Types==
This is a client specific form but it is used in conjunction with a Supplier Portal. In the Portal, when a new order is generated it will default to have an order line for each of the DUs held on this tab.

[[Image:loc_13.png]]

To enter a DU Type select the '''New''' button and the below screen is populated. Enter a DU Type manually or use the available list of values to find the relevant DU Type

[[Image:loc_14.png]]

Click '''OK''' to return back to the main screen

==References==
This Tab has been designed to add any additional Location Level references that may be needed for a specific project

[[Image:loc_15.png]]

To add a reference click the '''New''' button. The below screen is then populated:

[[Image:loc_16.png]]

Enter a Reference code. If known it can be typed in manually or selected from a list of values. The description is automatically populated and is a read only field. Then enter the relevant value

'''Please note the list of values is maintained in the Imports screen, within the Decodes tab as shown in the screenshot below'''

[[Image:loc_17.png]]

== LOTS ==
LOTS (Live Order Tracking System) or TTM (Track and Trace Module) can be used to track orders through a a portal.

This screen can be used to determine whether a customer is included or excluded from the data sent to Calidus Portal TTM.

== EPOD ==
This screen allows you to maintain location-specific parameters controlling how and when jobs for this location are sent to EPOD.

[[Image:loc_epod.png|800px]]

You can enter:
* Send EPOD Jobs Load/Unload - whether these jobs are sent to C-ePOD on this activity.
* Consolidate EPOD Jobs Load/Unload - whether these jobs are automatically consolidated when sent to C-ePOD on this activity.
* Send EPOD Dets Load/Unload - whether these jobs are sent with details (items) to C-ePOD on this activity.
* Job Group for EPOD Load/Unload - a specific job group to use when sending these jobs to C-ePOD on this activity.

All parameters are initially set to Default - the system uses the location type defaults set up in the [[Business Data Maintenance]] screen.

== Linked Locations ==
This tab allows for locations to be linked. Locations may be linked where they are the same building or same site. Linking may be automatically applied through EPOD or manually applied in C-TMS. While linked locations will create separate stops on a C-TMS trip, they will be presented in EPOD as a single stop.

[[Image:loc_linked_locations.png|800px]]

To manually link locations, click the '''Linked Maint''' button. This will display the following screen:

[[Image:loc_linked_locations_2.png|800px]]

Click on the '''Find''' button. This will populate the location details of the location you are linking to. Click the '''Add Link''' button.

[[Image:loc_linked_locations_3.png|800px]]

Enter data that you would like to search on, for example, data with 'Man' in the 'City' field with '%Man%'. Press the '''Find''' button to bring back the data:

[[Image:loc_linked_locations_4.png|800px]]

Select the locations that you want to link with the checkbox and then press the '''Add Link''' button as below:

[[Image:loc_linked_locations_5.png|800px]]

The linked locations screen will be shown again with all linked locations.

Press the '''Close''' button and you are returned to the main screen. {{Note}} At this point you will need to close the screen completely and go back in to show the change.

You can remove linked locations with the '''Break Link''' button.

== Lat/Long ==
Here you can view the auditing of when the location's co-ordinates were automatically processed.

[[Image:loc_latlong.png|800px]]

As described earlier in this document, C-TMS can be integrated with an online web service to automatically set the latitude and longitude values against a location.

== Preferred Carriers ==
You can use this tab to set preferred carriers and the preference (priority).

This is required for some scheduling engine processes, in order to determine whether a route for a carrier can be used from this location.

== Location Usage ==
You can maintain location usage here.

Location usage helps filter location data automatically depending on which customer or customer group your user has been configured to see.

Location usage can be by customer group or individual customer.

You can allocate location usage here by double-clicking on the location usage available section.

You can remove location usage here by double-clicking on the location usage allocated section.

You can also add or remove all location usage allocations by using the '''Add All''' and '''Remove All''' buttons.

== Information ==
You can add notes against a location here.

Note types are set up in the [[Business Data Maintenance]] screen.

== Network ==
You can view all point to point (network) distances and times from and to this location in this tab. These are used by the planning system to determine the time between stops, and are calculated automatically.

You can also delete, edit and add new network entries here.

== MCS ==
You can maintain the configuration of your depot item scanning solution Calidus MCS here.

{{Note}} You can only configure MCS against locations of type "RDC".

The following flags may be configured:
* ''MCS Active'' - this flag controls whether C-MCS is used at this location.
* ''MCS Identifier'' - this is an identifier of the depot, used by MCS. This is displayed against items in receipt, so the user can see from which depot the items originated, to aid in unloading.
* ''Receipt Only'' - this flag controls whether the onward stops on this trip (and subsequent trips to the next RDC) are automatically debriefed with the time this stop is debriefed. If set, only the stop being receipted will be debriefed.
* ''Despatch Only'' - this flag controls whether the previous stops on this trip (and prior trips back to the previous RDC) are automatically debriefed with the time this stop is debriefed. If set, only the stop being despatched will be debriefed.
* ''Print Pallet Label'' - this flag controls whether pallets built through C-MCS at this location will use pre-printed stationary (when unchecked), or will print the label from C-MCS (when checked).
* ''Pallet Building validation'' - this flag controls the validation of pallets built through MCS. In all cases, pallets are retained until the pallet is received at the next depot location, whether this is an MCS-enabled location or not. Values are:
** "To Next RDC" - items built onto pallets at this location will be validated that they are all going to the same next depot location;
** "To Final RDC" - items built onto pallets at this location will be validated that they are all going to the same final delivery depot;
** "By Final RDC Trip" - items built onto pallets at this location will be validated that they are all being delivered on the same final delivery trip.

* ''Pallet Building Process'' - values are:
** "Continuous"
** "Single"
* ''Pallet Closure'' - this flag controls whether pallet closure is an option for the C-MCS mobile device users.
* ''Pallet Seal at Closure'' - this option controls whether Seal number will be prompted for at pallet closure. Seal numbers are stored against a pallet in the AWB/Cons reference.
* ''Trans-ship Enabled'' - this flag enables the Trans-Ship process at this location. Trans-ship processing will identify whether the item is planned out of this location on a trip and, if so, will show the user the trip and vehicle and ask them to confirm by entering the vehicle registration. For pallets on the received trip, all items on the pallet must be planned out on the same trip. Successfully trans-shipped items will be marked as despatched on the outbound trip. if any item is not planned out of this location, or not all items on a pallet are planned together, the system will inform the user that trans-ship can't be completed and the items must be despatched separately.
* ''Debrief Stop Times'' - this flag controls whether C-MCS loading or unloading will debrief the stop times at that location.
* ''Set Trip Status at Receipt'' - if checked, the system will attempt to automatically move the trip to COMPLETED status when it is completed in C-MCS.
* ''Set Trip Status at Despatch'' - if checked, the system will attempt to automatically move the trip onto the next applicable status when it is completed in C-MCS. For PLANNED or TENDERED trips, this will be ACCEPTED status. For ACCEPTED trips, this will be EN-ROUTE.

== Fleet Inspection ==
{{Note}} This functionality affects only Vehicle Fleet Maintenance systems.

A customer's location's fleet of vehicles has a checking period. This could differ per customer location i.e. a hub depot might check once a month, a radial depot might check once every three months.

The period could differ for each location for the customer. So, a hub location (with a large number of vehicles that pass through and work regularly) might require checking more regularly than a small depot with minimal vehicles and lower runs.

The period for checking may be rolling or fixed. I.e. check 90% of vehicles in any 3-month period from any date or check 90% of vehicles between a fixed date range.

The Calidus systems will support a fixed period against the location only, consisting of:
* A start date.
* A period type, of the following values only:
** Calendar month.
** Days.
* A period value, consisting of a numeric entry.

[[Image:loc_fleet1.png|800px]]

For example, if the period value was 30 and the type was Days, if this was a fixed period that started 1st February (non-leap year), it would end 2nd March. The next period would begin 3rd March.

If the period was 1 calendar month fixed, that starts 1st February (non-leap year), it would end 28th February. The next period would begin 1st March and end 31st March.

The period start date and length will be determined when the inspection reports are run, determined by the date entered when the report is run.

== Route Details ==
{{Note}} This is specific to the Fixed Drop Scheduling Engine.

You can maintain the route and drop number for this location on this tab. This defines which fixed routes the location is on, and what drop number it should be on.
You can also specify whether the route/drop identified here is for use on bank holidays only.

== Location Windows ==
Location windows can be added or amended using the location windows tab.

[[Image: loc_window1.png|800px]]

Windows can be Added by pressing the '''New''' button.

[[Image: loc_window2.png|800px]]

* Day must be be between 1 and 7.
* Both windows must be entered in a HH24:MI format.
* Duplicate values are not allowed.
* Windows must not overlap.

Windows can be edited by pressing the '''Edit''' button.

[[Image: loc_window3.png|800px]]

Edited records will be validated in the same way as new records.

Windows can be removed by pressing the '''Delete''' button a confirmation message will be displayed to confirm the deletion.

[[Image: loc_window4.png|800px]]

== Imports ==
Locations may also be created or modified through the customer onboarding interface, when adding orders (through EDI, imports or manual entry) or through [[Imports]]:
* [[Customer Onboarding Interface]]
* [[Imports_Details#LOCATION|LOCATION]]
* [[Imports_Details#LOC_UPDATE|LOC_UPDATE]]
* [[Imports_Details#TI_ORDER|TI_ORDER]]

<noinclude>
[[Category:Maintenance|160]]
[[Category:C-TMS Modules|D-160]]
[[Category:C-TMS User Guide|BD-160]]
</noinclude>

FAQ

2025-12-02T15:42:33Z

Anw: Updated

CTMS Frequently Asked Questions

== How can I select what can be seen on screens? ==
* [[Layout Configuration]]

== What criteria can I use to find orders? ==
* [[New_Order#Order_Search]]

== What do the order statuses mean? ==
* [[Overview_-_Order_Import_and_Handling]]

== How can I Rebook an Order? ==
* [[New_Order#Re-booking_Orders]]
* [[Trip_Debrief#Rebook_Process]]

== How can I add additional References to an Order? ==
* [[New_Order#Add_Details_Tab]]

== How can I see the Revenue generated against an order? ==
* [[New_Order#Finance_Tab]]
* [[New_Order#Order_Search]]

== How can I see the trips on which an order is scheduled? ==
* [[New_Order#Trip_Detail_Tab]]
* [[Trip Overview (Waterfall)]]

== How do I manually create a new trip? ==
* [[Planning#Create_New_Trip]]

== How do I assign resources to a trip? ==
* [[Planning#Assign Resources]]
* [[Trip Overview (Waterfall)]]
* [[Trip Overview (Waterfall)#Allocate_Resources]]

== How do I put an order onto a trip that has already been created? ==
* [[Planning#Apply to Trip/Apply to Stop]]

== How do I check that everything is OK on a trip? ==
* [[Planning#Revalidate Trip]]

== How do I force the system to manually recalculate distances and times? ==
* [[Planning#Recalculate Distance and Time]]

== How do I set or reset a trip status? ==
* [[Overview_-_Order_Import_and_Handling]]
* [[Planning#Set Trip Status]]
* [[Trip Overview (Waterfall)#Set_Trip_Status]]

== How do I manipulate a trip? ==
* [[Planning#Manipulating a Trip]]

== How to I change the order of stops on a trip? ==
* [[Planning#Manoeuvre Stops]]
* [[Planning#Move Stop]]

== How do I merge trips together? ==
* [[Planning#Merge Trip]]

== How do I split a trip into smaller trips? ==
* [[Planning#Split Trip]]

== How do I delete a trip I don't want anymore? ==
* [[Planning#Delete Trip]]

== How do I add a stop to a trip? ==
* [[Planning#Insert Stop]]
* [[Planning#Append Stop]]

== How do I over-ride the calculated stop times? ==
* [[Planning#Over-riding Stop Times]]
* [[Planning#Wait_Times]]

== How do I remove orders from a trip? ==
* [[Planning#Removing Order(s)]]
* [[Planning#Delete Stop]]
* [[Planning#Unschedule Orders]]

== How do I change order details when the order is already on a trip? ==
* [[Planning#Change Order Details (whilst on a trip)]]
* [[Planning#Amending Order Values]]

== How do I transfer orders from 1 trip to another? ==
* [[Planning#Transfer Order(s)]]

== How do I move an unscheduled order to a new schedule? ==
* [[Planning#Move to Schedule]]
* [[Planning#Carry Forward]]

== How do I manually cross-dock an order between depots? ==
* [[Planning#Creating Trips via Crossdocks]]

== How do I Pass a Depot Trip to Another Depot or Carrier? ==
* [[Planning#Pass a Depot Trip to Another Depot or Carrier]]

== How do I change a driver on a trip? ==
* [[Planning#Change a Driver on a Trip]]
* [[Trip_Overview_(Waterfall)#Allocate_Resources]]

== Why is my time and distance zero between trip stops? ==
This is controlled by the Network table. This should be automatically calculated by your system based on the GPS co-ordinates of the location, which themselves should be automatically calculated.

* Find your locations of the two adjacent stops.
* In the Network screen, enter your first location in the criteria and find. Then check whether there is an entry for the second location

* If there is no entry between those locations, that is why no distance and time.

That may be because of the Location GPS co-ordinates:

* Go to the location screen.
* Find the locations in sequence.
* Check that the locations have a GPS co-ordinate against them.
* If they do, then check whether they are the exact same co-ordinate - if they are, change one.

If they have GPS co-ordinates, then this may be to do with the trailer on the trip,

* You can check this by removing the trailer and trailer type from the trips.
* Alternatively, check the trailer type in the Resources screen.
* If the drive time modifier (DT Mod) is 0, this should be changed to 1 (normal drive time), or a positive value that will be used to modify the drive time (less than 1 = faster, greater than 1 = slower).

Reference:

* [[System Parameters List]] - HERE Maps parameters.

* [[Network]]
* [[Resources]] screen, [[Trailer Types]] tab.
* [[Locations]], main tab

== How do I set up a new user? ==
* [[Access Control / User Maintenance#Creating a New User]]

== How do I edit a user? ==
* [[Access Control / User Maintenance#Editing a New User]]

== How do I change a user password? ==
* [[Access Control / User Maintenance#Change User Password]]

== How do I assign screens or functions to a user? ==
* [[Access Control / User Maintenance#Editing a Group]]
* [[Access Control / User Maintenance#Group Maintenance – Accessible Functionality]]
* [[Access Control / User Maintenance#Users and Groups]]
* [[Access Control / User Maintenance#Adding a User to Group]]

== I'm getting an import error about checksum ==
An error along the lines of the following is displayed when you try to upload an import file:
"A file with checksum value xxxxxx has previously been loaded."

This is a protective part of the import process - a unique checksum is generated from the filename and content, and is compared to any previous uploads, to prevent repeated uploads of the same data, which may cause problems to import processes and duplicated data.

If you are sure that the data is correct and want to import anyway, you can change the filename being uploaded or append and extra content column (e.g. ,1) to the end of one of the import lines - this will change the checksum and the file will then upload.

== How can I update or fix the planning region of a location? ==
If you have changed your postal/planning region setup, you may need to update your locations.

* Find the location in the ''Locations'' form.
* Click '''Update''' - this should update your location from the planning/post region mapping.

If you want to fix the location to a particular planning region outside of the mapping, that's possible too. It’s just a checkbox against the locations.

* Find the location in the ''Locations'' form.
* Change the ''Planning Reg'' value to what you want – you can use a lookup.
* Click the ''Special'' tab.
* Check the “''Retain Planning Region''” box.
* Click '''Save'''.

You can do several locations in sequence that way – the ''Special'' tab will stay focussed as you move between locations.

See here for details of the Locations form:

[[Locations#Special|https://calidusassist.adcservices.apteancloud.com/calidus-assist/MTS/index.php/Locations#Special]]

<noinclude>
[[Category:FAQ]]
</noinclude>

FAQ

2025-12-02T15:02:25Z

Anw: Added retain planning region FAQ

CTMS Frequently Asked Questions

== How can I select what can be seen on screens? ==
* [[Layout Configuration]]

== What criteria can I use to find orders? ==
* [[New_Order#Order_Search]]

== What do the order statuses mean? ==
* [[Overview_-_Order_Import_and_Handling]]

== How can I Rebook an Order? ==
* [[New_Order#Re-booking_Orders]]
* [[Trip_Debrief#Rebook_Process]]

== How can I add additional References to an Order? ==
* [[New_Order#Add_Details_Tab]]

== How can I see the Revenue generated against an order? ==
* [[New_Order#Finance_Tab]]
* [[New_Order#Order_Search]]

== How can I see the trips on which an order is scheduled? ==
* [[New_Order#Trip_Detail_Tab]]
* [[Trip Overview (Waterfall)]]

== How do I manually create a new trip? ==
* [[Planning#Create_New_Trip]]

== How do I assign resources to a trip? ==
* [[Planning#Assign Resources]]
* [[Trip Overview (Waterfall)]]
* [[Trip Overview (Waterfall)#Allocate_Resources]]

== How do I put an order onto a trip that has already been created? ==
* [[Planning#Apply to Trip/Apply to Stop]]

== How do I check that everything is OK on a trip? ==
* [[Planning#Revalidate Trip]]

== How do I force the system to manually recalculate distances and times? ==
* [[Planning#Recalculate Distance and Time]]

== How do I set or reset a trip status? ==
* [[Overview_-_Order_Import_and_Handling]]
* [[Planning#Set Trip Status]]
* [[Trip Overview (Waterfall)#Set_Trip_Status]]

== How do I manipulate a trip? ==
* [[Planning#Manipulating a Trip]]

== How to I change the order of stops on a trip? ==
* [[Planning#Manoeuvre Stops]]
* [[Planning#Move Stop]]

== How do I merge trips together? ==
* [[Planning#Merge Trip]]

== How do I split a trip into smaller trips? ==
* [[Planning#Split Trip]]

== How do I delete a trip I don't want anymore? ==
* [[Planning#Delete Trip]]

== How do I add a stop to a trip? ==
* [[Planning#Insert Stop]]
* [[Planning#Append Stop]]

== How do I over-ride the calculated stop times? ==
* [[Planning#Over-riding Stop Times]]
* [[Planning#Wait_Times]]

== How do I remove orders from a trip? ==
* [[Planning#Removing Order(s)]]
* [[Planning#Delete Stop]]
* [[Planning#Unschedule Orders]]

== How do I change order details when the order is already on a trip? ==
* [[Planning#Change Order Details (whilst on a trip)]]
* [[Planning#Amending Order Values]]

== How do I transfer orders from 1 trip to another? ==
* [[Planning#Transfer Order(s)]]

== How do I move an unscheduled order to a new schedule? ==
* [[Planning#Move to Schedule]]
* [[Planning#Carry Forward]]

== How do I manually cross-dock an order between depots? ==
* [[Planning#Creating Trips via Crossdocks]]

== How do I Pass a Depot Trip to Another Depot or Carrier? ==
* [[Planning#Pass a Depot Trip to Another Depot or Carrier]]

== How do I change a driver on a trip? ==
* [[Planning#Change a Driver on a Trip]]
* [[Trip_Overview_(Waterfall)#Allocate_Resources]]

== Why is my time and distance zero between trip stops? ==
This is controlled by the Network table. This should be automatically calculated by your system based on the GPS co-ordinates of the location, which themselves should be automatically calculated.

* Find your locations of the two adjacent stops.
* In the Network screen, enter your first location in the criteria and find. Then check whether there is an entry for the second location

* If there is no entry between those locations, that is why no distance and time.

That may be because of the Location GPS co-ordinates:

* Go to the location screen.
* Find the locations in sequence.
* Check that the locations have a GPS co-ordinate against them.
* If they do, then check whether they are the exact same co-ordinate - if they are, change one.

If they have GPS co-ordinates, then this may be to do with the trailer on the trip,

* You can check this by removing the trailer and trailer type from the trips.
* Alternatively, check the trailer type in the Resources screen.
* If the drive time modifier (DT Mod) is 0, this should be changed to 1 (normal drive time), or a positive value that will be used to modify the drive time (less than 1 = faster, greater than 1 = slower).

Reference:

* [[System Parameters List]] - HERE Maps parameters.

* [[Network]]
* [[Resources]] screen, [[Trailer Types]] tab.
* [[Locations]], main tab

== How do I set up a new user? ==
* [[Access Control / User Maintenance#Creating a New User]]

== How do I edit a user? ==
* [[Access Control / User Maintenance#Editing a New User]]

== How do I change a user password? ==
* [[Access Control / User Maintenance#Change User Password]]

== How do I assign screens or functions to a user? ==
* [[Access Control / User Maintenance#Editing a Group]]
* [[Access Control / User Maintenance#Group Maintenance – Accessible Functionality]]
* [[Access Control / User Maintenance#Users and Groups]]
* [[Access Control / User Maintenance#Adding a User to Group]]

== I'm getting an import error about checksum ==
An error along the lines of the following is displayed when you try to upload an import file:
"A file with checksum value xxxxxx has previously been loaded."

This is a protective part of the import process - a unique checksum is generated from the filename and content, and is compared to any previous uploads, to prevent repeated uploads of the same data, which may cause problems to import processes and duplicated data.

If you are sure that the data is correct and want to import anyway, you can change the filename being uploaded or append and extra content column (e.g. ,1) to the end of one of the import lines - this will change the checksum and the file will then upload.

== How can I fix the planning region of a location? ==
It’s just a checkbox against the locations.

* Find the location in the ''Locations'' form.
* Change the ''Planning Reg'' value to what you want – you can use a lookup.
* Click the ''Special'' tab.
* Check the “''Retain Planning Region''” box.
* Click '''Update'''.

You can do several locations in sequence that way – the ''Special'' tab will stay focussed as you move between locations.

See here for details of the Locations form:

[[Locations#Special|https://calidusassist.adcservices.apteancloud.com/calidus-assist/MTS/index.php/Locations#Special]]

<noinclude>
[[Category:FAQ]]
</noinclude>

Drivers

2025-11-14T12:48:49Z

Anw: Minor formatting change

This allows a record to be kept of each driver in the system. Typically, this allows reports to show which drivers are assigned to which trips.

<center>[[Image:res_drivers.png|800px]]</center>

In much the same way as the "Trailers" tab enables specific trailer resources to be set up, the "Drivers" tab enables the actual drivers to be set up so that they can be allocated to trips with vehicles.

Isotrak's Manifest system, used by some client's transport personnel, allows drivers to be assigned to trips. Isotrak updates C-TMS with this information as trips are assigned to and accepted by drivers.

There are several actions available through buttons on the bottom of the screen:
* '''Diary Exceptions''' - see section below.
* '''Show Shifts''' - see section below.
* '''Show Attributes''' - see section below.
* '''New''' will allow a new activity to be entered for the current resource.
* '''Edit''' will allow editing of a record. When a resource is marked as unavailable, on holiday, absent or off the road if it has been allocated to any subsequent activity a message will be displayed warning the user they may need to take action to remove resources from trips etc.
* '''Delete''' will display a confirmation message and once confirmed will remove the record
* '''Apply''' allows you to save any changes you have made.
* '''Close''' will save any changes and return you to the main resource diary page.

=== Adding a New Driver ===
New drivers can be entered using the '''New''' button and existing drivers either edited or inactivated using the '''Edit''' button.

From the Drivers box click '''New''':

<center>[[Image:res_drivers.png|800px]]</center>

Enter the "Id" this is a free text field and would normally be the drivers payroll number, "Job Title" which is a system value and will generally be "DRIVER" enter D and return, "Forename" and "Surname" are both free text fields. A driver can be set to indicate that they have access to a Tom Tom or WEBFLEET device.

You can allocate to resources (carriers) here, as well as entering attributes for the driver - both of these processes are covered in sections below.

Click '''Save''' and the system will confirm the driver has been saved, but needs to be linked to a carrier. Click '''OK'''. You can then enter a subsequent driver or click '''Cancel''' to return to the main form.

=== Allocate to Resources ===
To allocate to resources, select the driver and from the Allocation to Resources section, click '''New'''. Allocate a carrier id to the driver. This will be the carrier id of the depot where the driver is based.

<center>[[Image:res_drivers_2.png|800px]]</center>

Click '''Save'''. The driver is now allocated to the carrier id. The driver will now be available to assign to trips using the chosen carrier.

Note that you can also specify the following here:
* Hub Location - a location where the driver is based, for example, another depot, home, etc. CTMS will use this location in preference to the carrier hub location when creating trips.
* Vehicle ID - where the driver has a default vehicle, you may specify this here. Note that this affects ONLY the CTL Call Logging screen, not core CTMS.

=== Making a Driver Inactive ===
If the driver id is no longer required you are able to make it inactive. This follows the same process as making a trailer id inactive.

Using the search buttons find the driver you want to make inactive and click '''Edit''' from the Allocation to Resources box.

Click in the "Inactive" check box, so a tick appears.

Click '''Save'''. The driver id is now inactive.

=== Driver Attributes ===
Additionally, more detailed driver attributes can be recorded. Pressing the Attributes button displays a popup window in which the specific attributes can be entered:

<center>[[Image:res_drivers_3.png|800px]]</center>

Each section of the screen has three buttons:
* '''New''' – See Below
* '''Edit''' - See Below
* '''Delete''' – A message will be displayed asking the user to confirm the deletion, once confirmation is received the current record will be removed from the database.

A '''Close''' button is included in the bottom of the screen, when pressed if there are any un-committed changes a message will be displayed to ask the user to Save or abandon the changes before the screen is closed.

==== New/Edit ====
The '''New''' or '''Edit''' buttons are pressed a popup window will be displayed to allow creation or updating of a record.

==== Driver Details ====
<center>[[Image:res_drivers_3a.png]]</center>

The address fields are free format text and the DOB and start date will be date values.

==== Qualifications ====
<center>[[Image:res_drivers_3b.png]]</center>

The Qualification field is free format text and the "Valid From" and "Valid To" are both Date fields.

==== Vehicle Types ====
<center>[[Image:res_drivers_3c.png]]</center>

The Vehicle type will be selected from a list of values from the Trailer Type master data.

In all cases two buttons are included
* '''OK''' – validate and commit changes then close the popup.
* '''Cancel''' – display a conformation message if there are uncommitted changes, once confirmation is received changes will be rolled back and the popup window closed.

These driver attributes can also be directly accessed for view and edit from the main Drivers tab using the '''Show Attributes''' button at the bottom of the screen.

=== Diary Exceptions ===
The Diary Exception button displays a popup window showing the activity a current resource has been allocated to, along with any diary exceptions added for that driver, such as holidays, sickness, etc.

The data will be displayed in descending date and will be display only when first opened:

<center>[[Image:res_drivers_4.png|800px]]</center>

There are four buttons on the screen:
* '''New''' will allow a new activity to be entered for the current resource.
* '''Edit''' will allow editing of a record. When a resource is marked as unavailable, on holiday, absent or off the road if it has been allocated to any subsequent activity a message will be displayed warning the user they may need to take action to remove resources from trips etc.
* '''Delete''' will display a confirmation message and once confirmed will remove the record
* '''Close''' will save any changes and return you to the main resource diary page.

Note that the exceptions screen will be used to setup manual exceptions to the driver’s shift availability, for example, the driver is unavailable for transport work while attending a training session.

To create a new record press the '''New''' button and enter the reason for the exception. Then enter the start and end date and time. The duration is calculated automatically.

Press the '''Save''' button to commit the record to the database. To delete a record press the '''Delete''' button.

{{Note}} Exceptions records created by planned trip activity related to the vehicle cannot be deleted.

Pressing the '''Close''' button will return you to the main screen.

=== View Shifts ===
You can view drivers shifts from here.

The '''Show Shifts''' button will display a new popup window to display the drivers shift patterns:

<center>[[Image:res_drivers_5.png|800px]]</center>

All data is display only.

The following actions are available from the buttons on the bottom of the screen:
* The '''Close''' button will return you to the main screen.
* The '''Delete''' button will display a confirmation message to confirm the delete. Once deletion is confirmed the record will be removed.

This data is related to the "Shift Patterns" data which is maintained in the "Business Data Maintenance" screen. This also provides functionality to generate shifts against the drivers. Further information can be found in the user guide covering the [[Business Data Maintenance]] screen.

=== Imports ===
Drivers (and associated reference data) may also be imported through [[Imports]]:
* [[Imports_Details#DRIVERS|DRIVERS]]
* [[Imports_Details#DRIVER_SHIFT|DRIVER_SHIFT]]
* [[Imports_Details#PERSON|PERSON]]

BI Data Extract Guide

2025-11-04T09:18:54Z

Anw: Minor formatting change

=Introduction=

Data exports are available to populate BI or MIS systems. These exports are based upon all columns in the following tables within the CTMS database.

CNT_CHARGE
CNT_CONTRACT
CNT_CHARGE_TIER
CNT_TARIFF
GEO_LOCATION
GEO_LOCATION_USAGE
IMP_DECODE_ENTRY
INT_BOOKING_DETAIL
ORG_CUSTOMER
RES_CARRIER
RES_CARRIER_TYPE
RES_PERSON
RES_TRAILER_TYPE
SAP_PRODUCT_ITEM
SCH_BOOKING
SCH_HAULAGE_ACTIVITY
SCH_ORD
SCH_ORD_NON_CONFORM
SCH_ORDER_LINE
SCH_ORDER_ITEMS
SCH_ORDER_ITEMS_REASONS
SCH_PRODUCT_SUMMARY
SCH_REASON_CODE
SCH_SCHEDULE
SCH_TRIP
SCH_TRIP_STOP
Note: Other tables are available and may be exported – these are the most common. The tables and fields exported can be configured (added to or removed, based on customer processing requirements).

= Schematic =

The following schemas indicate the links between the tables (Primary & Foreign keys)

<gallery widths="600" heights="800px" perrow="1">
Image:BI_Data_Extract_Links_1.png
Image:BI_Data_Extract_Links_2.png
Image:BI_Data_Extract_Links_3.png
Image:BI_Data_Extract_Links_4.png
Image:BI_Data_Extract_Links_5.png
</gallery>

= Data Fields =

The tables are listed. It is expected that each column will be delimited with a '®' symbol and that extract can be scheduled and run on with records created or updated in the last 4 days.

{{Note|* Up to 50 columns may be configured per extract.
* The list below shows common fields for the tables, and these may be selected from for the 50 columns.
* If more than 50 columns are required, then an additional extract for that table may be defined.
}}

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
CNT_CHARGE CHRG_PARAM VARCHAR2(12) 1
VALUE NUMBER(23,5) 2
CREATED_BY VARCHAR2(40) 3
CREATED_DATE DATE 4
UPDATED_BY VARCHAR2(40) 5
UPDATED_DATE DATE 6
CHARGE_ID NUMBER(20,0) 7
CONDITION_NAME VARCHAR2(12) 8
CONDITION_VALUE VARCHAR2(12) 9
TIER_ID NUMBER(12,0) 10
CHARGEABLE_QUANTITY NUMBER(12,0) 11
CHARGE_TYPE VARCHAR2(12) 12
EFFECTIVE_FROM DATE 13
EXPIRY_DATE DATE 14

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
CNT_CHARGE_TIER UPPER_LIMIT NUMBER(12,2) 1
TARIFF_ID NUMBER(20,0) 2
TIER_NAME VARCHAR2(20) 3
MIN_CHARGE NUMBER(20,2) 4
MAX_CHARGE NUMBER(20,2) 5
CREATED_BY VARCHAR2(40) 6
CREATED_DATE DATE 7
UPDATED_BY VARCHAR2(40) 8
UPDATED_DATE DATE 9
TIER_ID NUMBER(12,0) 10
ADD_UPPER_LIMIT NUMBER(12,2) 11
ADD_TIER_NAME VARCHAR2(20) 12

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
CNT_CONTRACT CONTRACT_ID NUMBER(20,0) 1
CONTRACT_TYPE VARCHAR2(12) 2
LOCAL_PARTY VARCHAR2(12) 3
COUNTER_PARTY VARCHAR2(12) 4
EFFECTIVE_FROM DATE 5
CREATED_BY VARCHAR2(40) 6
CREATED_DATE DATE 7
UPDATED_BY VARCHAR2(40) 8
UPDATED_DATE DATE 9
DEFAULT_CCY VARCHAR2(3) 10
EXPIRY_DATE DATE 11
ORDER_MOVEMENT_RATE VARCHAR2(1) 12

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
CNT_TARIFF CONTRACT_ID NUMBER(20,0) 1
DEL_TYPE VARCHAR2(35) 2
TARIFF_ID NUMBER(20,0) 3
TARIFF_NAME VARCHAR2(50) 4
TIER_UNITS VARCHAR2(12) 5
EXPIRY_DATE DATE 6
CREATED_BY VARCHAR2(40) 7
CREATED_DATE DATE 8
UPDATED_BY VARCHAR2(40) 9
UPDATED_DATE DATE 10
CCY_CODE VARCHAR2(3) 11
CHARGE_TYPE VARCHAR2(12) 12
EFFECTIVE_FROM DATE 13
SEQUENCE NUMBER(5,0) 14
ADD_TIER_UNITS VARCHAR2(12) 15

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
GEO_LOCATION LOCATION_ID VARCHAR2(12) 1
DEPOT VARCHAR2(12) 2
LOCATION_NAME VARCHAR2(35) 3
EXT_REF VARCHAR2(50) 4
ROUTE_CODE VARCHAR2(12) 5
ADDRESS_LINE1 VARCHAR2(50) 6
ADDRESS_LINE2 VARCHAR2(50) 7
ADDRESS_LINE3 VARCHAR2(50) 8
TOWN VARCHAR2(50) 9
COUNTY VARCHAR2(50) 10
COUNTRY VARCHAR2(50) 11
COUNTRY_CODE VARCHAR2(3) 12
POSTCODE VARCHAR2(9) 13
POSTAL_REGION VARCHAR2(15) 14
PHONE VARCHAR2(50) 15
FAX VARCHAR2(50) 16
LATITUDE NUMBER(9,5) 17
LONGITUDE NUMBER(9,5) 18
LOADING_RATE VARCHAR2(12) 19
UNLOADING_RATE VARCHAR2(12) 20
SCHEDULE_OFFSET NUMBER(2,0) 21
RESPONSIBLE_COST_CENTRE VARCHAR2(50) 22
PARENT_LOC_ID VARCHAR2(12) 23
VENDOR_CODE VARCHAR2(12) 24
OPEN_MON VARCHAR2(5) 25
CLOSE_MON VARCHAR2(5) 26
OPEN_FRI VARCHAR2(5) 27
CLOSE_FRI VARCHAR2(5) 28
CREATE_EMPTIES VARCHAR2(1) 29
COMMENTS VARCHAR2(255) 30
INACTIVE VARCHAR2(1) 31
TRAILER_TYPE VARCHAR2(35) 32
ALT_COLL_LOC VARCHAR2(12) 33
ALT_DEL_LOC VARCHAR2(12) 34
DEFAULT_XDOCK VARCHAR2(12) 35
DFLT_SC_HANGING VARCHAR2(12) 36
DFLT_SC_BOXED VARCHAR2(12) 37
PROFILE_ID VARCHAR2(12) 38
CREATED_BY VARCHAR2(40) 39
CREATED_DATE DATE 40
UPDATED_BY VARCHAR2(40) 41
UPDATED_DATE DATE 42
CONTROL_TOWER VARCHAR2(1) 43
PLANNING_REGION VARCHAR2(5) 44
COST_CENTRE_NAME VARCHAR2(12) 45

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
GEO_LOCATION_USAGE LOCATION_ID VARCHAR2(12) 1
USAGE_TYPE VARCHAR2(12) 2
USAGE_ID VARCHAR2(12) 3
CREATED_BY VARCHAR2(40) 4
CREATED_DATE DATE 5
UPDATED_BY VARCHAR2(40) 6
UPDATED_DATE DATE 7

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
IMP_DECODE_ENTRY DECODE_NAME VARCHAR2(35) 1
SOURCE_VALUE VARCHAR2(256) 2
TARGET_VALUE VARCHAR2(256) 3
CUSTOMER_ID VARCHAR2(12) 4
DECODE_TYPE VARCHAR2(12) 5
CREATED_BY VARCHAR2(40) 6
CREATED_DATE DATE 7
UPDATED_BY VARCHAR2(40) 8
UPDATED_DATE DATE 9

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
INT_BOOKING_DETAIL INT_RECORD_ID VARCHAR2(100) 1
REC_NUM NUMBER(22,0) 2
FROM_LOC VARCHAR2(12) 3
TO_LOC VARCHAR2(12) 4
QUANTITY NUMBER(20,5) 5
DEL_DATE VARCHAR2(12) 6
PRODUCT_TYPE VARCHAR2(12) 7
DU_TYPE VARCHAR2(12) 8
BOOKING_REF VARCHAR2(20) 9
TRANSHIP_IND VARCHAR2(1) 10
RECORD_STATUS VARCHAR2(10) 11
VALIDATION_ERROR VARCHAR2(2000) 12
CREATED_DATE DATE 13
CREATED_BY VARCHAR2(40) 14
UPDATED_DATE DATE 15
UPDATED_BY VARCHAR2(40) 16
IDENTIFIER VARCHAR2(10) 17
ACTION VARCHAR2(1) 18
PRODUCT_ITEM VARCHAR2(100) 19
UOM VARCHAR2(3) 20
DEL_PRIORITY VARCHAR2(2) 21
HANDLING_CODE1 VARCHAR2(2) 22
HANDLING_CODE2 VARCHAR2(2) 23
HANDLING_CODE3 VARCHAR2(2) 24
CARRIER_CODE VARCHAR2(3) 25
INSP_REQ VARCHAR2(2) 26
TEST_REQ VARCHAR2(2) 27
WAREHOUSE_CODE VARCHAR2(3) 28
STORAGE_CODE VARCHAR2(3) 29
SOURCE_SYSTEM VARCHAR2(25) 30
DU_QTY NUMBER(24,4) 31
WEIGHT NUMBER(12,2) 32
VOLUME NUMBER(20,5) 33
BKG_PLANT VARCHAR2(4) 34
BKG_STORAGE_LOC VARCHAR2(4) 35
BKG_SHELF_LIFE DATE 36
BKG_REQUESTOR VARCHAR2(20) 37
BKG_TELEPHONE VARCHAR2(30) 38
BKG_ACCOUNT_NO VARCHAR2(20) 39
BKG_BUILDING VARCHAR2(10) 40
BKG_ROOM VARCHAR2(8) 41
BKG_COMMENTS VARCHAR2(200) 42
ASN_HANDLING_UNIT VARCHAR2(20) 43
OLD_MAT_NO VARCHAR2(18) 44
CHBNO VARCHAR2(30) 45
LAB_TEST VARCHAR2(80) 46
SHELF_LIFE_IND VARCHAR2(1) 47
MIN_REM_SHELF VARCHAR2(4) 48
TEMP_COND VARCHAR2(20) 49
REQ_NAME VARCHAR2(40) 50
REQ_PHONE VARCHAR2(30) 51
REQ_ACC_NO VARCHAR2(20) 52
REQ_BUILD VARCHAR2(20) 53
REQ_ROOM VARCHAR2(10) 54
COMMENTS VARCHAR2(80) 55
ADD_DATA_1 VARCHAR2(40) 56
ADD_DATA_2 VARCHAR2(40) 57
ADD_DATA_3 VARCHAR2(40) 58
BKG_ADD_DATA_1 VARCHAR2(40) 59
BKG_ADD_DATA_2 VARCHAR2(40) 60
BKG_ADD_DATA_3 VARCHAR2(40) 61
PRODUCT_DESC VARCHAR2(100) 62

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
ORG_CUSTOMER CUSTOMER_ID VARCHAR2(12) 1
CUSTOMER_NAME VARCHAR2(50) 2
CONTACT_NAME VARCHAR2(50) 3
LOCATION_ID VARCHAR2(12) 4
MTM_CUST_CODE VARCHAR2(2) 5
SELF_BILL VARCHAR2(1) 6
CUST_GROUP VARCHAR2(12) 7
COST_CENTRE_NAME VARCHAR2(12) 8
VAT_COUNTRY VARCHAR2(3) 9
VAT_REG_NO VARCHAR2(50) 10
CREATED_BY VARCHAR2(40) 11
CREATED_DATE DATE 12
UPDATED_BY VARCHAR2(40) 13
UPDATED_DATE DATE 14
COUNTRY VARCHAR2(3) 15
USE_LATE_ORDERS VARCHAR2(1) 16
USE_MANUAL_ORDERS VARCHAR2(1) 17
USE_URGENT_ORDERS VARCHAR2(1) 18
USE_TRANSACTION_CHARGING VARCHAR2(1) 19
TYPE VARCHAR2(12) 20
LATE_ORDER_DAYS_THRESHOLD NUMBER(5) 21
INT_ORD_TO_LOGNET VARCHAR2(1) 22
UNISON_IF_VALUE VARCHAR2(3) 23
TOK_POD_AVAIL VARCHAR2(1) 24
CONSOLIDATE_ORDERS VARCHAR2(1) 25
CONSOL_ALLOC_METHOD VARCHAR2(12) 26
ORDER_REVENUE_CHARGING_TYPE_ID NUMBER 27

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
RES_CARRIER CARRIER_ID VARCHAR2(12) 1
CARRIER_NAME VARCHAR2(50) 2
GROUP_NAME VARCHAR2(35) 3
COST_CENTRE_NAME VARCHAR2(12) 4
CARRIER_TYPE_ID VARCHAR2(35) 5
CURRENT_HAULAGE_UNITS NUMBER(5,0) 6
FIXED_COST_WEEKDAY NUMBER(20,2) 7
FIXED_COST_SAT NUMBER(20,2) 8
FIXED_COST_SUN NUMBER(20,2) 9
HUB_LOCATION VARCHAR2(12) 10
ENFORCE_START_AT_HUB VARCHAR2(1) 11
ENFORCE_END_AT_HUB VARCHAR2(1) 12
BARCODE_TYPE VARCHAR2(12) 13
TMS_REF VARCHAR2(12) 14
HQ_LOCATION VARCHAR2(12) 15
EXPORTFILE_TYPE VARCHAR2(12) 16
VAT_NUMBER VARCHAR2(35) 17
VAT_COUNTRY VARCHAR2(3) 18
STD_SHIFT_HOURS NUMBER(4,2) 19
STD_FACTOR NUMBER(4,2) 20
ALTERNATE_CARRIER VARCHAR2(1) 21
OVERTIME_FACTOR NUMBER(4,2) 22
MAX_SHIFT_HOURS NUMBER(4,2) 23
TRIP_THRESHOLD_HOURS NUMBER(4,2) 24
MAX_DRIVING_HOURS NUMBER(4,2) 25
ADDRESS_LINE1 VARCHAR2(35) 26
ADDRESS_LINE2 VARCHAR2(35) 27
CREATED_BY VARCHAR2(40) 28
ADDRESS_LINE3 VARCHAR2(35) 29
CREATED_DATE DATE 30
TOWN VARCHAR2(35) 31
UPDATED_BY VARCHAR2(40) 32
UPDATED_DATE DATE 33
COUNTY VARCHAR2(35) 34
COUNTRY VARCHAR2(35) 35
COUNTRY_CODE VARCHAR2(3) 36
POSTCODE VARCHAR2(9) 37
REGION VARCHAR2(2) 38
PHONE VARCHAR2(35) 39
FAX VARCHAR2(35) 40
DRIVER_BREAK_THRESHOLD_HOURS NUMBER(4,2) 41
DRIVER_BREAK_MINS NUMBER(3,0) 42
WORK_BREAK_THRESHOLD_HOURS NUMBER(4,2) 43
WORK_BREAK_MINS NUMBER(3,0) 44
DISPLAY_TYPE VARCHAR2(8) 45
PERMIT_DEBRIEF VARCHAR2(1) 46
CONTACT VARCHAR2(100) 47
WORK_STOPOVER_THRESHOLD_HOURS NUMBER(4,2) 48
STOPOVER_MINS NUMBER(3,0) 49
DRIVE_STOPOVER_THRESHOLD_HOURS NUMBER(4,2) 50

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
RES_CARRIER_TYPE CARRIER_TYPE_ID VARCHAR2(35) 1
TRIP_COST_METHOD VARCHAR2(12) 2
ORD_COST_METHOD VARCHAR2(12) 3
CREATED_BY VARCHAR2(40) 4
CREATED_DATE DATE 5
UPDATED_BY VARCHAR2(40) 6
UPDATED_DATE DATE 7

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
RES_PERSON ID NUMBER(22,0) 1
SURNAME VARCHAR2(50) 2
FORENAME VARCHAR2(50) 3
JOB_TITLE VARCHAR2(50) 4
LOCATION_ID VARCHAR2(12) 5
CREATED_BY VARCHAR2(40) 6
CREATED_DATE DATE 7
UPDATED_BY VARCHAR2(40) 8
UPDATED_DATE DATE 9

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
RES_TRAILER_TYPE TRAILER_TYPE VARCHAR2(12) 1
TEMPERATURE_TYPE VARCHAR2(12) 2
DESCRIPTION VARCHAR2(50) 3
MAX_KG NUMBER(20,2) 4
VOLUME NUMBER(20,5) 5
MAX_RPE NUMBER(8,2) 6
REFRIGERATED VARCHAR2(1) 7
TRAILER_LENGTH NUMBER(3,0) 8
COST_OF_USE NUMBER(3,0) 9
INACTIVE VARCHAR2(1) 10
RIGID VARCHAR2(1) 11
CREATED_BY VARCHAR2(40) 12
CREATED_DATE DATE 13
UPDATED_BY VARCHAR2(40) 14
UPDATED_DATE DATE 15
DRIVE_TIME_MODIFIER NUMBER(3,2) 16

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SAP_PRODUCT_ITEM PRODUCT_ITEM_ID VARCHAR2(18) 1
PRODUCT_ITEM_DESC VARCHAR2(100) 2
DEF_DU_TYPE VARCHAR2(12) 3
DEF_PRODUCT_TYPE VARCHAR2(12) 4
CREATED_BY VARCHAR2(40) 5
CREATED_DATE DATE 6
UPDATED_BY VARCHAR2(40) 7
UPDATED_DATE DATE 8

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_BOOKING SOURCE VARCHAR2(12) 1
DESTINATION VARCHAR2(12) 2
DELIVERY_DATE DATE 3
PROD_TYPE_ID VARCHAR2(12) 4
SCHEDULE_DATE DATE 5
TOTAL_WEIGHT NUMBER(12,2) 6
TOTAL_VOLUME NUMBER(20,5) 7
EFFECTIVE_WEIGHT NUMBER(12,2) 8
BOOKING_REF VARCHAR2(20) 9
COMMENTS VARCHAR2(100) 10
SPECIAL_FLAG VARCHAR2(35) 11
PLANNED VARCHAR2(1) 12
ROUTE VARCHAR2(12) 13
BROUGHT_IN VARCHAR2(1) 14
CREATED_BY VARCHAR2(40) 15
CREATED_DATE DATE 16
UPDATED_BY VARCHAR2(40) 17
UPDATED_DATE DATE 18
SCHED_NAME VARCHAR2(12) 19
TRANSHIP_IND VARCHAR2(1) 20
ORIG_PROD_TYPE VARCHAR2(12) 21

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_HAULAGE_ACTIVITY STOP_ID NUMBER(22,0) 1
SEQUENCE NUMBER(8,0) 2
OMS_REF VARCHAR2(12) 3
ACTIVITY_NAME VARCHAR2(35) 4
COMMENTS VARCHAR2(255) 5
CREATED_BY VARCHAR2(40) 6
CREATED_DATE DATE 7
UPDATED_BY VARCHAR2(40) 8
UPDATED_DATE DATE 9

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_ORD OMS_REF VARCHAR2(12) 1
ORDER_ID VARCHAR2(12) 2
STATUS VARCHAR2(12) 3
SOURCE_SYSTEM VARCHAR2(12) 4
SCHED_NAME VARCHAR2(12) 5
COST_CENTRE_NAME VARCHAR2(12) 6
CUSTOMER VARCHAR2(12) 7
DELIVERY_TYPE_ID VARCHAR2(35) 8
TEMP_COMBO_ID VARCHAR2(12) 9
PARENT_ORDER VARCHAR2(12) 10
TEMPLATE_ID VARCHAR2(35) 11
FROM_LOC VARCHAR2(12) 12
TO_LOC VARCHAR2(12) 13
ORIG_FROM_LOC VARCHAR2(12) 14
FINAL_TO_LOC VARCHAR2(12) 15
CONTRACT_FROM_LOC VARCHAR2(12) 16
CONTRACT_TO_LOC VARCHAR2(12) 17
TARGET_TIME VARCHAR2(5) 18
EARLY_AVAIL DATE 19
LATE_AVAIL DATE 20
EARLY_DEL DATE 21
LATE_DEL DATE 22
TARGET VARCHAR2(12) 23
DISTANCE NUMBER(12,2) 24
TOTAL_RPE_QTY NUMBER(8,2) 25
TOTAL_WEIGHT NUMBER(20,5) 26
TOTAL_VOLUME NUMBER(20,5) 27
TOTAL_PALLETS NUMBER(24,4) 28
TOTAL_PIECES NUMBER(24,4) 29
TOTAL_EFFECTIVE_WEIGHT NUMBER(20,2) 30
TOTAL_ACTUAL_RPE_QTY NUMBER(8,2) 31
CONTRACTUAL_WEIGHT NUMBER(20,2) 32
CONTRACTUAL_PALLETS NUMBER(24,4) 33
CONTRACTUAL_RPE_QTY NUMBER(8,2) 34
ACTUAL_WEIGHT NUMBER(20,2) 35
ACTUAL_VOLUME NUMBER(20,5) 36
ACTUAL_PALLETS NUMBER(24,4) 37
ACTUAL_PIECES NUMBER(24,4) 38
ACTUAL_EFFECTIVE_WEIGHT NUMBER(20,2) 39
DELIVERED_TIME DATE 40
ORD_STD_COST NUMBER(20,2) 41
DO_NOT_CALC_STD_COST VARCHAR2(1) 42
REVENUE_STATUS VARCHAR2(1) 43
ORD_REVENUE NUMBER(20,2) 44
REVENUE_VAT NUMBER(20,2) 45
COST_STATUS VARCHAR2(1) 46
ORD_COST NUMBER(20,2) 47
COST_VAT NUMBER(20,2) 48
COST_ALLOC NUMBER(20,2) 49
ORD_REVENUE_VS NUMBER(20,2) 50
PROFIT NUMBER(20,2) 51
MARGIN NUMBER(8,2) 52
ORD_TIER_NAME VARCHAR2(50) 53
SJC_DATA VARCHAR2(2000) 54
EXTERNAL_REF VARCHAR2(20) 55
COMMENTS VARCHAR2(2000) 56
DELIVERY_INSTRUCTIONS VARCHAR2(60) 57
POD_NAME VARCHAR2(50) 58
LAST_ERROR VARCHAR2(256) 59
SEND_TO_MTM VARCHAR2(1) 60
GROUP_NAME VARCHAR2(12) 61
TRANSCODE VARCHAR2(1) 62
MTM_SPLIT_ID VARCHAR2(20) 63
MTM_FLF VARCHAR2(1) 64
CONF_NO VARCHAR2(12) 65
SHIPPING_REF VARCHAR2(12) 66
CREATED_USER VARCHAR2(50) 67
CREATED_DATE DATE 68
CHANGED_USER VARCHAR2(50) 69
CHANGED_DATE DATE 70
INFO VARCHAR2(255) 71
CREATE_EMPTIES VARCHAR2(1) 72
NUM_ADV_NOTES NUMBER(4,0) 73
AETC_REF VARCHAR2(20) 74
DEL_POINT_REF VARCHAR2(20) 75
DROP_COUNT NUMBER(8,0) 76
COLLECTED_BY VARCHAR2(1) 77
DELIVERED_BY VARCHAR2(1) 78
POC VARCHAR2(1) 79
POD VARCHAR2(1) 80
ORDER_COMMENTS VARCHAR2(2000) 81
LANE_COMMENTS VARCHAR2(2000) 82
SCHED_DATE DATE 83
BOOKING_REF VARCHAR2(20) 84
SAVING NUMBER(20,2) 85
LATE_ORDER VARCHAR2(1) 86
MANUAL_ORDER VARCHAR2(1) 87
URGENT_ORDER VARCHAR2(1) 88
SERVICE_TYPE VARCHAR2(20) 89
SOURCE_REF VARCHAR2(50) 90
CURRENT_DEPOT VARCHAR2(12) 91
CCY_CODE VARCHAR2(3) 92
CONTAINER_NO VARCHAR2(50) 93
BILL_OF_LADING VARCHAR2(50) 94
TOTAL_CASES NUMBER(8,0) 95
NUM_ORDER_LINES NUMBER(22,0) 96
SPECIAL_INSTRUCTIONS VARCHAR2(4000) 97
BOOKED_IN VARCHAR2(1) 98
STD_COST_DATA VARCHAR2(2000) 99
ORD_REV_DATA VARCHAR2(2000) 100
INTERNAL_CHARGE_DATA VARCHAR2(2000) 101
ACTUAL_DELIVERED_PALLETS NUMBER(24,4) 102
ACTUAL_DELIVERED_PIECES NUMBER(24,4) 103
TOTAL_ACTUAL_DELIVERED_RPE_QTY NUMBER(8,2) 104
ACTUAL_DESPATCHED_PALLETS NUMBER(24,4) 105
ACTUAL_DESPATCHED_PIECES NUMBER(24,4) 106
TOTAL_ACTUAL_DESPTCHD_RPE_QTY NUMBER(8,2) 107
BOOKING_SEQ NUMBER(22,0) 108
TRANSHIP_IND VARCHAR2(1) 109
UOM VARCHAR2(3) 110
ORIGINAL_QTY NUMBER(22,0) 111
EXC_FIXED_ROUTES VARCHAR2(1) 112
DEL_PRIORITY VARCHAR2(2) 113
HANDLING_CODE1 VARCHAR2(2) 114
HANDLING_CODE2 VARCHAR2(2) 115
HANDLING_CODE3 VARCHAR2(2) 116
CARRIER_CODE VARCHAR2(3) 117
INSP_REQ VARCHAR2(2) 118
TEST_REQ VARCHAR2(2) 119
SAP_PRODUCT_ITEM VARCHAR2(18) 120
WAREHOUSE_CODE VARCHAR2(3) 121
STORAGE_CODE VARCHAR2(3) 122
EFX_REF VARCHAR2(50) 123

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_ORD_NON_CONFORM OMS_REF VARCHAR2(12) 1
ACTIVITY VARCHAR2(20) 2
REASON_CODE VARCHAR2(12) 3
COMMENTS VARCHAR2(256) 4
NON_CONFORM_ID NUMBER 5
TRIP_ID VARCHAR2(12) 6
SCHED_NAME VARCHAR2(12) 7
CREATED_DATE DATE 8
CREATED_BY VARCHAR2(50) 9
UPDATED_DATE DATE 10
UPDATED_BY VARCHAR2(50) 11

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_ORDER_LINE ORDER_LINE_ID NUMBER(20,0) 1
OMS_REF VARCHAR2(12) 2
LINE_NO NUMBER(8,0) 3
PRODUCT_TYPE VARCHAR2(12) 4
DU_TYPE VARCHAR2(12) 5
QUANTITY NUMBER(24,4) 6
WEIGHT NUMBER(20,2) 7
CUBE NUMBER(20,5) 8
ACTUAL_QUANTITY NUMBER(24,4) 9
ACTUAL_WEIGHT NUMBER(20,2) 10
ACTUAL_CUBE NUMBER(12,5) 11
ACTUAL_RPE_QTY NUMBER(8,2) 12
EFFECTIVE_WEIGHT NUMBER(20,2) 13
ACTUAL_EFFECTIVE_WEIGHT NUMBER(20,2) 14
SCH_PROD_SUM_ID NUMBER(20,0) 15
ORIGINAL_DEL_DATE DATE 16
SPECIAL VARCHAR2(12) 17
RPE_QTY NUMBER(8,2) 18
ACTUAL_CASES NUMBER(6,0) 19
UPDATED_BY VARCHAR2(40) 20
UPDATED_DATE DATE 21
CREATED_BY VARCHAR2(40) 22
CREATED_DATE DATE 23
CASES NUMBER(8,0) 24
ACTUAL_DELIVERED_QUANTITY NUMBER(24,4) 25
ACTUAL_DELIVERED_RPE_QTY NUMBER(24,4) 26
ACTUAL_DESPATCHED_QUANTITY NUMBER(24,4) 27
ACTUAL_DESPATCHED_RPE_QTY NUMBER(24,4) 28
MEDIA_RETURNS_DU_TYPE VARCHAR2(12) 29
MEDIA_RETURNS_QUANTITY NUMBER(24,4) 30

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ----------------------------- ---------------- -----------
SCH_ORD_ITEMS OMS_REF VARCHAR2(48) 1
CUSTOMER VARCHAR2(48) 2
EXTERNAL_REF VARCHAR2(80) 3
PROD_TYPE_ID VARCHAR2(48) 4
ITEM_IDENTIFIER VARCHAR2(80) 5
ITEM_AKA_CODE VARCHAR2(120) 6
ITEM_DESCRIPTION VARCHAR2(488) 7
ITEM_FACTOR VARCHAR2(48) 8
LIFTS NUMBER(8,2) 9
STACK NUMBER(3,0) 10
QTY_ORDERED NUMBER(8,0) 11
QTY_TO_DELIVER NUMBER(8,0) 12
QTY_DELIVERED NUMBER(8,0) 13
WEIGHT NUMBER(20,2) 14
VOLUME NUMBER(20,4) 15
CREATED_DATE DATE 16
CREATED_BY VARCHAR2(160) 17
UPDATED_DATE DATE 18
UPDATED_BY VARCHAR2(160) 19
DU_TYPE VARCHAR2(48) 20
CURRENT_LOCATION VARCHAR2(48) 21
SAP_LINE_NO NUMBER(12,0) 22
DAMAGED_FLAG VARCHAR2(4) 23
ALTERNATIVE_ITEM_ID VARCHAR2(80) 24
PALLET_ID VARCHAR2(80) 25
ORDER_ITEM_ID NUMBER(20,0) 26
HEIGHT NUMBER(5,2) 27
WIDTH NUMBER(5,2) 28
LENGTH NUMBER(5,2) 29
CLASS VARCHAR2(400) 30
DG VARCHAR2(4) 31
ACTUAL_LENGTH NUMBER(5,2) 32
ACTUAL_WIDTH NUMBER(5,2) 33
ACTUAL_HEIGHT NUMBER(5,2) 34
ACTUAL_WEIGHT NUMBER(20,2) 35
ACTUAL_DIMENSIONAL_WEIGHT NUMBER(20,2) 36
CONTRACTUAL_WEIGHT NUMBER(20,2) 37
DIMENSIONAL_WEIGHT NUMBER(20,2) 38
UNITS NUMBER(20,0) 39
COMMODITY VARCHAR2(200) 40
GEL_PACK_QTY NUMBER(8,0) 41
DRY_ICE_QTY NUMBER(10,2) 42
EQ VARCHAR2(4) 43
PARENT_ITEM_ID VARCHAR2(80) 44
ITEM_LONG_DESCRIPTION VARCHAR2(4000) 45

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ----------------------------- ---------------- -----------
SCH_ORD_ITEMS_REASONS OMS_REF VARCHAR2(48) 1
CUSTOMER VARCHAR2(48) 2
EXTERNAL_REF VARCHAR2(80) 3
PROD_TYPE_ID VARCHAR2(48) 4
ITEM_IDENTIFIER VARCHAR2(80) 5
REASON_CODE VARCHAR2(48) 6
QTY NUMBER(8,0) 7
REASON_COMMENTS VARCHAR2(800) 8
CREATED_DATE DATE 9
CREATED_BY VARCHAR2(160) 10
UPDATED_DATE DATE 11
UPDATED_BY VARCHAR2(160) 12
DEPOT VARCHAR2(48) 13
TRIP_ID VARCHAR2(48) 14
SCAN_TYPE VARCHAR2(80) 15

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_PRODUCT_SUMMARY SOURCE VARCHAR2(12) 1
DESTINATION VARCHAR2(12) 2
DELIVERY_DATE DATE 3
PROD_TYPE_ID VARCHAR2(12) 4
DU_TYPE VARCHAR2(12) 5
SUM_CASES NUMBER(20,0) 6
LEFTOFF_QTY NUMBER(24,4) 7
LEFTOFF_PLANNED NUMBER(24,4) 8
SUM_QTY NUMBER(24,4) 9
ADJ_SUM_QTY NUMBER(24,4) 10
PREV_ADV_QTY NUMBER(24,4) 11
PLANNED_QTY NUMBER(24,4) 12
VARIANCE_QTY NUMBER(24,4) 13
ADVANCE_QTY NUMBER(24,4) 14
ADV_PLANNED NUMBER(24,4) 15
ACTUAL_QTY NUMBER(24,4) 16
SCH_PROD_SUM_ID NUMBER(20,0) 17
LOG 18
ORIG_SUM_QTY NUMBER(24,4) 19
GROUP_NAME VARCHAR2(12) 20
CREATED_BY VARCHAR2(40) 21
CREATED_DATE DATE 22
UPDATED_BY VARCHAR2(40) 23
UPDATED_DATE DATE 24
SCHED_NAME VARCHAR2(12) 25
TRANSHIP_IND VARCHAR2(1) 26
BOOKING_REF VARCHAR2(20) 27
UOM VARCHAR2(3) 28
ORIGINAL_QTY NUMBER(22,0) 29
STATUS VARCHAR2(20) 30
WEIGHT NUMBER(12,2) 31
VOLUME NUMBER(20,5) 32
SOURCE_SYSTEM VARCHAR2(12) 33
DEL_PRIORITY VARCHAR2(2) 34
HANDLING_CODE1 VARCHAR2(2) 35
HANDLING_CODE2 VARCHAR2(2) 36
HANDLING_CODE3 VARCHAR2(2) 37
CARRIER_CODE VARCHAR2(3) 38
INSP_REQ VARCHAR2(2) 39
TEST_REQ VARCHAR2(2) 40
SAP_PRODUCT_ITEM VARCHAR2(18) 41
WAREHOUSE_CODE VARCHAR2(3) 42
STORAGE_CODE VARCHAR2(3) 43
ORIG_PROD_TYPE VARCHAR2(12) 44

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_REASON_CODE REASON_CODE VARCHAR2(12) 1
USAGE VARCHAR2(12) 2
DESCRIPTION VARCHAR2(35) 3
CREATED_BY VARCHAR2(40) 4
CREATED_DATE DATE 5
UPDATED_BY VARCHAR2(40) 6
UPDATED_DATE DATE 7

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_SCHEDULE SCHED_NAME VARCHAR2(12) 1
COST_CENTRE VARCHAR2(12) 2
SCHED_STATUS VARCHAR2(12) 3
UPDATES_PENDING VARCHAR2(1) 4
SCHED_START DATE 5
SCHED_END DATE 6
LOCKED_BY VARCHAR2(35) 7
CREATED_BY VARCHAR2(40) 8
CREATED_DATE DATE 9
UPDATED_BY VARCHAR2(40) 10
UPDATED_DATE DATE 11

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_TRIP SCHED_NAME VARCHAR2(12) 1
TRIP_ID VARCHAR2(12) 2
TRIP_STATUS VARCHAR2(12) 3
EXT_REF VARCHAR2(50) 4
EXT_SHIP_DATE DATE 5
COST_CENTRE VARCHAR2(12) 6
CARRIER_ID VARCHAR2(12) 7
OWNING_DEPOT VARCHAR2(12) 8
HU_ID NUMBER(10,0) 9
DRIVER_ID NUMBER(10,0) 10
TRIP_COST NUMBER(20,2) 11
ALLOCABLE_COST NUMBER(20,2) 12
TRIP_COST_CCY VARCHAR2(3) 13
TRIP_COST_UPDATED DATE 14
COST_VAT NUMBER(20,2) 15
TRIP_REVENUE NUMBER(20,2) 16
TRIP_REVENUE_CCY VARCHAR2(3) 17
TRIP_REVENUE_UPDATED DATE 18
REVENUE_VAT NUMBER(20,2) 19
MTM_COST NUMBER(20,2) 20
TRIP_STD_COST NUMBER(20,2) 21
PAYMENT_REF VARCHAR2(50) 22
DISTANCE NUMBER(12,2) 23
SOURCE_SYSTEM VARCHAR2(12) 24
LAST_ERROR VARCHAR2(256) 25
TRAILER_TYPE VARCHAR2(12) 26
PROFIT NUMBER(20,2) 27
MARGIN NUMBER(8,2) 28
TRAILER_ID VARCHAR2(50) 29
TRACTOR_ID VARCHAR2(12) 30
BILL_OF_LADING VARCHAR2(12) 31
START_TIME DATE 32
END_TIME DATE 33
ELAPSED_TIME NUMBER(5,0) 34
DRIVE_TIME NUMBER(5,0) 35
MANUAL_MOD VARCHAR2(1) 36
LAST_UPDATED DATE 37
SEAL_NO NUMBER(35,0) 38
ODO_START NUMBER(7,0) 39
ODO_END NUMBER(7,0) 40
FUEL_DRAWN NUMBER(7,1) 41
MAX_SHIFT_HOURS_BREACH VARCHAR2(1) 42
MAX_DRIVING_HOURS_BREACH VARCHAR2(1) 43
HOURS_BREACH_USERNAME VARCHAR2(40) 44
HOURS_BREACH_DATETIME DATE 45
BREAKS_BREACH VARCHAR2(1) 46
UTILISATION NUMBER(8,2) 47
MTM_PS_CREATED VARCHAR2(1) 48
MTM_FEASIBLE VARCHAR2(1) 49
ROUTE_CODE VARCHAR2(12) 50
FIX_TRAILER VARCHAR2(1) 51
DRIVER_ID2 NUMBER(10,0) 52
DRIVER_ID3 NUMBER(10,0) 53
SVC_TYPE VARCHAR2(12) 54
LAST_INVITATION_DATE DATE 55
LAST_ACCEPTED_DATE DATE 56
LAST_REJECTED_DATE DATE 57
TRIP_AMENDED_FLAG VARCHAR2(1) 58
CTM_CHASER_COUNT NUMBER(5,0) 59
ROUTE_CREATION_DAYNO NUMBER(22,0) 60
SEND_AMENDED_EMAIL VARCHAR2(1) 61
SJC_DATA VARCHAR2(2000) 62
TOTAL_TRIP_WORK NUMBER(5,0) 63
TOTAL_TRIP_BREAK NUMBER(5,0) 64
SHIFT_START DATE 65
SHIFT_END DATE 66
CREATED_DATE DATE 67
CREATED_USER VARCHAR2(50) 68
CARRIER_REF VARCHAR2(25) 69
CCY_CODE VARCHAR2(3) 70
CONTAINER_NO VARCHAR2(50) 71
OWNING_DEPOT_MAN_MOD VARCHAR2(1) 72
SYS_DELETED VARCHAR2(1) 73
PLANNED_ARRIVE_FIRST_STOP DATE 74
PLANNED_ARRIVE_LAST_STOP DATE 75
LAST_ENROUTE_DATE DATE 76
LAST_COMPLETED_DATE DATE 77
OUTBOUND_VEHICLE_FILL NUMBER(5,2) 78
INBOUND_VEHICLE_FILL NUMBER(5,2) 79
TRIP_HAS_COLLECTION VARCHAR2(1) 80
TRIP_EXPIRY_TIME DATE 81
EFX_REF VARCHAR2(50) 82
EFX_SEND_FLAG VARCHAR2(1) 83
TRAILER_ID2 VARCHAR2(50) 84
FULL_LOAD VARCHAR2(10) 85

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_TRIP_STOP STOP_ID NUMBER(22,0) 1
SCHED_NAME VARCHAR2(12) 2
TRIP_ID VARCHAR2(12) 3
STOP_NO NUMBER(13,5) 4
STOP_TYPE VARCHAR2(2) 5
LOCATION_ID VARCHAR2(12) 6
ARRIVE DATE 7
LOAD_START DATE 8
LOAD_COMPLETE DATE 9
DEPART DATE 10
LAYOVER VARCHAR2(6) 11
DISTANCE_FROM_PREV_STOP NUMBER(10,0) 12
DRIVE_TIME_FROM_PREV_STOP NUMBER(10,0) 13
ACTUAL_ARRIVE DATE 14
ACTUAL_DEPART DATE 15
WEIGHT_ON_DEPART NUMBER(20,2) 16
VOLUME_ON_DEPART NUMBER(20,5) 17
RPE_ON_DEPART NUMBER(22,2) 18
TRAILER_ID VARCHAR2(12) 19
FIXED VARCHAR2(1) 20
TRAILER_TYPE VARCHAR2(12) 21
SEAL_NO VARCHAR2(50) 22
DT_CALC_METHOD VARCHAR2(12) 23
RPE_ON_DEPART_ROUND NUMBER(20,0) 24
MANUAL_APPLY_STOPOVER VARCHAR2(1) 25
MANUAL_OVERRIDE_STOPOVER VARCHAR2(1) 26
STOPOVER VARCHAR2(1) 27
WAIT_TIME_MINS NUMBER(10,0) 28
LOAD_TIME_MINS NUMBER(10,0) 29
LAYOVER_MINS NUMBER(10,0) 30
BOOKING_TIME VARCHAR2(25) 31
PICK_BY DATE 32
DU_QTY_ON_DEPART NUMBER(24,4) 33
TRAILER_ID2 VARCHAR2(12) 34
CREATED_BY VARCHAR2(40) 35
CREATED_DATE DATE 36
UPDATED_BY VARCHAR2(40) 37
UPDATED_DATE DATE 38

= Extraction =

Data is scheduled to run on an Oracle DMBS_JOB that will produce delimited flat files that will be pushed to an agreed server. <center>
[[File:BI Data Extract EDI.png|800x800px]]
</center>The set up must contain

* A unique Process Name
* Direction Outbound
* File Type PROCESS
* The interval should be once daily at a defined time after midnight.
* The folders should point to a known folder within the CTMS system data structure.
* The Params should be
** Title PACKAGE_NAME, name PROCESS, Value DP_MIS.pr_create_all_extracts

The following shows the data extracted, grouped by type.

Business Area Trip
SCH_HAULAGE_ACTIVITY
SCH_TRIP
SCH_TRIP_STOP

Business Area Resources
IMP_DECODE_ENTRY
ORG_CUSTOMER
RES_CARRIER
RES_CARRIER_TYPE
RES_PERSON
RES_TRAILER_TYPE

Business Area Orders
SCH_ORD
SCH_ORD_NON_CONFORM
SCH_ORDER_LINE
SCH_ORDER_ITEMS
SCH_ORDER_ITEMS_REASONS

Business Area Locations
GEO_LOCATION
GEO_LOCATION_USAGE

Business Area Contracts
CNT_CHARGE
CNT_CHARGE_TIER
CNT_CONTRACT
CNT_TARIFF

Business Area Bookings
INT_BOOKING_DETAIL
SAP_PRODUCT_ITEM
SCH_BOOKING
SCH_PRODUCT_SUMMARY
SCH_REASON_CODE

Business Area Schedule
SCH_SCHEDULE

The export will include all agreed columns on the agreed tables.

All tables will contain columns to identify record created date and records updated date.

Empty csv files will be produced if there is no new data to send to the MIS solution.

There is no method to identify when records are deleted. Therefore records removed from CTMS will not be extracted.

<noinclude>
[[Category: Interfaces]]
</noinclude>

BI Data Extract Guide

2025-11-04T09:17:42Z

Anw: Minor update

=Introduction=

Data exports are available to populate BI or MIS systems. These exports are based upon all columns in the following tables within the CTMS database.

CNT_CHARGE
CNT_CONTRACT
CNT_CHARGE_TIER
CNT_TARIFF
GEO_LOCATION
GEO_LOCATION_USAGE
IMP_DECODE_ENTRY
INT_BOOKING_DETAIL
ORG_CUSTOMER
RES_CARRIER
RES_CARRIER_TYPE
RES_PERSON
RES_TRAILER_TYPE
SAP_PRODUCT_ITEM
SCH_BOOKING
SCH_HAULAGE_ACTIVITY
SCH_ORD
SCH_ORD_NON_CONFORM
SCH_ORDER_LINE
SCH_ORDER_ITEMS
SCH_ORDER_ITEMS_REASONS
SCH_PRODUCT_SUMMARY
SCH_REASON_CODE
SCH_SCHEDULE
SCH_TRIP
SCH_TRIP_STOP
Note: Other tables are available and may be exported – these are the most common. The tables and fields exported can be configured (added to or removed, based on customer processing requirements).

= Schematic =

The following schemas indicate the links between the tables (Primary & Foreign keys)

<gallery widths="600" heights="800px" perrow="1">
Image:BI_Data_Extract_Links_1.png
Image:BI_Data_Extract_Links_2.png
Image:BI_Data_Extract_Links_3.png
Image:BI_Data_Extract_Links_4.png
Image:BI_Data_Extract_Links_5.png
</gallery>

= Data Fields =

The tables are listed. It is expected that each column will be delimited with a '®' symbol and that extract can be scheduled and run on with records created or updated in the last 4 days.

{{Note}} * Up to 50 columns may be configured per extract.
* The list below shows common fields for the tables, and these may be selected from for the 50 columns.
* If more than 50 columns are required, then an additional extract for that table may be defined.

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
CNT_CHARGE CHRG_PARAM VARCHAR2(12) 1
VALUE NUMBER(23,5) 2
CREATED_BY VARCHAR2(40) 3
CREATED_DATE DATE 4
UPDATED_BY VARCHAR2(40) 5
UPDATED_DATE DATE 6
CHARGE_ID NUMBER(20,0) 7
CONDITION_NAME VARCHAR2(12) 8
CONDITION_VALUE VARCHAR2(12) 9
TIER_ID NUMBER(12,0) 10
CHARGEABLE_QUANTITY NUMBER(12,0) 11
CHARGE_TYPE VARCHAR2(12) 12
EFFECTIVE_FROM DATE 13
EXPIRY_DATE DATE 14

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
CNT_CHARGE_TIER UPPER_LIMIT NUMBER(12,2) 1
TARIFF_ID NUMBER(20,0) 2
TIER_NAME VARCHAR2(20) 3
MIN_CHARGE NUMBER(20,2) 4
MAX_CHARGE NUMBER(20,2) 5
CREATED_BY VARCHAR2(40) 6
CREATED_DATE DATE 7
UPDATED_BY VARCHAR2(40) 8
UPDATED_DATE DATE 9
TIER_ID NUMBER(12,0) 10
ADD_UPPER_LIMIT NUMBER(12,2) 11
ADD_TIER_NAME VARCHAR2(20) 12

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
CNT_CONTRACT CONTRACT_ID NUMBER(20,0) 1
CONTRACT_TYPE VARCHAR2(12) 2
LOCAL_PARTY VARCHAR2(12) 3
COUNTER_PARTY VARCHAR2(12) 4
EFFECTIVE_FROM DATE 5
CREATED_BY VARCHAR2(40) 6
CREATED_DATE DATE 7
UPDATED_BY VARCHAR2(40) 8
UPDATED_DATE DATE 9
DEFAULT_CCY VARCHAR2(3) 10
EXPIRY_DATE DATE 11
ORDER_MOVEMENT_RATE VARCHAR2(1) 12

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
CNT_TARIFF CONTRACT_ID NUMBER(20,0) 1
DEL_TYPE VARCHAR2(35) 2
TARIFF_ID NUMBER(20,0) 3
TARIFF_NAME VARCHAR2(50) 4
TIER_UNITS VARCHAR2(12) 5
EXPIRY_DATE DATE 6
CREATED_BY VARCHAR2(40) 7
CREATED_DATE DATE 8
UPDATED_BY VARCHAR2(40) 9
UPDATED_DATE DATE 10
CCY_CODE VARCHAR2(3) 11
CHARGE_TYPE VARCHAR2(12) 12
EFFECTIVE_FROM DATE 13
SEQUENCE NUMBER(5,0) 14
ADD_TIER_UNITS VARCHAR2(12) 15

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
GEO_LOCATION LOCATION_ID VARCHAR2(12) 1
DEPOT VARCHAR2(12) 2
LOCATION_NAME VARCHAR2(35) 3
EXT_REF VARCHAR2(50) 4
ROUTE_CODE VARCHAR2(12) 5
ADDRESS_LINE1 VARCHAR2(50) 6
ADDRESS_LINE2 VARCHAR2(50) 7
ADDRESS_LINE3 VARCHAR2(50) 8
TOWN VARCHAR2(50) 9
COUNTY VARCHAR2(50) 10
COUNTRY VARCHAR2(50) 11
COUNTRY_CODE VARCHAR2(3) 12
POSTCODE VARCHAR2(9) 13
POSTAL_REGION VARCHAR2(15) 14
PHONE VARCHAR2(50) 15
FAX VARCHAR2(50) 16
LATITUDE NUMBER(9,5) 17
LONGITUDE NUMBER(9,5) 18
LOADING_RATE VARCHAR2(12) 19
UNLOADING_RATE VARCHAR2(12) 20
SCHEDULE_OFFSET NUMBER(2,0) 21
RESPONSIBLE_COST_CENTRE VARCHAR2(50) 22
PARENT_LOC_ID VARCHAR2(12) 23
VENDOR_CODE VARCHAR2(12) 24
OPEN_MON VARCHAR2(5) 25
CLOSE_MON VARCHAR2(5) 26
OPEN_FRI VARCHAR2(5) 27
CLOSE_FRI VARCHAR2(5) 28
CREATE_EMPTIES VARCHAR2(1) 29
COMMENTS VARCHAR2(255) 30
INACTIVE VARCHAR2(1) 31
TRAILER_TYPE VARCHAR2(35) 32
ALT_COLL_LOC VARCHAR2(12) 33
ALT_DEL_LOC VARCHAR2(12) 34
DEFAULT_XDOCK VARCHAR2(12) 35
DFLT_SC_HANGING VARCHAR2(12) 36
DFLT_SC_BOXED VARCHAR2(12) 37
PROFILE_ID VARCHAR2(12) 38
CREATED_BY VARCHAR2(40) 39
CREATED_DATE DATE 40
UPDATED_BY VARCHAR2(40) 41
UPDATED_DATE DATE 42
CONTROL_TOWER VARCHAR2(1) 43
PLANNING_REGION VARCHAR2(5) 44
COST_CENTRE_NAME VARCHAR2(12) 45

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
GEO_LOCATION_USAGE LOCATION_ID VARCHAR2(12) 1
USAGE_TYPE VARCHAR2(12) 2
USAGE_ID VARCHAR2(12) 3
CREATED_BY VARCHAR2(40) 4
CREATED_DATE DATE 5
UPDATED_BY VARCHAR2(40) 6
UPDATED_DATE DATE 7

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
IMP_DECODE_ENTRY DECODE_NAME VARCHAR2(35) 1
SOURCE_VALUE VARCHAR2(256) 2
TARGET_VALUE VARCHAR2(256) 3
CUSTOMER_ID VARCHAR2(12) 4
DECODE_TYPE VARCHAR2(12) 5
CREATED_BY VARCHAR2(40) 6
CREATED_DATE DATE 7
UPDATED_BY VARCHAR2(40) 8
UPDATED_DATE DATE 9

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
INT_BOOKING_DETAIL INT_RECORD_ID VARCHAR2(100) 1
REC_NUM NUMBER(22,0) 2
FROM_LOC VARCHAR2(12) 3
TO_LOC VARCHAR2(12) 4
QUANTITY NUMBER(20,5) 5
DEL_DATE VARCHAR2(12) 6
PRODUCT_TYPE VARCHAR2(12) 7
DU_TYPE VARCHAR2(12) 8
BOOKING_REF VARCHAR2(20) 9
TRANSHIP_IND VARCHAR2(1) 10
RECORD_STATUS VARCHAR2(10) 11
VALIDATION_ERROR VARCHAR2(2000) 12
CREATED_DATE DATE 13
CREATED_BY VARCHAR2(40) 14
UPDATED_DATE DATE 15
UPDATED_BY VARCHAR2(40) 16
IDENTIFIER VARCHAR2(10) 17
ACTION VARCHAR2(1) 18
PRODUCT_ITEM VARCHAR2(100) 19
UOM VARCHAR2(3) 20
DEL_PRIORITY VARCHAR2(2) 21
HANDLING_CODE1 VARCHAR2(2) 22
HANDLING_CODE2 VARCHAR2(2) 23
HANDLING_CODE3 VARCHAR2(2) 24
CARRIER_CODE VARCHAR2(3) 25
INSP_REQ VARCHAR2(2) 26
TEST_REQ VARCHAR2(2) 27
WAREHOUSE_CODE VARCHAR2(3) 28
STORAGE_CODE VARCHAR2(3) 29
SOURCE_SYSTEM VARCHAR2(25) 30
DU_QTY NUMBER(24,4) 31
WEIGHT NUMBER(12,2) 32
VOLUME NUMBER(20,5) 33
BKG_PLANT VARCHAR2(4) 34
BKG_STORAGE_LOC VARCHAR2(4) 35
BKG_SHELF_LIFE DATE 36
BKG_REQUESTOR VARCHAR2(20) 37
BKG_TELEPHONE VARCHAR2(30) 38
BKG_ACCOUNT_NO VARCHAR2(20) 39
BKG_BUILDING VARCHAR2(10) 40
BKG_ROOM VARCHAR2(8) 41
BKG_COMMENTS VARCHAR2(200) 42
ASN_HANDLING_UNIT VARCHAR2(20) 43
OLD_MAT_NO VARCHAR2(18) 44
CHBNO VARCHAR2(30) 45
LAB_TEST VARCHAR2(80) 46
SHELF_LIFE_IND VARCHAR2(1) 47
MIN_REM_SHELF VARCHAR2(4) 48
TEMP_COND VARCHAR2(20) 49
REQ_NAME VARCHAR2(40) 50
REQ_PHONE VARCHAR2(30) 51
REQ_ACC_NO VARCHAR2(20) 52
REQ_BUILD VARCHAR2(20) 53
REQ_ROOM VARCHAR2(10) 54
COMMENTS VARCHAR2(80) 55
ADD_DATA_1 VARCHAR2(40) 56
ADD_DATA_2 VARCHAR2(40) 57
ADD_DATA_3 VARCHAR2(40) 58
BKG_ADD_DATA_1 VARCHAR2(40) 59
BKG_ADD_DATA_2 VARCHAR2(40) 60
BKG_ADD_DATA_3 VARCHAR2(40) 61
PRODUCT_DESC VARCHAR2(100) 62

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
ORG_CUSTOMER CUSTOMER_ID VARCHAR2(12) 1
CUSTOMER_NAME VARCHAR2(50) 2
CONTACT_NAME VARCHAR2(50) 3
LOCATION_ID VARCHAR2(12) 4
MTM_CUST_CODE VARCHAR2(2) 5
SELF_BILL VARCHAR2(1) 6
CUST_GROUP VARCHAR2(12) 7
COST_CENTRE_NAME VARCHAR2(12) 8
VAT_COUNTRY VARCHAR2(3) 9
VAT_REG_NO VARCHAR2(50) 10
CREATED_BY VARCHAR2(40) 11
CREATED_DATE DATE 12
UPDATED_BY VARCHAR2(40) 13
UPDATED_DATE DATE 14
COUNTRY VARCHAR2(3) 15
USE_LATE_ORDERS VARCHAR2(1) 16
USE_MANUAL_ORDERS VARCHAR2(1) 17
USE_URGENT_ORDERS VARCHAR2(1) 18
USE_TRANSACTION_CHARGING VARCHAR2(1) 19
TYPE VARCHAR2(12) 20
LATE_ORDER_DAYS_THRESHOLD NUMBER(5) 21
INT_ORD_TO_LOGNET VARCHAR2(1) 22
UNISON_IF_VALUE VARCHAR2(3) 23
TOK_POD_AVAIL VARCHAR2(1) 24
CONSOLIDATE_ORDERS VARCHAR2(1) 25
CONSOL_ALLOC_METHOD VARCHAR2(12) 26
ORDER_REVENUE_CHARGING_TYPE_ID NUMBER 27

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
RES_CARRIER CARRIER_ID VARCHAR2(12) 1
CARRIER_NAME VARCHAR2(50) 2
GROUP_NAME VARCHAR2(35) 3
COST_CENTRE_NAME VARCHAR2(12) 4
CARRIER_TYPE_ID VARCHAR2(35) 5
CURRENT_HAULAGE_UNITS NUMBER(5,0) 6
FIXED_COST_WEEKDAY NUMBER(20,2) 7
FIXED_COST_SAT NUMBER(20,2) 8
FIXED_COST_SUN NUMBER(20,2) 9
HUB_LOCATION VARCHAR2(12) 10
ENFORCE_START_AT_HUB VARCHAR2(1) 11
ENFORCE_END_AT_HUB VARCHAR2(1) 12
BARCODE_TYPE VARCHAR2(12) 13
TMS_REF VARCHAR2(12) 14
HQ_LOCATION VARCHAR2(12) 15
EXPORTFILE_TYPE VARCHAR2(12) 16
VAT_NUMBER VARCHAR2(35) 17
VAT_COUNTRY VARCHAR2(3) 18
STD_SHIFT_HOURS NUMBER(4,2) 19
STD_FACTOR NUMBER(4,2) 20
ALTERNATE_CARRIER VARCHAR2(1) 21
OVERTIME_FACTOR NUMBER(4,2) 22
MAX_SHIFT_HOURS NUMBER(4,2) 23
TRIP_THRESHOLD_HOURS NUMBER(4,2) 24
MAX_DRIVING_HOURS NUMBER(4,2) 25
ADDRESS_LINE1 VARCHAR2(35) 26
ADDRESS_LINE2 VARCHAR2(35) 27
CREATED_BY VARCHAR2(40) 28
ADDRESS_LINE3 VARCHAR2(35) 29
CREATED_DATE DATE 30
TOWN VARCHAR2(35) 31
UPDATED_BY VARCHAR2(40) 32
UPDATED_DATE DATE 33
COUNTY VARCHAR2(35) 34
COUNTRY VARCHAR2(35) 35
COUNTRY_CODE VARCHAR2(3) 36
POSTCODE VARCHAR2(9) 37
REGION VARCHAR2(2) 38
PHONE VARCHAR2(35) 39
FAX VARCHAR2(35) 40
DRIVER_BREAK_THRESHOLD_HOURS NUMBER(4,2) 41
DRIVER_BREAK_MINS NUMBER(3,0) 42
WORK_BREAK_THRESHOLD_HOURS NUMBER(4,2) 43
WORK_BREAK_MINS NUMBER(3,0) 44
DISPLAY_TYPE VARCHAR2(8) 45
PERMIT_DEBRIEF VARCHAR2(1) 46
CONTACT VARCHAR2(100) 47
WORK_STOPOVER_THRESHOLD_HOURS NUMBER(4,2) 48
STOPOVER_MINS NUMBER(3,0) 49
DRIVE_STOPOVER_THRESHOLD_HOURS NUMBER(4,2) 50

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
RES_CARRIER_TYPE CARRIER_TYPE_ID VARCHAR2(35) 1
TRIP_COST_METHOD VARCHAR2(12) 2
ORD_COST_METHOD VARCHAR2(12) 3
CREATED_BY VARCHAR2(40) 4
CREATED_DATE DATE 5
UPDATED_BY VARCHAR2(40) 6
UPDATED_DATE DATE 7

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
RES_PERSON ID NUMBER(22,0) 1
SURNAME VARCHAR2(50) 2
FORENAME VARCHAR2(50) 3
JOB_TITLE VARCHAR2(50) 4
LOCATION_ID VARCHAR2(12) 5
CREATED_BY VARCHAR2(40) 6
CREATED_DATE DATE 7
UPDATED_BY VARCHAR2(40) 8
UPDATED_DATE DATE 9

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
RES_TRAILER_TYPE TRAILER_TYPE VARCHAR2(12) 1
TEMPERATURE_TYPE VARCHAR2(12) 2
DESCRIPTION VARCHAR2(50) 3
MAX_KG NUMBER(20,2) 4
VOLUME NUMBER(20,5) 5
MAX_RPE NUMBER(8,2) 6
REFRIGERATED VARCHAR2(1) 7
TRAILER_LENGTH NUMBER(3,0) 8
COST_OF_USE NUMBER(3,0) 9
INACTIVE VARCHAR2(1) 10
RIGID VARCHAR2(1) 11
CREATED_BY VARCHAR2(40) 12
CREATED_DATE DATE 13
UPDATED_BY VARCHAR2(40) 14
UPDATED_DATE DATE 15
DRIVE_TIME_MODIFIER NUMBER(3,2) 16

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SAP_PRODUCT_ITEM PRODUCT_ITEM_ID VARCHAR2(18) 1
PRODUCT_ITEM_DESC VARCHAR2(100) 2
DEF_DU_TYPE VARCHAR2(12) 3
DEF_PRODUCT_TYPE VARCHAR2(12) 4
CREATED_BY VARCHAR2(40) 5
CREATED_DATE DATE 6
UPDATED_BY VARCHAR2(40) 7
UPDATED_DATE DATE 8

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_BOOKING SOURCE VARCHAR2(12) 1
DESTINATION VARCHAR2(12) 2
DELIVERY_DATE DATE 3
PROD_TYPE_ID VARCHAR2(12) 4
SCHEDULE_DATE DATE 5
TOTAL_WEIGHT NUMBER(12,2) 6
TOTAL_VOLUME NUMBER(20,5) 7
EFFECTIVE_WEIGHT NUMBER(12,2) 8
BOOKING_REF VARCHAR2(20) 9
COMMENTS VARCHAR2(100) 10
SPECIAL_FLAG VARCHAR2(35) 11
PLANNED VARCHAR2(1) 12
ROUTE VARCHAR2(12) 13
BROUGHT_IN VARCHAR2(1) 14
CREATED_BY VARCHAR2(40) 15
CREATED_DATE DATE 16
UPDATED_BY VARCHAR2(40) 17
UPDATED_DATE DATE 18
SCHED_NAME VARCHAR2(12) 19
TRANSHIP_IND VARCHAR2(1) 20
ORIG_PROD_TYPE VARCHAR2(12) 21

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_HAULAGE_ACTIVITY STOP_ID NUMBER(22,0) 1
SEQUENCE NUMBER(8,0) 2
OMS_REF VARCHAR2(12) 3
ACTIVITY_NAME VARCHAR2(35) 4
COMMENTS VARCHAR2(255) 5
CREATED_BY VARCHAR2(40) 6
CREATED_DATE DATE 7
UPDATED_BY VARCHAR2(40) 8
UPDATED_DATE DATE 9

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_ORD OMS_REF VARCHAR2(12) 1
ORDER_ID VARCHAR2(12) 2
STATUS VARCHAR2(12) 3
SOURCE_SYSTEM VARCHAR2(12) 4
SCHED_NAME VARCHAR2(12) 5
COST_CENTRE_NAME VARCHAR2(12) 6
CUSTOMER VARCHAR2(12) 7
DELIVERY_TYPE_ID VARCHAR2(35) 8
TEMP_COMBO_ID VARCHAR2(12) 9
PARENT_ORDER VARCHAR2(12) 10
TEMPLATE_ID VARCHAR2(35) 11
FROM_LOC VARCHAR2(12) 12
TO_LOC VARCHAR2(12) 13
ORIG_FROM_LOC VARCHAR2(12) 14
FINAL_TO_LOC VARCHAR2(12) 15
CONTRACT_FROM_LOC VARCHAR2(12) 16
CONTRACT_TO_LOC VARCHAR2(12) 17
TARGET_TIME VARCHAR2(5) 18
EARLY_AVAIL DATE 19
LATE_AVAIL DATE 20
EARLY_DEL DATE 21
LATE_DEL DATE 22
TARGET VARCHAR2(12) 23
DISTANCE NUMBER(12,2) 24
TOTAL_RPE_QTY NUMBER(8,2) 25
TOTAL_WEIGHT NUMBER(20,5) 26
TOTAL_VOLUME NUMBER(20,5) 27
TOTAL_PALLETS NUMBER(24,4) 28
TOTAL_PIECES NUMBER(24,4) 29
TOTAL_EFFECTIVE_WEIGHT NUMBER(20,2) 30
TOTAL_ACTUAL_RPE_QTY NUMBER(8,2) 31
CONTRACTUAL_WEIGHT NUMBER(20,2) 32
CONTRACTUAL_PALLETS NUMBER(24,4) 33
CONTRACTUAL_RPE_QTY NUMBER(8,2) 34
ACTUAL_WEIGHT NUMBER(20,2) 35
ACTUAL_VOLUME NUMBER(20,5) 36
ACTUAL_PALLETS NUMBER(24,4) 37
ACTUAL_PIECES NUMBER(24,4) 38
ACTUAL_EFFECTIVE_WEIGHT NUMBER(20,2) 39
DELIVERED_TIME DATE 40
ORD_STD_COST NUMBER(20,2) 41
DO_NOT_CALC_STD_COST VARCHAR2(1) 42
REVENUE_STATUS VARCHAR2(1) 43
ORD_REVENUE NUMBER(20,2) 44
REVENUE_VAT NUMBER(20,2) 45
COST_STATUS VARCHAR2(1) 46
ORD_COST NUMBER(20,2) 47
COST_VAT NUMBER(20,2) 48
COST_ALLOC NUMBER(20,2) 49
ORD_REVENUE_VS NUMBER(20,2) 50
PROFIT NUMBER(20,2) 51
MARGIN NUMBER(8,2) 52
ORD_TIER_NAME VARCHAR2(50) 53
SJC_DATA VARCHAR2(2000) 54
EXTERNAL_REF VARCHAR2(20) 55
COMMENTS VARCHAR2(2000) 56
DELIVERY_INSTRUCTIONS VARCHAR2(60) 57
POD_NAME VARCHAR2(50) 58
LAST_ERROR VARCHAR2(256) 59
SEND_TO_MTM VARCHAR2(1) 60
GROUP_NAME VARCHAR2(12) 61
TRANSCODE VARCHAR2(1) 62
MTM_SPLIT_ID VARCHAR2(20) 63
MTM_FLF VARCHAR2(1) 64
CONF_NO VARCHAR2(12) 65
SHIPPING_REF VARCHAR2(12) 66
CREATED_USER VARCHAR2(50) 67
CREATED_DATE DATE 68
CHANGED_USER VARCHAR2(50) 69
CHANGED_DATE DATE 70
INFO VARCHAR2(255) 71
CREATE_EMPTIES VARCHAR2(1) 72
NUM_ADV_NOTES NUMBER(4,0) 73
AETC_REF VARCHAR2(20) 74
DEL_POINT_REF VARCHAR2(20) 75
DROP_COUNT NUMBER(8,0) 76
COLLECTED_BY VARCHAR2(1) 77
DELIVERED_BY VARCHAR2(1) 78
POC VARCHAR2(1) 79
POD VARCHAR2(1) 80
ORDER_COMMENTS VARCHAR2(2000) 81
LANE_COMMENTS VARCHAR2(2000) 82
SCHED_DATE DATE 83
BOOKING_REF VARCHAR2(20) 84
SAVING NUMBER(20,2) 85
LATE_ORDER VARCHAR2(1) 86
MANUAL_ORDER VARCHAR2(1) 87
URGENT_ORDER VARCHAR2(1) 88
SERVICE_TYPE VARCHAR2(20) 89
SOURCE_REF VARCHAR2(50) 90
CURRENT_DEPOT VARCHAR2(12) 91
CCY_CODE VARCHAR2(3) 92
CONTAINER_NO VARCHAR2(50) 93
BILL_OF_LADING VARCHAR2(50) 94
TOTAL_CASES NUMBER(8,0) 95
NUM_ORDER_LINES NUMBER(22,0) 96
SPECIAL_INSTRUCTIONS VARCHAR2(4000) 97
BOOKED_IN VARCHAR2(1) 98
STD_COST_DATA VARCHAR2(2000) 99
ORD_REV_DATA VARCHAR2(2000) 100
INTERNAL_CHARGE_DATA VARCHAR2(2000) 101
ACTUAL_DELIVERED_PALLETS NUMBER(24,4) 102
ACTUAL_DELIVERED_PIECES NUMBER(24,4) 103
TOTAL_ACTUAL_DELIVERED_RPE_QTY NUMBER(8,2) 104
ACTUAL_DESPATCHED_PALLETS NUMBER(24,4) 105
ACTUAL_DESPATCHED_PIECES NUMBER(24,4) 106
TOTAL_ACTUAL_DESPTCHD_RPE_QTY NUMBER(8,2) 107
BOOKING_SEQ NUMBER(22,0) 108
TRANSHIP_IND VARCHAR2(1) 109
UOM VARCHAR2(3) 110
ORIGINAL_QTY NUMBER(22,0) 111
EXC_FIXED_ROUTES VARCHAR2(1) 112
DEL_PRIORITY VARCHAR2(2) 113
HANDLING_CODE1 VARCHAR2(2) 114
HANDLING_CODE2 VARCHAR2(2) 115
HANDLING_CODE3 VARCHAR2(2) 116
CARRIER_CODE VARCHAR2(3) 117
INSP_REQ VARCHAR2(2) 118
TEST_REQ VARCHAR2(2) 119
SAP_PRODUCT_ITEM VARCHAR2(18) 120
WAREHOUSE_CODE VARCHAR2(3) 121
STORAGE_CODE VARCHAR2(3) 122
EFX_REF VARCHAR2(50) 123

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_ORD_NON_CONFORM OMS_REF VARCHAR2(12) 1
ACTIVITY VARCHAR2(20) 2
REASON_CODE VARCHAR2(12) 3
COMMENTS VARCHAR2(256) 4
NON_CONFORM_ID NUMBER 5
TRIP_ID VARCHAR2(12) 6
SCHED_NAME VARCHAR2(12) 7
CREATED_DATE DATE 8
CREATED_BY VARCHAR2(50) 9
UPDATED_DATE DATE 10
UPDATED_BY VARCHAR2(50) 11

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_ORDER_LINE ORDER_LINE_ID NUMBER(20,0) 1
OMS_REF VARCHAR2(12) 2
LINE_NO NUMBER(8,0) 3
PRODUCT_TYPE VARCHAR2(12) 4
DU_TYPE VARCHAR2(12) 5
QUANTITY NUMBER(24,4) 6
WEIGHT NUMBER(20,2) 7
CUBE NUMBER(20,5) 8
ACTUAL_QUANTITY NUMBER(24,4) 9
ACTUAL_WEIGHT NUMBER(20,2) 10
ACTUAL_CUBE NUMBER(12,5) 11
ACTUAL_RPE_QTY NUMBER(8,2) 12
EFFECTIVE_WEIGHT NUMBER(20,2) 13
ACTUAL_EFFECTIVE_WEIGHT NUMBER(20,2) 14
SCH_PROD_SUM_ID NUMBER(20,0) 15
ORIGINAL_DEL_DATE DATE 16
SPECIAL VARCHAR2(12) 17
RPE_QTY NUMBER(8,2) 18
ACTUAL_CASES NUMBER(6,0) 19
UPDATED_BY VARCHAR2(40) 20
UPDATED_DATE DATE 21
CREATED_BY VARCHAR2(40) 22
CREATED_DATE DATE 23
CASES NUMBER(8,0) 24
ACTUAL_DELIVERED_QUANTITY NUMBER(24,4) 25
ACTUAL_DELIVERED_RPE_QTY NUMBER(24,4) 26
ACTUAL_DESPATCHED_QUANTITY NUMBER(24,4) 27
ACTUAL_DESPATCHED_RPE_QTY NUMBER(24,4) 28
MEDIA_RETURNS_DU_TYPE VARCHAR2(12) 29
MEDIA_RETURNS_QUANTITY NUMBER(24,4) 30

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ----------------------------- ---------------- -----------
SCH_ORD_ITEMS OMS_REF VARCHAR2(48) 1
CUSTOMER VARCHAR2(48) 2
EXTERNAL_REF VARCHAR2(80) 3
PROD_TYPE_ID VARCHAR2(48) 4
ITEM_IDENTIFIER VARCHAR2(80) 5
ITEM_AKA_CODE VARCHAR2(120) 6
ITEM_DESCRIPTION VARCHAR2(488) 7
ITEM_FACTOR VARCHAR2(48) 8
LIFTS NUMBER(8,2) 9
STACK NUMBER(3,0) 10
QTY_ORDERED NUMBER(8,0) 11
QTY_TO_DELIVER NUMBER(8,0) 12
QTY_DELIVERED NUMBER(8,0) 13
WEIGHT NUMBER(20,2) 14
VOLUME NUMBER(20,4) 15
CREATED_DATE DATE 16
CREATED_BY VARCHAR2(160) 17
UPDATED_DATE DATE 18
UPDATED_BY VARCHAR2(160) 19
DU_TYPE VARCHAR2(48) 20
CURRENT_LOCATION VARCHAR2(48) 21
SAP_LINE_NO NUMBER(12,0) 22
DAMAGED_FLAG VARCHAR2(4) 23
ALTERNATIVE_ITEM_ID VARCHAR2(80) 24
PALLET_ID VARCHAR2(80) 25
ORDER_ITEM_ID NUMBER(20,0) 26
HEIGHT NUMBER(5,2) 27
WIDTH NUMBER(5,2) 28
LENGTH NUMBER(5,2) 29
CLASS VARCHAR2(400) 30
DG VARCHAR2(4) 31
ACTUAL_LENGTH NUMBER(5,2) 32
ACTUAL_WIDTH NUMBER(5,2) 33
ACTUAL_HEIGHT NUMBER(5,2) 34
ACTUAL_WEIGHT NUMBER(20,2) 35
ACTUAL_DIMENSIONAL_WEIGHT NUMBER(20,2) 36
CONTRACTUAL_WEIGHT NUMBER(20,2) 37
DIMENSIONAL_WEIGHT NUMBER(20,2) 38
UNITS NUMBER(20,0) 39
COMMODITY VARCHAR2(200) 40
GEL_PACK_QTY NUMBER(8,0) 41
DRY_ICE_QTY NUMBER(10,2) 42
EQ VARCHAR2(4) 43
PARENT_ITEM_ID VARCHAR2(80) 44
ITEM_LONG_DESCRIPTION VARCHAR2(4000) 45

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ----------------------------- ---------------- -----------
SCH_ORD_ITEMS_REASONS OMS_REF VARCHAR2(48) 1
CUSTOMER VARCHAR2(48) 2
EXTERNAL_REF VARCHAR2(80) 3
PROD_TYPE_ID VARCHAR2(48) 4
ITEM_IDENTIFIER VARCHAR2(80) 5
REASON_CODE VARCHAR2(48) 6
QTY NUMBER(8,0) 7
REASON_COMMENTS VARCHAR2(800) 8
CREATED_DATE DATE 9
CREATED_BY VARCHAR2(160) 10
UPDATED_DATE DATE 11
UPDATED_BY VARCHAR2(160) 12
DEPOT VARCHAR2(48) 13
TRIP_ID VARCHAR2(48) 14
SCAN_TYPE VARCHAR2(80) 15

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_PRODUCT_SUMMARY SOURCE VARCHAR2(12) 1
DESTINATION VARCHAR2(12) 2
DELIVERY_DATE DATE 3
PROD_TYPE_ID VARCHAR2(12) 4
DU_TYPE VARCHAR2(12) 5
SUM_CASES NUMBER(20,0) 6
LEFTOFF_QTY NUMBER(24,4) 7
LEFTOFF_PLANNED NUMBER(24,4) 8
SUM_QTY NUMBER(24,4) 9
ADJ_SUM_QTY NUMBER(24,4) 10
PREV_ADV_QTY NUMBER(24,4) 11
PLANNED_QTY NUMBER(24,4) 12
VARIANCE_QTY NUMBER(24,4) 13
ADVANCE_QTY NUMBER(24,4) 14
ADV_PLANNED NUMBER(24,4) 15
ACTUAL_QTY NUMBER(24,4) 16
SCH_PROD_SUM_ID NUMBER(20,0) 17
LOG 18
ORIG_SUM_QTY NUMBER(24,4) 19
GROUP_NAME VARCHAR2(12) 20
CREATED_BY VARCHAR2(40) 21
CREATED_DATE DATE 22
UPDATED_BY VARCHAR2(40) 23
UPDATED_DATE DATE 24
SCHED_NAME VARCHAR2(12) 25
TRANSHIP_IND VARCHAR2(1) 26
BOOKING_REF VARCHAR2(20) 27
UOM VARCHAR2(3) 28
ORIGINAL_QTY NUMBER(22,0) 29
STATUS VARCHAR2(20) 30
WEIGHT NUMBER(12,2) 31
VOLUME NUMBER(20,5) 32
SOURCE_SYSTEM VARCHAR2(12) 33
DEL_PRIORITY VARCHAR2(2) 34
HANDLING_CODE1 VARCHAR2(2) 35
HANDLING_CODE2 VARCHAR2(2) 36
HANDLING_CODE3 VARCHAR2(2) 37
CARRIER_CODE VARCHAR2(3) 38
INSP_REQ VARCHAR2(2) 39
TEST_REQ VARCHAR2(2) 40
SAP_PRODUCT_ITEM VARCHAR2(18) 41
WAREHOUSE_CODE VARCHAR2(3) 42
STORAGE_CODE VARCHAR2(3) 43
ORIG_PROD_TYPE VARCHAR2(12) 44

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_REASON_CODE REASON_CODE VARCHAR2(12) 1
USAGE VARCHAR2(12) 2
DESCRIPTION VARCHAR2(35) 3
CREATED_BY VARCHAR2(40) 4
CREATED_DATE DATE 5
UPDATED_BY VARCHAR2(40) 6
UPDATED_DATE DATE 7

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_SCHEDULE SCHED_NAME VARCHAR2(12) 1
COST_CENTRE VARCHAR2(12) 2
SCHED_STATUS VARCHAR2(12) 3
UPDATES_PENDING VARCHAR2(1) 4
SCHED_START DATE 5
SCHED_END DATE 6
LOCKED_BY VARCHAR2(35) 7
CREATED_BY VARCHAR2(40) 8
CREATED_DATE DATE 9
UPDATED_BY VARCHAR2(40) 10
UPDATED_DATE DATE 11

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_TRIP SCHED_NAME VARCHAR2(12) 1
TRIP_ID VARCHAR2(12) 2
TRIP_STATUS VARCHAR2(12) 3
EXT_REF VARCHAR2(50) 4
EXT_SHIP_DATE DATE 5
COST_CENTRE VARCHAR2(12) 6
CARRIER_ID VARCHAR2(12) 7
OWNING_DEPOT VARCHAR2(12) 8
HU_ID NUMBER(10,0) 9
DRIVER_ID NUMBER(10,0) 10
TRIP_COST NUMBER(20,2) 11
ALLOCABLE_COST NUMBER(20,2) 12
TRIP_COST_CCY VARCHAR2(3) 13
TRIP_COST_UPDATED DATE 14
COST_VAT NUMBER(20,2) 15
TRIP_REVENUE NUMBER(20,2) 16
TRIP_REVENUE_CCY VARCHAR2(3) 17
TRIP_REVENUE_UPDATED DATE 18
REVENUE_VAT NUMBER(20,2) 19
MTM_COST NUMBER(20,2) 20
TRIP_STD_COST NUMBER(20,2) 21
PAYMENT_REF VARCHAR2(50) 22
DISTANCE NUMBER(12,2) 23
SOURCE_SYSTEM VARCHAR2(12) 24
LAST_ERROR VARCHAR2(256) 25
TRAILER_TYPE VARCHAR2(12) 26
PROFIT NUMBER(20,2) 27
MARGIN NUMBER(8,2) 28
TRAILER_ID VARCHAR2(50) 29
TRACTOR_ID VARCHAR2(12) 30
BILL_OF_LADING VARCHAR2(12) 31
START_TIME DATE 32
END_TIME DATE 33
ELAPSED_TIME NUMBER(5,0) 34
DRIVE_TIME NUMBER(5,0) 35
MANUAL_MOD VARCHAR2(1) 36
LAST_UPDATED DATE 37
SEAL_NO NUMBER(35,0) 38
ODO_START NUMBER(7,0) 39
ODO_END NUMBER(7,0) 40
FUEL_DRAWN NUMBER(7,1) 41
MAX_SHIFT_HOURS_BREACH VARCHAR2(1) 42
MAX_DRIVING_HOURS_BREACH VARCHAR2(1) 43
HOURS_BREACH_USERNAME VARCHAR2(40) 44
HOURS_BREACH_DATETIME DATE 45
BREAKS_BREACH VARCHAR2(1) 46
UTILISATION NUMBER(8,2) 47
MTM_PS_CREATED VARCHAR2(1) 48
MTM_FEASIBLE VARCHAR2(1) 49
ROUTE_CODE VARCHAR2(12) 50
FIX_TRAILER VARCHAR2(1) 51
DRIVER_ID2 NUMBER(10,0) 52
DRIVER_ID3 NUMBER(10,0) 53
SVC_TYPE VARCHAR2(12) 54
LAST_INVITATION_DATE DATE 55
LAST_ACCEPTED_DATE DATE 56
LAST_REJECTED_DATE DATE 57
TRIP_AMENDED_FLAG VARCHAR2(1) 58
CTM_CHASER_COUNT NUMBER(5,0) 59
ROUTE_CREATION_DAYNO NUMBER(22,0) 60
SEND_AMENDED_EMAIL VARCHAR2(1) 61
SJC_DATA VARCHAR2(2000) 62
TOTAL_TRIP_WORK NUMBER(5,0) 63
TOTAL_TRIP_BREAK NUMBER(5,0) 64
SHIFT_START DATE 65
SHIFT_END DATE 66
CREATED_DATE DATE 67
CREATED_USER VARCHAR2(50) 68
CARRIER_REF VARCHAR2(25) 69
CCY_CODE VARCHAR2(3) 70
CONTAINER_NO VARCHAR2(50) 71
OWNING_DEPOT_MAN_MOD VARCHAR2(1) 72
SYS_DELETED VARCHAR2(1) 73
PLANNED_ARRIVE_FIRST_STOP DATE 74
PLANNED_ARRIVE_LAST_STOP DATE 75
LAST_ENROUTE_DATE DATE 76
LAST_COMPLETED_DATE DATE 77
OUTBOUND_VEHICLE_FILL NUMBER(5,2) 78
INBOUND_VEHICLE_FILL NUMBER(5,2) 79
TRIP_HAS_COLLECTION VARCHAR2(1) 80
TRIP_EXPIRY_TIME DATE 81
EFX_REF VARCHAR2(50) 82
EFX_SEND_FLAG VARCHAR2(1) 83
TRAILER_ID2 VARCHAR2(50) 84
FULL_LOAD VARCHAR2(10) 85

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_TRIP_STOP STOP_ID NUMBER(22,0) 1
SCHED_NAME VARCHAR2(12) 2
TRIP_ID VARCHAR2(12) 3
STOP_NO NUMBER(13,5) 4
STOP_TYPE VARCHAR2(2) 5
LOCATION_ID VARCHAR2(12) 6
ARRIVE DATE 7
LOAD_START DATE 8
LOAD_COMPLETE DATE 9
DEPART DATE 10
LAYOVER VARCHAR2(6) 11
DISTANCE_FROM_PREV_STOP NUMBER(10,0) 12
DRIVE_TIME_FROM_PREV_STOP NUMBER(10,0) 13
ACTUAL_ARRIVE DATE 14
ACTUAL_DEPART DATE 15
WEIGHT_ON_DEPART NUMBER(20,2) 16
VOLUME_ON_DEPART NUMBER(20,5) 17
RPE_ON_DEPART NUMBER(22,2) 18
TRAILER_ID VARCHAR2(12) 19
FIXED VARCHAR2(1) 20
TRAILER_TYPE VARCHAR2(12) 21
SEAL_NO VARCHAR2(50) 22
DT_CALC_METHOD VARCHAR2(12) 23
RPE_ON_DEPART_ROUND NUMBER(20,0) 24
MANUAL_APPLY_STOPOVER VARCHAR2(1) 25
MANUAL_OVERRIDE_STOPOVER VARCHAR2(1) 26
STOPOVER VARCHAR2(1) 27
WAIT_TIME_MINS NUMBER(10,0) 28
LOAD_TIME_MINS NUMBER(10,0) 29
LAYOVER_MINS NUMBER(10,0) 30
BOOKING_TIME VARCHAR2(25) 31
PICK_BY DATE 32
DU_QTY_ON_DEPART NUMBER(24,4) 33
TRAILER_ID2 VARCHAR2(12) 34
CREATED_BY VARCHAR2(40) 35
CREATED_DATE DATE 36
UPDATED_BY VARCHAR2(40) 37
UPDATED_DATE DATE 38

= Extraction =

Data is scheduled to run on an Oracle DMBS_JOB that will produce delimited flat files that will be pushed to an agreed server. <center>
[[File:BI Data Extract EDI.png|800x800px]]
</center>The set up must contain

* A unique Process Name
* Direction Outbound
* File Type PROCESS
* The interval should be once daily at a defined time after midnight.
* The folders should point to a known folder within the CTMS system data structure.
* The Params should be
** Title PACKAGE_NAME, name PROCESS, Value DP_MIS.pr_create_all_extracts

The following shows the data extracted, grouped by type.

Business Area Trip
SCH_HAULAGE_ACTIVITY
SCH_TRIP
SCH_TRIP_STOP

Business Area Resources
IMP_DECODE_ENTRY
ORG_CUSTOMER
RES_CARRIER
RES_CARRIER_TYPE
RES_PERSON
RES_TRAILER_TYPE

Business Area Orders
SCH_ORD
SCH_ORD_NON_CONFORM
SCH_ORDER_LINE
SCH_ORDER_ITEMS
SCH_ORDER_ITEMS_REASONS

Business Area Locations
GEO_LOCATION
GEO_LOCATION_USAGE

Business Area Contracts
CNT_CHARGE
CNT_CHARGE_TIER
CNT_CONTRACT
CNT_TARIFF

Business Area Bookings
INT_BOOKING_DETAIL
SAP_PRODUCT_ITEM
SCH_BOOKING
SCH_PRODUCT_SUMMARY
SCH_REASON_CODE

Business Area Schedule
SCH_SCHEDULE

The export will include all agreed columns on the agreed tables.

All tables will contain columns to identify record created date and records updated date.

Empty csv files will be produced if there is no new data to send to the MIS solution.

There is no method to identify when records are deleted. Therefore records removed from CTMS will not be extracted.

<noinclude>
[[Category: Interfaces]]
</noinclude>

FleXipod Interface

2025-11-03T11:04:39Z

Anw: Minor update

This guide shows how the Aptean Proof of Delivery system (APOD or formerly FleXipod) can be configured to be used from CTMS.

This require configuration as to when messages are sent, how they are formatted (the FleXipod attributes), at what level are messages sent (orders, stops, etc) and what information is expected to be received.

== Configuration ==
=== System Parameters ===
{| class="wikitable apt-searchable"
!Parameter !! Description !! Config By
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD ||Set to Y to indicate the FlexiPod interface is active ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_ACID ||Flexipod acid ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_BREAK_DROPS ||Flexipod include breaks for the drops in the Add API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CARRIERS ||Set to Y indicates the Carrier can control if a trip is sent to FlexiPod ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CLIENTNUM ||FleXipod ClientNum sent in interface ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CONSOLIDATE_APOD ||Flexipod consolidate the drops in the API calls (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CONSOLIDATE_APOD_REF ||Flexipod consolidate the orders for the drops as the OMS reference or a type of customer reference (OMS/CUST/BOOK/DEL) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DEPOTS ||Set to Y indicates the Depot can control if a trip is sent to FlexiPod ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DEPOT_DEPART_ACTION ||Flexipod Depot Depart Action (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DEPOT_RETURN_ACTION ||Flexipod Depot Return Action (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DIRECT ||Set to Y to indicate the FlexiPod interface is direct and not using Route Execution ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DROP ||Determines the Drop level STOP-OMS or ITEM ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_END_OF_TRIP_ACTION ||Flexipod End of Trip Action (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_EXPIRY ||Sets the expiry date for the manifest as a number of days after the end of the trip. ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_EXTERNALSYSTEMUPDATE ||Flexipod process the External System Update messages in the API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_FORCEITEMSCAN ||Force the items to be scanned separately: 0 to use the ScanLevel or 1 to force the scan by item. ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_LISTPENDINGMANIFESTS ||Flexipod process the List Pending Manifest Update messages in the API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_MERGE_DROPS ||Flexipod merge the orders on the drop in the Add API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_PASSWORD ||FleXipod Webservice password ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_PREDEPARTURE_ACTION ||Controls whether the system Flexipod Pre-Departure Action get sent as part of the manifest (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_PROXY ||Flexipod proxy server ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_READDROP ||Flexipod process the Read Drop messages in the API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SCAN_LEVEL ||1,2 or 3 to indicate line or item level scanning ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SCAN_TYPE ||Contents and items ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SIGNATORY ||Set to Y to store the SignedByName as the actual signatory as information for the order at its collection of delivery location ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_SPLIT ||Are orders to be split? ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SYSTEM ||FleXipod SYSTEM ID sent in interface ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_TIMEZONE ||Flexipod timezone for the UpdateManifests API calls ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_TPCLIENTNUM ||FleXipod TPClientNum sent in interface ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_UNALLOCATED_DRIVER ||FleXipod uses an unallocated driver when one is not assigned to a trip ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_UPDATE_MANIFESTS ||FleXipod use UpdateManifests to add manifests (Y/N) ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_USERCODE ||FleXipod webservice usercode ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_USERNAME ||FleXipod webservice username ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_WEBSERVICE ||Flexipod webservice endpoint URL ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_WEBSERVICE_TASK ||Flexipod webservice endpoint URL for Tasks ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_WEBSERVICE_UI ||Flexipod webservice endpoint URL ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_WEBSERVICE_UI_EXEC ||Flexipod webservice endpoint URL for Route Execution ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_X_API_KEY ||Flexipod x-api-key for External System Update messages ||SYSTEM
|- bgcolor="goldenrod" color="white" style="background-color: goldenrod; color: white;"
|FLEXIPOD_TENNANT ||? ||SYSTEM
|- bgcolor="goldenrod" color="white" style="background-color: goldenrod; color: white;"
|FLEXIPOD_TENNANT_KEY1 ||? ||SYSTEM
|}

Key:
* red: no longer in use
* green: in use
* amber: in use, but not defined

=== Carrier ===
The FLEXIPOD flag must be enabled when configured by carrier (system parameter FLEXIPOD_CARRIERS) for carriers that require the use of FlexiPOD.<center>
[[File:Res carrier.png|800x800px]]
</center>

=== Depot Locations ===
The FLEXIPOD flag must be enabled when configured by depot (system parameter FLEXIPOD_DEPOTS) for depots that require the use of FlexiPOD.<center>
[[File:Loc 7.png|800x800px]]
</center>

=== EDI Processes ===

'''FLEXIPOD_OUT'''

This process sends the triggered manifests to APOD.

* Flow Type: PROCESS
* Package Name: PROCESS, DP_FLEXIPOD.PROCESS_FLEXIPOD_OUT
* Process: i_process_name FLEXIPOD_OUT
* Interval: 5 minutes

'''FLEXIPOD_SENDLISTPENDING'''

This process checks to see if there are any pending updates from the manifests and imports the details.

* Flow Type: PROCESS
* Package Name: PROCESS DP_FLEXIPOD.send_listpendingmanifestupdates
* Process: PROCESS FLEXIPOD_SENDLISTPENDING
* Interval: 1 minute

=== Reason Codes and Decodes ===

A decode of name "FLX_RESULT_CODES" type "REFERENCE" must be configured to map all of the reason codes from APOD into CTMS.

Several ITEM_NON_CON reason codes must be created to map to the APOD reason codes.:

Examples:
{| class="wikitable"
!APOD !! CTMS !! Description || At Fault !! Action !! Type !! CBR
|-
|1 ||SD ||Successful Delivery || || || ||
|-
|10 ||SD ||Successful Delivery || || || ||
|-
|2 ||FV ||Failed Visit || || ||FAILURE ||Y
|-
|3 ||SD ||Successful Delivery || || || ||
|-
|4 ||UD ||Unsuccessful Delivery || || ||FAILURE ||
|-
|5 ||SC ||Successful Collection || || || ||
|-
|6 ||SJ ||Skipped Job || || ||FAILURE ||Y
|-
|7 ||NR ||No Longer Required || || ||FAILURE ||
|-
|8 ||PR ||Payment Refused || || || ||
|}

Plus any reason codes created in FlexiPOD must be created within TMS for the audit history to accurately represent any reasons selected by the driver.

{{Note}} For each implementation, the reason codes and numbers will differ. For example, 1 and 10 may not be "Successfully Delivered", so the decode mapping MUST be in place for the APOD interface.

=== Attribute Configuration ===
Attributes against Manifests, Drops and Items can be configured by your Aptean implementation team. Up to {{Warning}} 10 attributes may be defined at each level except Drop, which may contain 20 attributes.

In general, the following is allowed at each level:
* Manifest
** Information derived directly from the trip, such as route code, trailer type, driver, etc.
* Drop
** Information derived from the transport order header, such as the main references, instructions
** Information derived from the customer of the transport order, such as parameters against that customer.
** Any sub-reference held against that transport order.
** Any sub-reference held against the transport order's destination location.
* Item
** Information derived from the order items.
** Order Reference information
** Any references from the Drop above
** {{Note}} Including Quarantine status through the order reference STATUS)

An example is below:

{| class="wikitable apt-searchable"
!Project Name !!Level !!Number !!Source !!Target
|-
|Stapletons ||Drop ||1 ||so.booking_ref ||
|-
|Stapletons ||Drop ||2 ||so.del_point_ref ||
|-
|Stapletons ||Drop ||3 ||dp_flexipod.get_order_val("ORDER","PRICE", ||
|-
|Stapletons ||Drop ||4 || ||
|-
|Stapletons ||Drop ||5 || ||
|-
|Stapletons ||Drop ||6 ||dp_flexipod.get_ref("LOCATION","PERMIT_NUMBER", ||
|-
|Stapletons ||Drop ||7 ||oc.free_text1 ||
|-
|Stapletons ||Drop ||8 ||dp_flexipod.get_ref("LOCATION","UNITARY_AUTHORITY", ||
|-
|Stapletons ||Drop ||9 ||dp_flexipod.get_ref("LOCATION","LICENCE_NUMBER", ||
|-
|Stapletons ||Drop ||10 ||so.total_weight ||
|-
|Stapletons ||Drop ||11 ||so.total_pieces ||
|-
|Stapletons ||Drop ||12 ||oc.pay_on_delivery ||
|-
|Stapletons ||Drop ||13 ||oc.collect_casings ||
|-
|Stapletons ||Drop ||14 || ||
|-
|Stapletons ||Drop ||15 || ||
|-
|Stapletons ||ItemAttributes ||1 ||soi.du_type ||
|-
|Stapletons ||ItemAttributes ||2 ||soi.weight ||
|-
|Stapletons ||ItemAttributes ||3 ||dp_flexipod.get_order_val("ITEM","UNIT_WEIGHT", ||
|-
|Stapletons ||ItemAttributes ||4 ||dp_flexipod.get_order_val("ITEM","UNIT_PRICE", ||
|-
|Stapletons ||ItemAttributes ||5 ||dp_flexipod.get_order_val("ITEM",'STATUS", ||
|-
|Stapletons ||Manifest ||1 ||st.route_code ||
|-
|Stapletons ||Manifest ||2 ||st.trailer_type ||
|}

{{Warning}} You MUST use double-quotes when specifying attributes to dp_flexipod functions such as dp_flexipod.get_order_val.

== Sending Trips to FlexiPOD ==
This happens automatically when:
* the trip is set to status "ACCEPTED" or "EN-ROUTE"
* when any changes happen to the trip i.e. orders are added, removed or moved on a trip that is at those statuses.
* When the driver, carrier or tractor has been added or changed on a trip that is at those statuses.

The send to APOD has many parameters that affect it, which allow such functionality as:
* Consolidating all orders on a stop
* The scan level (pallets, contents, items only.
* Controlling whether pre-departure jobs are sent
* Controlling whether depot departure jobs are sent
* Controlling whether breaks are sent
* Controlling whether depot return jobs are sent
* Controlling whether end of trip jobs are sent

== Actions Taken on Update ==
Gets updates from FleXipod drops and processes them

Marks message as collected

Stores order references
* TrackingID
* TrackingURL
* JobReportName

Stores signatory and filename if present
* As ord_information
* As References
** SignedByName
** SignedByFilename
** SiteImageFilename

If item details provided:
* Updates stop Actual Arrive and Actual Depart

* If scan_type = 'I' (per scanned deliverable item)
** Creates Order Item Reasons from decoded reason code for actions against the drops and items (such as successful delivery, etc).
** Creates Order Item Reasons from decoded reason code if there are non-conformities
** Updates item delivered quantities
** Updates order line quantities
** Updates POC/POD flag against the order

* If scan_type = 'P' (per scanned deliverable item)
** Same for each item in the pallet.

If event_name = 'Pre-Departure'
* Updates SU (start-up) stop actual arrive

If event_name = 'Depot Depart'
* Updates SU (start-up) stop actual arrive and actual depart
* Sets the trip status
* Updates items as despatched
* Updates lines as despatched
* Validates the order

If event_name = 'Depot Return'
* Updates CL (close-down) stop actual arrive

If event_name = 'End of Trip'
* Updates CL (close-down) stop actual arrive and actual depart
* Sets the trip status

For all order updates:
* Change order status to DELIVERED if anything delivered
* Change order status to FAILED if nothing delivered

{{Note}} All changes to order are audited.

[[Category:Interfaces]]

FleXipod Interface

2025-11-03T10:32:58Z

Anw: Updated based on version 1.21 06/10/2025

{{Incomplete}}

This guide shows how the Aptean Proof of Delivery system (APOD or formerly FleXipod) can be configured to be used from CTMS.

This require configuration as to when messages are sent, how they are formatted (the FleXipod attributes), at what level are messages sent (orders, stops, etc) and what information is expected to be received.

== Configuration ==
=== System Parameters ===
{| class="wikitable apt-searchable"
!Parameter !! Description !! Config By
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD ||Set to Y to indicate the FlexiPod interface is active ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_ACID ||Flexipod acid ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_BREAK_DROPS ||Flexipod include breaks for the drops in the Add API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CARRIERS ||Set to Y indicates the Carrier can control if a trip is sent to FlexiPod ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CLIENTNUM ||FleXipod ClientNum sent in interface ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CONSOLIDATE_APOD ||Flexipod consolidate the drops in the API calls (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CONSOLIDATE_APOD_REF ||Flexipod consolidate the orders for the drops as the OMS reference or a type of customer reference (OMS/CUST/BOOK/DEL) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DEPOTS ||Set to Y indicates the Depot can control if a trip is sent to FlexiPod ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DEPOT_DEPART_ACTION ||Flexipod Depot Depart Action (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DEPOT_RETURN_ACTION ||Flexipod Depot Return Action (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DIRECT ||Set to Y to indicate the FlexiPod interface is direct and not using Route Execution ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DROP ||Determines the Drop level STOP-OMS or ITEM ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_END_OF_TRIP_ACTION ||Flexipod End of Trip Action (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_EXPIRY ||Sets the expiry date for the manifest as a number of days after the end of the trip. ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_EXTERNALSYSTEMUPDATE ||Flexipod process the External System Update messages in the API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_FORCEITEMSCAN ||Force the items to be scanned separately: 0 to use the ScanLevel or 1 to force the scan by item. ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_LISTPENDINGMANIFESTS ||Flexipod process the List Pending Manifest Update messages in the API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_MERGE_DROPS ||Flexipod merge the orders on the drop in the Add API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_PASSWORD ||FleXipod Webservice password ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_PREDEPARTURE_ACTION ||Controls whether the system Flexipod Pre-Departure Action get sent as part of the manifest (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_PROXY ||Flexipod proxy server ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_READDROP ||Flexipod process the Read Drop messages in the API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SCAN_LEVEL ||1,2 or 3 to indicate line or item level scanning ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SCAN_TYPE ||Contents and items ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SIGNATORY ||Set to Y to store the SignedByName as the actual signatory as information for the order at its collection of delivery location ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_SPLIT ||Are orders to be split? ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SYSTEM ||FleXipod SYSTEM ID sent in interface ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_TIMEZONE ||Flexipod timezone for the UpdateManifests API calls ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_TPCLIENTNUM ||FleXipod TPClientNum sent in interface ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_UNALLOCATED_DRIVER ||FleXipod uses an unallocated driver when one is not assigned to a trip ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_UPDATE_MANIFESTS ||FleXipod use UpdateManifests to add manifests (Y/N) ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_USERCODE ||FleXipod webservice usercode ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_USERNAME ||FleXipod webservice username ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_WEBSERVICE ||Flexipod webservice endpoint URL ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_WEBSERVICE_TASK ||Flexipod webservice endpoint URL for Tasks ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_WEBSERVICE_UI ||Flexipod webservice endpoint URL ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_WEBSERVICE_UI_EXEC ||Flexipod webservice endpoint URL for Route Execution ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_X_API_KEY ||Flexipod x-api-key for External System Update messages ||SYSTEM
|- bgcolor="goldenrod" color="white" style="background-color: goldenrod; color: white;"
|FLEXIPOD_TENNANT ||? ||SYSTEM
|- bgcolor="goldenrod" color="white" style="background-color: goldenrod; color: white;"
|FLEXIPOD_TENNANT_KEY1 ||? ||SYSTEM
|}

Key:
* red: no longer in use
* green: in use
* amber: in use, but not defined

=== Carrier ===
The FLEXIPOD flag must be enabled when configured by carrier (system parameter FLEXIPOD_CARRIERS) for carriers that require the use of FlexiPOD.<center>
[[File:Res carrier.png|800x800px]]
</center>

=== Depot Locations ===
The FLEXIPOD flag must be enabled when configured by depot (system parameter FLEXIPOD_DEPOTS) for depots that require the use of FlexiPOD.<center>
[[File:Loc 7.png|800x800px]]
</center>

=== EDI Processes ===

'''FLEXIPOD_OUT'''

This process sends the triggered manifests to APOD.

* Flow Type: PROCESS
* Package Name: PROCESS, DP_FLEXIPOD.PROCESS_FLEXIPOD_OUT
* Process: i_process_name FLEXIPOD_OUT
* Interval: 5 minutes

'''FLEXIPOD_SENDLISTPENDING'''

This process checks to see if there are any pending updates from the manifests and imports the details.

* Flow Type: PROCESS
* Package Name: PROCESS DP_FLEXIPOD.send_listpendingmanifestupdates
* Process: PROCESS FLEXIPOD_SENDLISTPENDING
* Interval: 1 minute

=== Reason Codes and Decodes ===

A decode of name "FLX_RESULT_CODES" type "REFERENCE" must be configured to map all of the reason codes from APOD into CTMS.

Several ITEM_NON_CON reason codes must be created to map to the APOD reason codes.:

Examples:
{| class="wikitable"
!APOD !! CTMS !! Description || At Fault !! Action !! Type !! CBR
|-
|1 ||SD ||Successful Delivery || || || ||
|-
|10 ||SD ||Successful Delivery || || || ||
|-
|2 ||FV ||Failed Visit || || ||FAILURE ||Y
|-
|3 ||SD ||Successful Delivery || || || ||
|-
|4 ||UD ||Unsuccessful Delivery || || ||FAILURE ||
|-
|5 ||SC ||Successful Collection || || || ||
|-
|6 ||SJ ||Skipped Job || || ||FAILURE ||Y
|-
|7 ||NR ||No Longer Required || || ||FAILURE ||
|-
|8 ||PR ||Payment Refused || || || ||
|}

Plus any reason codes created in FlexiPOD must be created within TMS for the audit history to accurately represent any reasons selected by the driver.

{{Note}} For each implementation, the reason codes and numbers will differ. For example, 1 and 10 may not be "Successfully Delivered", so the decode mapping MUST be in place for the APOD interface.

=== Attribute Configuration ===
Attributes against Manifests, Drops and Items can be configured by your Aptean implementation team. Up to {{Warning}} 10 attributes may be defined at each level except Drop, which may contain 20 attributes.

In general, the following is allowed at each level:
* Manifest
** Information derived directly from the trip, such as route code, trailer type, driver, etc.
* Drop
** Information derived from the transport order header, such as the main references, instructions
** Information derived from the customer of the transport order, such as parameters against that customer.
** Any sub-reference held against that transport order.
** Any sub-reference held against the transport order's destination location.
* Item
** Information derived from the order items.
** Order Reference information
** Any references from the Drop above
** {{Note}} Including Quarantine status through the order reference STATUS)

An example is below:

{| class="wikitable apt-searchable"
!Project Name !!Level !!Number !!Source !!Target
|-
|Stapletons ||Drop ||1 ||so.booking_ref ||
|-
|Stapletons ||Drop ||2 ||so.del_point_ref ||
|-
|Stapletons ||Drop ||3 ||dp_flexipod.get_order_val("ORDER","PRICE", ||
|-
|Stapletons ||Drop ||4 || ||
|-
|Stapletons ||Drop ||5 || ||
|-
|Stapletons ||Drop ||6 ||dp_flexipod.get_ref("LOCATION","PERMIT_NUMBER", ||
|-
|Stapletons ||Drop ||7 ||oc.free_text1 ||
|-
|Stapletons ||Drop ||8 ||dp_flexipod.get_ref("LOCATION","UNITARY_AUTHORITY", ||
|-
|Stapletons ||Drop ||9 ||dp_flexipod.get_ref("LOCATION","LICENCE_NUMBER", ||
|-
|Stapletons ||Drop ||10 ||so.total_weight ||
|-
|Stapletons ||Drop ||11 ||so.total_pieces ||
|-
|Stapletons ||Drop ||12 ||oc.pay_on_delivery ||
|-
|Stapletons ||Drop ||13 ||oc.collect_casings ||
|-
|Stapletons ||Drop ||14 || ||
|-
|Stapletons ||Drop ||15 || ||
|-
|Stapletons ||ItemAttributes ||1 ||soi.du_type ||
|-
|Stapletons ||ItemAttributes ||2 ||soi.weight ||
|-
|Stapletons ||ItemAttributes ||3 ||dp_flexipod.get_order_val("ITEM","UNIT_WEIGHT", ||
|-
|Stapletons ||ItemAttributes ||4 ||dp_flexipod.get_order_val("ITEM","UNIT_PRICE", ||
|-
|Stapletons ||ItemAttributes ||5 ||dp_flexipod.get_order_val("ITEM",'STATUS", ||
|-
|Stapletons ||Manifest ||1 ||st.route_code ||
|-
|Stapletons ||Manifest ||2 ||st.trailer_type ||
|}

{{Warning}} You MUST use double-quotes when specifying attributes to dp_flexipod functions such as dp_flexipod.get_order_val.

== Sending Trips to FlexiPOD ==
This happens automatically when:
* the trip is set to status "ACCEPTED" or "EN-ROUTE"
* when any changes happen to the trip i.e. orders are added, removed or moved on a trip that is at those statuses.
* When the driver, carrier or tractor has been added or changed on a trip that is at those statuses.

The send to APOD has many parameters that affect it, which allow such functionality as:
* Consolidating all orders on a stop
* The scan level (pallets, contents, items only.
* Controlling whether pre-departure jobs are sent
* Controlling whether depot departure jobs are sent
* Controlling whether breaks are sent
* Controlling whether depot return jobs are sent
* Controlling whether end of trip jobs are sent

== Actions Taken on Update ==
Gets updates from FleXipod drops and processes them

Marks message as collected

Stores order references
* TrackingID
* TrackingURL
* JobReportName

Stores signatory and filename if present
* As ord_information
* As References
** SignedByName
** SignedByFilename
** SiteImageFilename

If item details provided:
* Updates stop Actual Arrive and Actual Depart

* If scan_type = 'I' (per scanned deliverable item)
** Creates Order Item Reasons from decoded reason code for actions against the drops and items (such as successful delivery, etc).
** Creates Order Item Reasons from decoded reason code if there are non-conformities
** Updates item delivered quantities
** Updates order line quantities
** Updates POC/POD flag against the order

* If scan_type = 'P' (per scanned deliverable item)
** Same for each item in the pallet.

If event_name = 'Pre-Departure'
* Updates SU (start-up) stop actual arrive

If event_name = 'Depot Depart'
* Updates SU (start-up) stop actual arrive and actual depart
* Sets the trip status
* Updates items as despatched
* Updates lines as despatched
* Validates the order

If event_name = 'Depot Return'
* Updates CL (close-down) stop actual arrive

If event_name = 'End of Trip'
* Updates CL (close-down) stop actual arrive and actual depart
* Sets the trip status

For all order updates:
* Change order status to DELIVERED if anything delivered
* Change order status to FAILED if nothing delivered

{{Note}} All changes to order are audited.

[[Category:Interfaces]]

BI Data Extract Guide

2025-10-31T11:29:23Z

Anw: Added EDI to BI data extracts

=Introduction=

Data exports are available to populate BI or MIS systems. These exports are based upon all columns in the following tables within the CTMS database.

CNT_CHARGE
CNT_CONTRACT
CNT_CHARGE_TIER
CNT_TARIFF
GEO_LOCATION
GEO_LOCATION_USAGE
IMP_DECODE_ENTRY
INT_BOOKING_DETAIL
ORG_CUSTOMER
RES_CARRIER
RES_CARRIER_TYPE
RES_PERSON
RES_TRAILER_TYPE
SAP_PRODUCT_ITEM
SCH_BOOKING
SCH_HAULAGE_ACTIVITY
SCH_ORD
SCH_ORD_NON_CONFORM
SCH_ORDER_LINE
SCH_ORDER_ITEMS
SCH_ORDER_ITEMS_REASONS
SCH_PRODUCT_SUMMARY
SCH_REASON_CODE
SCH_SCHEDULE
SCH_TRIP
SCH_TRIP_STOP
Note: Other tables are available and may be exported – these are the most common. The tables and fields exported can be configured.

= Schematic =

The following schemas indicate the links between the tables (Primary & Foreign keys)

<gallery widths="600" heights="800px" perrow="1">
Image:BI_Data_Extract_Links_1.png
Image:BI_Data_Extract_Links_2.png
Image:BI_Data_Extract_Links_3.png
Image:BI_Data_Extract_Links_4.png
Image:BI_Data_Extract_Links_5.png
</gallery>

= Data Fields =

The tables are listed. It is expected that each column will be delimited with a '®' symbol and that extract can be scheduled and run on with records created or updated in the last 4 days.

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
CNT_CHARGE CHRG_PARAM VARCHAR2(12) 1
VALUE NUMBER(23,5) 2
CREATED_BY VARCHAR2(40) 3
CREATED_DATE DATE 4
UPDATED_BY VARCHAR2(40) 5
UPDATED_DATE DATE 6
CHARGE_ID NUMBER(20,0) 7
CONDITION_NAME VARCHAR2(12) 8
CONDITION_VALUE VARCHAR2(12) 9
TIER_ID NUMBER(12,0) 10
CHARGEABLE_QUANTITY NUMBER(12,0) 11
CHARGE_TYPE VARCHAR2(12) 12
EFFECTIVE_FROM DATE 13
EXPIRY_DATE DATE 14

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
CNT_CHARGE_TIER UPPER_LIMIT NUMBER(12,2) 1
TARIFF_ID NUMBER(20,0) 2
TIER_NAME VARCHAR2(20) 3
MIN_CHARGE NUMBER(20,2) 4
MAX_CHARGE NUMBER(20,2) 5
CREATED_BY VARCHAR2(40) 6
CREATED_DATE DATE 7
UPDATED_BY VARCHAR2(40) 8
UPDATED_DATE DATE 9
TIER_ID NUMBER(12,0) 10
ADD_UPPER_LIMIT NUMBER(12,2) 11
ADD_TIER_NAME VARCHAR2(20) 12

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
CNT_CONTRACT CONTRACT_ID NUMBER(20,0) 1
CONTRACT_TYPE VARCHAR2(12) 2
LOCAL_PARTY VARCHAR2(12) 3
COUNTER_PARTY VARCHAR2(12) 4
EFFECTIVE_FROM DATE 5
CREATED_BY VARCHAR2(40) 6
CREATED_DATE DATE 7
UPDATED_BY VARCHAR2(40) 8
UPDATED_DATE DATE 9
DEFAULT_CCY VARCHAR2(3) 10
EXPIRY_DATE DATE 11
ORDER_MOVEMENT_RATE VARCHAR2(1) 12

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
CNT_TARIFF CONTRACT_ID NUMBER(20,0) 1
DEL_TYPE VARCHAR2(35) 2
TARIFF_ID NUMBER(20,0) 3
TARIFF_NAME VARCHAR2(50) 4
TIER_UNITS VARCHAR2(12) 5
EXPIRY_DATE DATE 6
CREATED_BY VARCHAR2(40) 7
CREATED_DATE DATE 8
UPDATED_BY VARCHAR2(40) 9
UPDATED_DATE DATE 10
CCY_CODE VARCHAR2(3) 11
CHARGE_TYPE VARCHAR2(12) 12
EFFECTIVE_FROM DATE 13
SEQUENCE NUMBER(5,0) 14
ADD_TIER_UNITS VARCHAR2(12) 15

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
GEO_LOCATION LOCATION_ID VARCHAR2(12) 1
DEPOT VARCHAR2(12) 2
LOCATION_NAME VARCHAR2(35) 3
EXT_REF VARCHAR2(50) 4
ROUTE_CODE VARCHAR2(12) 5
ADDRESS_LINE1 VARCHAR2(50) 6
ADDRESS_LINE2 VARCHAR2(50) 7
ADDRESS_LINE3 VARCHAR2(50) 8
TOWN VARCHAR2(50) 9
COUNTY VARCHAR2(50) 10
COUNTRY VARCHAR2(50) 11
COUNTRY_CODE VARCHAR2(3) 12
POSTCODE VARCHAR2(9) 13
POSTAL_REGION VARCHAR2(15) 14
PHONE VARCHAR2(50) 15
FAX VARCHAR2(50) 16
LATITUDE NUMBER(9,5) 17
LONGITUDE NUMBER(9,5) 18
LOADING_RATE VARCHAR2(12) 19
UNLOADING_RATE VARCHAR2(12) 20
SCHEDULE_OFFSET NUMBER(2,0) 21
RESPONSIBLE_COST_CENTRE VARCHAR2(50) 22
PARENT_LOC_ID VARCHAR2(12) 23
VENDOR_CODE VARCHAR2(12) 24
OPEN_MON VARCHAR2(5) 25
CLOSE_MON VARCHAR2(5) 26
OPEN_FRI VARCHAR2(5) 27
CLOSE_FRI VARCHAR2(5) 28
CREATE_EMPTIES VARCHAR2(1) 29
COMMENTS VARCHAR2(255) 30
INACTIVE VARCHAR2(1) 31
TRAILER_TYPE VARCHAR2(35) 32
ALT_COLL_LOC VARCHAR2(12) 33
ALT_DEL_LOC VARCHAR2(12) 34
DEFAULT_XDOCK VARCHAR2(12) 35
DFLT_SC_HANGING VARCHAR2(12) 36
DFLT_SC_BOXED VARCHAR2(12) 37
PROFILE_ID VARCHAR2(12) 38
CREATED_BY VARCHAR2(40) 39
CREATED_DATE DATE 40
UPDATED_BY VARCHAR2(40) 41
UPDATED_DATE DATE 42
CONTROL_TOWER VARCHAR2(1) 43
PLANNING_REGION VARCHAR2(5) 44
COST_CENTRE_NAME VARCHAR2(12) 45

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
GEO_LOCATION_USAGE LOCATION_ID VARCHAR2(12) 1
USAGE_TYPE VARCHAR2(12) 2
USAGE_ID VARCHAR2(12) 3
CREATED_BY VARCHAR2(40) 4
CREATED_DATE DATE 5
UPDATED_BY VARCHAR2(40) 6
UPDATED_DATE DATE 7

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
IMP_DECODE_ENTRY DECODE_NAME VARCHAR2(35) 1
SOURCE_VALUE VARCHAR2(256) 2
TARGET_VALUE VARCHAR2(256) 3
CUSTOMER_ID VARCHAR2(12) 4
DECODE_TYPE VARCHAR2(12) 5
CREATED_BY VARCHAR2(40) 6
CREATED_DATE DATE 7
UPDATED_BY VARCHAR2(40) 8
UPDATED_DATE DATE 9

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
INT_BOOKING_DETAIL INT_RECORD_ID VARCHAR2(100) 1
REC_NUM NUMBER(22,0) 2
FROM_LOC VARCHAR2(12) 3
TO_LOC VARCHAR2(12) 4
QUANTITY NUMBER(20,5) 5
DEL_DATE VARCHAR2(12) 6
PRODUCT_TYPE VARCHAR2(12) 7
DU_TYPE VARCHAR2(12) 8
BOOKING_REF VARCHAR2(20) 9
TRANSHIP_IND VARCHAR2(1) 10
RECORD_STATUS VARCHAR2(10) 11
VALIDATION_ERROR VARCHAR2(2000) 12
CREATED_DATE DATE 13
CREATED_BY VARCHAR2(40) 14
UPDATED_DATE DATE 15
UPDATED_BY VARCHAR2(40) 16
IDENTIFIER VARCHAR2(10) 17
ACTION VARCHAR2(1) 18
PRODUCT_ITEM VARCHAR2(100) 19
UOM VARCHAR2(3) 20
DEL_PRIORITY VARCHAR2(2) 21
HANDLING_CODE1 VARCHAR2(2) 22
HANDLING_CODE2 VARCHAR2(2) 23
HANDLING_CODE3 VARCHAR2(2) 24
CARRIER_CODE VARCHAR2(3) 25
INSP_REQ VARCHAR2(2) 26
TEST_REQ VARCHAR2(2) 27
WAREHOUSE_CODE VARCHAR2(3) 28
STORAGE_CODE VARCHAR2(3) 29
SOURCE_SYSTEM VARCHAR2(25) 30
DU_QTY NUMBER(24,4) 31
WEIGHT NUMBER(12,2) 32
VOLUME NUMBER(20,5) 33
BKG_PLANT VARCHAR2(4) 34
BKG_STORAGE_LOC VARCHAR2(4) 35
BKG_SHELF_LIFE DATE 36
BKG_REQUESTOR VARCHAR2(20) 37
BKG_TELEPHONE VARCHAR2(30) 38
BKG_ACCOUNT_NO VARCHAR2(20) 39
BKG_BUILDING VARCHAR2(10) 40
BKG_ROOM VARCHAR2(8) 41
BKG_COMMENTS VARCHAR2(200) 42
ASN_HANDLING_UNIT VARCHAR2(20) 43
OLD_MAT_NO VARCHAR2(18) 44
CHBNO VARCHAR2(30) 45
LAB_TEST VARCHAR2(80) 46
SHELF_LIFE_IND VARCHAR2(1) 47
MIN_REM_SHELF VARCHAR2(4) 48
TEMP_COND VARCHAR2(20) 49
REQ_NAME VARCHAR2(40) 50
REQ_PHONE VARCHAR2(30) 51
REQ_ACC_NO VARCHAR2(20) 52
REQ_BUILD VARCHAR2(20) 53
REQ_ROOM VARCHAR2(10) 54
COMMENTS VARCHAR2(80) 55
ADD_DATA_1 VARCHAR2(40) 56
ADD_DATA_2 VARCHAR2(40) 57
ADD_DATA_3 VARCHAR2(40) 58
BKG_ADD_DATA_1 VARCHAR2(40) 59
BKG_ADD_DATA_2 VARCHAR2(40) 60
BKG_ADD_DATA_3 VARCHAR2(40) 61
PRODUCT_DESC VARCHAR2(100) 62

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
ORG_CUSTOMER CUSTOMER_ID VARCHAR2(12) 1
CUSTOMER_NAME VARCHAR2(50) 2
CONTACT_NAME VARCHAR2(50) 3
LOCATION_ID VARCHAR2(12) 4
MTM_CUST_CODE VARCHAR2(2) 5
SELF_BILL VARCHAR2(1) 6
CUST_GROUP VARCHAR2(12) 7
COST_CENTRE_NAME VARCHAR2(12) 8
VAT_COUNTRY VARCHAR2(3) 9
VAT_REG_NO VARCHAR2(50) 10
CREATED_BY VARCHAR2(40) 11
CREATED_DATE DATE 12
UPDATED_BY VARCHAR2(40) 13
UPDATED_DATE DATE 14
COUNTRY VARCHAR2(3) 15
USE_LATE_ORDERS VARCHAR2(1) 16
USE_MANUAL_ORDERS VARCHAR2(1) 17
USE_URGENT_ORDERS VARCHAR2(1) 18
USE_TRANSACTION_CHARGING VARCHAR2(1) 19
TYPE VARCHAR2(12) 20
LATE_ORDER_DAYS_THRESHOLD NUMBER(5) 21
INT_ORD_TO_LOGNET VARCHAR2(1) 22
UNISON_IF_VALUE VARCHAR2(3) 23
TOK_POD_AVAIL VARCHAR2(1) 24
CONSOLIDATE_ORDERS VARCHAR2(1) 25
CONSOL_ALLOC_METHOD VARCHAR2(12) 26
ORDER_REVENUE_CHARGING_TYPE_ID NUMBER 27

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
RES_CARRIER CARRIER_ID VARCHAR2(12) 1
CARRIER_NAME VARCHAR2(50) 2
GROUP_NAME VARCHAR2(35) 3
COST_CENTRE_NAME VARCHAR2(12) 4
CARRIER_TYPE_ID VARCHAR2(35) 5
CURRENT_HAULAGE_UNITS NUMBER(5,0) 6
FIXED_COST_WEEKDAY NUMBER(20,2) 7
FIXED_COST_SAT NUMBER(20,2) 8
FIXED_COST_SUN NUMBER(20,2) 9
HUB_LOCATION VARCHAR2(12) 10
ENFORCE_START_AT_HUB VARCHAR2(1) 11
ENFORCE_END_AT_HUB VARCHAR2(1) 12
BARCODE_TYPE VARCHAR2(12) 13
TMS_REF VARCHAR2(12) 14
HQ_LOCATION VARCHAR2(12) 15
EXPORTFILE_TYPE VARCHAR2(12) 16
VAT_NUMBER VARCHAR2(35) 17
VAT_COUNTRY VARCHAR2(3) 18
STD_SHIFT_HOURS NUMBER(4,2) 19
STD_FACTOR NUMBER(4,2) 20
ALTERNATE_CARRIER VARCHAR2(1) 21
OVERTIME_FACTOR NUMBER(4,2) 22
MAX_SHIFT_HOURS NUMBER(4,2) 23
TRIP_THRESHOLD_HOURS NUMBER(4,2) 24
MAX_DRIVING_HOURS NUMBER(4,2) 25
ADDRESS_LINE1 VARCHAR2(35) 26
ADDRESS_LINE2 VARCHAR2(35) 27
CREATED_BY VARCHAR2(40) 28
ADDRESS_LINE3 VARCHAR2(35) 29
CREATED_DATE DATE 30
TOWN VARCHAR2(35) 31
UPDATED_BY VARCHAR2(40) 32
UPDATED_DATE DATE 33
COUNTY VARCHAR2(35) 34
COUNTRY VARCHAR2(35) 35
COUNTRY_CODE VARCHAR2(3) 36
POSTCODE VARCHAR2(9) 37
REGION VARCHAR2(2) 38
PHONE VARCHAR2(35) 39
FAX VARCHAR2(35) 40
DRIVER_BREAK_THRESHOLD_HOURS NUMBER(4,2) 41
DRIVER_BREAK_MINS NUMBER(3,0) 42
WORK_BREAK_THRESHOLD_HOURS NUMBER(4,2) 43
WORK_BREAK_MINS NUMBER(3,0) 44
DISPLAY_TYPE VARCHAR2(8) 45
PERMIT_DEBRIEF VARCHAR2(1) 46
CONTACT VARCHAR2(100) 47
WORK_STOPOVER_THRESHOLD_HOURS NUMBER(4,2) 48
STOPOVER_MINS NUMBER(3,0) 49
DRIVE_STOPOVER_THRESHOLD_HOURS NUMBER(4,2) 50

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
RES_CARRIER_TYPE CARRIER_TYPE_ID VARCHAR2(35) 1
TRIP_COST_METHOD VARCHAR2(12) 2
ORD_COST_METHOD VARCHAR2(12) 3
CREATED_BY VARCHAR2(40) 4
CREATED_DATE DATE 5
UPDATED_BY VARCHAR2(40) 6
UPDATED_DATE DATE 7

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
RES_PERSON ID NUMBER(22,0) 1
SURNAME VARCHAR2(50) 2
FORENAME VARCHAR2(50) 3
JOB_TITLE VARCHAR2(50) 4
LOCATION_ID VARCHAR2(12) 5
CREATED_BY VARCHAR2(40) 6
CREATED_DATE DATE 7
UPDATED_BY VARCHAR2(40) 8
UPDATED_DATE DATE 9

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
RES_TRAILER_TYPE TRAILER_TYPE VARCHAR2(12) 1
TEMPERATURE_TYPE VARCHAR2(12) 2
DESCRIPTION VARCHAR2(50) 3
MAX_KG NUMBER(20,2) 4
VOLUME NUMBER(20,5) 5
MAX_RPE NUMBER(8,2) 6
REFRIGERATED VARCHAR2(1) 7
TRAILER_LENGTH NUMBER(3,0) 8
COST_OF_USE NUMBER(3,0) 9
INACTIVE VARCHAR2(1) 10
RIGID VARCHAR2(1) 11
CREATED_BY VARCHAR2(40) 12
CREATED_DATE DATE 13
UPDATED_BY VARCHAR2(40) 14
UPDATED_DATE DATE 15
DRIVE_TIME_MODIFIER NUMBER(3,2) 16

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SAP_PRODUCT_ITEM PRODUCT_ITEM_ID VARCHAR2(18) 1
PRODUCT_ITEM_DESC VARCHAR2(100) 2
DEF_DU_TYPE VARCHAR2(12) 3
DEF_PRODUCT_TYPE VARCHAR2(12) 4
CREATED_BY VARCHAR2(40) 5
CREATED_DATE DATE 6
UPDATED_BY VARCHAR2(40) 7
UPDATED_DATE DATE 8

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_BOOKING SOURCE VARCHAR2(12) 1
DESTINATION VARCHAR2(12) 2
DELIVERY_DATE DATE 3
PROD_TYPE_ID VARCHAR2(12) 4
SCHEDULE_DATE DATE 5
TOTAL_WEIGHT NUMBER(12,2) 6
TOTAL_VOLUME NUMBER(20,5) 7
EFFECTIVE_WEIGHT NUMBER(12,2) 8
BOOKING_REF VARCHAR2(20) 9
COMMENTS VARCHAR2(100) 10
SPECIAL_FLAG VARCHAR2(35) 11
PLANNED VARCHAR2(1) 12
ROUTE VARCHAR2(12) 13
BROUGHT_IN VARCHAR2(1) 14
CREATED_BY VARCHAR2(40) 15
CREATED_DATE DATE 16
UPDATED_BY VARCHAR2(40) 17
UPDATED_DATE DATE 18
SCHED_NAME VARCHAR2(12) 19
TRANSHIP_IND VARCHAR2(1) 20
ORIG_PROD_TYPE VARCHAR2(12) 21

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_HAULAGE_ACTIVITY STOP_ID NUMBER(22,0) 1
SEQUENCE NUMBER(8,0) 2
OMS_REF VARCHAR2(12) 3
ACTIVITY_NAME VARCHAR2(35) 4
COMMENTS VARCHAR2(255) 5
CREATED_BY VARCHAR2(40) 6
CREATED_DATE DATE 7
UPDATED_BY VARCHAR2(40) 8
UPDATED_DATE DATE 9

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_ORD OMS_REF VARCHAR2(12) 1
ORDER_ID VARCHAR2(12) 2
STATUS VARCHAR2(12) 3
SOURCE_SYSTEM VARCHAR2(12) 4
SCHED_NAME VARCHAR2(12) 5
COST_CENTRE_NAME VARCHAR2(12) 6
CUSTOMER VARCHAR2(12) 7
DELIVERY_TYPE_ID VARCHAR2(35) 8
TEMP_COMBO_ID VARCHAR2(12) 9
PARENT_ORDER VARCHAR2(12) 10
TEMPLATE_ID VARCHAR2(35) 11
FROM_LOC VARCHAR2(12) 12
TO_LOC VARCHAR2(12) 13
ORIG_FROM_LOC VARCHAR2(12) 14
FINAL_TO_LOC VARCHAR2(12) 15
CONTRACT_FROM_LOC VARCHAR2(12) 16
CONTRACT_TO_LOC VARCHAR2(12) 17
TARGET_TIME VARCHAR2(5) 18
EARLY_AVAIL DATE 19
LATE_AVAIL DATE 20
EARLY_DEL DATE 21
LATE_DEL DATE 22
TARGET VARCHAR2(12) 23
DISTANCE NUMBER(12,2) 24
TOTAL_RPE_QTY NUMBER(8,2) 25
TOTAL_WEIGHT NUMBER(20,5) 26
TOTAL_VOLUME NUMBER(20,5) 27
TOTAL_PALLETS NUMBER(24,4) 28
TOTAL_PIECES NUMBER(24,4) 29
TOTAL_EFFECTIVE_WEIGHT NUMBER(20,2) 30
TOTAL_ACTUAL_RPE_QTY NUMBER(8,2) 31
CONTRACTUAL_WEIGHT NUMBER(20,2) 32
CONTRACTUAL_PALLETS NUMBER(24,4) 33
CONTRACTUAL_RPE_QTY NUMBER(8,2) 34
ACTUAL_WEIGHT NUMBER(20,2) 35
ACTUAL_VOLUME NUMBER(20,5) 36
ACTUAL_PALLETS NUMBER(24,4) 37
ACTUAL_PIECES NUMBER(24,4) 38
ACTUAL_EFFECTIVE_WEIGHT NUMBER(20,2) 39
DELIVERED_TIME DATE 40
ORD_STD_COST NUMBER(20,2) 41
DO_NOT_CALC_STD_COST VARCHAR2(1) 42
REVENUE_STATUS VARCHAR2(1) 43
ORD_REVENUE NUMBER(20,2) 44
REVENUE_VAT NUMBER(20,2) 45
COST_STATUS VARCHAR2(1) 46
ORD_COST NUMBER(20,2) 47
COST_VAT NUMBER(20,2) 48
COST_ALLOC NUMBER(20,2) 49
ORD_REVENUE_VS NUMBER(20,2) 50
PROFIT NUMBER(20,2) 51
MARGIN NUMBER(8,2) 52
ORD_TIER_NAME VARCHAR2(50) 53
SJC_DATA VARCHAR2(2000) 54
EXTERNAL_REF VARCHAR2(20) 55
COMMENTS VARCHAR2(2000) 56
DELIVERY_INSTRUCTIONS VARCHAR2(60) 57
POD_NAME VARCHAR2(50) 58
LAST_ERROR VARCHAR2(256) 59
SEND_TO_MTM VARCHAR2(1) 60
GROUP_NAME VARCHAR2(12) 61
TRANSCODE VARCHAR2(1) 62
MTM_SPLIT_ID VARCHAR2(20) 63
MTM_FLF VARCHAR2(1) 64
CONF_NO VARCHAR2(12) 65
SHIPPING_REF VARCHAR2(12) 66
CREATED_USER VARCHAR2(50) 67
CREATED_DATE DATE 68
CHANGED_USER VARCHAR2(50) 69
CHANGED_DATE DATE 70
INFO VARCHAR2(255) 71
CREATE_EMPTIES VARCHAR2(1) 72
NUM_ADV_NOTES NUMBER(4,0) 73
AETC_REF VARCHAR2(20) 74
DEL_POINT_REF VARCHAR2(20) 75
DROP_COUNT NUMBER(8,0) 76
COLLECTED_BY VARCHAR2(1) 77
DELIVERED_BY VARCHAR2(1) 78
POC VARCHAR2(1) 79
POD VARCHAR2(1) 80
ORDER_COMMENTS VARCHAR2(2000) 81
LANE_COMMENTS VARCHAR2(2000) 82
SCHED_DATE DATE 83
BOOKING_REF VARCHAR2(20) 84
SAVING NUMBER(20,2) 85
LATE_ORDER VARCHAR2(1) 86
MANUAL_ORDER VARCHAR2(1) 87
URGENT_ORDER VARCHAR2(1) 88
SERVICE_TYPE VARCHAR2(20) 89
SOURCE_REF VARCHAR2(50) 90
CURRENT_DEPOT VARCHAR2(12) 91
CCY_CODE VARCHAR2(3) 92
CONTAINER_NO VARCHAR2(50) 93
BILL_OF_LADING VARCHAR2(50) 94
TOTAL_CASES NUMBER(8,0) 95
NUM_ORDER_LINES NUMBER(22,0) 96
SPECIAL_INSTRUCTIONS VARCHAR2(4000) 97
BOOKED_IN VARCHAR2(1) 98
STD_COST_DATA VARCHAR2(2000) 99
ORD_REV_DATA VARCHAR2(2000) 100
INTERNAL_CHARGE_DATA VARCHAR2(2000) 101
ACTUAL_DELIVERED_PALLETS NUMBER(24,4) 102
ACTUAL_DELIVERED_PIECES NUMBER(24,4) 103
TOTAL_ACTUAL_DELIVERED_RPE_QTY NUMBER(8,2) 104
ACTUAL_DESPATCHED_PALLETS NUMBER(24,4) 105
ACTUAL_DESPATCHED_PIECES NUMBER(24,4) 106
TOTAL_ACTUAL_DESPTCHD_RPE_QTY NUMBER(8,2) 107
BOOKING_SEQ NUMBER(22,0) 108
TRANSHIP_IND VARCHAR2(1) 109
UOM VARCHAR2(3) 110
ORIGINAL_QTY NUMBER(22,0) 111
EXC_FIXED_ROUTES VARCHAR2(1) 112
DEL_PRIORITY VARCHAR2(2) 113
HANDLING_CODE1 VARCHAR2(2) 114
HANDLING_CODE2 VARCHAR2(2) 115
HANDLING_CODE3 VARCHAR2(2) 116
CARRIER_CODE VARCHAR2(3) 117
INSP_REQ VARCHAR2(2) 118
TEST_REQ VARCHAR2(2) 119
SAP_PRODUCT_ITEM VARCHAR2(18) 120
WAREHOUSE_CODE VARCHAR2(3) 121
STORAGE_CODE VARCHAR2(3) 122
EFX_REF VARCHAR2(50) 123

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_ORD_NON_CONFORM OMS_REF VARCHAR2(12) 1
ACTIVITY VARCHAR2(20) 2
REASON_CODE VARCHAR2(12) 3
COMMENTS VARCHAR2(256) 4
NON_CONFORM_ID NUMBER 5
TRIP_ID VARCHAR2(12) 6
SCHED_NAME VARCHAR2(12) 7
CREATED_DATE DATE 8
CREATED_BY VARCHAR2(50) 9
UPDATED_DATE DATE 10
UPDATED_BY VARCHAR2(50) 11

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_ORDER_LINE ORDER_LINE_ID NUMBER(20,0) 1
OMS_REF VARCHAR2(12) 2
LINE_NO NUMBER(8,0) 3
PRODUCT_TYPE VARCHAR2(12) 4
DU_TYPE VARCHAR2(12) 5
QUANTITY NUMBER(24,4) 6
WEIGHT NUMBER(20,2) 7
CUBE NUMBER(20,5) 8
ACTUAL_QUANTITY NUMBER(24,4) 9
ACTUAL_WEIGHT NUMBER(20,2) 10
ACTUAL_CUBE NUMBER(12,5) 11
ACTUAL_RPE_QTY NUMBER(8,2) 12
EFFECTIVE_WEIGHT NUMBER(20,2) 13
ACTUAL_EFFECTIVE_WEIGHT NUMBER(20,2) 14
SCH_PROD_SUM_ID NUMBER(20,0) 15
ORIGINAL_DEL_DATE DATE 16
SPECIAL VARCHAR2(12) 17
RPE_QTY NUMBER(8,2) 18
ACTUAL_CASES NUMBER(6,0) 19
UPDATED_BY VARCHAR2(40) 20
UPDATED_DATE DATE 21
CREATED_BY VARCHAR2(40) 22
CREATED_DATE DATE 23
CASES NUMBER(8,0) 24
ACTUAL_DELIVERED_QUANTITY NUMBER(24,4) 25
ACTUAL_DELIVERED_RPE_QTY NUMBER(24,4) 26
ACTUAL_DESPATCHED_QUANTITY NUMBER(24,4) 27
ACTUAL_DESPATCHED_RPE_QTY NUMBER(24,4) 28
MEDIA_RETURNS_DU_TYPE VARCHAR2(12) 29
MEDIA_RETURNS_QUANTITY NUMBER(24,4) 30

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ----------------------------- ---------------- -----------
SCH_ORD_ITEMS OMS_REF VARCHAR2(48) 1
CUSTOMER VARCHAR2(48) 2
EXTERNAL_REF VARCHAR2(80) 3
PROD_TYPE_ID VARCHAR2(48) 4
ITEM_IDENTIFIER VARCHAR2(80) 5
ITEM_AKA_CODE VARCHAR2(120) 6
ITEM_DESCRIPTION VARCHAR2(488) 7
ITEM_FACTOR VARCHAR2(48) 8
LIFTS NUMBER(8,2) 9
STACK NUMBER(3,0) 10
QTY_ORDERED NUMBER(8,0) 11
QTY_TO_DELIVER NUMBER(8,0) 12
QTY_DELIVERED NUMBER(8,0) 13
WEIGHT NUMBER(20,2) 14
VOLUME NUMBER(20,4) 15
CREATED_DATE DATE 16
CREATED_BY VARCHAR2(160) 17
UPDATED_DATE DATE 18
UPDATED_BY VARCHAR2(160) 19
DU_TYPE VARCHAR2(48) 20
CURRENT_LOCATION VARCHAR2(48) 21
SAP_LINE_NO NUMBER(12,0) 22
DAMAGED_FLAG VARCHAR2(4) 23
ALTERNATIVE_ITEM_ID VARCHAR2(80) 24
PALLET_ID VARCHAR2(80) 25
ORDER_ITEM_ID NUMBER(20,0) 26
HEIGHT NUMBER(5,2) 27
WIDTH NUMBER(5,2) 28
LENGTH NUMBER(5,2) 29
CLASS VARCHAR2(400) 30
DG VARCHAR2(4) 31
ACTUAL_LENGTH NUMBER(5,2) 32
ACTUAL_WIDTH NUMBER(5,2) 33
ACTUAL_HEIGHT NUMBER(5,2) 34
ACTUAL_WEIGHT NUMBER(20,2) 35
ACTUAL_DIMENSIONAL_WEIGHT NUMBER(20,2) 36
CONTRACTUAL_WEIGHT NUMBER(20,2) 37
DIMENSIONAL_WEIGHT NUMBER(20,2) 38
UNITS NUMBER(20,0) 39
COMMODITY VARCHAR2(200) 40
GEL_PACK_QTY NUMBER(8,0) 41
DRY_ICE_QTY NUMBER(10,2) 42
EQ VARCHAR2(4) 43
PARENT_ITEM_ID VARCHAR2(80) 44
ITEM_LONG_DESCRIPTION VARCHAR2(4000) 45

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ----------------------------- ---------------- -----------
SCH_ORD_ITEMS_REASONS OMS_REF VARCHAR2(48) 1
CUSTOMER VARCHAR2(48) 2
EXTERNAL_REF VARCHAR2(80) 3
PROD_TYPE_ID VARCHAR2(48) 4
ITEM_IDENTIFIER VARCHAR2(80) 5
REASON_CODE VARCHAR2(48) 6
QTY NUMBER(8,0) 7
REASON_COMMENTS VARCHAR2(800) 8
CREATED_DATE DATE 9
CREATED_BY VARCHAR2(160) 10
UPDATED_DATE DATE 11
UPDATED_BY VARCHAR2(160) 12
DEPOT VARCHAR2(48) 13
TRIP_ID VARCHAR2(48) 14
SCAN_TYPE VARCHAR2(80) 15

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_PRODUCT_SUMMARY SOURCE VARCHAR2(12) 1
DESTINATION VARCHAR2(12) 2
DELIVERY_DATE DATE 3
PROD_TYPE_ID VARCHAR2(12) 4
DU_TYPE VARCHAR2(12) 5
SUM_CASES NUMBER(20,0) 6
LEFTOFF_QTY NUMBER(24,4) 7
LEFTOFF_PLANNED NUMBER(24,4) 8
SUM_QTY NUMBER(24,4) 9
ADJ_SUM_QTY NUMBER(24,4) 10
PREV_ADV_QTY NUMBER(24,4) 11
PLANNED_QTY NUMBER(24,4) 12
VARIANCE_QTY NUMBER(24,4) 13
ADVANCE_QTY NUMBER(24,4) 14
ADV_PLANNED NUMBER(24,4) 15
ACTUAL_QTY NUMBER(24,4) 16
SCH_PROD_SUM_ID NUMBER(20,0) 17
LOG 18
ORIG_SUM_QTY NUMBER(24,4) 19
GROUP_NAME VARCHAR2(12) 20
CREATED_BY VARCHAR2(40) 21
CREATED_DATE DATE 22
UPDATED_BY VARCHAR2(40) 23
UPDATED_DATE DATE 24
SCHED_NAME VARCHAR2(12) 25
TRANSHIP_IND VARCHAR2(1) 26
BOOKING_REF VARCHAR2(20) 27
UOM VARCHAR2(3) 28
ORIGINAL_QTY NUMBER(22,0) 29
STATUS VARCHAR2(20) 30
WEIGHT NUMBER(12,2) 31
VOLUME NUMBER(20,5) 32
SOURCE_SYSTEM VARCHAR2(12) 33
DEL_PRIORITY VARCHAR2(2) 34
HANDLING_CODE1 VARCHAR2(2) 35
HANDLING_CODE2 VARCHAR2(2) 36
HANDLING_CODE3 VARCHAR2(2) 37
CARRIER_CODE VARCHAR2(3) 38
INSP_REQ VARCHAR2(2) 39
TEST_REQ VARCHAR2(2) 40
SAP_PRODUCT_ITEM VARCHAR2(18) 41
WAREHOUSE_CODE VARCHAR2(3) 42
STORAGE_CODE VARCHAR2(3) 43
ORIG_PROD_TYPE VARCHAR2(12) 44

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_REASON_CODE REASON_CODE VARCHAR2(12) 1
USAGE VARCHAR2(12) 2
DESCRIPTION VARCHAR2(35) 3
CREATED_BY VARCHAR2(40) 4
CREATED_DATE DATE 5
UPDATED_BY VARCHAR2(40) 6
UPDATED_DATE DATE 7

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_SCHEDULE SCHED_NAME VARCHAR2(12) 1
COST_CENTRE VARCHAR2(12) 2
SCHED_STATUS VARCHAR2(12) 3
UPDATES_PENDING VARCHAR2(1) 4
SCHED_START DATE 5
SCHED_END DATE 6
LOCKED_BY VARCHAR2(35) 7
CREATED_BY VARCHAR2(40) 8
CREATED_DATE DATE 9
UPDATED_BY VARCHAR2(40) 10
UPDATED_DATE DATE 11

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_TRIP SCHED_NAME VARCHAR2(12) 1
TRIP_ID VARCHAR2(12) 2
TRIP_STATUS VARCHAR2(12) 3
EXT_REF VARCHAR2(50) 4
EXT_SHIP_DATE DATE 5
COST_CENTRE VARCHAR2(12) 6
CARRIER_ID VARCHAR2(12) 7
OWNING_DEPOT VARCHAR2(12) 8
HU_ID NUMBER(10,0) 9
DRIVER_ID NUMBER(10,0) 10
TRIP_COST NUMBER(20,2) 11
ALLOCABLE_COST NUMBER(20,2) 12
TRIP_COST_CCY VARCHAR2(3) 13
TRIP_COST_UPDATED DATE 14
COST_VAT NUMBER(20,2) 15
TRIP_REVENUE NUMBER(20,2) 16
TRIP_REVENUE_CCY VARCHAR2(3) 17
TRIP_REVENUE_UPDATED DATE 18
REVENUE_VAT NUMBER(20,2) 19
MTM_COST NUMBER(20,2) 20
TRIP_STD_COST NUMBER(20,2) 21
PAYMENT_REF VARCHAR2(50) 22
DISTANCE NUMBER(12,2) 23
SOURCE_SYSTEM VARCHAR2(12) 24
LAST_ERROR VARCHAR2(256) 25
TRAILER_TYPE VARCHAR2(12) 26
PROFIT NUMBER(20,2) 27
MARGIN NUMBER(8,2) 28
TRAILER_ID VARCHAR2(50) 29
TRACTOR_ID VARCHAR2(12) 30
BILL_OF_LADING VARCHAR2(12) 31
START_TIME DATE 32
END_TIME DATE 33
ELAPSED_TIME NUMBER(5,0) 34
DRIVE_TIME NUMBER(5,0) 35
MANUAL_MOD VARCHAR2(1) 36
LAST_UPDATED DATE 37
SEAL_NO NUMBER(35,0) 38
ODO_START NUMBER(7,0) 39
ODO_END NUMBER(7,0) 40
FUEL_DRAWN NUMBER(7,1) 41
MAX_SHIFT_HOURS_BREACH VARCHAR2(1) 42
MAX_DRIVING_HOURS_BREACH VARCHAR2(1) 43
HOURS_BREACH_USERNAME VARCHAR2(40) 44
HOURS_BREACH_DATETIME DATE 45
BREAKS_BREACH VARCHAR2(1) 46
UTILISATION NUMBER(8,2) 47
MTM_PS_CREATED VARCHAR2(1) 48
MTM_FEASIBLE VARCHAR2(1) 49
ROUTE_CODE VARCHAR2(12) 50
FIX_TRAILER VARCHAR2(1) 51
DRIVER_ID2 NUMBER(10,0) 52
DRIVER_ID3 NUMBER(10,0) 53
SVC_TYPE VARCHAR2(12) 54
LAST_INVITATION_DATE DATE 55
LAST_ACCEPTED_DATE DATE 56
LAST_REJECTED_DATE DATE 57
TRIP_AMENDED_FLAG VARCHAR2(1) 58
CTM_CHASER_COUNT NUMBER(5,0) 59
ROUTE_CREATION_DAYNO NUMBER(22,0) 60
SEND_AMENDED_EMAIL VARCHAR2(1) 61
SJC_DATA VARCHAR2(2000) 62
TOTAL_TRIP_WORK NUMBER(5,0) 63
TOTAL_TRIP_BREAK NUMBER(5,0) 64
SHIFT_START DATE 65
SHIFT_END DATE 66
CREATED_DATE DATE 67
CREATED_USER VARCHAR2(50) 68
CARRIER_REF VARCHAR2(25) 69
CCY_CODE VARCHAR2(3) 70
CONTAINER_NO VARCHAR2(50) 71
OWNING_DEPOT_MAN_MOD VARCHAR2(1) 72
SYS_DELETED VARCHAR2(1) 73
PLANNED_ARRIVE_FIRST_STOP DATE 74
PLANNED_ARRIVE_LAST_STOP DATE 75
LAST_ENROUTE_DATE DATE 76
LAST_COMPLETED_DATE DATE 77
OUTBOUND_VEHICLE_FILL NUMBER(5,2) 78
INBOUND_VEHICLE_FILL NUMBER(5,2) 79
TRIP_HAS_COLLECTION VARCHAR2(1) 80
TRIP_EXPIRY_TIME DATE 81
EFX_REF VARCHAR2(50) 82
EFX_SEND_FLAG VARCHAR2(1) 83
TRAILER_ID2 VARCHAR2(50) 84
FULL_LOAD VARCHAR2(10) 85

TABLE_NAME COLUMN_NAME DATA_TYPE_SIZE COLUMN_POSN
-------------------- ------------------------------ ---------------- -----------
SCH_TRIP_STOP STOP_ID NUMBER(22,0) 1
SCHED_NAME VARCHAR2(12) 2
TRIP_ID VARCHAR2(12) 3
STOP_NO NUMBER(13,5) 4
STOP_TYPE VARCHAR2(2) 5
LOCATION_ID VARCHAR2(12) 6
ARRIVE DATE 7
LOAD_START DATE 8
LOAD_COMPLETE DATE 9
DEPART DATE 10
LAYOVER VARCHAR2(6) 11
DISTANCE_FROM_PREV_STOP NUMBER(10,0) 12
DRIVE_TIME_FROM_PREV_STOP NUMBER(10,0) 13
ACTUAL_ARRIVE DATE 14
ACTUAL_DEPART DATE 15
WEIGHT_ON_DEPART NUMBER(20,2) 16
VOLUME_ON_DEPART NUMBER(20,5) 17
RPE_ON_DEPART NUMBER(22,2) 18
TRAILER_ID VARCHAR2(12) 19
FIXED VARCHAR2(1) 20
TRAILER_TYPE VARCHAR2(12) 21
SEAL_NO VARCHAR2(50) 22
DT_CALC_METHOD VARCHAR2(12) 23
RPE_ON_DEPART_ROUND NUMBER(20,0) 24
MANUAL_APPLY_STOPOVER VARCHAR2(1) 25
MANUAL_OVERRIDE_STOPOVER VARCHAR2(1) 26
STOPOVER VARCHAR2(1) 27
WAIT_TIME_MINS NUMBER(10,0) 28
LOAD_TIME_MINS NUMBER(10,0) 29
LAYOVER_MINS NUMBER(10,0) 30
BOOKING_TIME VARCHAR2(25) 31
PICK_BY DATE 32
DU_QTY_ON_DEPART NUMBER(24,4) 33
TRAILER_ID2 VARCHAR2(12) 34
CREATED_BY VARCHAR2(40) 35
CREATED_DATE DATE 36
UPDATED_BY VARCHAR2(40) 37
UPDATED_DATE DATE 38

= Extraction =

Data is scheduled to run on an Oracle DMBS_JOB that will produce delimited flat files that will be pushed to an agreed server. <center>
[[File:BI Data Extract EDI.png|800x800px]]
</center>The set up must contain

* A unique Process Name
* Direction Outbound
* File Type PROCESS
* The interval should be once daily at a defined time after midnight.
* The folders should point to a known folder within teh CTMS system data structure.
* The Params should be
** Title PACKAGE_NAME, name PROCESS, Value MP_MIS.pr_create_all_extracts

The following shows the data extracted, grouped by type.

Business Area Trip
SCH_HAULAGE_ACTIVITY
SCH_TRIP
SCH_TRIP_STOP

Business Area Resources
IMP_DECODE_ENTRY
ORG_CUSTOMER
RES_CARRIER
RES_CARRIER_TYPE
RES_PERSON
RES_TRAILER_TYPE

Business Area Orders
SCH_ORD
SCH_ORD_NON_CONFORM
SCH_ORDER_LINE
SCH_ORDER_ITEMS
SCH_ORDER_ITEMS_REASONS

Business Area Locations
GEO_LOCATION
GEO_LOCATION_USAGE

Business Area Contracts
CNT_CHARGE
CNT_CHARGE_TIER
CNT_CONTRACT
CNT_TARIFF

Business Area Bookings
INT_BOOKING_DETAIL
SAP_PRODUCT_ITEM
SCH_BOOKING
SCH_PRODUCT_SUMMARY
SCH_REASON_CODE

Business Area Schedule
SCH_SCHEDULE

The export will include all agreed columns on the agreed tables.

All tables will contain columns to identify record created date and records updated date.

Empty csv files will be produced if there is no new data to send to the MIS solution.

There is no method to identify when records are deleted. Therefore records removed from CTMS will not be extracted.

<noinclude>
[[Category: Interfaces]]
</noinclude>

File:BI Data Extract EDI.png

2025-10-31T11:25:55Z

Anw:

BI Data Extract EDI

Using the LogiNext Carrier Interface

2025-10-29T08:40:07Z

Anw: Minor change

This guide is intended to show the features, configuration and operation of the LogiNext carrier interface within CTMS.

== Overview ==
The process automates the interface to and from LogiNext enabled carriers, providing an interface for:

* Tendering Trips.
* Acceptance of orders on trips.
* Execution of trips.
* Automatic debrief of trips from information entered into LogiNext systems.
LogiNext is a 4PL system operated by K+N. They do not offer transport themselves, they offer transport services from other carriers on their behalf. As such, LogiNext is ALSO sending messages to and from those carriers' systems in order to offer orders, confirm acceptance, get debrief information, just like the interface between CTMS and LogiNext systems.

= Configuration =

== System Parameters ==
A system level system parameter “LOGINEXT_ENDPOINT” which will contain the endpoint address for LogiNext.

A system level system parameter “LOGINEXT_API_TOKEN” which will contain the API token for LogiNext.

The above 2 parameters will be able to be viewed but not modified in the System parameters screen. These will be configured by your implementation teams from Aptean and LogiNext.

A new carrier level system parameter ALLOW_TRP_DEL_TYPE_UPDATE which will control the updating of the Delivery Type in the Planning screen.

The above parameter will be available for modification in the [[System Parameters]] screen. This must be set to "Y" for each carrier that is enabled.

[[File:LogiNext-SysParams.png|800x800px]]

== Decodes ==
A new decode will be created for the delivery types and will be available to be maintained in the [[Imports]] screen, Decodes tab.

* ''Decode Name'': LOGINEXT_DEL_TYPES
* ''Decode Type'': Reference
* ''Source Value'': The CTMS Delivery Type
* ''Target Value'': The LogiNext Delivery Type

[[File:LogiNext-Decodes.png|800x800px]]

== Resources ==
The LogiNext enabled carriers can be indicated through the flag against the carrier, which is enabled through the [[Resources]] screen, ''Carriers'' tab.

[[File:LogiNext-Carriers.png|800x800px]]

== Reason Codes ==
Reason codes will need to be created to record activity against orders. These can be maintained through the [[Business Data Maintenance|Business Data]] screen, Reason Codes tab.

These will be at item level (ITEM_NON_CON) for the following.

* SI - INSCANNED
* SO - OUTSCANNED
* HO - HANDEDOVER
* OC – CLOSED
* OACK – Order Acknowledged
* OA – Order Accepted
* OR – Order Rejected
* OC – Order Cancelled
The following are also required, but would already exist if your organisation uses the Aptean POD - Calidus Edition (CALIDIUS ePOD) product:

* SD - Successfully Delivered
* SC - Successfully Collected

In addition, all reason codes expected to be used by the carrier must be set up here. This must be manually done, through comparison with LogiNext and the Carriers' expected reason codes.

[[File:LogiNext-ReasonCodes.png|800x800px]]

== EDI ==
A new EDI process will be created to process outbound messages to LogiNext. This is maintained in the [[EDI Maintenance]] screen.

[[File:LogiNext-EDI-Maintenance.png|800x800px]]

The flow will be ''Direction'' Outbound and have a ''Flow Type'' of “PROCESS”.

The process will have a ''Frequency Type'' of "Regular Interval" and will run at regular intervals – in the above example the flow is set to run every 2 minutes through the ''Interval Length''.

The flow will have Report Values (accessed through the '''Params''' button), which specify the process being called.

[[File:LogiNext-EDI-Maintenance2.png|800x800px]]
{| class="wikitable"
|+
!Title
!Name
!Value
|-
|Package Name
|PROCESS
|DP_LOGINEXT.PROCESS_OUTBOUND
|-
|Process Name
|p_process_name
|LOGINEXT_OUTBOUND
|}

= Operation =

== Planning ==
Orders will arrive drip-fed throughout the intervening days, from external systems.

The planning process will be a mix of automatic and manual planning.
* Pre-created trips (fixed schedules) can be pre-assigned to the LogiNext carriers up to 14 days in advance.
** Template trips like this are set up through the Fixed Schedule and through automated processes. This is not covered in this guide. For more information on this, please see [[Scheduling Engine Overview]] and [[Fixed Templates|Fixed Schedules]].
** The Delivery Type is set by the first order that is planned onto the trip.
** The structure is sent, without any real details except locations to be visited. There will be no orders on these template trips at this time.
** {{Note}}Currently the trips in the fixed schedule are not pre-assigned to a LogiNext carrier, and no driver and vehicle is preset.
* Or manually create a trip and assign to a LogiNext carrier.
** Select the Delivery Type of the trip from the drop-down list. The list will display only those values that have been configured in the decode list for LogiNext use. No manual entry is allowed.
** Set the vehicle to the vehicle required - this will indicate the vehicle type, and will be replaced when the order is accepted and assigned.
** Set the driver to the default driver for that carrier
* Plan orders to the trip as normal
** Automatic or manual.
*** Fixed Routes can plan and create trips for the LogiNext carriers. This is not covered in this guide - see [[Fixed Routes]] for more information.
*** The NHSBT Scheduling Engine has a process that can automatically schedule regular drops onto Fixed Templates. This is not covered in this guide - see [[Scheduling Engine Overview]] and [[Fixed Templates|Fixed Schedules]] for more information.
*** Any order (including Ad Hoc or Emergency orders) can be planned onto existing trips or onto newly created trips. This is not covered in detail in this guide - see [[Planning]] for more information.
** As amendments are made (orders added or removed from the trip), these amendments are sent through to the carrier.

== Tendering the Trip to the Carrier ==
In order to pass the trip over to the Carrier for acknowledgement and acceptance, TENDER the trip.
* This is accomplished through setting the status of the trip to TENDERED status. This is not covered in detail in this guide - see [[Planning]] and [[Trip Overview (Waterfall)]] for more information.
* You will not be allowed to tender the trip to the carrier without a set and correct delivery type.
* You will not be able to change to TENDERED status without a driver and vehicle.

== Interface to LogiNext ==
When transport bookings are sent to LogiNext, they are combined at the delivery location (the stop number).

So, in the case where there are multiple orders being delivered to the same location, and the items have been packed into multiple boxes mixing the items inside, there is only one transport booking sent to LogiNext, for that location, just stating the boxes that need to be delivered.

The transport booking sent to LogiNext will be a point to point order - that means that the pickup point (collection location) and drop-off point (delivery location) information will be sent to LogiNext.

The LogiNext delivery type set against the trip determines how we send the transport booking:

* On a ROUND, the system will always sent a transport booking for each delivery point. We also create a return to base stop is now only sent if the trip is a ROUND and the last stop is at the depot with no orders to unload.
* On ADHOCs and SESSIONs, the system will send a transport booking for all delivery stops AND the final stop on the trip as the final stop will be at the last delivery location.

The transport bookings will be organised in the sequence they are organised on the trip in CTMS, through means of a route message through to LogiNext, which will tell LogiNext which transport bookings are to be done on this route, and in which order.

== Acceptance by the Carrier ==
LogiNext will indicate successful acknowledgement of the transport bookings (the stops on the trip).

* Each item on the order will be marked with an item history that says that this item has been acknowledged (received) by the LogiNext.
* When all orders are acknowledged, the trip audit will show this.

{{Warning}}This interface from LogiNext is currently not in use.
LogiNext will pass this on to the carrier (the delivery associate). The carrier will indicate acceptance or non-acceptance of the transport bookings.

LogiNext will pass this on to the carrier (the delivery associate). The carrier will indicate acceptance or non-acceptance of the transport bookings.

* The carrier is expected to accept all transport bookings on a trip.
** When the first transport booking is accepted, CTMS will mark the trip as ACCEPTED status.
** As long as there is one accepted transport booking on the trip, the trip is valid for execution.
** Each item on the order will be marked with an item history that says that this item has been accepted by the carrier.
** When all orders are accepted by the carrier, the trip audit will show this.
* The carrier may reject any transport booking on a trip.
** In this case, the order will be removed from the trip in CTMS (unplanned and the status set back to UNSCHEDULED or SCHED-COL).
** Each item on the order will be marked with an item history that says that this item has been rejected by the carrier.

{{Note}}

* ANY warnings or notes against the trip will be visible in the Trip Comments screens
* ANY rejections (or cancellations - see later) will be visible in the Trip list in the Planning screen - the truck icon will be RED.
* ALL success and failures of messages to and from LogiNext are shown in the the LogiNext Auditing tab of the EDI Interface Errors screen. This will also show the reasons why this has happened. See later for details on checking this audit screen.
LogiNext will inform the carrier of the stops on the trip and how they are to be executed. The carrier will resource the trip (identifying the driver and actual vehicle) and send this information to LogiNext, which will be forwarded on to CTMS. CTMS will update the information on the trip.

LogiNext will inform the carrier of the stops on the trip and how they are to be executed. The carrier will resource the trip (identifying the driver and actual vehicle) and send this information to LogiNext, which will be forwarded on to CTMS. CTMS will update the information on the trip.

{{Warning}}This interface from LogiNext is currently not in use.

== Planning Amendments by You ==
Planning manually can change what is passed to LogiNext carriers, adding or removing stops/orders, or even removing the trips completely. Each of these changes will send the details through to LogiNext for acceptance.

'''Note'''. Any changes made to a trip or its orders after the trip has been set to EN-ROUTE status will not be communicated to LogiNext this must be done by calling the control tower to inform them of the changes.

* You will not be able to add a stop to a trip while the trip is not at PLANNED status.

Actions that you take against the trip and the orders on that trip will trigger messages being sent to LogiNext systems for trips assigned to LogiNext carriers:
* If you decide that the trip is not to be completed by that carrier after all, you can change the from a LogiNext enabled carrier to a non-LogiNext enabled carrier, LogiNext will be informed to cancel all of the transport orders on the trip.
* If you decide that a trip that you were going to execute you want a LogiNext carrier to to, change the non LogiNext carrier to a LogiNext carrier. LogiNext will be informed of this new trip and the orders on it.
* If you decide that you want a DIFFERENT LogiNext carrier to do the trip other than the one originally assigned, you can change to a different LogiNext carrier. This will trigger an update to LogiNext telling them that the carrier assignment has changed.
* If you remove an order or stop from a trip, LogiNext will be told to remove the order
** If this is to a stop that has other orders against it, then this will instead amend the transport booking that has been sent to LogiNext, removing the order volume (and items) as required.
* If you add an order to a trip, LogiNext will be informed that the order is added to the trip.
** If this is to a stop that already exists and already has orders against it, then this will instead amend the transport booking that has been sent to LogiNext, adding to the order volume as required.
* If you remove ALL orders from a trip, LogiNext will be informed that all transport orders they have received on that trip must be cancelled.

Additionally, you can change the status of the trips generated during a standard planning day. Changes to the status of the trips affect the messages sent to the LogiNext system for trips assigned to LogiNext carriers:
* Status change from PLANNED to TENDERED: If the carrier of the trip is found to be a LogiNext-enabled carrier, all transport bookings on this trip will be sent to the LogiNext system, as well as a Trip message (the sequence of the deliveries on the trip. {{Note}} This will be the only Trip message sent to LogiNext.
* Status change from TENDERED back to PLANNED: If the carrier of the trip is found to be a LogiNext-enabled carrier, messages will be sent to cancel all of the transport bookings on the trip.
* Status change to DELETED: If the carrier of the trip is found to be a LogiNext-enabled carrier, all transport bookings for this trip will be deleted from LogiNext.

== Tag to Asset ==
Tag to Asset is the process of recording the picking of the product to be shipped on orders into transport units (e.g. temp-controlled boxes).

The Tag to Asset process will be amended to allow T2A scanning at TENDERED status without raising errors.

This process is essentially adding and removing items from the orders, indicating the deliverable boxes and their IDs and contents..

If an item is removed from an order, an item is added to an order or the quantities are changed on any item on an order, LogiNext will be informed of the items on the order, replacing all items and updating the information against them.

{{Note|* Items messages are not sent to LogiNext after the trip has been set to EN ROUTE
* There is no "Final send" before cut-off - this was part of the original design, but removed during development with the agreement of the customer.}}

== Execution ==
When sent to and accepted by the carrier, the carrier will begin the execution around half an hour before the departure of the trip.

Whilst being executed by the carrier, the carrier systems will pass messages to the LogiNext system around the events that have occurred during the execution. These will be passed onto CTMS and broadly result in the following processing:

* Cancelled - the carrier has cancelled the transport booking.
** Each item on the order will be marked with the quantity as delivered, with an item history that says that this item has been cancelled by the carrier.
** In this case, the order will be removed from the trip in CTMS (unplanned and the status set back to UNSCHEDULED or SCHED-COL).
** An audit record will be added showing the order has been cancelled by the external carrier
* Picked Up - the carrier has declared that the transport booking has been collected from the collection location successfully.
**Each item on the order will be marked with the quantity as despatched, with an item history that says that this item has been successfully collected by the carrier.
** The actual collection time will be noted.
** If this is the first order picked up on this trip, the trip will be set to status EN-ROUTE.
* Not Picked Up - the carrier has declared that the transport booking has NOT been collected from the collection location.
**Each item on the order will be marked with a 0 quantity despatched, with an item history showing the reason code that was entered by the carrier.
** The actual collection time will be noted.
** If this is the first order not picked up on this trip, the trip will be set to status EN-ROUTE.
** The order will be set as status FAILED.
* Delivered - the carrier has declared that the transport booking has been delivered in full to the delivery location.
** Each item on the order will be marked with the quantity as delivered, with an item history that says that this item has been successfully delivered by the carrier.
** The order will be set as status DELIVERED.
** The actual delivery time will be noted.
* Partially Delivered - the carrier has declared that the transport booking has been delivered in part to the delivery location.
** Each item shown as not delivered in the message will be marked with a 0 quantity delivered, with an item history showing the reason code that was entered by the carrier.
** Each item on the order will be marked with the quantity as delivered, with an item history that says that this item has been successfully delivered by the carrier.
** The order will be set as status DELIVERED.
** The actual delivery time will be noted.
* Not Delivered - the carrier has declared that the transport booking has been not been delivered at all (for particular reasons) to the delivery location.
** Each item on the order will be marked with a 0 quantity delivered, with an item history showing the reason code that was entered by the carrier.
** The order will be set as status FAILED.
** The actual delivery time will be noted.

{{Warning}}Ad Hoc Collections (i.e. non-planned collections of empties during a job) are not being executed by the carriers, and no interface exists to process these. This may be added in a later phase.

{{Note}}

* ANY warnings or notes against the trip will be visible in the Trip Comments screens
* ANY rejections or cancellations will be visible in the Trip list in the Planning screen - the truck icon will be RED.
* ALL success and failures of messages to and from LogiNext are shown in the the LogiNext Auditing tab of the EDI Interface Errors screen. This will also show the reasons why this has happened. See later for details on checking this audit screen.

= Auditing =

== User Auditing ==
Any errors are recorded in the processing of the LogiNext trips, these will be displayed in the Comments/Errors tab and the truck icon in the trip tree will be displayed in RED.

[[File:LogiNext-Audit-Trip.png|800x800px]]

Additional information regarding the change of status times, changes of order quantities, etc, which are triggered by the LogiNext interface, can also be viewed on the following standard Audit screens:

* Planning screen - Audit tab.

* New Order screen - Audit tab.

== System Auditing ==
The detailed system auditing can be seen in the Interface Errors screen, on the LogiNext tab.

{{:Interface Errors - LogiNext Details}}

Using the LogiNext Carrier Interface

2025-10-29T08:39:30Z

Anw: Amended to reflect current implementation, confirmed by @cak 29/10/2025

{{Incomplete}}

This guide is intended to show the features, configuration and operation of the LogiNext carrier interface within CTMS.

== Overview ==
The process automates the interface to and from LogiNext enabled carriers, providing an interface for:

* Tendering Trips.
* Acceptance of orders on trips.
* Execution of trips.
* Automatic debrief of trips from information entered into LogiNext systems.
LogiNext is a 4PL system operated by K+N. They do not offer transport themselves, they offer transport services from other carriers on their behalf. As such, LogiNext is ALSO sending messages to and from those carriers' systems in order to offer orders, confirm acceptance, get debrief information, just like the interface between CTMS and LogiNext systems.

= Configuration =

== System Parameters ==
A system level system parameter “LOGINEXT_ENDPOINT” which will contain the endpoint address for LogiNext.

A system level system parameter “LOGINEXT_API_TOKEN” which will contain the API token for LogiNext.

The above 2 parameters will be able to be viewed but not modified in the System parameters screen. These will be configured by your implementation teams from Aptean and LogiNext.

A new carrier level system parameter ALLOW_TRP_DEL_TYPE_UPDATE which will control the updating of the Delivery Type in the Planning screen.

The above parameter will be available for modification in the [[System Parameters]] screen. This must be set to "Y" for each carrier that is enabled.

[[File:LogiNext-SysParams.png|800x800px]]

== Decodes ==
A new decode will be created for the delivery types and will be available to be maintained in the [[Imports]] screen, Decodes tab.

* ''Decode Name'': LOGINEXT_DEL_TYPES
* ''Decode Type'': Reference
* ''Source Value'': The CTMS Delivery Type
* ''Target Value'': The LogiNext Delivery Type

[[File:LogiNext-Decodes.png|800x800px]]

== Resources ==
The LogiNext enabled carriers can be indicated through the flag against the carrier, which is enabled through the [[Resources]] screen, ''Carriers'' tab.

[[File:LogiNext-Carriers.png|800x800px]]

== Reason Codes ==
Reason codes will need to be created to record activity against orders. These can be maintained through the [[Business Data Maintenance|Business Data]] screen, Reason Codes tab.

These will be at item level (ITEM_NON_CON) for the following.

* SI - INSCANNED
* SO - OUTSCANNED
* HO - HANDEDOVER
* OC – CLOSED
* OACK – Order Acknowledged
* OA – Order Accepted
* OR – Order Rejected
* OC – Order Cancelled
The following are also required, but would already exist if your organisation uses the Aptean POD - Calidus Edition (CALIDIUS ePOD) product:

* SD - Successfully Delivered
* SC - Successfully Collected

In addition, all reason codes expected to be used by the carrier must be set up here. This must be manually done, through comparison with LogiNext and the Carriers' expected reason codes.

[[File:LogiNext-ReasonCodes.png|800x800px]]

== EDI ==
A new EDI process will be created to process outbound messages to LogiNext. This is maintained in the [[EDI Maintenance]] screen.

[[File:LogiNext-EDI-Maintenance.png|800x800px]]

The flow will be ''Direction'' Outbound and have a ''Flow Type'' of “PROCESS”.

The process will have a ''Frequency Type'' of "Regular Interval" and will run at regular intervals – in the above example the flow is set to run every 2 minutes through the ''Interval Length''.

The flow will have Report Values (accessed through the '''Params''' button), which specify the process being called.

[[File:LogiNext-EDI-Maintenance2.png|800x800px]]
{| class="wikitable"
|+
!Title
!Name
!Value
|-
|Package Name
|PROCESS
|DP_LOGINEXT.PROCESS_OUTBOUND
|-
|Process Name
|p_process_name
|LOGINEXT_OUTBOUND
|}

= Operation =

== Planning ==
Orders will arrive drip-fed throughout the intervening days, from external systems.

The planning process will be a mix of automatic and manual planning.
* Pre-created trips (fixed schedules) can be pre-assigned to the LogiNext carriers up to 14 days in advance.
** Template trips like this are set up through the Fixed Schedule and through automated processes. This is not covered in this guide. For more information on this, please see [[Scheduling Engine Overview]] and [[Fixed Templates|Fixed Schedules]].
** The Delivery Type is set by the first order that is planned onto the trip.
** The structure is sent, without any real details except locations to be visited. There will be no orders on these template trips at this time.
** {{Note}}Currently the trips in the fixed schedule are not pre-assigned to a LogiNext carrier, and no driver and vehicle is preset.
* Or manually create a trip and assign to a LogiNext carrier.
** Select the Delivery Type of the trip from the drop-down list. The list will display only those values that have been configured in the decode list for LogiNext use. No manual entry is allowed.
** Set the vehicle to the vehicle required - this will indicate the vehicle type, and will be replaced when the order is accepted and assigned.
** Set the driver to the default driver for that carrier
* Plan orders to the trip as normal
** Automatic or manual.
*** Fixed Routes can plan and create trips for the LogiNext carriers. This is not covered in this guide - see [[Fixed Routes]] for more information.
*** The NHSBT Scheduling Engine has a process that can automatically schedule regular drops onto Fixed Templates. This is not covered in this guide - see [[Scheduling Engine Overview]] and [[Fixed Templates|Fixed Schedules]] for more information.
*** Any order (including Ad Hoc or Emergency orders) can be planned onto existing trips or onto newly created trips. This is not covered in detail in this guide - see [[Planning]] for more information.
** As amendments are made (orders added or removed from the trip), these amendments are sent through to the carrier.

== Tendering the Trip to the Carrier ==
In order to pass the trip over to the Carrier for acknowledgement and acceptance, TENDER the trip.
* This is accomplished through setting the status of the trip to TENDERED status. This is not covered in detail in this guide - see [[Planning]] and [[Trip Overview (Waterfall)]] for more information.
* You will not be allowed to tender the trip to the carrier without a set and correct delivery type.
* You will not be able to change to TENDERED status without a driver and vehicle.

== Interface to LogiNext ==
When transport bookings are sent to LogiNext, they are combined at the delivery location (the stop number).

So, in the case where there are multiple orders being delivered to the same location, and the items have been packed into multiple boxes mixing the items inside, there is only one transport booking sent to LogiNext, for that location, just stating the boxes that need to be delivered.

The transport booking sent to LogiNext will be a point to point order - that means that the pickup point (collection location) and drop-off point (delivery location) information will be sent to LogiNext.

The LogiNext delivery type set against the trip determines how we send the transport booking:

* On a ROUND, the system will always sent a transport booking for each delivery point. We also create a return to base stop is now only sent if the trip is a ROUND and the last stop is at the depot with no orders to unload.
* On ADHOCs and SESSIONs, the system will send a transport booking for all delivery stops AND the final stop on the trip as the final stop will be at the last delivery location.

The transport bookings will be organised in the sequence they are organised on the trip in CTMS, through means of a route message through to LogiNext, which will tell LogiNext which transport bookings are to be done on this route, and in which order.

== Acceptance by the Carrier ==
LogiNext will indicate successful acknowledgement of the transport bookings (the stops on the trip).

* Each item on the order will be marked with an item history that says that this item has been acknowledged (received) by the LogiNext.
* When all orders are acknowledged, the trip audit will show this.

{{Warning}}This interface from LogiNext is currently not in use.
LogiNext will pass this on to the carrier (the delivery associate). The carrier will indicate acceptance or non-acceptance of the transport bookings.

LogiNext will pass this on to the carrier (the delivery associate). The carrier will indicate acceptance or non-acceptance of the transport bookings.

* The carrier is expected to accept all transport bookings on a trip.
** When the first transport booking is accepted, CTMS will mark the trip as ACCEPTED status.
** As long as there is one accepted transport booking on the trip, the trip is valid for execution.
** Each item on the order will be marked with an item history that says that this item has been accepted by the carrier.
** When all orders are accepted by the carrier, the trip audit will show this.
* The carrier may reject any transport booking on a trip.
** In this case, the order will be removed from the trip in CTMS (unplanned and the status set back to UNSCHEDULED or SCHED-COL).
** Each item on the order will be marked with an item history that says that this item has been rejected by the carrier.

{{Note}}

* ANY warnings or notes against the trip will be visible in the Trip Comments screens
* ANY rejections (or cancellations - see later) will be visible in the Trip list in the Planning screen - the truck icon will be RED.
* ALL success and failures of messages to and from LogiNext are shown in the the LogiNext Auditing tab of the EDI Interface Errors screen. This will also show the reasons why this has happened. See later for details on checking this audit screen.
LogiNext will inform the carrier of the stops on the trip and how they are to be executed. The carrier will resource the trip (identifying the driver and actual vehicle) and send this information to LogiNext, which will be forwarded on to CTMS. CTMS will update the information on the trip.

LogiNext will inform the carrier of the stops on the trip and how they are to be executed. The carrier will resource the trip (identifying the driver and actual vehicle) and send this information to LogiNext, which will be forwarded on to CTMS. CTMS will update the information on the trip.

{{Warning}}This interface from LogiNext is currently not in use.

== Planning Amendments by You ==
Planning manually can change what is passed to LogiNext carriers, adding or removing stops/orders, or even removing the trips completely. Each of these changes will send the details through to LogiNext for acceptance.

'''Note'''. Any changes made to a trip or its orders after the trip has been set to EN-ROUTE status will not be communicated to LogiNext this must be done by calling the control tower to inform them of the changes.

* You will not be able to add a stop to a trip while the trip is not at PLANNED status.

Actions that you take against the trip and the orders on that trip will trigger messages being sent to LogiNext systems for trips assigned to LogiNext carriers:
* If you decide that the trip is not to be completed by that carrier after all, you can change the from a LogiNext enabled carrier to a non-LogiNext enabled carrier, LogiNext will be informed to cancel all of the transport orders on the trip.
* If you decide that a trip that you were going to execute you want a LogiNext carrier to to, change the non LogiNext carrier to a LogiNext carrier. LogiNext will be informed of this new trip and the orders on it.
* If you decide that you want a DIFFERENT LogiNext carrier to do the trip other than the one originally assigned, you can change to a different LogiNext carrier. This will trigger an update to LogiNext telling them that the carrier assignment has changed.
* If you remove an order or stop from a trip, LogiNext will be told to remove the order
** If this is to a stop that has other orders against it, then this will instead amend the transport booking that has been sent to LogiNext, removing the order volume (and items) as required.
* If you add an order to a trip, LogiNext will be informed that the order is added to the trip.
** If this is to a stop that already exists and already has orders against it, then this will instead amend the transport booking that has been sent to LogiNext, adding to the order volume as required.
* If you remove ALL orders from a trip, LogiNext will be informed that all transport orders they have received on that trip must be cancelled.

Additionally, you can change the status of the trips generated during a standard planning day. Changes to the status of the trips affect the messages sent to the LogiNext system for trips assigned to LogiNext carriers:
* Status change from PLANNED to TENDERED: If the carrier of the trip is found to be a LogiNext-enabled carrier, all transport bookings on this trip will be sent to the LogiNext system, as well as a Trip message (the sequence of the deliveries on the trip. {{Note}} This will be the only Trip message sent to LogiNext.
* Status change from TENDERED back to PLANNED: If the carrier of the trip is found to be a LogiNext-enabled carrier, messages will be sent to cancel all of the transport bookings on the trip.
* Status change to DELETED: If the carrier of the trip is found to be a LogiNext-enabled carrier, all transport bookings for this trip will be deleted from LogiNext.

== Tag to Asset ==
Tag to Asset is the process of recording the picking of the product to be shipped on orders into transport units (e.g. temp-controlled boxes).

The Tag to Asset process will be amended to allow T2A scanning at TENDERED status without raising errors.

This process is essentially adding and removing items from the orders, indicating the deliverable boxes and their IDs and contents..

If an item is removed from an order, an item is added to an order or the quantities are changed on any item on an order, LogiNext will be informed of the items on the order, replacing all items and updating the information against them.

{{Note|* Items messages are not sent to LogiNext after the trip has been set to EN ROUTE
* There is no "Final send" before cut-off - this was part of the original design, but removed during development with the agreement of the customer.}}

== Execution ==
When sent to and accepted by the carrier, the carrier will begin the execution around half an hour before the departure of the trip.

Whilst being executed by the carrier, the carrier systems will pass messages to the LogiNext system around the events that have occurred during the execution. These will be passed onto CTMS and broadly result in the following processing:

* Cancelled - the carrier has cancelled the transport booking.
** Each item on the order will be marked with the quantity as delivered, with an item history that says that this item has been cancelled by the carrier.
** In this case, the order will be removed from the trip in CTMS (unplanned and the status set back to UNSCHEDULED or SCHED-COL).
** An audit record will be added showing the order has been cancelled by the external carrier
* Picked Up - the carrier has declared that the transport booking has been collected from the collection location successfully.
**Each item on the order will be marked with the quantity as despatched, with an item history that says that this item has been successfully collected by the carrier.
** The actual collection time will be noted.
** If this is the first order picked up on this trip, the trip will be set to status EN-ROUTE.
* Not Picked Up - the carrier has declared that the transport booking has NOT been collected from the collection location.
**Each item on the order will be marked with a 0 quantity despatched, with an item history showing the reason code that was entered by the carrier.
** The actual collection time will be noted.
** If this is the first order not picked up on this trip, the trip will be set to status EN-ROUTE.
** The order will be set as status FAILED.
* Delivered - the carrier has declared that the transport booking has been delivered in full to the delivery location.
** Each item on the order will be marked with the quantity as delivered, with an item history that says that this item has been successfully delivered by the carrier.
** The order will be set as status DELIVERED.
** The actual delivery time will be noted.
* Partially Delivered - the carrier has declared that the transport booking has been delivered in part to the delivery location.
** Each item shown as not delivered in the message will be marked with a 0 quantity delivered, with an item history showing the reason code that was entered by the carrier.
** Each item on the order will be marked with the quantity as delivered, with an item history that says that this item has been successfully delivered by the carrier.
** The order will be set as status DELIVERED.
** The actual delivery time will be noted.
* Not Delivered - the carrier has declared that the transport booking has been not been delivered at all (for particular reasons) to the delivery location.
** Each item on the order will be marked with a 0 quantity delivered, with an item history showing the reason code that was entered by the carrier.
** The order will be set as status FAILED.
** The actual delivery time will be noted.

{{Warning}}Ad Hoc Collections (i.e. non-planned collections of empties during a job) are not being executed by the carriers, and no interface exists to process these. This may be added in a later phase.

{{Note}}

* ANY warnings or notes against the trip will be visible in the Trip Comments screens
* ANY rejections or cancellations will be visible in the Trip list in the Planning screen - the truck icon will be RED.
* ALL success and failures of messages to and from LogiNext are shown in the the LogiNext Auditing tab of the EDI Interface Errors screen. This will also show the reasons why this has happened. See later for details on checking this audit screen.

= Auditing =

== User Auditing ==
Any errors are recorded in the processing of the LogiNext trips, these will be displayed in the Comments/Errors tab and the truck icon in the trip tree will be displayed in RED.

[[File:LogiNext-Audit-Trip.png|800x800px]]

Additional information regarding the change of status times, changes of order quantities, etc, which are triggered by the LogiNext interface, can also be viewed on the following standard Audit screens:

* Planning screen - Audit tab.

* New Order screen - Audit tab.

== System Auditing ==
The detailed system auditing can be seen in the Interface Errors screen, on the LogiNext tab.

{{:Interface Errors - LogiNext Details}}

FleXipod Interface

2025-09-25T14:05:07Z

Anw: Updated

{{Incomplete}}

This guide shows how the Aptean Proof of Delivery system (APOD or formerly FleXipod) can be configured to be used from CTMS.

This require configuration as to when messages are sent, how they are formatted (the FleXipod attributes), at what level are messages sent (orders, stops, etc) and what information is expected to be received.

== Configuration ==
=== System Parameters ===
{| class="wikitable apt-searchable"
!Parameter !! Description !! Config By
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD ||Set to Y to indicate the FlexiPod interface is active ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_ACID ||Flexipod acid ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_BREAK_DROPS ||Flexipod include breaks for the drops in the Add API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CARRIERS ||Set to Y indicates the Carrier can control if a trip is sent to FlexiPod ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CLIENTNUM ||FleXipod ClientNum sent in interface ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CONSOLIDATE_APOD ||Flexipod consolidate the drops in the API calls (Y/N) ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_CONSOLIDATE_APOD_REF ||Flexipod consolidate the orders for the drops as the OMS reference or a type of customer reference (OMS/CUST/BOOK/DEL) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DEPOTS ||Set to Y indicates the Depot can control if a trip is sent to FlexiPod ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DEPOT_DEPART_ACTION ||Flexipod Depot Depart Action (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DEPOT_RETURN_ACTION ||Flexipod Depot Return Action (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DIRECT ||Set to Y to indicate the FlexiPod interface is direct and not using Route Execution ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DROP ||Determines the Drop level STOP-OMS or ITEM ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_END_OF_TRIP_ACTION ||Flexipod End of Trip Action (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_EXPIRY ||Sets the expiry date for the manifest as a number of days after the end of the trip. ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_EXTERNALSYSTEMUPDATE ||Flexipod process the External System Update messages in the API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_FORCEITEMSCAN ||Force the items to be scanned separately: 0 to use the ScanLevel or 1 to force the scan by item. ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_LISTPENDINGMANIFESTS ||Flexipod process the List Pending Manifest Update messages in the API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_MERGE_DROPS ||Flexipod merge the orders on the drop in the Add API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_PASSWORD ||FleXipod Webservice password ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_PREDEPARTURE_ACTION ||Controls whether the system Flexipod Pre-Departure Action get sent as part of the manifest (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_PROXY ||Flexipod proxy server ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_READDROP ||Flexipod process the Read Drop messages in the API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SCAN_LEVEL ||1,2 or 3 to indicate line or item level scanning ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SCAN_TYPE ||Contents and items ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SIGNATORY ||Set to Y to store the SignedByName as the actual signatory as information for the order at its collection of delivery location ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_SPLIT ||Are orders to be split? ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SYSTEM ||FleXipod SYSTEM ID sent in interface ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_TIMEZONE ||Flexipod timezone for the UpdateManifests API calls ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_TPCLIENTNUM ||FleXipod TPClientNum sent in interface ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_UNALLOCATED_DRIVER ||FleXipod uses an unallocated driver when one is not assigned to a trip ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_UPDATE_MANIFESTS ||FleXipod use UpdateManifests to add manifests (Y/N) ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_USERCODE ||FleXipod webservice usercode ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_USERNAME ||FleXipod webservice username ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_WEBSERVICE ||Flexipod webservice endpoint URL ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_WEBSERVICE_TASK ||Flexipod webservice endpoint URL for Tasks ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_WEBSERVICE_UI ||Flexipod webservice endpoint URL ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_WEBSERVICE_UI_EXEC ||Flexipod webservice endpoint URL for Route Execution ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_X_API_KEY ||Flexipod x-api-key for External System Update messages ||SYSTEM
|- bgcolor="goldenrod" color="white" style="background-color: goldenrod; color: white;"
|FLEXIPOD_TENNANT ||? ||SYSTEM
|- bgcolor="goldenrod" color="white" style="background-color: goldenrod; color: white;"
|FLEXIPOD_TENNANT_KEY1 ||? ||SYSTEM
|}

Key:
* red: no longer in use
* green: in use
* amber: in use, but not defined

=== Carrier ===
The FLEXIPOD flag must be enabled when configured by carrier (system parameter FLEXIPOD_CARRIERS) for carriers that require the use of FlexiPOD.<center>
[[File:Res carrier.png|800x800px]]
</center>

=== Depot Locations ===
The FLEXIPOD flag must be enabled when configured by depot (system parameter FLEXIPOD_DEPOTS) for depots that require the use of FlexiPOD.<center>
[[File:Loc 7.png|800x800px]]
</center>

=== EDI Processes ===

'''FLEXIPOD_OUT'''

This process sends the triggered manifests to APOD.

* Flow Type: PROCESS
* Package Name: PROCESS, DP_FLEXIPOD.PROCESS_FLEXIPOD_OUT
* Process: i_process_name FLEXIPOD_OUT
* Interval: 5 minutes

'''FLEXIPOD_SENDLISTPENDING'''

This process checks to see if there are any pending updates from the manifests and imports the details.

* Flow Type: PROCESS
* Package Name: PROCESS DP_FLEXIPOD.send_listpendingmanifestupdates
* Process: PROCESS FLEXIPOD_SENDLISTPENDING
* Interval: 1 minute

=== Reason Codes and Decodes ===

A decode of name "FLX_RESULT_CODES" type "REFERENCE" must be configured to map all of the reason codes from APOD into CTMS.

Several ITEM_NON_CON reason codes must be created to map to the APOD reason codes.:

Examples:
{| class="wikitable"
!APOD !! CTMS !! Description || At Fault !! Action !! Type !! CBR
|-
|1 ||SD ||Successful Delivery || || || ||
|-
|10 ||SD ||Successful Delivery || || || ||
|-
|2 ||FV ||Failed Visit || || ||FAILURE ||Y
|-
|3 ||SD ||Successful Delivery || || || ||
|-
|4 ||UD ||Unsuccessful Delivery || || ||FAILURE ||
|-
|5 ||SC ||Successful Collection || || || ||
|-
|6 ||SJ ||Skipped Job || || ||FAILURE ||Y
|-
|7 ||NR ||No Longer Required || || ||FAILURE ||
|-
|8 ||PR ||Payment Refused || || || ||
|}

Plus any reason codes created in FlexiPOD must be created within TMS for the audit history to accurately represent any reasons selected by the driver.

{{Note}} For each implementation, the reason codes and numbers will differ. For example, 1 and 10 may not be "Successfully Delivered", so the decode mapping MUST be in place for the APOD interface.

=== Attribute Configuration ===
Attributes against Manifests, Drops and Items can be configured by your Aptean implementation team. Up to {{Warning}} 10 attributes may be defined at each level except Drop, which may contain 20 attributes.

In general, the following is allowed at each level:
* Manifest
** Information derived directly from the trip, such as route code, trailer type, driver, etc.
* Drop
** Information derived from the transport order header, such as the main references, instructions
** Information derived from the customer of the transport order, such as parameters against that customer.
** Any sub-reference held against that transport order.
** Any sub-reference held against the transport order's destination location.
* Item
** Information derived from the order items.
** Order Reference information
** Any references from the Drop above
** {{Note}} Including Quarantine status through the order reference STATUS)

An example is below:

{| class="wikitable apt-searchable"
!Project Name !!Level !!Number !!Source !!Target
|-
|Stapletons ||Drop ||1 ||so.booking_ref ||
|-
|Stapletons ||Drop ||2 ||so.del_point_ref ||
|-
|Stapletons ||Drop ||3 ||dp_flexipod.get_order_val("ORDER","PRICE", ||
|-
|Stapletons ||Drop ||4 || ||
|-
|Stapletons ||Drop ||5 || ||
|-
|Stapletons ||Drop ||6 ||dp_flexipod.get_ref("LOCATION","PERMIT_NUMBER", ||
|-
|Stapletons ||Drop ||7 ||oc.free_text1 ||
|-
|Stapletons ||Drop ||8 ||dp_flexipod.get_ref("LOCATION","UNITARY_AUTHORITY", ||
|-
|Stapletons ||Drop ||9 ||dp_flexipod.get_ref("LOCATION","LICENCE_NUMBER", ||
|-
|Stapletons ||Drop ||10 ||so.total_weight ||
|-
|Stapletons ||Drop ||11 ||so.total_pieces ||
|-
|Stapletons ||Drop ||12 ||oc.pay_on_delivery ||
|-
|Stapletons ||Drop ||13 ||oc.collect_casings ||
|-
|Stapletons ||Drop ||14 || ||
|-
|Stapletons ||Drop ||15 || ||
|-
|Stapletons ||ItemAttributes ||1 ||soi.du_type ||
|-
|Stapletons ||ItemAttributes ||2 ||soi.weight ||
|-
|Stapletons ||ItemAttributes ||3 ||dp_flexipod.get_order_val("ITEM","UNIT_WEIGHT", ||
|-
|Stapletons ||ItemAttributes ||4 ||dp_flexipod.get_order_val("ITEM","UNIT_PRICE", ||
|-
|Stapletons ||ItemAttributes ||5 ||dp_flexipod.get_order_val("ITEM",'STATUS", ||
|-
|Stapletons ||Manifest ||1 ||st.route_code ||
|-
|Stapletons ||Manifest ||2 ||st.trailer_type ||
|}

{{Warning}} You MUST use double-quotes when specifying attributes to dp_flexipod functions such as dp_flexipod.get_order_val.

== Sending Trips to FlexiPOD ==
{{Warning}} This has changed

This happens automatically when:
* the trip is set to status "ACCEPTED" or "EN-ROUTE"
* when any changes happen to the trip i.e. orders are added, removed or moved on a trip that is at those statuses.
* When the driver, carrier or tractor has been added or changed on a trip that is at those statuses.

== Actions Taken on Update ==
Gets updates from FleXipod drops and processes them

Marks message as collected

Stores order references
* TrackingID
* TrackingURL
* JobReportName

Stores signatory and filename if present
* As ord_information
* As References
** SignedByName
** SignedByFilename
** SiteImageFilename

If item details provided:
* Updates stop Actual Arrive and Actual Depart

* If scan_type = 'I'
** Creates Order Item Reasons from decoded reason code for actions against the drops and items (such as successful delivery, etc).
** Creates Order Item Reasons from decoded reason code if there are non-conformities
** Updates item delivered quantities
** Updates order line quantities
** Updates POC/POD flag against the order

* If scan_type = 'P'
** Same for each item in the pallet.

If event_name = 'Pre-Departure'
* Updates SU stop actual arrive

If event_name = 'Depot Depart'
* Updates SU stop actual arrive and actual depart
* Sets the trip status
* Updates items as despatched
* Updates lines as despatched
* Validates the order

If event_name = 'Depot Return'
* Updates CL stop actual arrive

If event_name = 'End of Trip'
* Updates CL stop actual arrive and actual depart
* Sets the trip status

For all order updates:
* Change order status to DELIVERED if anything delivered
* Change order status to FAILED if nothing delivered

{{Note}} All changes to order are audited.

[[Category:Interfaces]]

Carriers

2025-09-25T07:33:33Z

Anw: Minor formatting change

The Carrier tab of the Resources Maintenance screen allows carrier information to be configured. <center>
[[File:Res carrier main.png|800x800px]]
</center>Carriers can be connected to carrier groups and can be of a certain type. For example, FLEET type is part of the business or client using C-TMS whereas HAULIER may be deemed to be 3rd parties.

One use of the carrier records is to record typical fleet routes or groups so that planning personnel in other areas of the system, such as when using Trip Manipulation can easily identify them.

You can click '''New Carrier''' to create a new carrier:

<center>[[Image:res_carrier.png|800px]]</center>

A variety of attributes are configured here for each Carrier record such as ''V.A.T. number, hub location, maximum shift time, fixed costs'' and head quarters (''HQ Location'').

'''Save''' will save the changes, note a message at the bottom of the form will confirm the save.

You can continue entering your next haulier or click '''Cancel''' to close the form.

The haulier is now visible in the ''Carrier'' tab.

Additional fields include:
* ''Display Type'' - Note that the ''Display Type'' can be set to either "''Poplist''" or "''Freetext''", the latter will allow free text entry of data into the trips allocated to this carrier (driver, vehicle etc) and the former will force you to select data from predetermined lists which we will see later in this section. This is normally set to "''Poplist''" for internal fleet carriers, as the assets should be fixed and can therefore be pre-populated.
* ''Hub Location''/''Enforce Start at Hub''/''Enforce End at Hub'' - ''Fleet'' resources should be set up with a ''Hub Location'' and the ''Enforce Start at Hub'' and ''Enforce End at Hub'' boxes ticked to enable them to operate correctly. This will ensure that all trips allocated to these carriers will start and end at this location as opposed to hauliers who will generally be utilized from location to location rather than round trips.
* Additionally the ''Trip Threshold Hours'', ''Standard Shift Hours'', ''Overtime Factor'', ''Max Shift Hours'' and ''Standard Factor'' should be populated with default fleet data.
* ''Current Haulage units'' - This is a numeric field that has no validation behind it but give the user an indication as to how many Tractor Units the Carrier has control over. It assists mainly when tendering out large jobs to 3rd party Hauliers so that they can see if the Haulier is big enough to take the job on.
* ''Permit Debrief'' - Checking this box gives Permission to the Carrier to allow them to debrief their own Trips via the [[Carrier Trip Management]] Screen.
* ''Transport Mode'' - indicates the type of carrier (ROAD or AIR).
* ''Tracking'' – This drop down list triggers the interface with a Smartphone application that allows real time debriefing. It can be set against a Carrier or an individual Driver. There are also a number of system parameters shown in the table below that need to be enabled for the Application.
* ''EPOD enabled'' - indicates if trips the carrier is assigned to are sent to Aptean POD - Calidus Edition (CALIDUS ePOD) for execution and automatic debrief.
* ''Flexipod'' - indicates if the carrier is using the Aptean POD (APOD or formerly FleXipod) system for execution and automatic debrief. This applies only if the system is configured to use this flag in system parameters.
* ''LogiNext Enabled'' - indicates if the carrier is using the LogiNext 4PL system to manage a 3rd party carrier trip assignment and automatic debrief. See [[Using the LogiNext Carrier Interface]] for more information on this process.

You can edit an existing carrier by selecting it from the table and clicking the '''Edit''' button. This will show the same screen as adding a new carrier, but with all of the information populated.

You can delete an existing carrier (if it has not been used) by clicking the '''Delete''' button.

You can also access and edit the following information about the carrier through the buttons provided:

* '''Fuel Surcharges'''.
* '''Contacts'''.

=== Fuel Surcharges ===
Fuel surcharges are used when generating trip costs for trips executed by that carrier.<center>
[[File:Res carrier fuel.png|800x800px]]
</center>The fuel surcharge is applied on trips that were executed (started) on or following the ''Effective Date'' supplied.

You can add a new surcharge by clicking in an empty row and entering the information (''Effective Date, Fuel Surcharge''). You can edit a row by clicking on that row. You can '''Save''' your changes with the button provided, or discard any changes with the '''Close''' button. You can also delete an existing contact using the '''Delete Record''' button provided.

=== Contacts ===
This information may be used for reference if sending documents to the carrier.<center>
[[File:Res carrier contacts.png|800x800px]]
</center>You can add a new contact by clicking in an empty row and entering the information (''Surname, Forename, Title, Phone, Email''). You can edit a row by clicking on that row. You can '''Save''' or '''Cancel''' your changes with the buttons provided. You can also '''Delete''' an existing contact using the button provided.

=== Imports ===
Carrier records can also be created and updated by synchronisation between the external applications and C-TMS, especially where the client offers the trips for tender to third-party hauliers, and, where new hauliers may bid for business.

Carriers may be created via imports:
* [[Imports_Details#CARRIER|CARRIER]]

Carriers

2025-09-25T07:25:21Z

Anw: Minor formatting change

The Carrier tab of the Resources Maintenance screen allows carrier information to be configured. <center>
[[File:Res carrier main.png|800x800px]]
</center>Carriers can be connected to carrier groups and can be of a certain type. For example, FLEET type is part of the business or client using C-TMS whereas HAULIER may be deemed to be 3rd parties.

One use of the carrier records is to record typical fleet routes or groups so that planning personnel in other areas of the system, such as when using Trip Manipulation can easily identify them.

You can click '''New Carrier''' to create a new carrier:

<center>[[Image:res_carrier.png|800px]]</center>

A variety of attributes are configured here for each Carrier record such as V.A.T. number, hub location, maximum shift time, fixed costs and head quarters.

Note that the "Display Type" can be set to either "''Poplist''" or "''Freetext''", the latter will allow free text entry of data into the trips allocated to this carrier (driver, vehicle etc) and the former will force you to select data from predetermined lists which we will see later in this section. '''Save''' will save the changes, note a message at the bottom of the form will confirm the save.

You can continue entering your next haulier or click '''Cancel''' to close the form.

The haulier is now visible in the carrier tab.

"''Fleet''" resources should be set up with a "''Hub Location''" and the "''Enforce Start at Hub''" and "''Enforce End at Hub''" boxes ticked to enable them to operate correctly. This will ensure that all trips allocated to these carriers will start and end at this location as opposed to hauliers who will generally be utilized from location to location rather than round trips.

Note that the "''Display Type''" is normally set to "''Poplist''" for internal fleet carriers, as the assets should be fixed and can therefore be pre-populated. Additionally the "''Trip Threshold Hours''", "''Standard Shift Hours''", "''Overtime Factor''", "''Max Shift Hours''" and "''Standard Factor''" should populate with default fleet data.

"''Current Haulage units''" - This is a numeric field that has no validation behind it but give the user an indication as to how many Tractor Units the Carrier has control over. It assists mainly when tendering out large jobs to 3rd party Hauliers so that they can see if the Haulier is big enough to take the job on.

"''Permit Debrief''" - Checking this box gives Permission to the Carrier to allow them to debrief their own Trips via the [[Carrier Trip Management]] Screen.

"''Transport Mode''" - indicates the type of carrier (ROAD or AIR).

"''Tracking''"– This drop down list triggers the interface with a Smartphone application that allows real time debriefing. It can be set against a Carrier or an individual Driver. There are also a number of system parameters shown in the table below that need to be enabled for the Application.

"''EPOD enabled''" indicates if trips the carrier is assigned to are sent to Aptean POD - Calidus Edition (CALIDUS ePOD) for execution and automatic debrief.

"''Flexipod''" indicates if the carrier is using the Aptean POD (APOD or formerly FleXipod) system for execution and automatic debrief. This applies only if the system is configured to use this flag in system parameters.

"''LogiNext Enabled''" indicates if the carrier is using the LogiNext 4PL system to manage a 3rd party carrier trip assignment and automatic debrief. See [[Using the LogiNext Carrier Interface]] for more information on this process.

You can edit an existing carrier by selecting it from the table and clicking the '''Edit''' button. This will show the same screen as adding a new carrier, but with all of the information populated.

You can delete an existing carrier (if it has not been used) by clicking the '''Delete''' button.

You can also access and edit the following information about the carrier through the buttons provided:

* '''Fuel Surcharges'''.
* '''Contacts'''.

=== Fuel Surcharges ===
Fuel surcharges are used when generating trip costs for trips executed by that carrier.<center>
[[File:Res carrier fuel.png|800x800px]]
</center>The fuel surcharge is applied on trips that were executed (started) on or following the ''Effective Date'' supplied.

You can add a new surcharge by clicking in an empty row and entering the information (''Effective Date, Fuel Surcharge''). You can edit a row by clicking on that row. You can '''Save''' your changes with the button provided, or discard any changes with the '''Close''' button. You can also delete an existing contact using the '''Delete Record''' button provided.

=== Contacts ===
This information may be used for reference if sending documents to the carrier.<center>
[[File:Res carrier contacts.png|800x800px]]
</center>You can add a new contact by clicking in an empty row and entering the information (''Surname, Forename, Title, Phone, Email''). You can edit a row by clicking on that row. You can '''Save''' or '''Cancel''' your changes with the buttons provided. You can also '''Delete''' an existing contact using the button provided.

=== Imports ===
Carrier records can also be created and updated by synchronisation between the external applications and C-TMS, especially where the client offers the trips for tender to third-party hauliers, and, where new hauliers may bid for business.

Carriers may be created via imports:
* [[Imports_Details#CARRIER|CARRIER]]

FleXipod Interface

2025-09-25T07:22:17Z

Anw: Updated

{{Incomplete}}

This guide shows how the Aptean Proof of Delivery system (APOD or formerly FleXipod) can be configured to be used from CTMS.

This require configuration as to when messages are sent, how they are formatted (the FleXipod attributes), at what level are messages sent (orders, stops, etc) and what information is expected to be received.

== Configuration ==
=== System Parameters ===
{| class="wikitable apt-searchable"
!Parameter !! Description !! Config By
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD ||Set to Y to indicate the FlexiPod interface is active ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_ACID ||Flexipod acid ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_BREAK_DROPS ||Flexipod include breaks for the drops in the Add API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CARRIERS ||Set to Y indicates the Carrier can control if a trip is sent to FlexiPod ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CLIENTNUM ||FleXipod ClientNum sent in interface ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CONSOLIDATE_APOD ||Flexipod consolidate the drops in the API calls (Y/N) ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_CONSOLIDATE_APOD_REF ||Flexipod consolidate the orders for the drops as the OMS reference or a type of customer reference (OMS/CUST/BOOK/DEL) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DEPOTS ||Set to Y indicates the Depot can control if a trip is sent to FlexiPod ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DEPOT_DEPART_ACTION ||Flexipod Depot Depart Action (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DEPOT_RETURN_ACTION ||Flexipod Depot Return Action (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DIRECT ||Set to Y to indicate the FlexiPod interface is direct and not using Route Execution ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DROP ||Determines the Drop level STOP-OMS or ITEM ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_END_OF_TRIP_ACTION ||Flexipod End of Trip Action (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_EXPIRY ||Sets the expiry date for the manifest as a number of days after the end of the trip. ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_EXTERNALSYSTEMUPDATE ||Flexipod process the External System Update messages in the API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_FORCEITEMSCAN ||Force the items to be scanned separately: 0 to use the ScanLevel or 1 to force the scan by item. ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_LISTPENDINGMANIFESTS ||Flexipod process the List Pending Manifest Update messages in the API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_MERGE_DROPS ||Flexipod merge the orders on the drop in the Add API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_PASSWORD ||FleXipod Webservice password ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_PREDEPARTURE_ACTION ||Controls whether the system Flexipod Pre-Departure Action get sent as part of the manifest (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_PROXY ||Flexipod proxy server ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_READDROP ||Flexipod process the Read Drop messages in the API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SCAN_LEVEL ||1,2 or 3 to indicate line or item level scanning ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SCAN_TYPE ||Contents and items ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SIGNATORY ||Set to Y to store the SignedByName as the actual signatory as information for the order at its collection of delivery location ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_SPLIT ||Are orders to be split? ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SYSTEM ||FleXipod SYSTEM ID sent in interface ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_TIMEZONE ||Flexipod timezone for the UpdateManifests API calls ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_TPCLIENTNUM ||FleXipod TPClientNum sent in interface ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_UNALLOCATED_DRIVER ||FleXipod uses an unallocated driver when one is not assigned to a trip ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_UPDATE_MANIFESTS ||FleXipod use UpdateManifests to add manifests (Y/N) ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_USERCODE ||FleXipod webservice usercode ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_USERNAME ||FleXipod webservice username ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_WEBSERVICE ||Flexipod webservice endpoint URL ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_WEBSERVICE_TASK ||Flexipod webservice endpoint URL for Tasks ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_WEBSERVICE_UI ||Flexipod webservice endpoint URL ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_WEBSERVICE_UI_EXEC ||Flexipod webservice endpoint URL for Route Execution ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_X_API_KEY ||Flexipod x-api-key for External System Update messages ||SYSTEM
|- bgcolor="goldenrod" color="white" style="background-color: goldenrod; color: white;"
|FLEXIPOD_TENNANT ||? ||SYSTEM
|- bgcolor="goldenrod" color="white" style="background-color: goldenrod; color: white;"
|FLEXIPOD_TENNANT_KEY1 ||? ||SYSTEM
|}

Key:
* red: no longer in use
* green: in use
* amber: in use, but not defined

=== Carrier ===
The FLEXIPOD flag must be enabled when configured by carrier (system parameter FLEXIPOD_CARRIERS) for carriers that require the use of FlexiPOD.<center>
[[File:Res carrier.png|800x800px]]
</center>

=== Depot Locations ===
The FLEXIPOD flag must be enabled when configured by depot (system parameter FLEXIPOD_DEPOTS) for depots that require the use of FlexiPOD.<center>
[[File:Loc 7.png|800x800px]]
</center>

=== EDI Processes ===

'''FLEXIPOD_OUT'''

This process sends the triggered manifests to APOD.

* Flow Type: PROCESS
* Package Name: PROCESS, DP_FLEXIPOD.PROCESS_FLEXIPOD_OUT
* Process: i_process_name FLEXIPOD_OUT
* Interval: 5 minutes

'''FLEXIPOD_SENDLISTPENDING'''

This process checks to see if there are any pending updates from the manifests and imports the details.

* Flow Type: PROCESS
* Package Name: PROCESS DP_FLEXIPOD.send_listpendingmanifestupdates
* Process: PROCESS FLEXIPOD_SENDLISTPENDING
* Interval: 1 minute

=== Reason Codes and Decodes ===

A decode of name "FLX_RESULT_CODES" type "REFERENCE" must be configured to map all of the reason codes from APOD into CTMS.

Several ITEM_NON_CON reason codes must be created to map to the APOD reason codes.:

Examples:
{| class="wikitable"
!APOD !! CTMS !! Description || At Fault !! Action !! Type !! CBR
|-
|1 ||SD ||Successful Delivery || || || ||
|-
|10 ||SD ||Successful Delivery || || || ||
|-
|2 ||FV ||Failed Visit || || ||FAILURE ||Y
|-
|3 ||SD ||Successful Delivery || || || ||
|-
|4 ||UD ||Unsuccessful Delivery || || ||FAILURE ||
|-
|5 ||SC ||Successful Collection || || || ||
|-
|6 ||SJ ||Skipped Job || || ||FAILURE ||Y
|-
|7 ||NR ||No Longer Required || || ||FAILURE ||
|-
|8 ||PR ||Payment Refused || || || ||
|}

Plus any reason codes created in FlexiPOD must be created within TMS for the audit history to accurately represent any reasons selected by the driver.

{{Note}} For each implementation, the reason codes and numbers will differ. For example, 1 and 10 may not be "Successfully Delivered", so the decode mapping MUST be in place for the APOD interface.

=== Attribute Configuration ===
Attributes against Manifests, Drops and Items can be configured by your Aptean implementation team. Up to {{Warning}} 10 attributes may be defined at each level except Drop, which may contain 20 attributes.

In general, the following is allowed at each level:
* Manifest
** Information derived directly from the trip, such as route code, trailer type, driver, etc.
* Drop
** Information derived from the transport order header, such as the main references, instructions
** Information derived from the customer of the transport order, such as parameters against that customer.
** Any sub-reference held against that transport order.
** Any sub-reference held against the transport order's destination location.
* Item
** Information derived from the order items.
** Order Reference information
** Any references from the Drop above
** {{Note}} Including Quarantine status through the order reference STATUS)

An example is below:

{| class="wikitable apt-searchable"
!Project Name !!Level !!Number !!Source !!Target
|-
|Stapletons ||Drop ||1 ||so.booking_ref ||
|-
|Stapletons ||Drop ||2 ||so.del_point_ref ||
|-
|Stapletons ||Drop ||3 ||dp_flexipod.get_order_val('ORDER','PRICE', ||
|-
|Stapletons ||Drop ||4 || ||
|-
|Stapletons ||Drop ||5 || ||
|-
|Stapletons ||Drop ||6 ||dp_flexipod.get_ref('LOCATION','PERMIT_NUMBER', ||
|-
|Stapletons ||Drop ||7 ||oc.free_text1 ||
|-
|Stapletons ||Drop ||8 ||dp_flexipod.get_ref('LOCATION','UNITARY_AUTHORITY', ||
|-
|Stapletons ||Drop ||9 ||dp_flexipod.get_ref('LOCATION','LICENCE_NUMBER', ||
|-
|Stapletons ||Drop ||10 ||so.total_weight ||
|-
|Stapletons ||Drop ||11 ||so.total_pieces ||
|-
|Stapletons ||Drop ||12 ||oc.pay_on_delivery ||
|-
|Stapletons ||Drop ||13 ||oc.collect_casings ||
|-
|Stapletons ||Drop ||14 || ||
|-
|Stapletons ||Drop ||15 || ||
|-
|Stapletons ||ItemAttributes ||1 ||soi.du_type ||
|-
|Stapletons ||ItemAttributes ||2 ||soi.weight ||
|-
|Stapletons ||ItemAttributes ||3 ||dp_flexipod.get_order_val('ITEM','UNIT_WEIGHT', ||
|-
|Stapletons ||ItemAttributes ||4 ||dp_flexipod.get_order_val('ITEM','UNIT_PRICE', ||
|-
|Stapletons ||ItemAttributes ||5 ||dp_flexipod.get_order_val('ITEM','STATUS', ||
|-
|Stapletons ||Manifest ||1 ||st.route_code ||
|-
|Stapletons ||Manifest ||2 ||st.trailer_type ||
|}

== Sending Trips to FlexiPOD ==
{{Warning}} This has changed

This happens automatically when:
* the trip is set to status "ACCEPTED" or "EN-ROUTE"
* when any changes happen to the trip i.e. orders are added, removed or moved on a trip that is at those statuses.
* When the driver, carrier or tractor has been added or changed on a trip that is at those statuses.

== Actions Taken on Update ==
Gets updates from FleXipod drops and processes them

Marks message as collected

Stores order references
* TrackingID
* TrackingURL
* JobReportName

Stores signatory and filename if present
* As ord_information
* As References
** SignedByName
** SignedByFilename
** SiteImageFilename

If item details provided:
* Updates stop Actual Arrive and Actual Depart

* If scan_type = 'I'
** Creates Order Item Reasons from decoded reason code for actions against the drops and items (such as successful delivery, etc).
** Creates Order Item Reasons from decoded reason code if there are non-conformities
** Updates item delivered quantities
** Updates order line quantities
** Updates POC/POD flag against the order

* If scan_type = 'P'
** Same for each item in the pallet.

If event_name = 'Pre-Departure'
* Updates SU stop actual arrive

If event_name = 'Depot Depart'
* Updates SU stop actual arrive and actual depart
* Sets the trip status
* Updates items as despatched
* Updates lines as despatched
* Validates the order

If event_name = 'Depot Return'
* Updates CL stop actual arrive

If event_name = 'End of Trip'
* Updates CL stop actual arrive and actual depart
* Sets the trip status

For all order updates:
* Change order status to DELIVERED if anything delivered
* Change order status to FAILED if nothing delivered

{{Note}} All changes to order are audited.

[[Category:Interfaces]]

Locations

2025-09-25T07:20:15Z

Anw: Updated Special tab to show Flexipod configuration (and others)

Locations are used to maintain the details related to a specific location such as their Address information, Contacts and Constraints. Location Maintenance form can be accessed from Maintenance Menu as shown below:

[[Image:loc_1.png]]

The Locations module assists in the creation, maintenance and retrieval of C-TMS data pertaining to how each location functions. The Locations data determines to a small degree how the orders are created in the Bookings form.

A Default Loading and Unloading rate controlled by 2 system parameters (GEO_DEFAULT_LOAD_RATE and GEO_DEFAULT_UNLOAD_RATE) is populated when a location is created.

The Locations data can be viewed, created, edited and maintained through the following Locations form.

[[Image:loc_2.png]]

==Query existing Locations:==

To query for a Location, enter the ID of the location with a '%' as shown and click on the query button. This will provide the details of the Location queried. An example is shown below.

[[Image:loc_3.png]]

You can traverse through the relevant tabs to get details of them. '''Note the tabs will be discussed later in the document'''

[[Image:loc_4.png]]

You can also query using a lookup against the location ID. press the button indicated by the red square below to get a list of locations:

[[Image:loc_query_lookup.png|800px]]

Choose your location and press the '''OK''' button. The data for the chosen location is displayed.

==Creation of a new Location:==
The Address tab provides the facility to define and maintain Depots. As well as the address, the depot can be defined as a Branch or RDC. The longitudes and latitudes of the depot are entered along with open and close times - if required.

To create a new Location, click on the '''New Location''' button and enter the Location ID, Location Type and the Location Name as shown below.

[[Image:loc_5.png]]

When creating a new location, you may assign a time zone, which will be used to set transaction times at the location. You may also assign a customer client code which allows you to select a subset of locations in order entry.

The Location ID should identify the location uniquely. The Location Type can hold one of the types set up in the system, typically from the below:
* BRANCH - if the location is a delivery point.
* RDC - if the location is a depot/distribution centre.
* SUPPLIER - if the location is a vendor/supplier location.

Types are maintained in the system, so you can have many others, such as:
* CROSSDOCK
* HOSPITAL
* SESSION - if the location is a session location.
* SWAP - if the location is a SWAP location (PARK, LAYBY etc.)
* TEAMBASE - if the location is a session teambase location.
* AIRPORT - if the location is an airport

==Address==
This tab contains the address of the location.

[[Image:loc_6.png]]

In the address tab, enter the address details and the most important fields in this tab are the Postal Code, Town and Country (ISO Code). The 'Postal Reg' and the 'Planning Reg' will be populated by the system based on the postal code.

The Lat and Long fields will be populated by the [[External Map Applications]] used to geocode locations, once the location is used in an Order. This can also be manually entered here. The location needs to be required upon first entry to display the latitude and longitude values.

The Loading Rate and Unloading Rate specify the time required to load and unload a truck in the given location. This will be described in the Resources section of the training.

The Paragon id can contain up to 40 characters no additional validation is performed.

The Ext Ref can contain up to 50 characters and must be unique to the location. If a duplicate value is entered an error will be raised and the changes will not be saved.

UNL Location is related to emissions reporting. The code will be automatically created for you when the location is created, from the country code and the first 3 characters of the Town. This is used in the Carbon Emissions extract only.

You can click the '''Show on Map''' button to open a new tab in your browser to show the position of the location on a map.

Once you have entered the required information, click on the '''Save''' button to save the changes that you have made.

To delete the location, use the '''Delete''' button - you will be prompted for confirmation before it is deleted, and the system will not allow you to delete a location where that location has been used on orders.

==Special==
Additional data such as Alternative Collection/Delivery Location can be attached to a location or comments can be added.

[[Image:loc_7.png|800x800px]]

The following fields are available

* ''Comments'' - Location comments are for reference - these are used in some interfaces to electronic POD systems (such as Aptean Proof of Delivery (FleXipod) and are used as location instructions.
* ''Default SC Hanging''
* ''Default SC Boxed''
* ''Alternative Collection Loc''
* ''Alternative Delivery Loc''
* ''Alternative Code''
* ''Default Du Type'' - A default DU type can be added against the location which can be used to automatically assign to orders generated for collection from this location.
* ''Collecting Depot''
* ''Default Despatch Lane''
* ''Tracking System'' - a drop-down list of ''ISOTRAK, MICROLISE, TOMTOM''.
* ''Parent Location''
* ''Default Label Printer''
* ''Hub Location''
* ''RF Cross-dock'' (Checkbox) - this controls whether the location is used for item scanning through CALIDUS WCS.
* ''Early Stop Window'' (Checkbox)
* Fixed Lat Longs (Checkbox)
* ''Email Trip Manifest'' (Checkbox)
* ''Exclusive Drop'' (Checkbox)
* ''Allow DG Pallets'' (Checkbox) - whether the location allows dangerous goods.
* ''Create Empties'' (Checkbox)
* ''WCS Item to Asset'' (Checkbox) - whether goods scanned at this depot through CALIDUS WCS may be added to assets.
* ''Master Location'' (Checkbox)
* ''MIX MOVE'' (Checkbox)
* ''Retain Planning Region'' (Checkbox) - see notes below.
* ''Flexipod'' (Checkbox) - controls whether this depot (RDC) location is using Aptean POD (APOD or FleXipod) for execution of trips, if configured at depot level.

{{Note}} The system will always automatically default to the planning region associated with the postal region of the address. If you want to change the planning region of location, you can over-ride this by checking the "Retain Planning Region" checkbox and
change the planning region in the screen against the location (you can use a lookup for this). When you save (or use the '''Update''' button), the new region will be saved and the system will not automatically reset it.

==Slots==
Collection and Delivery [[Slot]]s are maintained for each location. Each [[Slot]] details the collection and delivery windows on a particular day that the collection or delivery of goods from one location to another should be scheduled. [[Slot]]s can be configured to use a specific Trailer Type and accept specific [[Product Types]]. [[Slot]]s are filled by the [[Create Transport Instructions]] process invoked from the [[Bookings]] form.

[[Image:loc_8.png]]

The slots are relative to a particular day of the week and cover a specified collection and delivery time window. It is these windows that are propagated onto the generated order.

===Manual Slot Manipulation===
Provides the facility to manually add, edit, delete and inactivate Slots. Only Slots in a Status of Active are displayed by default in the Slots tab as only Active Slots are considered by the system in the [[Create Transport Instructions]]'s process. A function to view Inactive Slots is included. An inactive slot gets ignored during the Create TI's process.

This also provides the facility to add, edit and delete Product Types and a Trailer Type from a Slot.

===Slot Import===
Slots can be imported into C-MTS Host via an inbound interface. In the case of Sainsbury's Supermarkets this is the VAST interface that runs nightly. This interface process inactivates all Slots in the system then either reactivates any Slots that exist in both the system and the new interface file or creates any new Slots. The Slot Import functionality on the Slots tab simply allows this import process to be invoked manually if required.

===Multiple Slot Deletion===
This function allows Inactive Slots to be removed from the system if they have not been activated for a user specified period of time. This ensures a manageable number of entries are displayed in the Slots tab if the option to display Inactive Slots is selected.

===Dynamic Day Offsets===
All Slots have collection and delivery windows and apply to a particular day. Slot windows are held with actual times, e.g. 10:00 - 11:00, and day offset. The use of day offset minimizes user maintenance as the actual date a Slot is used is not stored, it is implied by the day offset e.g. on Friday 12th July 2002, a Slot stored with a delivery window of 0 23:30 to 1 00:30 will be interpreted as 12th July 23:30 - 13th July 00:30 i.e. the day offset is used to decrement or increment the actual date on which the Slot is being used.

===Slot Trailers===
Each Slot can be configured with a specific Trailer Type. This allows a Slot to be configured to use, for example, a more maneuverable Trailer if access is restricted.

===Slot Products===
Slots can be configured to accept one or more Product Types. When Orders are created in Slots by the Create Transport Instructions process, the process is constrained to only fill Slots with permissible Product Types. If a Product Type is not compatible with a Slot it cannot be assigned to the Slot.

Each Product Type in a Slot has a Priority. If the Priority is one then the Product Type will always be assigned to the Slot. However, if the Priority is two, the Product Type will only be assigned to the Slot if it is topping up the Slot i.e. the Slot already contains some Priority one Product Type.

Slot Product Types can also be designated as Advance Only so that only Advance Orders for the appropriate Product Type are assigned to the Slot

==Constraints==
This tab allows for constraints to be set up against a location.

Constraints can be added to a location, which are taken into account when orders are created. If a constraint is added to a location, then the constraint name, day, start time, end time and value are required. For example if a constraint MAX_TRLR_LENGTH with a value of 33 exists for a location, then, it indicates that trailers over the length of 33 cannot be used on a particular day, for the location in question.

To create constraints for the location, click on the '''New''' button and enter the details as shown. The Constraint Type specifies the constraint in a specific location such as only an 11 ft truck is allowed on Mondays between 10:00 to 17:00 hours. Once the details are entered, click on the '''OK''' button to save it.

[[Image:loc_9.png]]

==Trailer Types==
The Trailer Types tab specifies the trailers that are compatible with the location.

To create a new record click the '''New''' button.

For the example here, this location can handle only 45ft curtain side trailers, i.e. when the 'Include' option is selected then only those trailer mentioned in the list are compatible with the location.

When the 'Exclude' option is selected then, excluding those trailer all other trailers are compatible with the location.

[[Image:loc_10.png]]

{{Note}} A location may only use one trailer type or many.

==Contacts==
This tab allows for the details of the contacts for the location to be maintained.

Type in the contract details into the empty fields. Please ensure that you click on the '''Save''' button to save all the changes that you have made.

[[Image:loc_11.png]]

Once contacts are in the system, users can use this screen to set a default value for Email Tracking, Email Service Report and Send Text.
* Email Tracking – This contact’s email will be used when sending a tracking link for the Portal TTM system.
* Email Service Report – This contact’s email will be used when sending the completed work report from the EPOD system.
* Send Text – This contact’s phone number will be used when sending a text from the EPOD system.

The Email Tracking, Email Service Report and Send Text check boxes will show how they are set up within CTMS.

This information is assessed when sending data to EPOD and TTM on the created jobs.

==Roles==
A single location could behave as multiple location types, so that, for example, a [[Crossdock]] could also be a depot. This functionality is not currently used by any automated part of the system and is for reference only.

[[Image:loc_12.png]]

==DU Types==
This is a client specific form but it is used in conjunction with a Supplier Portal. In the Portal, when a new order is generated it will default to have an order line for each of the DUs held on this tab.

[[Image:loc_13.png]]

To enter a DU Type select the '''New''' button and the below screen is populated. Enter a DU Type manually or use the available list of values to find the relevant DU Type

[[Image:loc_14.png]]

Click '''OK''' to return back to the main screen

==References==
This Tab has been designed to add any additional Location Level references that may be needed for a specific project

[[Image:loc_15.png]]

To add a reference click the '''New''' button. The below screen is then populated:

[[Image:loc_16.png]]

Enter a Reference code. If known it can be typed in manually or selected from a list of values. The description is automatically populated and is a read only field. Then enter the relevant value

'''Please note the list of values is maintained in the Imports screen, within the Decodes tab as shown in the screenshot below'''

[[Image:loc_17.png]]

== LOTS ==
LOTS (Live Order Tracking System) or TTM (Track and Trace Module) can be used to track orders through a a portal.

This screen can be used to determine whether a customer is included or excluded from the data sent to Calidus Portal TTM.

== EPOD ==
This screen allows you to maintain location-specific parameters controlling how and when jobs for this location are sent to EPOD.

[[Image:loc_epod.png|800px]]

You can enter:
* Send EPOD Jobs Load/Unload - whether these jobs are sent to C-ePOD on this activity.
* Consolidate EPOD Jobs Load/Unload - whether these jobs are automatically consolidated when sent to C-ePOD on this activity.
* Send EPOD Dets Load/Unload - whether these jobs are sent with details (items) to C-ePOD on this activity.
* Job Group for EPOD Load/Unload - a specific job group to use when sending these jobs to C-ePOD on this activity.

All parameters are initially set to Default - the system uses the location type defaults set up in the [[Business Data Maintenance]] screen.

== Linked Locations ==
This tab allows for locations to be linked. Locations may be linked where they are the same building or same site. Linking may be automatically applied through EPOD or manually applied in C-TMS. While linked locations will create separate stops on a C-TMS trip, they will be presented in EPOD as a single stop.

[[Image:loc_linked_locations.png|800px]]

To manually link locations, click the '''Linked Maint''' button. This will display the following screen:

[[Image:loc_linked_locations_2.png|800px]]

Click on the '''Find''' button. This will populate the location details of the location you are linking to. Click the '''Add Link''' button.

[[Image:loc_linked_locations_3.png|800px]]

Enter data that you would like to search on, for example, data with 'Man' in the 'City' field with '%Man%'. Press the '''Find''' button to bring back the data:

[[Image:loc_linked_locations_4.png|800px]]

Select the locations that you want to link with the checkbox and then press the '''Add Link''' button as below:

[[Image:loc_linked_locations_5.png|800px]]

The linked locations screen will be shown again with all linked locations.

Press the '''Close''' button and you are returned to the main screen. {{Note}} At this point you will need to close the screen completely and go back in to show the change.

You can remove linked locations with the '''Break Link''' button.

== Lat/Long ==
Here you can view the auditing of when the location's co-ordinates were automatically processed.

[[Image:loc_latlong.png|800px]]

As described earlier in this document, C-TMS can be integrated with an online web service to automatically set the latitude and longitude values against a location.

== Preferred Carriers ==
You can use this tab to set preferred carriers and the preference (priority).

This is required for some scheduling engine processes, in order to determine whether a route for a carrier can be used from this location.

== Location Usage ==
You can maintain location usage here.

Location usage helps filter location data automatically depending on which customer or customer group your user has been configured to see.

Location usage can be by customer group or individual customer.

You can allocate location usage here by double-clicking on the location usage available section.

You can remove location usage here by double-clicking on the location usage allocated section.

You can also add or remove all location usage allocations by using the '''Add All''' and '''Remove All''' buttons.

== Information ==
You can add notes against a location here.

Note types are set up in the [[Business Data Maintenance]] screen.

== Network ==
You can view all point to point (network) distances and times from and to this location in this tab. These are used by the planning system to determine the time between stops, and are calculated automatically.

You can also delete, edit and add new network entries here.

== MCS ==
You can maintain the configuration of your depot item scanning solution Calidus MCS here.

{{Note}} You can only configure MCS against locations of type "RDC".

The following flags may be configured:
* ''MCS Active'' - this flag controls whether C-MCS is used at this location.
* ''MCS Identifier'' - this is an identifier of the depot, used by MCS. This is displayed against items in receipt, so the user can see from which depot the items originated, to aid in unloading.
* ''Receipt Only'' - this flag controls whether the onward stops on this trip (and subsequent trips to the next RDC) are automatically debriefed with the time this stop is debriefed. If set, only the stop being receipted will be debriefed.
* ''Despatch Only'' - this flag controls whether the previous stops on this trip (and prior trips back to the previous RDC) are automatically debriefed with the time this stop is debriefed. If set, only the stop being despatched will be debriefed.
* ''Print Pallet Label'' - this flag controls whether pallets built through C-MCS at this location will use pre-printed stationary (when unchecked), or will print the label from C-MCS (when checked).
* ''Pallet Building validation'' - this flag controls the validation of pallets built through MCS. In all cases, pallets are retained until the pallet is received at the next depot location, whether this is an MCS-enabled location or not. Values are:
** "To Next RDC" - items built onto pallets at this location will be validated that they are all going to the same next depot location;
** "To Final RDC" - items built onto pallets at this location will be validated that they are all going to the same final delivery depot;
** "By Final RDC Trip" - items built onto pallets at this location will be validated that they are all being delivered on the same final delivery trip.

* ''Pallet Building Process'' - values are:
** "Continuous"
** "Single"
* ''Pallet Closure'' - this flag controls whether pallet closure is an option for the C-MCS mobile device users.
* ''Pallet Seal at Closure'' - this option controls whether Seal number will be prompted for at pallet closure. Seal numbers are stored against a pallet in the AWB/Cons reference.
* ''Trans-ship Enabled'' - this flag enables the Trans-Ship process at this location. Trans-ship processing will identify whether the item is planned out of this location on a trip and, if so, will show the user the trip and vehicle and ask them to confirm by entering the vehicle registration. For pallets on the received trip, all items on the pallet must be planned out on the same trip. Successfully trans-shipped items will be marked as despatched on the outbound trip. if any item is not planned out of this location, or not all items on a pallet are planned together, the system will inform the user that trans-ship can't be completed and the items must be despatched separately.
* ''Debrief Stop Times'' - this flag controls whether C-MCS loading or unloading will debrief the stop times at that location.
* ''Set Trip Status at Receipt'' - if checked, the system will attempt to automatically move the trip to COMPLETED status when it is completed in C-MCS.
* ''Set Trip Status at Despatch'' - if checked, the system will attempt to automatically move the trip onto the next applicable status when it is completed in C-MCS. For PLANNED or TENDERED trips, this will be ACCEPTED status. For ACCEPTED trips, this will be EN-ROUTE.

== Fleet Inspection ==
{{Note}} This functionality affects only Vehicle Fleet Maintenance systems.

A customer's location's fleet of vehicles has a checking period. This could differ per customer location i.e. a hub depot might check once a month, a radial depot might check once every three months.

The period could differ for each location for the customer. So, a hub location (with a large number of vehicles that pass through and work regularly) might require checking more regularly than a small depot with minimal vehicles and lower runs.

The period for checking may be rolling or fixed. I.e. check 90% of vehicles in any 3-month period from any date or check 90% of vehicles between a fixed date range.

The Calidus systems will support a fixed period against the location only, consisting of:
* A start date.
* A period type, of the following values only:
** Calendar month.
** Days.
* A period value, consisting of a numeric entry.

[[Image:loc_fleet1.png|800px]]

For example, if the period value was 30 and the type was Days, if this was a fixed period that started 1st February (non-leap year), it would end 2nd March. The next period would begin 3rd March.

If the period was 1 calendar month fixed, that starts 1st February (non-leap year), it would end 28th February. The next period would begin 1st March and end 31st March.

The period start date and length will be determined when the inspection reports are run, determined by the date entered when the report is run.

== Route Details ==
{{Note}} This is specific to the Fixed Drop Scheduling Engine.

You can maintain the route and drop number for this location on this tab. This defines which fixed routes the location is on, and what drop number it should be on.
You can also specify whether the route/drop identified here is for use on bank holidays only.

== Location Windows ==
Location windows can be added or amended using the location windows tab.

[[Image: loc_window1.png|800px]]

Windows can be Added by pressing the '''New''' button.

[[Image: loc_window2.png|800px]]

* Day must be be between 1 and 7.
* Both windows must be entered in a HH24:MI format.
* Duplicate values are not allowed.
* Windows must not overlap.

Windows can be edited by pressing the '''Edit''' button.

[[Image: loc_window3.png|800px]]

Edited records will be validated in the same way as new records.

Windows can be removed by pressing the '''Delete''' button a confirmation message will be displayed to confirm the deletion.

[[Image: loc_window4.png|800px]]

== Imports ==
Locations may also be created or modified through the customer onboarding interface, when adding orders (through EDI, imports or manual entry) or through [[Imports]]:
* [[Customer Onboarding Interface]]
* [[Imports_Details#LOCATION|LOCATION]]
* [[Imports_Details#LOC_UPDATE|LOC_UPDATE]]
* [[Imports_Details#TI_ORDER|TI_ORDER]]

<noinclude>
[[Category:Maintenance|160]]
[[Category:C-TMS Modules|D-160]]
[[Category:C-TMS User Guide|BD-160]]
</noinclude>

File:Loc 7.png

2025-09-25T07:12:59Z

Anw: Anw uploaded a new version of File:Loc 7.png

Carriers

2025-09-25T07:06:00Z

Anw: Updated

The Carrier tab of the Resources Maintenance screen allows carrier information to be configured. <center>
[[File:Res carrier main.png|800x800px]]
</center>Carriers can be connected to carrier groups and can be of a certain type. For example, FLEET type is part of the business or client using C-TMS whereas HAULIER may be deemed to be 3rd parties.

One use of the carrier records is to record typical fleet routes or groups so that planning personnel in other areas of the system, such as when using Trip Manipulation can easily identify them.

You can click '''New Carrier''' to create a new carrier:

<center>[[Image:res_carrier.png|800px]]</center>

A variety of attributes are configured here for each Carrier record such as V.A.T. number, hub location, maximum shift time, fixed costs and head quarters.

Note that the "Display Type" can be set to either "''Poplist''" or "''Freetext''", the latter will allow free text entry of data into the trips allocated to this carrier (driver, vehicle etc) and the former will force you to select data from predetermined lists which we will see later in this section. '''Save''' will save the changes, note a message at the bottom of the form will confirm the save.

You can continue entering your next haulier or click '''Cancel''' to close the form.

The haulier is now visible in the carrier tab.

"''Fleet''" resources should be set up with a "''Hub Location''" and the "''Enforce Start at Hub''" and "''Enforce End at Hub''" boxes ticked to enable them to operate correctly. This will ensure that all trips allocated to these carriers will start and end at this location as opposed to hauliers who will generally be utilized from location to location rather than round trips.

Note that the "''Display Type''" is normally set to "''Poplist''" for internal fleet carriers, as the assets should be fixed and can therefore be pre-populated. Additionally the "''Trip Threshold Hours''", "''Standard Shift Hours''", "''Overtime Factor''", "''Max Shift Hours''" and "''Standard Factor''" should populate with default fleet data.

"''Current Haulage units''" - This is a numeric field that has no validation behind it but give the user an indication as to how many Tractor Units the Carrier has control over. It assists mainly when tendering out large jobs to 3rd party Hauliers so that they can see if the Haulier is big enough to take the job on.

"''Permit Debrief''" - Checking this box gives Permission to the Carrier to allow them to debrief their own Trips via the [[Carrier Trip Management]] Screen.

"''Transport Mode''" - indicates the type of carrier (ROAD or AIR).

"''Tracking''"– This drop down list triggers the interface with a Smartphone application that allows real time debriefing. It can be set against a Carrier or an individual Driver. There are also a number of system parameters shown in the table below that need to be enabled for the Application.

"''EPOD enabled''" indicates if trips the carrier is assigned to are sent to Aptean POD - Calidus Edition (CALIDUS ePOD) for execution and automatic debrief.

"''Flexipod''" indicates if the carrier is using the Aptean POD (APOD or formerly FleXipod) system for execution and automatic debrief. This applies only if the system is configured to use this flag in system parameters.

"''LogiNext Enabled''" indicates if the carrier is using the LogiNext 4PL system to manage a 3rd party carrier trip assignment and automatic debrief. See [[Using the LogiNext Carrier Interface]] for more information on this process.

You can edit an existing carrier by selecting it from the table and clicking the '''Edit''' button. This will show the same screen as adding a new carrier, but with all of the information populated.

You can delete an existing carrier (if it has not been used) by clicking the '''Delete''' button.

You can also access and edit the following information about the carrier through the buttons provided:

* '''Fuel Surcharges'''.
* '''Contacts'''.

=== Fuel Surcharges ===
Fuel surcharges are used when generating trip costs for trips executed by that carrier.<center>
[[File:Res carrier fuel.png|800x800px]]
</center>The fuel surcharge is applied on trips that were executed (started) on or following the ''Effective Date'' supplied.

You can add a new surcharge by clicking in an empty row and entering the information (''Effective Date, Fuel Surcharge''). You can edit a row by clicking on that row. You can '''Save''' your changes with the button provided, or discard any changes with the '''Close''' button. You can also delete an existing contact using the '''Delete Record''' button provided.

=== Contacts ===
This information may be used for reference if sending documents to the carrier.<center>
[[File:Res carrier contacts.png|800x800px]]
</center>You can add a new contact by clicking in an empty row and entering the information (''Surname, Forename, Title, Phone, Email''). You can edit a row by clicking on that row. You can '''Save''' or '''Cancel''' your changes with the buttons provided. You can also '''Delete''' an existing contact using the button provided.

=== Additional Information ===
Carrier records can also be created and updated by synchronisation between the external applications and C-TMS, especially where the client offers the trips for tender to third-party hauliers, and, where new hauliers may bid for business.

Carriers may be created via imports:
* [[Imports_Details#CARRIER|CARRIER]]

File:Res carrier.png

2025-09-25T06:59:34Z

Anw: Anw uploaded a new version of File:Res carrier.png

File:Res carrier contacts.png

2025-09-25T06:52:53Z

Anw:

Carrier Contacts

File:Res carrier fuel.png

2025-09-25T06:50:18Z

Anw:

Carrier Fuel Surcharges

File:Res carrier main.png

2025-09-25T06:44:35Z

Anw:

Carriers main screen

FleXipod Interface

2025-09-24T13:42:01Z

Anw: Updated system parameters

{{Incomplete}}

This guide shows how the Aptean Proof of Delivery system (APOD or formerly FleXipod) can be configured to be used from CTMS.

This require configuration as to when messages are sent, how they are formatted (the FleXipod attributes), at what level are messages sent (orders, stops, etc) and what information is expected to be received.

== Configuration ==
=== System Parameters ===
{| class="wikitable apt-searchable"
!Parameter !! Description !! Config By
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD ||Set to Y to indicate the FlexiPod interface is active ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_ACID ||Flexipod acid ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_BREAK_DROPS ||Flexipod include breaks for the drops in the Add API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CARRIERS ||Set to Y indicates the Carrier can control if a trip is sent to FlexiPod ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CLIENTNUM ||FleXipod ClientNum sent in interface ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_CONSOLIDATE_APOD ||Flexipod consolidate the drops in the API calls (Y/N) ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_CONSOLIDATE_APOD_REF ||Flexipod consolidate the orders for the drops as the OMS reference or a type of customer reference (OMS/CUST/BOOK/DEL) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DEPOTS ||Set to Y indicates the Depot can control if a trip is sent to FlexiPod ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DEPOT_DEPART_ACTION ||Flexipod Depot Depart Action (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DEPOT_RETURN_ACTION ||Flexipod Depot Return Action (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DIRECT ||Set to Y to indicate the FlexiPod interface is direct and not using Route Execution ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_DROP ||Determines the Drop level STOP-OMS or ITEM ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_END_OF_TRIP_ACTION ||Flexipod End of Trip Action (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_EXPIRY ||Sets the expiry date for the manifest as a number of days after the end of the trip. ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_EXTERNALSYSTEMUPDATE ||Flexipod process the External System Update messages in the API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_FORCEITEMSCAN ||Force the items to be scanned separately: 0 to use the ScanLevel or 1 to force the scan by item. ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_LISTPENDINGMANIFESTS ||Flexipod process the List Pending Manifest Update messages in the API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_MERGE_DROPS ||Flexipod merge the orders on the drop in the Add API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_PASSWORD ||FleXipod Webservice password ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_PREDEPARTURE_ACTION ||Controls whether the system Flexipod Pre-Departure Action get sent as part of the manifest (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_PROXY ||Flexipod proxy server ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_READDROP ||Flexipod process the Read Drop messages in the API call (Y/N) ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SCAN_LEVEL ||1,2 or 3 to indicate line or item level scanning ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SCAN_TYPE ||Contents and items ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SIGNATORY ||Set to Y to store the SignedByName as the actual signatory as information for the order at its collection of delivery location ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_SPLIT ||Are orders to be split? ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_SYSTEM ||FleXipod SYSTEM ID sent in interface ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_TIMEZONE ||Flexipod timezone for the UpdateManifests API calls ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_TPCLIENTNUM ||FleXipod TPClientNum sent in interface ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_UNALLOCATED_DRIVER ||FleXipod uses an unallocated driver when one is not assigned to a trip ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_UPDATE_MANIFESTS ||FleXipod use UpdateManifests to add manifests (Y/N) ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_USERCODE ||FleXipod webservice usercode ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_USERNAME ||FleXipod webservice username ||SYSTEM
|- bgcolor="red" color="white" style="background-color: red; color: white;"
|FLEXIPOD_WEBSERVICE ||Flexipod webservice endpoint URL ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_WEBSERVICE_TASK ||Flexipod webservice endpoint URL for Tasks ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_WEBSERVICE_UI ||Flexipod webservice endpoint URL ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_WEBSERVICE_UI_EXEC ||Flexipod webservice endpoint URL for Route Execution ||SYSTEM
|- bgcolor="lightgreen" style="background-color: lightgreen;"
|FLEXIPOD_X_API_KEY ||Flexipod x-api-key for External System Update messages ||SYSTEM
|- bgcolor="goldenrod" color="white" style="background-color: goldenrod; color: white;"
|FLEXIPOD_TENNANT ||? ||SYSTEM
|- bgcolor="goldenrod" color="white" style="background-color: goldenrod; color: white;"
|FLEXIPOD_TENNANT_KEY1 ||? ||SYSTEM
|}

Key:
* red: no longer in use
* green: in use
* amber: in use, but not defined

=== Carrier ===
The FLEXIPOD flag must be enabled when configured by carrier (system parameter FLEXIPOD_CARRIERS) for carriers that require the use of FlexiPOD.

=== Depot Locations ===
The FLEXIPOD flag must be enabled when configured by depot (system parameter FLEXIPOD_DEPOTS) for depots that require the use of FlexiPOD.

=== EDI Processes ===

'''FLEXIPOD_OUT'''

This process sends the triggered manifests to APOD.

* Flow Type: PROCESS
* Package Name: PROCESS, DP_FLEXIPOD.PROCESS_FLEXIPOD_OUT
* Process: i_process_name FLEXIPOD_OUT
* Interval: 5 minutes

'''FLEXIPOD_SENDLISTPENDING'''

This process checks to see if there are any pending updates from the manifests and imports the details.

* Flow Type: PROCESS
* Package Name: PROCESS DP_FLEXIPOD.send_listpendingmanifestupdates
* Process: PROCESS FLEXIPOD_SENDLISTPENDING
* Interval: 1 minute

=== Reason Codes and Decodes ===

A decode of name "FLX_RESULT_CODES" type "REFERENCE" must be configured to map all of the reason codes from APOD into CTMS.

Several ITEM_NON_CON reason codes must be created to map to the APOD reason codes.:

Examples:
{| class="wikitable"
!APOD !! CTMS !! Description || At Fault !! Action !! Type !! CBR
|-
|1 ||SD ||Successful Delivery || || || ||
|-
|10 ||SD ||Successful Delivery || || || ||
|-
|2 ||FV ||Failed Visit || || ||FAILURE ||Y
|-
|3 ||SD ||Successful Delivery || || || ||
|-
|4 ||UD ||Unsuccessful Delivery || || ||FAILURE ||
|-
|5 ||SC ||Successful Collection || || || ||
|-
|6 ||SJ ||Skipped Job || || ||FAILURE ||Y
|-
|7 ||NR ||No Longer Required || || ||FAILURE ||
|-
|8 ||PR ||Payment Refused || || || ||
|}

Plus any reason codes created in FlexiPOD must be created within TMS for the audit history to accurately represent any reasons selected by the driver.

{{Note}} For each implementation, the reason codes and numbers will differ. For example, 1 and 10 may not be "Successfully Delivered", so the decode mapping MUST be in place for the APOD interface.

=== Attribute Configuration ===
Attributes against Manifests, Drops and Items can be configured by your Aptean implementation team. Up to {{Warning}} 10 attributes may be defined at each level except Drop, which may contain 20 attributes.

In general, the following is allowed at each level:
* Manifest
** Information derived directly from the trip, such as route code, trailer type, driver, etc.
* Drop
** Information derived from the transport order header, such as the main references, instructions
** Information derived from the customer of the transport order, such as parameters against that customer.
** Any sub-reference held against that transport order.
** Any sub-reference held against the transport order's destination location.
* Item
** Information derived from the order items.
** Order Reference information
** Any references from the Drop above
** {{Note}} Including Quarantine status through the order reference STATUS)

An example is below:

{| class="wikitable apt-searchable"
!Project Name !!Level !!Number !!Source !!Target
|-
|Stapletons ||Drop ||1 ||so.booking_ref ||
|-
|Stapletons ||Drop ||2 ||so.del_point_ref ||
|-
|Stapletons ||Drop ||3 ||dp_flexipod.get_order_val('ORDER','PRICE', ||
|-
|Stapletons ||Drop ||4 || ||
|-
|Stapletons ||Drop ||5 || ||
|-
|Stapletons ||Drop ||6 ||dp_flexipod.get_ref('LOCATION','PERMIT_NUMBER', ||
|-
|Stapletons ||Drop ||7 ||oc.free_text1 ||
|-
|Stapletons ||Drop ||8 ||dp_flexipod.get_ref('LOCATION','UNITARY_AUTHORITY', ||
|-
|Stapletons ||Drop ||9 ||dp_flexipod.get_ref('LOCATION','LICENCE_NUMBER', ||
|-
|Stapletons ||Drop ||10 ||so.total_weight ||
|-
|Stapletons ||Drop ||11 ||so.total_pieces ||
|-
|Stapletons ||Drop ||12 ||oc.pay_on_delivery ||
|-
|Stapletons ||Drop ||13 ||oc.collect_casings ||
|-
|Stapletons ||Drop ||14 || ||
|-
|Stapletons ||Drop ||15 || ||
|-
|Stapletons ||ItemAttributes ||1 ||soi.du_type ||
|-
|Stapletons ||ItemAttributes ||2 ||soi.weight ||
|-
|Stapletons ||ItemAttributes ||3 ||dp_flexipod.get_order_val('ITEM','UNIT_WEIGHT', ||
|-
|Stapletons ||ItemAttributes ||4 ||dp_flexipod.get_order_val('ITEM','UNIT_PRICE', ||
|-
|Stapletons ||ItemAttributes ||5 ||dp_flexipod.get_order_val('ITEM','STATUS', ||
|-
|Stapletons ||Manifest ||1 ||st.route_code ||
|-
|Stapletons ||Manifest ||2 ||st.trailer_type ||
|}

== Sending Trips to FlexiPOD ==
{{Warning}} This has changed

This happens automatically when:
* the trip is set to status "ACCEPTED" or "EN-ROUTE"
* when any changes happen to the trip i.e. orders are added, removed or moved on a trip that is at those statuses.
* When the driver, carrier or tractor has been added or changed on a trip that is at those statuses.

== Actions Taken on Update ==
Gets updates from FleXipod drops and processes them

Marks message as collected

Stores order references
* TrackingID
* TrackingURL
* JobReportName

Stores signatory and filename if present
* As ord_information
* As References
** SignedByName
** SignedByFilename
** SiteImageFilename

If item details provided:
* Updates stop Actual Arrive and Actual Depart

* If scan_type = 'I'
** Creates Order Item Reasons from decoded reason code for actions against the drops and items (such as successful delivery, etc).
** Creates Order Item Reasons from decoded reason code if there are non-conformities
** Updates item delivered quantities
** Updates order line quantities
** Updates POC/POD flag against the order

* If scan_type = 'P'
** Same for each item in the pallet.

If event_name = 'Pre-Departure'
* Updates SU stop actual arrive

If event_name = 'Depot Depart'
* Updates SU stop actual arrive and actual depart
* Sets the trip status
* Updates items as despatched
* Updates lines as despatched
* Validates the order

If event_name = 'Depot Return'
* Updates CL stop actual arrive

If event_name = 'End of Trip'
* Updates CL stop actual arrive and actual depart
* Sets the trip status

For all order updates:
* Change order status to DELIVERED if anything delivered
* Change order status to FAILED if nothing delivered

{{Note}} All changes to order are audited.

[[Category:Interfaces]]

System Parameters List

2025-09-23T09:23:37Z

Anw: Minor correction

{| class="wikitable apt-searchable" border="1" id="systemparams"
|- bgcolor="silver"
!Parameter !! Description !! Level
|-
| ACC_ACTUAL_DISTANCE || Controls if the distance is rated using actual distance || SYSTEM
|-
| ACC_ADD_LINES || Does the user rate by lines and additional tariffs || COST_CENTRE
|-
| ACC_ALLOCATE_MANUAL_COST || Allow manual cost payments on orders || SYSTEM
|-
| ACC_ALLOW_MULTIPLE_CCY || Can multiple currencies be defined in the database? || SYSTEM
|-
| ACC_ALLOW_ZERO_RPE || Allow zero quantity to be returned from get charges (for RPE tier) || SYSTEM
|-
| ACC_ALWAYS_APPLY || There are tariffs that should always be applied || SYSTEM
|-
| ACC_CALC_SECURITY || Indicates if Security charges are applicable || SYSTEM
|-
| ACC_CALC_SERVICES || Service charges applicable || SYSTEM
|-
| ACC_CHECK_ORDER || Should order be assessed for rating || SYSTEM
|-
| ACC_CONSOL_RADIAL_COSTS || Indicates if radial charges are consolidated at delivery location || SYSTEM
|-
| ACC_CONTRACT_OWN || To control if the system looks at the contract or the existing table to identify the charges for own packaging || SYSTEM
|-
| ACC_CONTRACT_PICKPACK || To check the relevant contract for a PICKPACK tariff and generate a payment || SYSTEM
|-
| ACC_CONTRACT_SERVICES || To control a procedure that will check if there are any service records on the order || SYSTEM
|-
| ACC_CUST_FUEL || Apply Customer Fuel Charges || SYSTEM
|-
| ACC_Calc_Payment_Ord || Controls whether payment button is displayed on Orders forms - Y or N, Internal Charges are being applied to orders) || SYSTEM
|-
| ACC_Calc_Payment_Trip || Controls whether payment button is displayed on Trip forms - Y or N, Trip Cost method is defined against the Carrier Type || SYSTEM
|-
| ACC_Calc_Revenue_Ord || Control Order revenue calculation method - CONTRACT or CONTRACT-TPL || SYSTEM
|-
| ACC_Calc_Revenue_Trip || Controls whether revenue button is displayed on Trip forms - Y or N, Trip Cost method is defined against the Carrier Type) || SYSTEM
|-
| ACC_Calc_Saving_Ord || Controls whether the saving button is displayed on Orders forms - Y or N || SYSTEM
|-
| ACC_DEMURRAGE || Number of hours before demurrage charge start || SYSTEM
|-
| ACC_EDIT_ORD_CHARGE || Allow users to edit revenue charges || SYSTEM
|-
| ACC_FUELSURCH_EVENTDATE || Details whether Fuel Surcharges are calculated based on TENDERED or TRIPSTART date. || SYSTEM
|-
| ACC_FUEL_SEC_MODE || Are Fuel and security charges controlled by transport mode || SYSTEM
|-
| ACC_INC_ALL_ORDER_COST_PAYMENTS || Include all order cost payments (Y/N)? || COST_CENTRE
|-
| ACC_INDEXES || Use Acc indexes || SYSTEM
|-
| ACC_INT_CHRG_AT_TRUNK_LEG || Indicates if Internal Charges (trunk and radial) are generated by the trunk leg || SYSTEM
|-
| ACC_INVOICE_LOGO || Invoice Logo || COST_CENTRE
|-
| ACC_KNOWN_ZONE || Can rating Zone be predicted? || SYSTEM
|-
| ACC_LINES_OR_HEADER || Rate orders by line level only (Y), or by header level only or both levels (N) || CUSTOMER
|-
| ACC_OF_VERSION || Controls format of extract to OF || SYSTEM
|-
| ACC_ORD_STD_COST || Control Order standard cost calculation method - CONTRACT or CONTRACT-TPL || COST_CENTRE
|-
| ACC_PACKAGES || Are DU type charges separately || SYSTEM
|-
| ACC_PLAN_COSTS || Allows user to calc costs from Planned trips || COST_CENTRE
|-
| ACC_PROTECT_STATUS || Indicates if Payment status are protected from update to F || SYSTEM
|-
| ACC_RATE_BY_PARTY || To control if the rating process will look for a party contract when rating || SYSTEM
|-
| ACC_ROUND_AVG_DU_WEIGHT || Round Avg Du Weight to 3 decimal places for rating || COST_CENTRE
|-
| ACC_SCREENING_CHARGES || Are screening charges applied || SYSTEM
|-
| ACC_SERVICE_METHODS || Controls is services are allocated by methods || COST_CENTRE
|-
| ACC_SHOW_PROFIT || Controls the display of the Profit Field || COST_CENTRE
|-
| ACC_SUPPRESS_RATING || Should rating be prevented when validating orders || CUSTOMER
|-
| ACC_TRANSPORT_MODE || Is transport mode included in Contract charges || SYSTEM
|-
| ACC_USE_ORD_TRLR_TYPE || Should order revenue be calculated from the order trailer type even when scheduled || COST_CENTRE
|-
| ACC_ZERO_DESPATCHED || Controls if Zero despatched lines are ignored from rating || COST_CENTRE
|-
| ACTIVE_ROLE_DISPLAY || Indicates if the active role is displayed in the tool bar || SYSTEM
|-
| ADDITIONAL_ORDER_VALIDATION || Additional order validation required for product weight || COST_CENTRE
|-
| ADD_CSV_COL_FORMATTING || Add Column Formatting to CSV extracts || SYSTEM
|-
| ADM_EXCLUDE_AUDIT_LOG || Processes that will be excluded from writing audit log records. || SYSTEM
|-
| ADM_EXCLUDE_PACKAGE_MSG || Packages whose adm log messages are not to be written || SYSTEM
|-
| ADM_LOG_ARC_DEL_DAYS || Number of days that ADM_LOG_ARCHIVE messages should be kept for || SYSTEM
|-
| ADM_NO_DISPLAY_MENU || Enable the user to access the menu item || SYSTEM
|-
| ADM_UNKOWN_ORDERS || Identify amended/duplicate orders || SYSTEM
|-
| ADM_UPSHIFT_DU_TYPE || Upshifts the despatch unit type when Y. || SYSTEM
|-
| ADM_UPSHIFT_PRODUCT_TYPE || Upshifts the product type when Y || SYSTEM
|-
| ADM_WRITE_ERRORS || Store fatal form errors in FORM_ERROR_LOG || SYSTEM
|-
| ADR_REGS || Are ADR regulations displayed for trips || COST_CENTRE
|-
| ALLOC_RESOURCE || Are drivers and tractors allocated to own fleet carriers? || SYSTEM
|-
| ALLOC_TRIP_PMNTS || Allocate the trip payments as order costs || SYSTEM
|-
| ALLOW_DIRECT_BAY_MOVES || Should orders be moved directly from the receipt bay or to the despatch bay from the grid? || SYSTEM
|-
| ALLOW_DUPLICATE_CUST_REF || Allow orders with duplicate cust refs but different to locations. || SYSTEM
|-
| ALLOW_ETA_UPDATES || Determines whether the user can update ETA values || COST_CENTRE
|-
| ALLOW_HOLD_ORDERS || allow orders to be place don hold || SYSTEM
|-
| ALLOW_MANUAL_RPE || Allow RPE to be entered (via the inbound EDI) and do not overwrite. || SYSTEM
|-
| ALLOW_MISSING_DEL || Is unit weight sent in the items || SYSTEM
|-
| ALLOW_MULTIPLE_ADD_REFS || Allow multiple additional references for an order values will be (Y/N) || COST_CENTRE
|-
| ALLOW_POC_EDIT || Allow users to edit the POC Flag in Debrief || SYSTEM
|-
| ALLOW_TENDERED_PARAGON_TRIPS || Allow Tendered Trips in Paragon || COST_CENTRE
|-
| ALLOW_TENDERED_PARAGON_TRIPS || Allow Tendered Trips in Paragon || COST_CENTRE
|-
| ALLOW_TRP_DEL_TYPE_UPDATE || Allow Delivery type updates in the planning screen || CARRIER
|-
| ALLOW_UNLOAD_ASSET || Controls if asset records are created as part of unload || SYSTEM
|-
| ALLOW_UNSCHEDULE_SCHED_COLL || Controls if menu item Unschedule sched coll is displayed || SYSTEM
|-
| ALTERNATE_DB_NAME || Alternate DB Name || SYSTEM
|-
| ALTERNATE_ORDER_ENTRY || Validate item identifier field || COST_CENTRE
|-
| AMAZON_OWNER_CODE || Asset owner code to pass to Amazon || SYSTEM
|-
| API_CARRIER || Carrier ID for API || SYSTEM
|-
| API_EVENTS || Are events sent out via API || SYSTEM
|-
| API_TEXT_AUTHORISATION || authorisation code for API text || SYSTEM
|-
| API_TEXT_END || Time of day the system stops sending texts || SYSTEM
|-
| API_TEXT_ENDPOINT_URL || URL endpoint for API text || SYSTEM
|-
| API_TEXT_START || Time of day the system can start sending texts || SYSTEM
|-
| API_WS_ADDRESS || WebService endpoint for API events || SYSTEM
|-
| API_WS_ELUCID_ADDRESS || WebService endpoint for API events for Elucid || SYSTEM
|-
| API_WS_ELUCID_PASSWD || WebService password for API events for Elucid || SYSTEM
|-
| API_WS_ELUCID_USER || WebService username for API events for Elucid || SYSTEM
|-
| APPLY_ADDITIONAL_LOC_CHECKS || To enable additional validation checks for location entry. || SYSTEM
|-
| ARDO_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header (Unilever) || SYSTEM
|-
| ARDO_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header (Unilever) || SYSTEM
|-
| ARDO_INBOUND_PATH || Path for yet to be processed XML files (Ardo) || SYSTEM
|-
| ASSEMBLY_DU_TYPE || Assembly DU Type || COST_CENTRE
|-
| ASSET_AT_FIXED_ORIGIN || Asset At Fixed Origin || COST_CENTRE
|-
| ASSET_DEBRIEF || Indicates if assets debriefed with Items || COST_CENTRE
|-
| ASSET_FORMAT || Indicates which order item field will identify an asset || COST_CENTRE
|-
| AUTO_COMMIT_EMPTY_STOPS || Commit After Deletion of Empty Stops || COST_CENTRE
|-
| AUTO_PLAN_ORDERS || Auto Plan orders onto an existing trip || COST_CENTRE
|-
| AUTO_ROUTE_NEW_ORDERS || Automatically plan orders loaded || SYSTEM
|-
| AUTO_SCHEDULING || Auto Scheduling of orders || COST_CENTRE
|-
| AUTO_SCHED_INACTIVE_DEPOTS || List the inactive depots to exclude from the fixed drop scheduling engine. || SYSTEM
|-
| AUTO_SET_DELIVERY_TYPES || Automatically set delivery type rules || COST_CENTRE
|-
| BEIG2_FTP_DESTINATION_DIRECTORY || Directory for FTP of BirdsEye Files || SYSTEM
|-
| BEIG2_FTP_DESTINATION_IP_ADDRESS || IP for FTP of BirdsEye Files || SYSTEM
|-
| BEIG2_FTP_DESTINATION_PASSWORD || Password for FTP of BirdsEye Files || SYSTEM
|-
| BEIG2_FTP_DESTINATION_PORT || Port for FTP of BirdsEye Files || SYSTEM
|-
| BEIG2_FTP_DESTINATION_USERNAME || Username for FTP of BirdsEye Files || SYSTEM
|-
| BEIG2_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header || SYSTEM
|-
| BEIG2_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header || SYSTEM
|-
| BEIG2_INBOUND_PATH || Path for yet to be processed XML files || SYSTEM
|-
| BEIG2_OUTBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header || SYSTEM
|-
| BEIG2_OUTBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header || SYSTEM
|-
| BEIG2_OUTBOUND_PATH || Path for yet to be processed XML files || SYSTEM
|-
| BEIG_ENABLED || To enable the inbound and outbound file processing on this DB || SYSTEM
|-
| BEIG_FTP_DESTINATION_DIRECTORY || Directory for FTP of BirdsEye Files || SYSTEM
|-
| BEIG_FTP_DESTINATION_IP_ADDRESS || IP for FTP of BirdsEye Files || SYSTEM
|-
| BEIG_FTP_DESTINATION_PASSWORD || Password for FTP of BirdsEye Files || SYSTEM
|-
| BEIG_FTP_DESTINATION_PORT || Port for FTP of BirdsEye Files || SYSTEM
|-
| BEIG_FTP_DESTINATION_USERNAME || Username for FTP of BirdsEye Files || SYSTEM
|-
| BEIG_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header || SYSTEM
|-
| BEIG_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header || SYSTEM
|-
| BEIG_INBOUND_PATH || Path for yet to be processed XML files || SYSTEM
|-
| BEIG_OUTBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header || SYSTEM
|-
| BEIG_OUTBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header || SYSTEM
|-
| BEIG_OUTBOUND_PATH || Path for yet to be processed XML files || SYSTEM
|-
| BGW_AUTO_REBOOK || Indicates if auto rebook is switched on when non conformance is added || COST_CENTRE
|-
| BGW_DUMMY_WASTE || Defines Dummy waste location for BGW. || COST_CENTRE
|-
| BGW_TRAILER_SET || Defines which Trailer Types are allowed. || COST_CENTRE
|-
| BKG_APPEND_TO_ORDERS || Controls whether Bookings can append to an existing Order if the Slot is already used. || SYSTEM
|-
| BKG_AUTO_CREATE_SLOT || Creates slots if no slot exists || SYSTEM
|-
| BKG_DEF_COST || Default Cost Centre for Bookings || SYSTEM
|-
| BKG_DEF_CUST || Default Customer for Bookings || SYSTEM
|-
| BKG_DEF_DELIVERY_DEL_TYPE || Any order that are created via the interface, that are delivering to their final loc || SYSTEM
|-
| BKG_DEF_POPULATE_DEL || Any order that are created via bookings will have Del Type populated by system, specific to DSG || SYSTEM
|-
| BKG_DEF_TRUNK_DEL_TYPE || Defines the default booking trunk delivery type for any orders being delivered inti a x-dock location, default to null || SYSTEM
|-
| BKG_GEN_TI_METHOD || Defines whether Gen TI does standard, xdock of both processes, STANDARD, BOTH or XDOCK. || SYSTEM
|-
| BKG_INCREMENT || Increment exiting Bookings on import rather than overwriting || SYSTEM
|-
| BKG_REV_TI_DISBAND_INV_FIX_RTE || Should Reverse TIs disband Fixed Trips - Y or N || SYSTEM
|-
| BKG_SLOT_INACTIVATE || Controls whether existing Slots are updated to INACTIVE during a Slot Import. || SYSTEM
|-
| BKG_TYPE_9_DU_TYPE || Default DU Type for Type 9 Orders || SYSTEM
|-
| BKG_USE_BOOKING_STATUS || Defines whether booking status is being used, N, PROVISIONAL, PLANNED or CONFIRMED. || SYSTEM
|-
| BMW_DOT_CODE || Tyre Age for BMW || SYSTEM
|-
| BUF_OLD_ORD_CLEAR_DAYS || Number of days in the past to be checked by the Buffaload order clear down || SYSTEM
|-
| BWSC_GEO_ADD_NETWORK_LOV_LIMIT || When set to Y the LOV for adding network locations will only show SSS, BRANCH and PLANT locations || SYSTEM
|-
| CALCULATE_CONTRACTUAL_WEIGHT_TRG || Allow contractual weights to be re-calculated via database trigger (set to N for LFS testing) || SYSTEM
|-
| CALC_DIMEN || Calculate volume from dimensions || COST_CENTRE
|-
| CALIDUS_ASSIST_BASE_URL || URL for Calidus Assist Install || SYSTEM
|-
| CALIDUS_ASSIST_RELEASE_DB || The final part of the URL used to view the release notes, for this database, on Calidus assist. || SYSTEM
|-
| CALL_LOGGING_DATE_RANGE || Call Logging Date Range Days || SYSTEM
|-
| CAL_DEFAULT_TIME_OFFSET || Default time offset which gets added to times in Order tracking, for users viewing data in different timezone || SYSTEM
|-
| CAL_DEFAULT_TIME_ZONE || Description of timezone, used in Order Tracking form, freetext || SYSTEM
|-
| CAL_WORKING_DAY_MAP || Defines which days of the week are being worked - Sunday to Saturday, Y or N. || COST_CENTRE
|-
| CANCEL_STATUS_CHK || Only orders on Planned trips cn be cancelled || SYSTEM
|-
| CARGOWISE_BILLING_BRANCH_CODE || Billing Branch Code for Cargowise || COST_CENTRE
|-
| CARGOWISE_BRANCH || Branch for Cargowise || COST_CENTRE
|-
| CARGOWISE_CONSIGNEE || Consignee name for Cargowise || COST_CENTRE
|-
| CARGOWISE_DATABASE || Controls which cargowise database invoices are exported to || COST_CENTRE
|-
| CARGOWISE_DEPARTMENT || Department code || COST_CENTRE
|-
| CARGOWISE_DESTINATION_PORT || Destination Port || COST_CENTRE
|-
| CARGOWISE_EXPORT || Payments are exported to Cargowise || COST_CENTRE
|-
| CARGOWISE_ORIGIN_PORT || Origin Port for Cargowise || COST_CENTRE
|-
| CARRIER_API_CLIENT_CODE || Value sent across to LFE in API || SYSTEM
|-
| CARRIER_API_MANIFEST_READY_TIME || The cut-off time for the ready time for the carrier manifest (HH24:MI). || SYSTEM
|-
| CARRIER_API_WS || Endpoint for LFE API || SYSTEM
|-
| CARRIER_API_WS_AMEND || Endpoint for Carrier API updates || SYSTEM
|-
| CARRIER_API_WS_CANCEL || Endpoint for Carrier API cancellations || SYSTEM
|-
| CARRIER_INVOICE_TYPE || Carrier Invoice type || SYSTEM
|-
| CARRIER_RULES_ALL || Controls if all du types and products are checked || SYSTEM
|-
| CARRIER_WORK_REP_FOOTER_1 || The footing printed at the bottom of the CARRIER_WORK_CONF report (first part). || SYSTEM
|-
| CARRIER_WORK_REP_FOOTER_2 || The footing printed at the bottom of the CARRIER_WORK_CONF report (second part). || SYSTEM
|-
| CARR_GAZ_POSTCODE_FORMAT || For which carrier gazetteer formats will the postcode in the file exclude spaces. (List delimited with semi-colons) || SYSTEM
|-
| CARR_SRVCE_LEVEL_OFFSET_DAYS || The default minimum number of offset days to calculate the collection job date for UKMail. || COST_CENTRE
|-
| CC_FORMAT_PATTERN || Click and Collect Ext Ref format || SYSTEM
|-
| CD_DIR || Directory used for copying zipped files || SYSTEM
|-
| CFX_CARRIER || Stores the name of CFX Carrier || CARRIER
|-
| CFX_CONTROL || Is there control over which trips go to CFX || SYSTEM
|-
| CFX_CONTROL_CUSTOMER || Controls which customers are configured for CFX || CUSTOMER
|-
| CFX_EXT_LOCATION_NAME || Include the extra location name in the CFX messages (Y/N) || SYSTEM
|-
| CFX_LINES_AND_ITEMS || Are items and lines included in CFX file, S,D,B,N || SYSTEM
|-
| CFX_NEW_ORDERS || Does adding orders to a trip re-trigger the CFX file? || SYSTEM
|-
| CFX_ORDER_ADDRESSES || Are order addresses include in the CFX file || SYSTEM
|-
| CFX_ORDER_HEADER || Are orders included in CFX file || SYSTEM
|-
| CFX_ORDER_HEADER_TMS || Is the order header TMS section included in CFX file || SYSTEM
|-
| CFX_OWNING_DEPOT || Is the owning depot included in the filename? || SYSTEM
|-
| CFX_SEND || Are trips sent to CFX || SYSTEM
|-
| CFX_STATUS_CHECK || Are carriers checked at status change for CFX? || SYSTEM
|-
| CHANGE_DEBRIEF_LABELS || Controls the labels for certain items in the debrief and orders screen || SYSTEM
|-
| CHANGE_PRINTER || Is change printer displayed || COST_CENTRE
|-
| CHECK_ELUCID_IMBALANCE || Check for stock imbalance at Elucid || COST_CENTRE
|-
| CHECK_RESOURCES || Check Resource on existing trips before allocation || SYSTEM
|-
| CHG_SCHED_DATE_TRIP || A comma-separated list of trip status for which the schedule may be changed || SYSTEM
|-
| CIM_CONF_INBOUND_IDENTIFIER || Pattern for MIC Order Inbound XML || SYSTEM
|-
| CIM_CONF_INBOUND_LISTING_NAME || Filename for list of files in directory for MIC XML Order Inbound || SYSTEM
|-
| CIM_CONF_LISTING_SCRIPT_NAME || Script name for MIC XML Order Inbound || SYSTEM
|-
| CIM_ENABLED || XML Isotrak enabled for this database || SYSTEM
|-
| CIM_INBOUND_ARCH || Path for CIM XML archiving || SYSTEM
|-
| CIM_INBOUND_FAIL || Path for CIM XML failures || SYSTEM
|-
| CIM_INBOUND_IDENTIFIER || Pattern for MIC Order Inbound XML || SYSTEM
|-
| CIM_INBOUND_LISTING_NAME || Filename for list of files in directory for MIC XML Order Inbound || SYSTEM
|-
| CIM_INBOUND_MAR_IDENTIFIER || Pattern for CIM Order update XML || SYSTEM
|-
| CIM_INBOUND_PATH || Path for yet to be processed XML files from CIM || SYSTEM
|-
| CIM_LISTING_SCRIPT_NAME || Script name for MIC XML Order Inbound || SYSTEM
|-
| CIM_OUTBOUND_ARCH || Path for archiving outbound CIM XML interfaces || SYSTEM
|-
| CIM_OUTBOUND_FAIL || Path for failing outbound CIM XML interfaces || SYSTEM
|-
| CIM_OUTBOUND_PATH || Path for outbound CIM XML interfaces || SYSTEM
|-
| CLICK_CUST || Click and Collect Customer || SYSTEM
|-
| CLIENT_CODE_CHECK || Client code assessment for Location import || SYSTEM
|-
| CMD_MERGE_DOCUMENTS || The command to merge documents can be stored with any paths that need to be unset to allow the process to be performed. || SYSTEM
|-
| CMR_NOTE || Name of the CMR note report || COST_CENTRE
|-
| CMR_NOTE1 || Name of the CMR note report || COST_CENTRE
|-
| CNT_SERVICE_LEVEL_OFFSETS || Enable collection and delivery offsets for service levels (Y/N) || SYSTEM
|-
| CNT_SUMMER || Date Summer starts this current year || SYSTEM
|-
| CNT_WINTER || Date WINTER starts this current year || SYSTEM
|-
| CO2_EMMISIONS_LTR || Defines Amount of CO2 emissions per litre of fuel. || COST_CENTRE
|-
| COMBINED_DOCUMENTS_REPORT || Name of the Combined Documents report. || COST_CENTRE
|-
| CONSOLIDATE_TRIPS || Remove Duplicate lines when trip is ACCEPTED || SYSTEM
|-
| CONSOL_BY_SHIPMENT || Consolidation at Shipment level || COST_CENTRE
|-
| CONSOL_RUNNING || Indicates whether the order consolidation process is currently running. || SYSTEM
|-
| CONTINGENCY_IMPORT || Contingency Import setting || COST_CENTRE
|-
| CON_MAX_RPE || Max RPE per shipment || COST_CENTRE
|-
| COST_CENTRE_LOGO || Customer logo filename || COST_CENTRE
|-
| COST_CENTRE_POST_MATRIX || Does this cost centre use Post Matrix type charging? || COST_CENTRE
|-
| COST_CENTRE_SEGREGATION || Segregate data by cost centre || SYSTEM
|-
| CREATE_ORD_MANF || Controls if an order manifest record is created || COST_CENTRE
|-
| CSB_EXPORT_PATH || Directory where carrier self billing exports are stored. || SYSTEM
|-
| CSB_REPORT_PATH || Directory where carrier self billing reports are stored. || SYSTEM
|-
| CS_CLOSE_BY || Display trips in cust serv that are within x miles of order || SYSTEM
|-
| CS_DEFAULT_BOOKING_STATUS_OLD || Customer Services Default Booking Status || SYSTEM
|-
| CS_DEFAULT_ORDER_STATUS_OLD || Customer Services Default Order Status || SYSTEM
|-
| CTMS_CITD_FTP_DESTINATION_DIRECTORY || CITD Destination Directory || SYSTEM
|-
| CTMS_CITD_FTP_DESTINATION_IP_ADDRESS || CITD Destination IP Address || SYSTEM
|-
| CTMS_CITD_FTP_DESTINATION_PASSWORD || CITD Destination Directory Password || SYSTEM
|-
| CTMS_CITD_FTP_DESTINATION_PORT || CITD Destination Directory Port || SYSTEM
|-
| CTMS_CITD_FTP_DESTINATION_USERNAME || CITD Destination Directory username || SYSTEM
|-
| CTMS_ESI_FTP_DESTINATION_DIRECTORY || Directory for FTP of Outbound Trips Files. || SYSTEM
|-
| CTMS_ESI_FTP_DESTINATION_IP_ADDRESS || IP Address for FTP of Outbound Trips Files. || SYSTEM
|-
| CTMS_ESI_FTP_DESTINATION_PASSWORD || Password for FTP of Outbound Trips Files. || SYSTEM
|-
| CTMS_ESI_FTP_DESTINATION_PORT || Port for FTP of Outbound Trips Files. || SYSTEM
|-
| CTMS_ESI_FTP_DESTINATION_USERNAME || Username for FTP of Outbound Trips Files. || SYSTEM
|-
| CTMS_MANF_FTP_DESTINATION_DIRECTORY || Manifest Destination Directory || SYSTEM
|-
| CTMS_MANF_FTP_DESTINATION_IP_ADDRESS || Manifest Destination IP Address || SYSTEM
|-
| CTMS_MANF_FTP_DESTINATION_PASSWORD || Manifest Destination Directory Password || SYSTEM
|-
| CTMS_MANF_FTP_DESTINATION_PORT || Manifest Destination Directory Port || SYSTEM
|-
| CTMS_MANF_FTP_DESTINATION_USERNAME || Manifest Destination Directory username || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_ARCH || File path for Outbound Trips. || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_ARCH_TEST || File path for Outbound Trips archive. || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_FILENAME || Filename for Outbound Trips. || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_FLAG || Flag to permit the creation of Outbound Trips (Y/N). || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_MSG_TYPE || The Message Type of the Outbound Trips (Y/N). || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_OWNING_DEPOT || The owning depot of the Outbound Trips (Y/N). || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_PATH || File path for Outbound Trips. || SYSTEM
|-
| CTM_ACCEPT_TRIP_UPDATE_DATA || Should Trip data be entered when user Accepts a trip - Y or N || CARR_GROUP
|-
| CTM_ACCEPT_TRIP_UPDATE_DATA || Should Trip data be entered when user Accepts a trip - Y or N || CARRIER
|-
| CTM_DISP_SCHEDTRIP_OR_BOL || Display Sched/Trip or BOL in Carrier Trip Management - SCHEDTRIP or BOL || CARRIER
|-
| CTM_MSG_CHASE_AFTER || Time(mins) after which a message should be sent to a carrier after failure to respond || CARRIER
|-
| CTM_MSG_CHASE_AFTER || Time(mins) after which a message should be sent to a carrier after failure to respond || CARR_GROUP
|-
| CTM_REFRESH_TIMER_INTERVAL || Automatic Timer Refresh Interval for Carrier Trip Management - Enter value in mins || CARRIER
|-
| CTM_SHOW_TRIP_TIMES || Show trip times in Carrier Trip Management form - Value is Y or N || CARRIER
|-
| CUSTOMER_CONTROLLED_ORDER_REVENUE_ACTUALS || Y/N- greater of planned and actual quantity || SYSTEM
|-
| CUSTOMER_LOGO || Customer logo filename || CUSTOMER
|-
| CUSTOMER_SERVICE_LEVEL || Enable Customer Specific Service Levels || SYSTEM
|-
| CUST_DU_CONS_SCHED || Consolidate DU By Schedule || CUSTOMER
|-
| CUST_UPDATE_ORDER_LINES || Update Orders || CUSTOMER
|-
| DEBRIEF_DRIVERS_HOURS || Enter Drivers hours worked at debrief || COST_CENTRE
|-
| DEBUG || Debug enabled ? - Y or N || SYSTEM
|-
| DEFAULT_DEL_TYPE || Default Delivery Type || COST_CENTRE
|-
| DEFAULT_DU_TYPE || Default Du Type for NHS || SYSTEM
|-
| DEFAULT_ORACLE_DIRECTORY || Stores System directory for TMP_DIR in EXPORT production || SYSTEM
|-
| DEFAULT_PART_NO || Default part Number || CUSTOMER
|-
| DEFAULT_PAR_DEL_TYPE || Default Del type for paragon || COST_CENTRE
|-
| DEFAULT_PROD_TYPE || Default Product Type || COST_CENTRE
|-
| DEFAULT_REBOOK_DEL_TYPE || Default Del type for Rebook || COST_CENTRE
|-
| DEFAULT_SLOT_DELETION_DAYS || Number of days after which an inactive slot is deleted || SYSTEM
|-
| DEFAULT_TRAILER_TYPE || Default Trailer Type || COST_CENTRE
|-
| DEFAULT_UNSCHEDULED_CARRIER || Indicates a default carrier may be used to print labels for unscheduled orders during packing. || SYSTEM
|-
| DEF_AQ_SCHEMA || Schema for use when starting advanced queues || SYSTEM
|-
| DEF_CALLOUT_DEL_TYPE || Default Callout Delivery Type || SYSTEM
|-
| DEF_COST || Default Cost Centre for NHSBT || SYSTEM
|-
| DEF_INSPECT_DEL_TYPE || Default Inspection Delivery Type || SYSTEM
|-
| DEF_INSPECT_SERVICE || Default Inspection Service Level || SYSTEM
|-
| DEF_SERVICE_LEVEL || Default service level for orders when null || COST_CENTRE
|-
| DELCONF_FTP_DESTINATION_DIRECTORY || Directory for FTP of Microlise Files || SYSTEM
|-
| DELCONF_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Microlise Files || SYSTEM
|-
| DELCONF_FTP_DESTINATION_PASSWORD || Password for FTP of Microlise Files || SYSTEM
|-
| DELCONF_FTP_DESTINATION_PORT || Port for FTP of Microlise Files || SYSTEM
|-
| DELCONF_FTP_DESTINATION_USERNAME || Username for FTP of Microlise Files || SYSTEM
|-
| DELETE_ALL_PMTS_AT_PLANNED || Delete All payments for a trip at Planned Status || COST_CENTRE
|-
| DELIVERY_CUTOFF || Cost Centre Delivery Cut Off || COST_CENTRE
|-
| DELIVERY_NOTE || Name of the delivery note report || COST_CENTRE
|-
| DEL_LEVEL_PARAM || Level of data reported in the Delivery docs || COST_CENTRE
|-
| DEL_TIME_OFFSET || The earliest delivery time ahead of the requested delivery date and time sent from PULSE || COST_CENTRE
|-
| DESPATCH_EMAIL || Create Despatch email control record || SYSTEM
|-
| DESPATCH_REPORT || Name of the despatch note report printed from the trip tree || COST_CENTRE
|-
| DHL_INV_EMAIL || List of emails (sep with ;) for monthly DHL Invoicing data || SYSTEM
|-
| DIM_CHARGE_WEIGHT || Kg Value for dimensional weight calculation || CUSTOMER
|-
| DIRECT_CARRIER || Stores the carrier ID that will go direct and not via a location - the via routing code will not be displayed. || SYSTEM
|-
| DISABLE_ITEM_ID || Disable the item identifier in order entry || COST_CENTRE
|-
| DISPLAY_DESPATCHED_RPE || Display the Actual Despatched RPE Quantity in the Order Detail and Trip Debrief screens? || COST_CENTRE
|-
| DISPLAY_PARAGON_LOC_ID || Display Paragon ID and EXT Ref in Locations Screen || SYSTEM
|-
| DISPLAY_PO_REF_REPORT || PO Ref to be displayed in delivery note || CUSTOMER
|-
| DISPLAY_WIC_CODE || Determines if the delivery type of the order for the customer contains a WIC Code and whether the title will be displayed in the Order Details screen || CUSTOMER
|-
| DISTRIBUTION_OFF || Is revenue distributed as part of trip charges? || SYSTEM
|-
| DOM_DIMS || Domestic version of dimensions functionality || COST_CENTRE
|-
| DONT_SEND_PLANNED_TO_WEBFLEET || When the parameter is set control record is not sent for PLANNED status || COST_CENTRE
|-
| DSG_ALLOW_BKG_IN_PAST || Allow Bookings in the past from the Dixons Bookings interface - Y or N. || SYSTEM
|-
| DSG_DEF_DU_TYPE || Default DU Type for Orders created via the Dixons Bookings interface. || SYSTEM
|-
| DSG_DEF_PRD_TYPE || Default Product Type for Orders created via the Dixons Bookings interface. || SYSTEM
|-
| DSG_TRIP_DTL_PATH || File path for DSG Trip detail messages. || SYSTEM
|-
| DU_PARAMS || DUs may be used as charge parameters || SYSTEM
|-
| EARLY_ARR_REASON_CODE || Early reason code for trip deliveries || SYSTEM
|-
| EDI1214_DELIMITER || File delimiter in EDI1214 file || SYSTEM
|-
| EDI1214_ENDOFLINE || File end of line delimiter in EDI1214 file || SYSTEM
|-
| EDI1214_SYSTEM || T for test P for Prod || SYSTEM
|-
| EDI_CN_ENTITY_CODE || Consignment Entity code for Invoice XML || SYSTEM
|-
| EDI_INVOICE_MSG_TYPE || Invoice Message type for Invoice XML || SYSTEM
|-
| EDI_MESSAGE_VERSION || Message Version for Invoice XML || SYSTEM
|-
| EDI_SH_ENTITY_CODE || Shipment Entity code for Invoice XML || SYSTEM
|-
| EDI_STRUCTURE_VERSION || Structure version for Invoice XML || SYSTEM
|-
| EFX_CANC_ARCH || Archive folder for EFX cancellation requests || SYSTEM
|-
| EFX_CANC_FTP_DESTINATION_DIRECTORY || Directory for FTP of Microlise Files || SYSTEM
|-
| EFX_CANC_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Microlise Files || SYSTEM
|-
| EFX_CANC_FTP_DESTINATION_PASSWORD || Password for FTP of Microlise Files || SYSTEM
|-
| EFX_CANC_FTP_DESTINATION_PORT || Port for FTP of Microlise Files || SYSTEM
|-
| EFX_CANC_FTP_DESTINATION_USERNAME || Username for FTP of Microlise Files || SYSTEM
|-
| EFX_DEADLINE_HOURS || EFX Default Deadline Hours || SYSTEM
|-
| EFX_DEFAULT_CARRIER || EFX Default Carrier || SYSTEM
|-
| EFX_DEF_WEIGHT || Default EFX weight per RPE, used in calculation of trip weight for EFX export || SYSTEM
|-
| EFX_EXCLUDE_CARR_TYPE_DEB || EFX Exclude Carrier Type from Debrief Messages || COST_CENTRE
|-
| EFX_EXT_LOCATION_NAME || Include the extra location name in the EFX messages (Y/N) || SYSTEM
|-
| EFX_FAILURE_PATH || File path for failed EFX filed || SYSTEM
|-
| EFX_FORMAT || EFX Format || SYSTEM
|-
| EFX_FTP_DESTINATION_DIRECTORY || Directory for FTP of Microlise Files || SYSTEM
|-
| EFX_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Microlise Files || SYSTEM
|-
| EFX_FTP_DESTINATION_PASSWORD || Password for FTP of Microlise Files || SYSTEM
|-
| EFX_FTP_DESTINATION_PORT || Port for FTP of Microlise Files || SYSTEM
|-
| EFX_FTP_DESTINATION_USERNAME || Username for FTP of Microlise Files || SYSTEM
|-
| EFX_IDENTIFIER || EFX file identifier || SYSTEM
|-
| EFX_INBOUND_LISTING_NAME || Filename for list of files in directory for EFX XML Trip Inbound || SYSTEM
|-
| EFX_INC_TRIP_VEH_TYPE || Include the vehicle type for the trip stop from EFX (Y/N) || COST_CENTRE
|-
| EFX_LISTING_SCRIPT_NAME || Script name foe EFX XML Inbound || SYSTEM
|-
| EFX_PATH || File path for EFX Inbound messages || SYSTEM
|-
| EFX_PROCESSED_PATH || File path for processed EFX files || SYSTEM
|-
| EFX_SEND_SUB || Send Sub-Contracted Trips to EFX when they go to ACCEPTED status || SYSTEM
|-
| EFX_TRIP_ARCH || Archive folder for EFX requests || SYSTEM
|-
| EFX_TRIP_DTL_PATH || File path for EFX Trip detail messages. || SYSTEM
|-
| EFX_XML_DEB_DELAY || EFX XML Outbound second debrief message delay in minutes || SYSTEM
|-
| EFX_XML_DEB_TRIP_STATUS || Determine which trip status generates debrief messages to EFX || COST_CENTRE
|-
| EFX_XML_INC_COUNTRYCODE || Will XML messages for EFX include COUNTRYCODE for load and drop locations (Y/N). || COST_CENTRE
|-
| EFX_XML_SYSTEM || EFX XML Outbound System Name || COST_CENTRE
|-
| EFX_XML_TYPE || EFX Type || COST_CENTRE
|-
| EFX_XML_UOM || EFX XML Outbound UOM || COST_CENTRE
|-
| ELUCID_API_PROXY || Proxy Sever Elucid || SYSTEM
|-
| ELUCID_WS_ADDRESS || Elucid WS Address || SYSTEM
|-
| ELUCID_WS_PWD || Elucid WS User || SYSTEM
|-
| ELUCID_WS_USER || Elucid WS User || SYSTEM
|-
| EMAIL_ACTUALS_FAILURE || Email address for Actuals Failure Email || CUSTOMER
|-
| EMAIL_CUSTOMER_CARE || Customer Care email address || SYSTEM
|-
| EMAIL_CUST_SERVICES_RECIPIENT || The address for the recipient of the emails. || COST_CENTRE
|-
| EMAIL_OWN_PACKAGE || Is an e-mail required for an order that contains own packaging (Y/N)? || COST_CENTRE
|-
| ENABLE_SEND_BORDERO || Send Bordero Messages || CUSTOMER
|-
| ENGINE_RUNNING || Indicates whether the Scheduling Engine is running || SYSTEM
|-
| EPL_CUST_REF || VPF Test param for 317770 || SYSTEM
|-
| EPOD_COLLECT_STOCK || To exclude sending a loading stop to EPOD which does not have an order for van stock or to fit new tyres(Y/N) || SYSTEM
|-
| EPOD_COMPLETED_UPDATE || Are epod updates sent for COMPLETED trips? || SYSTEM
|-
| EPOD_COMPLETE_ON_LOAD_UPDATE || Complete Trip when RTD job sent back from C-ePOD for load updates || COST_CENTRE
|-
| EPOD_COMPLETE_ON_RTD || Complete Trip when RTD job sent back from C-ePOD || COST_CENTRE
|-
| EPOD_CONCATENATE_JOB_INSTR || Concatenate the special instructions and the order comments for the collection/delivery location as the job instructions (Y/N). || COST_CENTRE
|-
| EPOD_CONSOLIDATION_LEVEL || Level of job consolidation for C-ePOD || COST_CENTRE
|-
| EPOD_CONTACT_DELIMITER || EPOD contact delimiter || COST_CENTRE
|-
| EPOD_CONTAINER_CODE1 || What populates this field in EPOD DIMS for dimensions(default) or PARTS for the part numbers if present || COST_CENTRE
|-
| EPOD_CONTAINER_CODE2 || What populates this field in EPOD DIMS for dimensions or PARTS for the part numbers if present (default) || COST_CENTRE
|-
| EPOD_CONTAINER_CODE3 || What populates this field in EPOD DIMS for dimensions or PARTS (for the part numbers if present) default NULL || COST_CENTRE
|-
| EPOD_CONTAINER_DESCRIPTION || What populates this field in EPOD COMMODITY for the item commodity(default) DESCRIPTION for item desc or PROD_DESC for the prod AKA code and item desc || COST_CENTRE
|-
| EPOD_CUSTOMER_INVOICE || Include an EPOD_CUSTOMER_INVOICE section within the EPOD_CUSTOMERS section for the service jobs (Y/N) || SYSTEM
|-
| EPOD_CUSTOMER_INVOICE_SXU || To include the EPOD_CUSTOMER section || SYSTEM
|-
| EPOD_IGNORE_COL_SIG_DEPOT || Controls is signatures are ignored for cols at depots || COST_CENTRE
|-
| EPOD_IGNORE_COL_SIG_DEPOT || Controls is signatures are ignored for cols at depots || SYSTEM
|-
| EPOD_ITEM_LEVEL || Send Containers (IC for items or LC for lines) or Products (IP for item or LP for lines) to EPOD || SYSTEM
|-
| EPOD_JOB_GROUP_FORMAT || Indicates whether the value passed in the EPL Job Group to EPOD is the Cost Centre (CC), Carried ID (CI), Customer Group (CG) or Customer (CU). || SYSTEM
|-
| EPOD_JOB_RETAIN_TIMES || Retain the actual times for the trip stop for the job (Y/N). || COST_CENTRE
|-
| EPOD_OWNER_CONFIG || C-ePOD Owner Configuration || COST_CENTRE
|-
| EPOD_PREVENT_ASSET_TRACK || Prevents asset tracking through EPOD || COST_CENTRE
|-
| EPOD_SEND_CLOSING_TIME || Send Location closing time to C-ePOD || SYSTEM
|-
| EPOD_SEND_COD_NAME || Send COD Name to C-ePOD values will be (Y/N) || COST_CENTRE
|-
| EPOD_SEND_CONTACT_INFO || Send Contact information to C-ePOD || COST_CENTRE
|-
| EPOD_SEND_DRIVER || Is the driver username included? (Y/N) || SYSTEM
|-
| EPOD_SEND_EPL_LAT_LONG || Send EPL_LAT and EPL_LONG for job addresses (Y/N) || COST_CENTRE
|-
| EPOD_SEND_EQUIPMENT || Controls if equipment requirements are sent to EPOD || SYSTEM
|-
| EPOD_SEND_ITEM_AKA_CODE || Send EPL_PRODUCT_CODE with the item AKA code (Y/N) || COST_CENTRE
|-
| EPOD_SEND_LOADING_TYPE || Send Loading Type to C-ePOD || COST_CENTRE
|-
| EPOD_SEND_RVA_UNIT_TYPE || Send EPL_UNIT_TYPE as the vehicle configuration ID for the services (Y/N) || COST_CENTRE
|-
| EPOD_SET_ACTUAL_SIGNATORY_BLANK || Set C-ePOD actual signatory to blank (Y/N)? || SYSTEM
|-
| EPOD_SIGNATORY || Controls if signatory is stored from C-ePOD || COST_CENTRE
|-
| EPOD_SIGNATURE_STORAGE || Store signature received from C-ePOD || COST_CENTRE
|-
| EPOD_SITE_ID_FORMAT || Indicates whether the value passed in the EPL Site ID to C-ePOD is the Database Name(DB), Cost Centre (CC) or Carrier ID (CI). || SYSTEM
|-
| EPOD_TNC_STORAGE || Store TNC declaration from C-ePOD || COST_CENTRE
|-
| EPOD_UPDATE_ETA || Update Later stops ETA on receipt from C-ePOD || COST_CENTRE
|-
| EPOD_VIEW_POD_URL || URL for C-ePOD Documents || SYSTEM
|-
| EPOD_WS_ADDRESS || C-ePOD Web Service End Point || SYSTEM
|-
| EPOD_WS_ADDRESS_NHSPRD || C-ePOD Web Service End Point || SYSTEM
|-
| EPOD_WS_MESSAGE_FORMAT || C-ePOD message format - can either be PARCEL, BULK, RETAIL, MODE1, MODE2 or DELTYPE to define where fields are sent in the web service message || SYSTEM
|-
| EPOD_WS_PASSWORD || C-ePOD Web Service Login Password || SYSTEM
|-
| EPOD_WS_TIMEOUT || Number of minutes before a WS message will be set to Held || SYSTEM
|-
| EPOD_WS_USERNAME || C-ePOD Web Service Login Username || SYSTEM
|-
| ETA_LOAD_TIME || Load time in minutes to be used in ETA calculation || SYSTEM
|-
| EXE_ARCH_DIRECTORY || Destination directory EXE rcp || SYSTEM
|-
| EXE_DESTINATION_DIRECTORY || Destination directory EXE rcp || SYSTEM
|-
| EXE_DESTINATION_IP_ADDRESS || Destination for EXE rcp || SYSTEM
|-
| EXE_DESTINATION_PASSWORD || Password for EXE rcp || SYSTEM
|-
| EXE_DESTINATION_USERNAME || Username for EXE rcp || SYSTEM
|-
| EXE_SOURCE_DIRECTORY || Source directory for EXE rcp || SYSTEM
|-
| EXTERNAL_CALL_LOGGING || Call Logging External User || SYSTEM
|-
| FASTER_SCANNING || Controls if the Planner splits order for planning || SYSTEM
|-
| FC_ACCESS_TOKEN || The FleetCheck Access Token, provided by FleetCheck. || SYSTEM
|-
| FC_FLEET_KEY || The FleetCheck fleet being updated by C-TMS. || SYSTEM
|-
| FC_TIMEOUT || The amount of time to wait when trying to update FleetCheck. || SYSTEM
|-
| FC_URL || The base URL for the FleetCheck system. || SYSTEM
|-
| FILE_INTERFACE_DIR || File Interface Directory || SYSTEM
|-
| FINDTRIP_URL || Find trip webservice URL || SYSTEM
|-
| FIT_PRESSURE_HIGH || FIT Report: Pressure Analysis High || SYSTEM
|-
| FIT_PRESSURE_LOW || FIT Report: Pressure Analysis Low || SYSTEM
|-
| FIT_PRESSURE_VHIGH || FIT Report: Pressure Analysis Very High || SYSTEM
|-
| FIT_PRESSURE_VLOW || FIT Report: Pressure Analysis Very Low || SYSTEM
|-
| FIT_TREAD_REPLACE_NEXT || FIT Report: RTD in Next Month || SYSTEM
|-
| FIT_TREAD_REPLACE_NEXT2 || FIT Report: RTD in Next 2 Months || SYSTEM
|-
| FIT_TREAD_REPLACE_NOW || FIT Report: RTD in Current Month || SYSTEM
|-
| FIXED_IMPORT || Customer is using fixed order import || CUSTOMER
|-
| FIX_NULL_BOOKING_REF || Set booking Ref to Null for fixed schedules || COST_CENTRE
|-
| FLEXIPOD || Set to Y to indicate the FleXipod interface is active || SYSTEM
|-
| FLEXIPOD_CARRIERS || Set to Y indicates the Carrier can control if a trip is sent to FleXipod || SYSTEM
|-
| FLEXIPOD_CLIENTNUM || FleXipod ClientNum sent in interface || SYSTEM
|-
| FLEXIPOD_DEPOTS || Set to Y indicates the Depot can control if a trip is sent to FleXipod || SYSTEM
|-
| FLEXIPOD_DROP || Determines the Drop level STOP-OMS or ITEM || SYSTEM
|-
| FLEXIPOD_PASSWORD || FleXipod Webservice password || SYSTEM
|-
| FLEXIPOD_SCAN_LEVEL || 1,2 or 3 to indicate line or item level scanning || SYSTEM
|-
| FLEXIPOD_SCAN_TYPE || Contents and items || SYSTEM
|-
| FLEXIPOD_SPLIT || Are orders to be split? || SYSTEM
|-
| FLEXIPOD_SYSTEM || FleXipod SYSTEM ID sent in interface || SYSTEM
|-
| FLEXIPOD_USERCODE || FleXipod Webservice usercode || SYSTEM
|-
| FLEXIPOD_USERNAME || FleXipod Webservice username || SYSTEM
|-
| FLEXIPOD_WEBSERVICE || FleXipod webservice endpoint URL || SYSTEM
|-
| FLEXIPOD_WEBSERVICE_TASK || FleXipod webservice endpoint URL for Tasks || SYSTEM
|-
| FLEXIPOD_WEBSERVICE_UI || FleXipod webservice endpoint URL || SYSTEM
|-
| FORCE_ITEM_SCAN || Is driver required to scan at debrief? || SYSTEM
|-
| FORMS_ALERT_MESSAGE_MODULE || Alert Messages Form || SYSTEM
|-
| FORMS_CS_PATH || Forms Client Server Path || SYSTEM
|-
| FORMS_DEFAULT_MODULE || Default Module accessed when C-TMS is started - ORI_STATS, ORI_STATS_JRL or ORI_STATS_WATERFALL || SYSTEM
|-
| FORMS_DEFAULT_ORDERS_MODULE || Default Orders Form - ORDERS_WIDE, ORDERS or ORD_ENTRY_TARGET || SYSTEM
|-
| FORMS_DEFAULT_TRIP_MODULE || Default Trip Form - TRIPSUM or TRIPSUM_JRL || SYSTEM
|-
| FORMS_PASSWORD_MODULE || Password Change form. || SYSTEM
|-
| FORMS_PATH || Forms Path || SYSTEM
|-
| FORMS_WEB_PATH || Determines where on the server forms are being obtained from for this database || SYSTEM
|-
| FORMS_WEB_PATH_BLUE || Blue forms || SYSTEM
|-
| FTP_SERVER_LOG || Create server logs for FTP send to prove delivery || SYSTEM
|-
| FTP_TRANSMIT_TIME_LIMIT || Determines the time limit (in minutes) above which a file being transferred is considered to be failed instead of pending. || SYSTEM
|-
| FTP_WRITE_LOC || FTP Write location || SYSTEM
|-
| FULL_LOAD_GROUPAGE_FLAG || Controls whether Full load \ Groupage flag is checked when changing Trip status || SYSTEM
|-
| FULL_LOAD_THRESHOLD || Maximum weight threshold for any FTL || SYSTEM
|-
| GEL_DU || Identifies which du types include GEL || COST_CENTRE
|-
| GEO_ASKGEO_PROXY || Proxy server setting for AskGEO web server || SYSTEM
|-
| GEO_ASKGEO_TIMEOUT || AskGEO web server time out || SYSTEM
|-
| GEO_ASKGEO_URL || AskGEO web server URL || SYSTEM
|-
| GEO_DEFAULT_COUNTRY || Default country for new locations || SYSTEM
|-
| GEO_DEFAULT_DEPOT || Default depot for new locations || SYSTEM
|-
| GEO_DEFAULT_LOAD_RATE || Default Loading Rate for locations. || SYSTEM
|-
| GEO_DEFAULT_SESSION_COUNTRY || Default Country Code for locations created from sessions || SYSTEM
|-
| GEO_DEFAULT_UNLOAD_RATE || Default Unloading Rate for locations. || SYSTEM
|-
| GEO_DRIVE_TIME_DTL_ONLY || Allows TRANSIT DAYS to be be overridden by Drive Time in GEO_NET, YES or NO. || SYSTEM
|-
| GEO_DT_ADDR_FMT || Determines the format of the Address string passed to external Map application, e.g. MapPoint, for Address Location Matching || SYSTEM
|-
| GEO_DT_CALC || Determines the distance and time calculation methods - NET, NETR, LINE, PCMS || SYSTEM
|-
| GEO_DT_CALC_ORD || Determines distance calculation method for orders || COST_CENTRE
|-
| GEO_DT_CALC_PAR_INT || Override for dist/time method for Paragon Interface || SYSTEM
|-
| GEO_DT_DFLT_SPEED || Default truck speed assumed in approximation of driving time. || SYSTEM
|-
| GEO_DT_DISTANCE_FACTOR || "Wiggle" factor applied to straight-line distance to approximate Road distance. || SYSTEM
|-
| GEO_DT_DISTANCE_UNITS || Current distance unit - miles or kilometres || SYSTEM
|-
| GEO_DT_DISTANCE_UNITS || Current distance unit - miles or kilometres || COST_CENTRE
|-
| GEO_DT_PCMS_TIMEOUT || Number of seconds to wait for PCMS to calculate distance and time. || SYSTEM
|-
| GEO_DT_PCMS_TIMEOUT_ORD || Number of seconds to wait for NAVTEQ for order distance calculation || COST_CENTRE
|-
| GEO_HERE_DISTANCE_TYPE || Set to either miles or leave blank || COST_CENTRE
|-
| GEO_HIDE_SWAP_LOCATIONS || It is to exclude SWAP locations from list of Location_ID in location maintenance screen || SYSTEM
|-
| GEO_KEEP_LATLONG || Keep Lat-Long when entered || SYSTEM
|-
| GEO_LOCATION_STACK || Switch on stack specific location fields || SYSTEM
|-
| GEO_LOC_ADD1_MAND || Address Line 1 must be entered || SYSTEM
|-
| GEO_LOC_CUST_CTRY || Enable a customer to be specified for a location to be maintained for one of multiple countries? (‘Y/N) || SYSTEM
|-
| GEO_LOC_IMP_POST_PLAN || Populate the postal and planning regions using rules in country and static data when doing location import || SYSTEM
|-
| GEO_LOC_PCDE_MAND || Post code must be entered || SYSTEM
|-
| GEO_LOC_RADIAL_ROUTES || Indicates if a radial route will be stored for the location based on the fixed route stop for collection/delivery (Y/N). || SYSTEM
|-
| GEO_LOC_TOWN_MAND || Town must be entered || SYSTEM
|-
| GEO_MAX_INVENTORY || Maximum inventory threshold for warning || SYSTEM
|-
| GEO_MIN_INVENTORY || Minimum inventory threshold for warning || SYSTEM
|-
| GEO_NAVTEQ_AJAX_LOGIN || NAVTEQ Ajax Login || SYSTEM
|-
| GEO_NAVTEQ_CITY_SPEED || City Road Speed for NAVTEQ || SYSTEM
|-
| GEO_NAVTEQ_COUNTRY_SPEED || Country Road Speed for NAVTEQ || SYSTEM
|-
| GEO_NAVTEQ_FAST_SHORT || Fastest or Shortest Method for NAVTEQ Route calculation || SYSTEM
|-
| GEO_NAVTEQ_JAVA || NAVTEQ Java || SYSTEM
|-
| GEO_NAVTEQ_LOGIN || NAVTEQ Login || SYSTEM
|-
| GEO_NAVTEQ_MAP_DIR || NAVTEQ Maps Folder || SYSTEM
|-
| GEO_NAVTEQ_MAP_SHOW || NAVTEQ Maps Folder for WEBSHOW || SYSTEM
|-
| GEO_NAVTEQ_MOTOR_SPEED || Motorway Speed for NAVTEQ || SYSTEM
|-
| GEO_NAVTEQ_PROXY || Proxy Sever for NAVTEQ || SYSTEM
|-
| GEO_NAVTEQ_URL_LOC || NAVTEQ Location URL || SYSTEM
|-
| GEO_NAVTEQ_URL_MAP || NAVTEQ Map URL || SYSTEM
|-
| GEO_NAVTEQ_URL_MAP_ALL || NAVTEQ Map URL || SYSTEM
|-
| GEO_NAVTEQ_URL_ROUTE || NAVTEQ Route URL || SYSTEM
|-
| GEO_NET_TABLE || Network Table || SYSTEM
|-
| GEO_NLP_ALT_PROXY || Proxy Sever for NLP 11g || SYSTEM
|-
| GEO_NLP_ALT_URL_LOC || Alternative URL for Geocode service on NLP system || SYSTEM
|-
| GEO_NLP_ALT_URL_ROUTE || Alternative URL for Calculate Route service on NLP system || SYSTEM
|-
| GEO_NLP_API_KEY || API Key for NLP || SYSTEM
|-
| GEO_NLP_APP_LOC || App_ID for Geo Code call to NLP system || SYSTEM
|-
| GEO_NLP_APP_MAP || App for Map service on NLP system || SYSTEM
|-
| GEO_NLP_APP_ROUTE || App_ID for Route call to NLP system || SYSTEM
|-
| GEO_NLP_CAR_TRUCK || Nokia travel time calculations to be based on a truck or a car || SYSTEM
|-
| GEO_NLP_DISTRICT_PARAM || Control which field (TOWN/LINE3) is sent as district to Nokia || SYSTEM
|-
| GEO_NLP_FORMAT_FREETEXT || NLP Freetext Format || SYSTEM
|-
| GEO_NLP_FORMAT_QUALIFIED || NLP Qualified Format || SYSTEM
|-
| GEO_NLP_JAVA || Java for NLP to create PDF || SYSTEM
|-
| GEO_NLP_JS_MULTI || Location for the show map multiple map printout in JavaScript || SYSTEM
|-
| GEO_NLP_LATLONG_ACCURACY || NLP Geocode Accuracy || SYSTEM
|-
| GEO_NLP_MAP_DIR || Directory for PDF of maps || SYSTEM
|-
| GEO_NLP_MAP_SHOW || Directory for PDF of maps || SYSTEM
|-
| GEO_NLP_MOTORWAY || Motorway Preference for NLP distance calculations || COST_CENTRE
|-
| GEO_NLP_PROXY || Proxy Sever for NLP || SYSTEM
|-
| GEO_NLP_TOKEN_LOC || NLP Geocode Token || SYSTEM
|-
| GEO_NLP_TOKEN_MAP || Login token for Map service on NLP system || SYSTEM
|-
| GEO_NLP_TOKEN_ROUTE || Login token for Calculate Route service on NLP system || SYSTEM
|-
| GEO_NLP_URL_LOC || Nokia Location Platform Geocode URL || SYSTEM
|-
| GEO_NLP_URL_MAP || URL for Map service on NLP system || SYSTEM
|-
| GEO_NLP_URL_ROUTE || URL for Calculate Route service on NLP system || SYSTEM
|-
| GEO_NLP_USE_ALTERNATE || Use Alternative URLS and Proxy || SYSTEM
|-
| GEO_POP_PLANNING_REGION || Controls whether the Planning Region is populated from the look up table - Y or N. || SYSTEM
|-
| GEO_SLOT_IMPORT_FILE || Name of Slot Import file || SYSTEM
|-
| GEO_SLOT_IMPORT_PATH || Slot Import path || SYSTEM
|-
| GEO_SUBURB || Town must match a Zone || SYSTEM
|-
| GEO_TOMTOM_ACCOUNT || TomTom account || SYSTEM
|-
| GEO_TOMTOM_ARCH_DAYS || Number of days to keep the TomTom data before archiving || SYSTEM
|-
| GEO_TOMTOM_AUTO_AREA_RADIUS || Radius (m) of temporary TomTom areas || SYSTEM
|-
| GEO_TOMTOM_FENCE_CARR || List of carriers to test TomTom Geo-fence breaks || SYSTEM
|-
| GEO_TOMTOM_FENCE_VAR || Variation of time in hours from planned for TomTom Geo-fence breaks to update stop || SYSTEM
|-
| GEO_TOMTOM_FENCE_VEH || List of vehicles to test TomTom Geo-fence breaks || SYSTEM
|-
| GEO_TOMTOM_GETMSGS_URL || TomTom web service || SYSTEM
|-
| GEO_TOMTOM_LATE_MINS || TomTom Late Reason Variance Minutes || SYSTEM
|-
| GEO_TOMTOM_LATE_REASON || TomTom Late Reason Code || SYSTEM
|-
| GEO_TOMTOM_ORDER_DEBRIEF || List of Delivery types allowing change || CARRIER
|-
| GEO_TOMTOM_PASSWORD || TomTom password || SYSTEM
|-
| GEO_TOMTOM_PROXY || Proxy server setting for TomTom web server || SYSTEM
|-
| GEO_TOMTOM_SENDORD_URL || TomTom web service to send orders || SYSTEM
|-
| GEO_TOMTOM_SEND_CUST_REF || Send order customer ref to TomTom || SYSTEM
|-
| GEO_TOMTOM_TIMEOUT || TomTom web server time out || SYSTEM
|-
| GEO_TOMTOM_TRIP_COMPLETE || TomTom to automatically complete trips || SYSTEM
|-
| GEO_TOMTOM_TRIP_EN-ROUTE || Set trip status to EN-ROUTE from TomTom || SYSTEM
|-
| GEO_TOMTOM_USERNAME || TomTom username || SYSTEM
|-
| GEO_VALIDATE_LOCATION_NAME || Indicates whether the system should check for duplicate location names (as well as IDs) when creating/updating locations || SYSTEM
|-
| GLO_CUSTOMER || Customer for Unilever Gloucester || SYSTEM
|-
| GLO_FTP_DESTINATION_DIRECTORY || Directory for FTP of Unilever Files || SYSTEM
|-
| GLO_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Unilever Files || SYSTEM
|-
| GLO_FTP_DESTINATION_PASSWORD || Password for FTP of Unilever Files || SYSTEM
|-
| GLO_FTP_DESTINATION_PORT || Port for FTP of Unilever Files || SYSTEM
|-
| GLO_FTP_DESTINATION_USERNAME || Username for FTP of Unilever Files || SYSTEM
|-
| GLO_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header (Unilever) || SYSTEM
|-
| GLO_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header (Unilever) || SYSTEM
|-
| GLO_INBOUND_PATH || Path for yet to be processed XML files (Unilever) || SYSTEM
|-
| GLO_LOCATION || Location for Unilever Gloucester || SYSTEM
|-
| GLO_OUTBOUND_ARCH || Path for processed XML files for Unilever || SYSTEM
|-
| GLO_OUTBOUND_FAIL || Path for processed XML files for Unilever that have failed processing || SYSTEM
|-
| GLO_OUTBOUND_PATH || Path for yet to be processed XML files for Unilever || SYSTEM
|-
| HIGHLIGHT_SMS_EMAIL || Highlight order Green if SMS or email notification required || COST_CENTRE
|-
| HKP_Clear_Archive_Messages || Age of ARCHIVED messaging records that are to be cleared. || SYSTEM
|-
| HKP_Clear_Messages || Age of messaging records that are to be cleared. || SYSTEM
|-
| HTTPS_CALL || It is related to switching from HTTP to HTTPS || SYSTEM
|-
| HTTPS_PASSWORD || The password for URL commands in the database. || SYSTEM
|-
| HTTPS_WALLET_FILE || The wallet file for URL commands in the database. || SYSTEM
|-
| HTTP_WALLET_TOMTOM || Location of wallets for TOMTOM https || SYSTEM
|-
| ICE_DU || Identifies which du types include ICE || COST_CENTRE
|-
| IGGESUND_IDENTIFIER || Identifier for IGGESUND inbound order files || SYSTEM
|-
| IGGESUND_LISTING_NAME || List for IGGESUND files || SYSTEM
|-
| IGGESUND_LISTING_SCRIPT_NAME || KSH for IGGESUND files || SYSTEM
|-
| IMP_BWSC_DEF_CARRIER || Default Carrier for BWSC import for self delivery suppliers || COST_CENTRE
|-
| IMP_CARRIER_LANE_COUNTRY_CODE || Country code for each cost centre imported on Carrier_Lane - INDUSTRIAL || COST_CENTRE
|-
| IMP_CHANGE_DECIMALS || Correct commas and decimal points for Dimensions || CUSTOMER
|-
| IMP_COL_DATE_REQD || Collection Date must be specified for imports || COST_CENTRE
|-
| IMP_CREATE_ITEM_ID || Controls if Item identifiers are system generated in CSV || CUSTOMER
|-
| IMP_FULL_LOC_ADDR_MATCH || Check the addresses match for the location name, address line 1, postcode, country and type for imported orders before creating a new location (Y/N). || SYSTEM
|-
| IMP_LOC_ID_ONLY || Only validate the location id when importing orders not the address lines || SYSTEM
|-
| IMP_OVERRIDE_SOURCE_REF || Set source system and control additional functionality in ORD_LINE_ITM CSV order import || SYSTEM
|-
| IMP_RESET_ORD_WINDOWS || Reset Order windows during Import || COST_CENTRE
|-
| IMP_RESET_ORD_WINDOWS || Reset Order windows during Import || CUSTOMER
|-
| IMP_TI_ORDER_CALC_WEIGHTS || CSV Import - Calculate weights from dims(Y=X*Y*Z/6000) || COST_CENTRE
|-
| IMP_TI_ORDER_CHECK_SMS || CSV Import - Check contact numbers can be used as SMS numbers || COST_CENTRE
|-
| IMP_TI_ORDER_DEFAULT_DU || CSV Import - Default DU Type Method || COST_CENTRE
|-
| IMP_TI_ORDER_GEN_ITEMS || CSV Import - Generate order items from Qty || COST_CENTRE
|-
| IMP_TI_ORDER_GEN_LOC || CSV Import - Location Name generation by Post Code || COST_CENTRE
|-
| IMP_TI_ORDER_QTY_ADD || CSV Import - Add line qty || COST_CENTRE
|-
| IMP_TI_ORDER_REVENUE_LIMIT || CSV Import -Pre-call above revenue limit (Numeric Limit).0 means no pre-call || COST_CENTRE
|-
| IMP_TI_ORD_GEN_LOC_NAME || Send Supplier Collection Messages || CUSTOMER
|-
| IMP_USE_DEFAULT_DU || Use Default DU Type in import || CUSTOMER
|-
| IMP_USE_DEFAULT_DU || Use Default DU Type in import || CUSTOMER
|-
| IMP_USE_GERMAN_DECODE || Controls if location names are decoded from German || SYSTEM
|-
| INBOUND_ARDO_IDENTIFIER || Identifier for MTS PO Inbound Ardo files || SYSTEM
|-
| INBOUND_ARDO_LISTING_NAME || Listing file for Ardo inbound XML files || SYSTEM
|-
| INBOUND_ARDO_SCRIPT_NAME || Command file for Ardo inbound XML files || SYSTEM
|-
| INBOUND_BEIG2_IDENTIFIER || Identifier for MTS PO Inbound DAI_TMS_BEIG_ORD_YYYYMMDDHHMMSSII.XML || SYSTEM
|-
| INBOUND_BEIG2_LISTING_NAME || Listing file for BEIG inbound XML files || SYSTEM
|-
| INBOUND_BEIG2_SCRIPT_NAME || Command file for BEIG inbound XML files || SYSTEM
|-
| INBOUND_BEIG_IDENTIFIER || Identifier for MTS PO Inbound DAI_TMS_BEIG_ORD_YYYYMMDDHHMMSSII.XML || SYSTEM
|-
| INBOUND_BEIG_LISTING_NAME || Listing file for BEIG inbound XML files || SYSTEM
|-
| INBOUND_BEIG_SCRIPT_NAME || Command file for BEIG inbound XML files || SYSTEM
|-
| INBOUND_FAILURES_PATH || Path for failed inbound files || SYSTEM
|-
| INBOUND_GLO_IDENTIFIER || Identifier for MTS PO Inbound Unilever files || SYSTEM
|-
| INBOUND_GLO_LISTING_NAME || Listing file for GLO inbound XML files || SYSTEM
|-
| INBOUND_GLO_LOA_IDENTIFIER || Identifier for MTS PO Inbound Unilever LOA files || SYSTEM
|-
| INBOUND_GLO_SCRIPT_NAME || Command file for GLO inbound XML files || SYSTEM
|-
| INBOUND_POM_IDENTIFIER || Identifier for MTS PO Inbound MTS_POMI_<YYYYMMDDHH24MISS>_<10 DIGIT SEQ>.XML || SYSTEM
|-
| INBOUND_POM_LISTING_NAME || Listing file for POM inbound XML files || SYSTEM
|-
| INBOUND_POM_SCRIPT_NAME || Command file for POM inbound XML files || SYSTEM
|-
| INBOUND_PROCESSED_PATH || Path for processed inbound files || SYSTEM
|-
| INBOUND_UNI_IDENTIFIER || Identifier for MTS PO Inbound Unilever files || SYSTEM
|-
| INBOUND_UNI_LISTING_NAME || Listing file for UNI inbound XML files || SYSTEM
|-
| INBOUND_UNI_SCRIPT_NAME || Command file for UNI inbound XML files || SYSTEM
|-
| INCLUDE_CDATA_TAG || Use CDATA tag around XML tags values and allowed values will be (Y/N) which will be used to control escaping of special characters like & || SYSTEM
|-
| INCLUDE_FAILED_ORDERS || Include Failed Orders as CANCELLED for API || COST_CENTRE
|-
| INCL_ROUTE_CODE || Include Baxter Route code and delivery method || COST_CENTRE
|-
| INCOMPLETE_ORDERS_WARNING || Display warning message on trip status change if no order items exist || COST_CENTRE
|-
| INHERIT_LAT_LONG || Inherit Lat/Long details from parent address || CUSTOMER
|-
| INNER_OUTER_DU || Inner and outer du types for rating || COST_CENTRE
|-
| INTERFACE_FORMAT || Controls the interface format for inbound orders || SYSTEM
|-
| INTERFACE_INBOUND_PATH || Path for Inbound files || SYSTEM
|-
| INT_ADD_MOD43_CD || Store the Modulo 43 check digit as a suffix for the order item for the barcode label (Y/N). || COST_CENTRE
|-
| INT_ADD_MOD43_CD || Store the Modulo 43 check digit as a suffix for the order item for the barcode label (Y/N). || CUSTOMER
|-
| INT_ALTERNATE_DB || Determines if alternate_db is used as a condition in the INT_MSG code || SYSTEM
|-
| INT_CARRIER_DETS || Used to control which carrier details cursor is fetched in INT_MSG.PROCESS_TRIP_DTL_MSG || SYSTEM
|-
| INT_CHARGES || Determines whether internal charging is based on COST_CENTRE or GROUP_NAME || SYSTEM
|-
| INT_DECODE_UNISON || Used to control which DECODE_VALUE is used in INT_MSG || SYSTEM
|-
| INT_DROP_POSTCODE || Determines how v_string is built within INT_MSG.PROCESS_EFX_TRIP_DTL_MSG part of INT_MSG alignment || SYSTEM
|-
| INT_ERRNUM || Used to establish whether error numbers should be inserted into VALIDATION_ERROR in INT_MSG || SYSTEM
|-
| INT_IGNORE_DESP_QTY || Send despatch messages even when despatch quantity is not set || SYSTEM
|-
| INT_KEEP_FILE || Do not remove files from delivery folder || SYSTEM
|-
| INT_MSG_TYPE || Determines whether a cursor is fetched or a hard coded if IN the INT_MSG.READ_BBOKING_HEADER procedure. Part of Alignment process. || SYSTEM
|-
| INT_ORDER_COMMENT || Indicates if the order_comments in INT_MSG.PROCESS_UNSION_FILE is selected as a substring || SYSTEM
|-
| INT_ORDER_CORRECT || Indicates if interface files are corrected || SYSTEM
|-
| INT_READ_EFX_COMMENTED_OUT || Indicated if code is commented out in EFX procedure of INT_MSG part of alignment || SYSTEM
|-
| INT_READ_EFX_CURSOR || Indicates if C_EFX_TRIPS cursor is based on trip or load part of INT_MSG alignment || SYSTEM
|-
| INT_REVERSE_DECODE || Indicates if INT_MSG.PROCESS_EXE_OUTBOUND_FILE requires a call to IMP_REVERSE_DECODE in the current database || SYSTEM
|-
| INT_TRAILER_TYPE || DECODE or REVERSE to determine how trailer type is extracted in INT_MSG.PROCESS_EFX_TRIP_DTL_MSG || SYSTEM
|-
| INT_TRANSHIP_POS || Used to determine TRANSHIP_IND is in the incoming file for INT_MSG.READ_BOOKING_DETAIL || SYSTEM
|-
| INT_TRIP_STOP_DATE || Determines which date (LATE DEL or DEPART) is passed to the string in INT_MSG || SYSTEM
|-
| INT_UNISON_ERRNUM || Indicates if errnum should be included when inserting data into validation_error field in INT_MSG.PROCESS_UNISON_FILE || SYSTEM
|-
| INT_USE_NEW_DB || Determines which procedures within INT_MSG use the new database name || SYSTEM
|-
| INT_XML_DAYS_PAST || Used to set how many days into the past the dp_pulse package should look for locked records || SYSTEM
|-
| INVOICE_DIR || Directory for storing invoices when printed || SYSTEM
|-
| INV_ACT_PMNTS_DAYS || Process payments for a set number of days prior to the period end date or the current date for the next invoice. || SYSTEM
|-
| INV_SEARCH_FROM_OFFSET || Controls how many days in the past to default the from search in the INVOICES form. || SYSTEM
|-
| INV_SEARCH_TO_OFFSET || Controls how many days in the future to default the from search in the INVOICES form. || SYSTEM
|-
| INV_SET_PERIOD || Set the period for the invoice based on the current date (Y/N) || SYSTEM
|-
| ISOTRAK_BATCH_JOB_SIZE || Number of job records that are processed each minute via the ISOTRAK interface || SYSTEM
|-
| ISO_ENABLED || ISO enabled for this database || SYSTEM
|-
| ISO_FTP_DESTINATION_DIRECTORY || Directory for FTP of ISOTRAK Files || SYSTEM
|-
| ISO_FTP_DESTINATION_IP_ADDRESS || IP for FTP of ISOTRAK Files || SYSTEM
|-
| ISO_FTP_DESTINATION_PASSWORD || Password for FTP of ISOTRAK Files || SYSTEM
|-
| ISO_FTP_DESTINATION_PORT || Port for FTP of ISOTRAK Files || SYSTEM
|-
| ISO_FTP_DESTINATION_USERNAME || Username for FTP of ISOTRAK Files || SYSTEM
|-
| ISO_INBOUND_ARCH || Path for inbound ISO XML archiving || SYSTEM
|-
| ISO_INBOUND_FAIL || Path for ISO XML failures || SYSTEM
|-
| ISO_INBOUND_IDENTIFIER || Pattern for ISO Trip Inbound XML || SYSTEM
|-
| ISO_INBOUND_LISTING_NAME || Filename for list of files in directory for ISO XML Trip Inbound || SYSTEM
|-
| ISO_INBOUND_PATH || Path for yet to be processed XML files from ISO || SYSTEM
|-
| ISO_LISTING_SCRIPT_NAME || Script name for ISO XML Trip Inbound || SYSTEM
|-
| ISO_OUTBOUND_ARCH || Path for archiving outbound ISO XML interfaces || SYSTEM
|-
| ISO_OUTBOUND_FAIL || Path for failing outbound ISO XML interfaces || SYSTEM
|-
| ISO_OUTBOUND_PATH || Path for outbound ISO XML interfaces || SYSTEM
|-
| ISO_Queue_Name || ISOTRAK Queue Name || SYSTEM
|-
| ISO_RECON_MODE || Determine whether messages should be deleted or reconciled, then delete or update as appropriate, ARCHIVE or DELETE || SYSTEM
|-
| ISO_Sched_Prefix || ISOTRAK Schedule Prefix || SYSTEM
|-
| ISO_Signature || ISOTRAK Signature || SYSTEM
|-
| JAVAVM_PROFILE || javavm profile || SYSTEM
|-
| KCC_DEL_INFO_PATH || File path for KCC Delivery Information Export || SYSTEM
|-
| KER_LOADING_FTP_DIRECTORY || Specify the directory for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_FILENAME || Specify the Filename for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_IP_ADDRESS || Specify the IP Address for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_PASSWORD || Specify the Password for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_PATH || Specify the path for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_PORT || Specify the Port for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_USERNAME || Specify the Username for the Kerridge Loading file || COST_CENTRE
|-
| KER_WEB_PATH || URL for show web Kerridge Files || COST_CENTRE
|-
| LABEL_DIR || Directory for storing the labels when printed || COST_CENTRE
|-
| LABEL_FILE || Directory for storing the labels when printed || COST_CENTRE
|-
| LABEL_FILE_UNSCHEDULED || The label format for when the order is UNSCHEDULED. || COST_CENTRE
|-
| LABEL_FORMAT || Label format for Orders || COST_CENTRE
|-
| LABEL_GROUP || Delivery Type for which labels will be printed || COST_CENTRE
|-
| LABEL_LOGO_FILE || Set label logo file || SYSTEM
|-
| LANE_RATE_CHARGING || lane rates calc || COST_CENTRE
|-
| LAST_RELEASE_DATE || Last release for this database. NB. UPDATED_DATE (updated by trigger) stores the real value (see ORI_STATS). Change VALUE after each release. || SYSTEM
|-
| LBO_CUTOFF_TIME_DEFAULT || Latest time by which a Lane Based Order must be places if Cut-off functionality is switched on || SYSTEM
|-
| LBO_CUTOFF_TIME_ENABLE || LBO Cut-off times enabled - Y or N || SYSTEM
|-
| LBO_FUTURE_ORDER_LIMIT_DAYS || Maximum number of days in future that LB Order can be created || SYSTEM
|-
| LFE_API_AUTHORISATION || Client Ref for authorisation || SYSTEM
|-
| LFE_API_VERSION || 11 for 11g, 12 for 12c || SYSTEM
|-
| LICENCE_MONITOR_LEVEL || Licence monitor alert level || SYSTEM
|-
| LINE_ITEM_TOTALS || Controls if service payments are generated || COST_CENTRE
|-
| LOADING_REPORT || NON Cost centre Loading Report || SYSTEM
|-
| LOAD_LEVEL_PARAM || Level of data reported in the Load List || COST_CENTRE
|-
| LOCATION_DECODE_VALIDATION || Validate Addresses using decode values || COST_CENTRE
|-
| LOGINEXT_API_TOKEN || API Token for Loginext || SYSTEM
|-
| LOGINEXT_ENDPOINT || Endpoint address for Loginext || SYSTEM
|-
| LOGIX_ARCH_DIR || Folder for archive of Logix files || SYSTEM
|-
| LOGIX_CREATE_FILE || Create a file containing CLOB || SYSTEM
|-
| LOGIX_DEL_PRIORITY_DAYS || Number of days before late delivery when prioritized in Route Optimiser || SYSTEM
|-
| LOGIX_DIR || Folder for Logix files || SYSTEM
|-
| LOGIX_MASTER_PROFILE || Profile for Logix API webservice || SYSTEM
|-
| LOGIX_MASTER_WORK_AREA || LogiX Master Work area directory name || SYSTEM
|-
| LOGIX_PASSWORD || Password for Logix API webservice || SYSTEM
|-
| LOGIX_PROFILE || Profile for Logix API webservice || SYSTEM
|-
| LOGIX_PROJECT || Project for Logix API webservice || SYSTEM
|-
| LOGIX_PROXY || Proxy server name for Logix API webservice || SYSTEM
|-
| LOGIX_RANGE || Range of schedules to send || SYSTEM
|-
| LOGIX_RANGE_OLD || Range of schedules to send || SYSTEM
|-
| LOGIX_SCHEDULE_MATRIX || How Many Days in the future to Recalculate Planned Transport? || SYSTEM
|-
| LOGIX_SERVER_NAME || LogiX server name || SYSTEM
|-
| LOGIX_SLOT_CUTOFF_TIME || Cut-off time for planning trunks in LogiX import || SYSTEM
|-
| LOGIX_TIMEOUT || Timeout for Logix API webservice || SYSTEM
|-
| LOGIX_URL || URL for Logix API webservice || SYSTEM
|-
| LOGIX_USERNAME || Username for Logix API webservice || SYSTEM
|-
| LOGNET_INT_DIR || LOGNET file path. || SYSTEM
|-
| LOGO_FILE || Logo file || SYSTEM
|-
| LOGO_FILE_BW || Logo file in Black and White for system usage (e.g. on labels). || SYSTEM
|-
| LOGO_PATH || Site specific location of logo files || SYSTEM
|-
| LOTS_ADD_DEBRIEF || LOTS Additional Debrief Details || COST_CENTRE
|-
| LOTS_DEL_CUST_SIGNATORY || Controls if DEL messages for LOTS require an actual signatory - Y to hold messages. || COST_CENTRE
|-
| LOTS_DEL_MSG_TRIP_STATUS_COMPLETE || Send LOTS DEL Message if trip status set to COMPLETE (Y/N) || COST_CENTRE
|-
| LOTS_EXPORT_TYRE || LOTS export tyre || COST_CENTRE
|-
| LOTS_FTP_DESTINATION_DIRECTORY || Final Destination directory for FTP of LOTS Files || SYSTEM
|-
| LOTS_FTP_DESTINATION_IP_ADDRESS || IP for FTP of LOTS Files || SYSTEM
|-
| LOTS_FTP_DESTINATION_PASSWORD || Password for FTP of LOTS Files || SYSTEM
|-
| LOTS_FTP_DESTINATION_PORT || Port for FTP of LOTS Files || SYSTEM
|-
| LOTS_FTP_DESTINATION_USERNAME || Username for FTP of LOTS Files || SYSTEM
|-
| LOTS_FTP_PUT_DIRECTORY || Mid-Send directory for FTP of LOTS Files || SYSTEM
|-
| LOTS_INBOUND_ARCH || Path for archiving inbound LOTS XML interfaces || SYSTEM
|-
| LOTS_INBOUND_FAIL || Path for failing inbound LOTS XML interfaces || SYSTEM
|-
| LOTS_INBOUND_IDENTIFIER || Pattern for LOTS Trip Inbound XML || SYSTEM
|-
| LOTS_INBOUND_LISTING_NAME || Filename for list of files in directory for LOTS XML Trip Inbound || SYSTEM
|-
| LOTS_INBOUND_PATH || Path for inbound LOTS XML interfaces || SYSTEM
|-
| LOTS_INC_ORDER_HEADER_CONFIRM || Includes the ORDER_HEADER_CONFIRM section in the DEL file for LOTS. || SYSTEM
|-
| LOTS_INC_STOP_SIGNATURE || Indicates if the STOP_SIGNATURE section will be displayed in the DEL outbound files to LOTS. || SYSTEM
|-
| LOTS_INC_STOP_TYPE_DESC || Include STOP-TYPE_DESC tag in XML || SYSTEM
|-
| LOTS_LISTING_SCRIPT_NAME || Script name foe LOTS XML Trip Inbound || SYSTEM
|-
| LOTS_MINI_LODGMENT_FILE || Lodgements || SYSTEM
|-
| LOTS_OUTBOUND_ARCH || Path for archiving outbound LOTS XML interfaces || SYSTEM
|-
| LOTS_OUTBOUND_FAIL || Path for failing outbound LOTS XML interfaces || SYSTEM
|-
| LOTS_OUTBOUND_PATH || Path for outbound LOTS XML interfaces || SYSTEM
|-
| LOTS_PREVENT_MULTI_VLI_VUI || Prevent multiple VLI and VUI files being sent to LOTS (Y/N). || SYSTEM
|-
| LOTS_SEND_PLANNED || Allow TRP message to be sent to LOTS when trip is still at status Planned || SYSTEM
|-
| LOTS_SEND_WHEN_VEHICLE_SCANNED || List of LOTS message types that will be held until a vehicle scan is received for the order. || COST_CENTRE
|-
| LOTS_VERSION_NUMBER || LOTS Poller Version || SYSTEM
|-
| LOTS_XFER_EXTENSION || Sets the LOTS transfer file extension || COST_CENTRE
|-
| LOWERCASE_REF || Allow lowercase bill of lading || COST_CENTRE
|-
| MAINTAIN_SCHEDULE_DATES || Use wholesale schedule dates || COST_CENTRE
|-
| MANF_RECIPIENT || Indicates the recipient type of the manifest || COST_CENTRE
|-
| MANF_REPORT || Indicates the name of the manifest report to be automatically generated when a trip is accepted || COST_CENTRE
|-
| MANF_REPORT || Driver Manifest Name || COST_CENTRE
|-
| MANIFEST_AT_ENROUTE_ONLY || Only Send XML manifest at En-Route status || CARRIER
|-
| MANIFEST_ORDERS || Indicates that the cost centre allows parent and child shipments to be imported || COST_CENTRE
|-
| MAX_LOCATION_INACTIVE_DAYS || Maximum number of days a location can remain inactive before being set to inactive automatically. || SYSTEM
|-
| MAX_REPORT_PARAM_VALUES || Maximum number of multiple values that can be selected for extracts || SYSTEM
|-
| MAX_VOLUME || Maximum Volume for any FTL || SYSTEM
|-
| MAX_WEIGHT || Maximum weight for any FTL || SYSTEM
|-
| MCS_AWB_REQUIRED || This flag control whether the AWB (Air Way Bill) is requested during the pallet building and despatch processes in C-MCS. || SYSTEM
|-
| MCS_DESPATCH_DISPLAY_DROP || Display the Drop Number in the Despatch Screen || SYSTEM
|-
| MCS_DESPATCH_TO_PLAN || Enforce the despatch scanning of packages and pallets to the planned trips? (Y/N) || SYSTEM
|-
| MCS_DISPLAY_ADDITIONAL || Display items scanned from different trips in MCS despatch? (Y/N) || SYSTEM
|-
| MCS_DISPLAY_COMMTYPE_HAZ || This flag controls whether commodity code and hazardous information is displayed against items and pallets in C MCS pallet building. || SYSTEM
|-
| MCS_DISPLAY_PROD_TYPE || This flag controls whether the Product Type is displayed against items and pallets in C- MCS in receipt, despatch and pallet building. || SYSTEM
|-
| MCS_DYNAMIC_PALLET_BUILDING || This flag controls whether to allow pallet building to occur while scanning items for despatch in the items screen || SYSTEM
|-
| MCS_EXCEPTIONS_DAMAGED || MCS exceptions at Receipt (excluding FNR and LATE) and Despatch will be marked as damaged items and be removed from onward trips (Y/N). || SYSTEM
|-
| MCS_FAST || This parameter will control the level of validation performed during MCS scanning. || SYSTEM
|-
| MCS_FAST_VALIDATION || Is fast validation enabled || SYSTEM
|-
| MCS_ITEM_DISPLAY_DU || This flag controls whether the DU type is displayed instead of the item type on item lists in MCS. || SYSTEM
|-
| MCS_LOCATION_PROMPT || Prompt for Receipt Location at Receipt || SYSTEM
|-
| MCS_MOVE_FULL_CONSIGNMENT || Move all items for an order during MCS split scanning. || SYSTEM
|-
| MCS_NEW_DESPATCH_MODE || This flag controls whether the new Despatch screen is run || SYSTEM
|-
| MCS_PALLET_LABEL_FORMAT || The format of pallet label produced by the pallet building option when printing pallet labels. || SYSTEM
|-
| MCS_PREVENT_UNPLANNED || Prevent unplanned items being scanned for pallet building, despatch and receipt although expected for the route (Y/N)? || SYSTEM
|-
| MCS_RECEIVE_TO_PLAN || Enforce the receipt scanning of packages and pallets to the planned trips? (Y/N) || SYSTEM
|-
| MCS_SET_PALLET_ID || MCS set item Pallet Id || SYSTEM
|-
| MCS_TEMPERATURE_SCAN || Prompt for Temperature Type at MCS Despatch || SYSTEM
|-
| MCS_TENDERED_ITEMS || This flag controls whether MCS items are generated at the change to TENDERED status as well as at ACCEPTED status, or just ACCEPTED status. || SYSTEM
|-
| MCS_UPDATE_SCAN_IMMEDIATELY || Allow items to count as despatched immediately after scanning? (Y/N) || SYSTEM
|-
| MSC_STD_STATUS_CHANGES || Do trips go to EN-ROUTE and COMPLETED auto? Affects Despatch only. N means set to ACCEPTED if at PLANNED or TENDERED, otherwise EN-ROUTE. Any other value means set to EN-ROUTE status. || SYSTEM
|-
| MICD_DONT_SEND_DRVR_ID || Microlise Direct Don't send driver id || COST_CENTRE
|-
| MICD_EE_PATH_IN_IDENT || Pattern for MICD EventExport Inbound XML || SYSTEM
|-
| MICD_JSE_PATH_IN_IDENT || Pattern for MICD JourneySummaryExport Inbound XML || SYSTEM
|-
| MIC_3PL_TRIP_HOURS || The number of elapsed hours that Microlise requires a trip not to exceed. || SYSTEM
|-
| MIC_ACTUAL_DISTANCE || Will Microlise receive an actual distance from Paragon for a trip (Y/N)? || SYSTEM
|-
| MIC_ADD_STOP_BARCODE || Include new tag STOP_BARCODE on Microlise outbound xml || SYSTEM
|-
| MIC_ALLOW_CREATE_ORDERS || Allow orders to be created || SYSTEM
|-
| MIC_AUTO_CONFIRM_COLLECTION_ORDERS || Create Service Types via Microlise || COST_CENTRE
|-
| MIC_CALC_REASON_QTY || Set the item reason quantity to the despatched quantity if a reason code is provided with a quantity of 0 instead of an accurate quantity (Y/N). || COST_CENTRE
|-
| MIC_COLLECTION_ORDER_TASKS || Create ad hoc orders via Microlise || COST_CENTRE
|-
| MIC_CONSOL_ORDERS || Consolidate the orders for the Microlise outbound XML flow, if Y then the orders will be consolidated. || COST_CENTRE
|-
| MIC_CONSOL_STOPS || Consolidate the stops for the Microlise outbound XML flow, if Y then the stops will be consolidated. || COST_CENTRE
|-
| MIC_CREATE_CD || Microlise interface to create CD reason for successful deliveries when not provided || SYSTEM
|-
| MIC_CREATE_FAILED_ORDERS || Controls if orders be set to FAILED status on inbound Microlise flow || COST_CENTRE
|-
| MIC_DEBRIEF_POC || Allow the collection orders to set their POC flag when they are confirmed with actual delivered quantities and generate a ORD_COLL_XML file? (Y/N) || COST_CENTRE
|-
| MIC_DEFAULT_DELIVER || Should the actual times be set to the planned ones upon receipt of a STA or DEP message || COST_CENTRE
|-
| MIC_DEFAULT_PRODUCT_TYPE || Create Service Types via Microlise || COST_CENTRE
|-
| MIC_DEFINE_GROUP_NAME || Group Name For Microlise Collection Orders || COST_CENTRE
|-
| MIC_DEF_COST || Cost Centre default || SYSTEM
|-
| MIC_DEF_CUST || Customer ID default for Microlise || COST_CENTRE
|-
| MIC_DEF_DEL_TYPE || Default Del Type for empty orders || SYSTEM
|-
| MIC_DEF_DU_TYPE || Du Type || SYSTEM
|-
| MIC_DEF_PRODUCT || Product Type || SYSTEM
|-
| MIC_DELETE_REASONS || Delete Reason codes before adding new reason codes. || COST_CENTRE
|-
| MIC_DEL_DAY_OFFSET || Delivery Day Offset || SYSTEM
|-
| MIC_DIRECT_DEF_COST || Cost Centre default || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_DIRECTORY || Directory for FTP of Microlise Direct Files || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_IP_ADDRESS || IP for FTP of Microlise Files || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_PASSWORD || Password for FTP of Microlise Direct Files || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_PORT || Port for FTP of Microlise Direct Files || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_PROTOCOL || Protocol for FTP of Microlise Direct Files || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_USERNAME || Username for FTP of Microlise Direct Files || SYSTEM
|-
| MIC_DIRECT_PATH_IN || Inbound Directory for Direct Microlise XML || SYSTEM
|-
| MIC_DIRECT_PATH_IN_ARCH || Archive Directory for Inbound Direct Microlise XML || SYSTEM
|-
| MIC_DIRECT_PATH_IN_FAIL || Failure Directory for Inbound Direct Microlise XML || SYSTEM
|-
| MIC_DIRECT_PATH_IN_IDENT || Pattern for MIC Trip Inbound XML || SYSTEM
|-
| MIC_DIRECT_PATH_IN_LIST || Filename for list of files in directory for MIC Direct XML Trip Inbound || SYSTEM
|-
| MIC_DIRECT_PATH_IN_SCRIPT || Script name for MIC Direct XML Trip Inbound || SYSTEM
|-
| MIC_DIRECT_PATH_OUT || Outbound Directory for Direct Microlise XML || COST_CENTRE
|-
| MIC_DIRECT_PATH_OUT_ARCH || Outbound Archive Directory for Direct Microlise XML || SYSTEM
|-
| MIC_DIRECT_SEND_CUSTOMER || Microlise direct will send customer group instead of carrier || SYSTEM
|-
| MIC_DIRECT_SEND_ROUTE_CODE || Set Microlise direct to send route code in the Journey Alias field. || SYSTEM
|-
| MIC_DIRECT_UPDATE_PRIORITY || Flag indicating priority for del/arr updates Manual, EventExport, PodPoc updates || COST_CENTRE
|-
| MIC_DISABLE_EMPTY_ITEM_STOPS || Allows disabling of stops with no items on || SYSTEM
|-
| MIC_EXCLUDE_ASSET_ID || A comma-delimited list of prefixes that determines if the new asset ID will not be stored (e.g. for loose items). || SYSTEM
|-
| MIC_EXCLUDE_UNPACKED_LINES || Exclude any order lines that have not been packed from the Microlise files (Y/N). || COST_CENTRE
|-
| MIC_EXTENDED_INSTRUCTIONS || Are extended instructions sent to MICROLISE || COST_CENTRE
|-
| MIC_FTP_DESTINATION_DIRECTORY || Directory for FTP of Microlise Files || SYSTEM
|-
| MIC_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Microlise Files || SYSTEM
|-
| MIC_FTP_DESTINATION_PASSWORD || Password for FTP of Microlise Files || SYSTEM
|-
| MIC_FTP_DESTINATION_PORT || Port for FTP of Microlise Files || SYSTEM
|-
| MIC_FTP_DESTINATION_USERNAME || Username for FTP of Microlise Files || SYSTEM
|-
| MIC_INBOUND_ARCH || Path for Microlise XML archiving || SYSTEM
|-
| MIC_INBOUND_CONTINUE_ON_ERROR || Continue processing MICROLISE message if invalid items exist within the file? (Y/N) || COST_CENTRE
|-
| MIC_INBOUND_FAIL || Path for Microlise XML failures || SYSTEM
|-
| MIC_INBOUND_IDENTIFIER || Pattern for MIC Trip Inbound XML || SYSTEM
|-
| MIC_INBOUND_LISTING_NAME || Filename for list of files in directory for MIC XML Trip Inbound || SYSTEM
|-
| MIC_INBOUND_PATH || Path for yet to be processed XML files from Microlise || SYSTEM
|-
| MIC_INC_SERVICES || List of services to be sent out to Microlise || COST_CENTRE
|-
| MIC_LISTING_SCRIPT_NAME || Script name foe MIC XML Trip Inbound || SYSTEM
|-
| MIC_ORDER_FULFILLMENT || Send Additional Order Fulfillment values to Microlise. || COST_CENTRE
|-
| MIC_OUTBOUND_ARCH || Path for archiving outbound Microlise XML interfaces || SYSTEM
|-
| MIC_OUTBOUND_FAIL || Path for failing outbound Microlise XML interfaces || SYSTEM
|-
| MIC_OUTBOUND_PATH || Path for outbound Microlise XML interfaces || SYSTEM
|-
| MIC_OWNING_DEPOT || Indicates if the Microlise file is sent with Database or owning depot in the name || SYSTEM
|-
| MIC_PACKED_DESPATCHED || Only packed/despatched lines and items sent to Microlise || COST_CENTRE
|-
| MIC_POCPOD_NON_DEPOT || Microlise to set POC/POD for non depot orders || COST_CENTRE
|-
| MIC_REDUCED_EVENTS || Will Microlise receive a reduced number of defined events (Y/N)? || SYSTEM
|-
| MIC_RESOURCE_UPDATE || Update resources on recipt of Microlise message || COST_CENTRE
|-
| MIC_SEND_ACCEPTED || Send Microlise Trip message when status changed to ACCEPTED || SYSTEM
|-
| MIC_SEND_ADDR_CONTACTS || Send Contacts to Microlise (DEP/DEL/BOTH) || COST_CENTRE
|-
| MIC_SEND_ADD_REF || Send Address references in Mircolise XML flow || COST_CENTRE
|-
| MIC_SEND_ALL_CONTACTS || Send All Contacts to Microlise (Y/N) || COST_CENTRE
|-
| MIC_SEND_CHILDREN || Are child locations sent to Microlise || COST_CENTRE
|-
| MIC_SEND_COST || Send Costs in Mircolise XML flow || COST_CENTRE
|-
| MIC_SEND_DETAIL_ID || Send DETAIL_ID in the MIC XML flow || COST_CENTRE
|-
| MIC_SEND_DIRECT || Flag indicating needing to send direct message to Microlise or not || COST_CENTRE
|-
| MIC_SEND_EMPTY || Are empty resources sent to Microlise || SYSTEM
|-
| MIC_SEND_HAULIER_TYPE || Include Haulier Type in outbound microlise flow || COST_CENTRE
|-
| MIC_SEND_ORD_LINE_AND_ITEM || Send both Order Lines and Items to Microlise. || COST_CENTRE
|-
| MIC_SEND_ORD_REF || Send Order sub references in Mircolise XML flow || COST_CENTRE
|-
| MIC_SEND_SUB_TYPE || Are VAN carriers indicated || COST_CENTRE
|-
| MIC_SERVICE_TASKS || Create Service Types via Microlise || COST_CENTRE
|-
| MIC_SET_TO_COMP_CONF || Set trip to P-Completed, F-Confirmed, N-Neither once Microlise has finished its updates || SYSTEM
|-
| MIC_SHIPMENT_SO_REF || Is external ref included in the Shipment detail tag? || SYSTEM
|-
| MIC_SO_REF || So_ref sent to MICROLISE is oms_ref concatenated with external_ref || SYSTEM
|-
| MIC_SO_REF_FORMAT || Format for the SO_REF for Microlise for non-consolidated orders: 0 = Standard (Customer Ref), 1 = Type-SO_REF-Trip-Seq-Act (eg C-12345-MAN-1234-001-L) || SYSTEM
|-
| MIC_SO_REF_FORMAT || Format for the SO_REF for Microlise for non-consolidated orders: 0 = Standard (Customer Ref), 1 = Type-SO_REF-Trip-Seq-Act (eg C-12345-MAN-1234-001-L) || COST_CENTRE
|-
| MIC_SO_REF_FORMAT || Contingency Import setting || COST_CENTRE
|-
| MIC_SUPPRESS_ORDER_SEGMENT || Only show orders against the stop for the final delivery || COST_CENTRE
|-
| MIC_TRUNK_CONSOL || Are trunk trips consolidated to send to Microlise || COST_CENTRE
|-
| MIC_UPDATE_ACTUALS_FROM_PODPOC || Update Actuals based on POD/POC Message. || COST_CENTRE
|-
| MIC_UPDATE_TO_DELIVER || Update To Deliver based on Delivered Amount || COST_CENTRE
|-
| MIC_USE_ALT_STOP_ID || Prefix stop id with route code for first and last stops || COST_CENTRE
|-
| MIC_USE_PALLET_ID || Use Pallet ID in Microlise || COST_CENTRE
|-
| MIC_USE_STOP_ID || Determines if the stop ID or the stop sequence will be used by Microlise, if Y then the stop ID will be used. || COST_CENTRE
|-
| MIC_USE_STOP_ID || Determines if the stop ID or the stop sequence will be used by Microlise, if Y then the stop ID will be used. || SYSTEM
|-
| MILK_ROUND_ORDERS || Allow orders to be added to Milk round Routes based on delivery information || COST_CENTRE
|-
| MILK_ROUND_TRIP_GENERATION || Trips Generated using milk round processing || COST_CENTRE
|-
| MINIMUM_COLLECTION || Are Minimum collection charges applicable at each stop || SYSTEM
|-
| MINS_TRUNKS_ACCEPTED || How many minutes to auto accept trunk trips? || SYSTEM
|-
| MIN_COLLECTION_CHARGE || Minimum Collection charge per stop || SYSTEM
|-
| MIN_CONSIGNMENT_CHARGE || Minimum charge per consignment || SYSTEM
|-
| MIS_CHAR_SET || Character set for MIS extracts || SYSTEM
|-
| MIS_DELETED_DAYS || The number of days after which the data on the MIS_DELETED table will be removed. || SYSTEM
|-
| MIS_DELETE_REQUIRED || Determines whether MSI table needs to be updated || SYSTEM
|-
| MIS_FTP_ARCH_DIR || MIS FTP archive directory || SYSTEM
|-
| MIS_FTP_DESTINATION_DIRECTORY || MIS FTP Dir || SYSTEM
|-
| MIS_FTP_DESTINATION_IP_ADDRESS || MIS FTP IP || SYSTEM
|-
| MIS_FTP_DESTINATION_PASSWORD || MIS FTP Password || SYSTEM
|-
| MIS_FTP_DESTINATION_PORT || MIS FTP Port || SYSTEM
|-
| MIS_FTP_DESTINATION_USERNAME || MIS FTP User || SYSTEM
|-
| MIS_FTP_PROTOCOL || MIS FTP Protocol || SYSTEM
|-
| MIS_TAB_DELIMITER || Use a tab as a delimiter for the MIS files (Y/N)? || SYSTEM
|-
| MIXMOVE || Is MIMOVE interface enabled? || SYSTEM
|-
| ML_REQUIRED || Whether database is multi-lingual. || SYSTEM
|-
| MSC_STD_STATUS_CHANGES || Do trips go to EN-ROUTE and COMPLETED auto || SYSTEM
|-
| MSG_CONCAT_TIME_PERIOD || Message concatenation time period (minutes) || SYSTEM
|-
| MSG_LOC_ORD_DEL_BY_DELIVERY || Set to Y if message body for event LOC_ORD_DEL is to show delivery details || SYSTEM
|-
| MSG_NAKS || Send an email message for NAK responses (Y/N) || SYSTEM
|-
| MSG_NAKS_EMAIL || The email recipient for a message for NAK responses || SYSTEM
|-
| MSG_NAKS_TYPE || A list of NAK event types to send an email message || SYSTEM
|-
| MSG_SCHEMA_URL || XSD Schema URL Path || SYSTEM
|-
| MSG_SCHEMA_XSD || XSD Schema XSD Name || SYSTEM
|-
| MSG_SENDER_TRIP_ACCEPT || The sending email address for a the trip accept message. || COST_CENTRE
|-
| MSG_SEND_HOURS_THRESHOLD || Threshold in hours before current date when Trip messages will still be sent (using trip start date) || SYSTEM
|-
| MSG_SUBJECT_BKNG_DTL || Message Subject for Booking Detail message || SYSTEM
|-
| MSG_SUBJECT_BKNG_DTL_L || Message Subject for Lane Booking Detail message || SYSTEM
|-
| MSG_SUBJECT_CTM_AUTCHASE || Message Subject for Carrier Trip Management (CTM) Auto Chase Messages || SYSTEM
|-
| MSG_SUBJECT_CTM_MANCHASE || Message Subject for Carrier Trip Management (CTM) Manual Chase Messages || SYSTEM
|-
| MSG_SUBJECT_LANE_ACD_DTL || Message Subject for Lane Accepted Detail message || SYSTEM
|-
| MSG_SUBJECT_LANE_ACPTD || Message Subject for Lane Accepted message || SYSTEM
|-
| MSG_SUBJECT_LANE_ACPTD_A || Message Subject for Lane Accepted Amended message || SYSTEM
|-
| MSG_SUBJECT_LANE_A_DTL_A || Message Subject for Lane Accepted Amended Detail message || SYSTEM
|-
| MSG_SUBJECT_LOC_ORD_DEL || Message Subject for Pre-warning Order delivery message || SYSTEM
|-
| MSG_SUBJECT_MANIFEST || Message Subject for Network Rail Manifest message || COST_CENTRE
|-
| MSG_SUBJECT_MANIFEST || Message Subject for Manifest message || SYSTEM
|-
| MSG_SUBJECT_MANIFEST_A || Message Subject for Manifest Amended message || SYSTEM
|-
| MSG_SUBJECT_MANIFEST_DTL || Message Subject for Manifest Detail message || SYSTEM
|-
| MSG_SUBJECT_MANIFEST_SUM || Message Subject for Manifest Summary message || SYSTEM
|-
| MSG_SUBJECT_MANIFE_DTL_A || Message Subject for Manifest Detail Amended message || SYSTEM
|-
| MSG_SUBJECT_SELF_BIL_INV || Message Subject for Self bill Credit note || SYSTEM
|-
| MSG_SUBJECT_TENDER_INVT || Message Subject for Tender Invitation message || SYSTEM
|-
| MSG_SUBJECT_TENDER_INV_A || Message Subject for Tender Invitation Amended message || SYSTEM
|-
| MSG_SUBJECT_TENDER_SUM || Message Subject for Tender Invitation Summary message || SYSTEM
|-
| MSG_SUBJECT_TEND_INV_DTL || Message Subject for Tender Invitation Detail message || SYSTEM
|-
| MSG_SUBJECT_TND_INV_DT_A || Message Subject for Tender Invitation Detail Amended message || SYSTEM
|-
| MSG_SUBJECT_TRIP_COM_LST || Message Subject for Trip Completed List || SYSTEM
|-
| MSG_SUB_DEPOT || Identifies the depot to replace with the current depot of the order items in the emails to invite tenders. || SYSTEM
|-
| MSG_TRIP_CONTACT || Messaging Contact Details || COST_CENTRE
|-
| MTMIF_DEFAULT_CUR || Default value for DEFAULT_CUR in MTM LOCATION table. || SYSTEM
|-
| MTMIF_DELV_SRV_CLASS_ID || Default value for DELV_SRV_CLASS_ID in MTM LOCATION table. || SYSTEM
|-
| MTMIF_DEL_STOPTM || Default value for DEL_STOPTM in MTM LOCATION table. || SYSTEM
|-
| MTMIF_ITEM_SOURCE || Defines what item information is uploaded to MTM into item_id column, PROD_TYPE, TEMP_COMBO or DU_TYPE || SYSTEM
|-
| MTMIF_LOAD_CLASS_ID || Default value for LOAD_CLASS_ID in MTM LOCATION table. || SYSTEM
|-
| MTMIF_LOAD_TYPE_SOURCE || Defines what Load information is uploaded to MTM into load_type_id column, PROD_TYPE, TEMP_COMBO or DU_TYPE || SYSTEM
|-
| MTMIF_PICK_SRV_CLASS_ID || Default value for PICK_SRV_CLASS_ID in MTM LOCATION table. || SYSTEM
|-
| MTMIF_PRODUCT_SOURCE || Defines what Product information is uploaded to MTM into product_id column, PROD_TYPE or NULL || SYSTEM
|-
| MTMIF_PU_STOPTM || Default value for PU_STOPTM in MTM LOCATION table. || SYSTEM
|-
| MTMIF_SEND_DUS || MTM Interface Send DUs - Y, N or RPE (Y sends DU Qty, RPE sends RPE Qty). || SYSTEM
|-
| MTMIF_SEND_PIECES || MTM Interface Send Pieces - Y, N or RPE (Y sends DU Qty, RPE sends RPE Qty). || SYSTEM
|-
| MTMIF_SEND_VOLUME || MTM Interface Send Volume - Y or N || SYSTEM
|-
| MTMIF_SEND_WEIGHT || MTM Interface Send Weight - Y or N || SYSTEM
|-
| MTMIF_SPLIT_CUBE || Default value for SPLIT_CUBE in MTM LOCATION table. || SYSTEM
|-
| MTMIF_SPLIT_PALLET || Default value for SPLIT_PALLET in MTM LOCATION table. || SYSTEM
|-
| MTMIF_SPLIT_PIECES || Default value for SPLIT_PIECES in MTM LOCATION table. || SYSTEM
|-
| MTMIF_SPLIT_WEIGHT || Default value for SPLIT_WEIGHT in MTM LOCATION table. || SYSTEM
|-
| MTMIF_XDOCK_HANDLING_TIME || Default value for XDOCK_HANDLING_TIME in MTM LOCATION table. || SYSTEM
|-
| MTM_INSTALLED || MTM Installed ? - YES or NO || SYSTEM
|-
| MTM_OPTIMISE_WAIT_TIME || Should wait time incurred at a stop be moved to end of the preceding stop if the latter is an RDC. || SYSTEM
|-
| MTM_PATH || MTM Path || SYSTEM
|-
| MTM_UPDATE_ORDERS || MTM Interface Update Orders - Y or N || SYSTEM
|-
| MTM_VERSION || MTM Version || SYSTEM
|-
| MTS_CSV_EXPORT_PATH || First path that exports looks for when writing a csv to the file system || SYSTEM
|-
| MTS_CSV_EXPORT_PATH_ORS || First path that exports looks for when writing a csv to the file system for ORS || SYSTEM
|-
| MTS_CSV_FTP_PATH || used by EXPORTS Form to set the Client Server FTP Path || SYSTEM
|-
| MTS_CSV_IP_ADDR || CSV IP Address || SYSTEM
|-
| MTS_CSV_LOCAL_PATH || used by EXPORTS Form in Client Server mode - sets where on users PC exports will be written to || SYSTEM
|-
| MTS_CSV_PASSWORD || CSV Password || SYSTEM
|-
| MTS_CSV_USER || CSV User || SYSTEM
|-
| MTS_CSV_WEB_ADDR || CSV Web address || SYSTEM
|-
| MTS_CSV_WEB_PATH || forms part of the URL when generating an export, different value depending on environment || SYSTEM
|-
| MTS_CURRENT_VERSION || MTS Client Server current version || SYSTEM
|-
| MTS_ENABLE_SECURITY || Is Security Enabled - Y or N || SYSTEM
|-
| MTS_EXPORT_PATH || Second path that exports looks for when writing a csv to the file system || SYSTEM
|-
| MTS_FILE_UPLOAD_URL || URL for launching the MTS File Upload || SYSTEM
|-
| MTS_FTP_USER || Mts ftp user to be used within the stand-alone Upload/Import application. || SYSTEM
|-
| MTS_FTP_USER_PWORD || Mts ftp user account password. || SYSTEM
|-
| MTS_FTP_VBAPP_IMPORT_PATH || MTS Import Path for the VB ftp application || SYSTEM
|-
| MTS_IMPORT_PATH || MTS Import Path || SYSTEM
|-
| MTS_IMPORT_VIRTUAL_PATH || MTS Virtual Import Path || SYSTEM
|-
| MTS_INTERFACE || The standard file structure for interfacing || SYSTEM
|-
| MTS_LATEST_REVISION || Latest MTS Version || SYSTEM
|-
| MTS_LOCATION_USAGE || Controls how Locations are grouped, either via CUST_GROUP, CUSTOMER, used in Customer form to display correct tab || SYSTEM
|-
| MTS_LOG_DIR || Path where MTS application error logs are written to || SYSTEM
|-
| MTS_OUTBOUND_ORDER_PATH || File path for Outbound Orders . || SYSTEM
|-
| MTS_PRODUCT_RELEASE || MTS Product RELEASE || SYSTEM
|-
| MTS_PRODUCT_VERSION || MTS Product Version || SYSTEM
|-
| MTS_TRACKING_SYSTEM_1 || Stores the name of one of the tracking systems used in MTS || SYSTEM
|-
| MTS_TRACKING_SYSTEM_2 || Stores the name of one of the tracking systems used in MTS || SYSTEM
|-
| MTS_TRACKING_SYSTEM_3 || TomTom Tracking System || SYSTEM
|-
| MTS_UNQ_DEPOT_DEPARTS || Do departure times need to be unique ? - Y or N || COST_CENTRE
|-
| MTS_WIDE_SCREEN || Should Execution screen de available in Wide Screen || SYSTEM
|-
| NEW_ORDER_CONF || Controls if customers are emailed an order confirmation || COST_CENTRE
|-
| NORTHERN_MANIFEST || Depot Linked to Northern Manifests || SYSTEM
|-
| NO_RECALC_VOL || Controls volume is calculated from the system || COST_CENTRE
|-
| NO_VALID_ORDS_ACPT || When Y -setting trip to Accepted will not call validate order || SYSTEM
|-
| NULL_EXT_REF || Error if external ref is null on manual order || COST_CENTRE
|-
| OBS_BACKGROUND || Background Colour || SYSTEM
|-
| OF_CURRENCY_CODE || Oracle Financial Currency Code || SYSTEM
|-
| OF_FILE_ARCHIVE || Oracle financials archive file path. || SYSTEM
|-
| OF_FILE_NAME_SECTION2 || Stores the name of section 2 on the OF filename || SYSTEM
|-
| OF_FILE_PATH || Oracle financials file path. || SYSTEM
|-
| OF_FTP_DESTINATION_DIRECTORY || Oracle Financials FTP Dir || COST_CENTRE
|-
| OF_FTP_DESTINATION_DIRECTORY || Oracle Financials FTP Dir || SYSTEM
|-
| OF_FTP_DESTINATION_IP_ADDRESS || Oracle Financials FTP IP || SYSTEM
|-
| OF_FTP_DESTINATION_IP_ADDRESS || Oracle Financials FTP IP || COST_CENTRE
|-
| OF_FTP_DESTINATION_PASSWORD || Oracle Financials FTP Password || COST_CENTRE
|-
| OF_FTP_DESTINATION_PASSWORD || Oracle Financials FTP Password || SYSTEM
|-
| OF_FTP_DESTINATION_PORT || Oracle Financials FTP Port || SYSTEM
|-
| OF_FTP_DESTINATION_PORT || Oracle Financials FTP Port || COST_CENTRE
|-
| OF_FTP_DESTINATION_USERNAME || Oracle Financials FTP User || SYSTEM
|-
| OF_FTP_DESTINATION_USERNAME || Oracle Financials FTP User || COST_CENTRE
|-
| OF_FTP_DEST_DTL_DIRECTORY || Cargowise Details directory || COST_CENTRE
|-
| OF_FTP_DEST_DTL_PASSWORD || Cargowise Details password || COST_CENTRE
|-
| OF_FTP_DEST_DTL_USERNAME || Cargowise Details username || COST_CENTRE
|-
| OF_IF_DTL || Oracle Financial IF DTL || SYSTEM
|-
| OF_IF_FTR || Oracle Financial IF FTR || SYSTEM
|-
| OF_IF_HDR || Oracle Financial IF HDR || SYSTEM
|-
| OF_JRNL_ENTRY_SOURCE_NAME || Oracle Financial Journal Entry Source Name || SYSTEM
|-
| OF_ORIGID || Stores the name of ORIGID || SYSTEM
|-
| OF_SECTION2 || Stores the name of section 2 on the OF filename || SYSTEM
|-
| OF_SETTINGS || Controls if Oracle Financial settings are required for 11i and R12 || SYSTEM
|-
| OF_SOURCE_SYSTEM_CODE || Oracle Financial System Code || SYSTEM
|-
| OMS_ACTUALS_MANDATORY || Governs which ACTUAL_QUANTITY fields require mandatory population in Debrief forms. || SYSTEM
|-
| OMS_ADD_ORDER_TO_LOCS || Should orders added to a Trip be added to existing stops based on Location Id - YES or NO || SYSTEM
|-
| OMS_ADD_ORDER_TO_MILK || Allow orders to be added to Milk round Routes || COST_CENTRE
|-
| OMS_ADD_PACKED_LINE || Allow an order to be valid when it contains an order line with a planned qty of zero? (Y/N) || COST_CENTRE
|-
| OMS_ALLOW_DUPL_CUST_REF || This parameter when set will allow the duplicate customer references || SYSTEM
|-
| OMS_ALLOW_MANUAL_SCHEDULE || Display Manual Schedule Flag in orders screen || COST_CENTRE
|-
| OMS_ALTERNATE_REBOOK || Alternative Rebook Functionality || COST_CENTRE
|-
| OMS_AMEND_SVC_FLAGS || OMS_AMEND_SVC_FLAGS || SYSTEM
|-
| OMS_AVG_WEIGHT || Uses average weight to calculate the weight against an order || COST_CENTRE
|-
| OMS_CHANGE_DEL_TYPE || List of Delivery types allowing change || SYSTEM
|-
| OMS_CHECK_CUTOFF || Controls if cut of times for product and du are considered when creating orders || SYSTEM
|-
| OMS_CONSOLIDATE_DUPLICATE_LINES || Enables the consolidation of duplicate order lines during order entry (Y/N). || COST_CENTRE
|-
| OMS_CONSOL_ITEMS || Controls if items are consolidated in order xml || COST_CENTRE
|-
| OMS_CONTACT_TRACKING || To control the use of the order and location contacts for the contacts when they are sent to EPOD and Portal TTM. || SYSTEM
|-
| OMS_CREATE_DUMMY_SOL || Create dummy SOL records for Dunelm || SYSTEM
|-
| OMS_CREATE_POD || Create CSV POD files for the customer? (Y/N) || CUSTOMER
|-
| OMS_CUTOFF_TIME_DEFAULT || Sets the default cut-off time in format HH24:MI for the order time window calculation should a schedule rule not exist for the locations. || SYSTEM
|-
| OMS_DEFAULT_ORDER_CREATION || Controls dates needed when creating Orders in Orders form. ALL, COLLECTION, DELIVERY or STANDARD || SYSTEM
|-
| OMS_DEFAULT_SERVICE_LEVEL || Default service level for the derivation of the time windows for parcel orders. || COST_CENTRE
|-
| OMS_DEFAULT_TEMPLATE_METHOD || Default method for generating orders from order template screen (M for Multiple, S for Single) || SYSTEM
|-
| OMS_DEF_PROD_TYPE || Default Prod Type for Dunelm || SYSTEM
|-
| OMS_EXCLUDE_AUDIT || Exclude changes to field from audit || SYSTEM
|-
| OMS_FOOTPRINT_FOR_VOLUME || Will the footprint of the order line be include in the VOLUME item for the outbound XML file for the despatch units instead of the cubic volume (Y/N)? || COST_CENTRE
|-
| OMS_INCLUDE_X_ITEM_PREFIX || Allow items with a prefix of X to be included in the Load Management screen and Microlise files (Y/N)? || COST_CENTRE
|-
| OMS_INVALID_SAME_LOCS || Set the order status to INVALID when the from and to locations are the same (Y/N) || SYSTEM
|-
| OMS_ITEMS || Generate Item Identifier using OMS reference and count of items || COST_CENTRE
|-
| OMS_ITEM_AKA_DISPLAY || Controls the label on the AKA Code field || COST_CENTRE
|-
| OMS_LEAVE_AS_NEW || To indicate if orders currently at status NEW are to be left at that status after validation other than the paragon interface? (Y/N) || SYSTEM
|-
| OMS_MIC_DEL_DATE || Are MIC files generated when delivery windows are updated || SYSTEM
|-
| OMS_NO_LIFTS || Controls if lifts are included in order xml || COST_CENTRE
|-
| OMS_NO_TRIP_REF_TRG || Do not obtain trip information in order triggers || SYSTEM
|-
| OMS_OFFERED_EARLY_OFFSET || The number of hours (minus) to offset the early collection or delivery time for the order when its booking status is OFFERED. || COST_CENTRE
|-
| OMS_OFFERED_LATE_OFFSET || The number of hours (plus) to offset the late collection or delivery time for the order when its booking status is OFFERED. || COST_CENTRE
|-
| OMS_ORDER_ARCH_DEL_DAYS || Number of days that archived Order Audit messages will be retained for. || SYSTEM
|-
| OMS_ORDER_AUDIT_ARCH_DAYS || Number of days that Order Audit message should be retained in the main table before being archived. || SYSTEM
|-
| OMS_ORDER_ID || Use the OMS Ref for the Order ID || COST_CENTRE
|-
| OMS_RECALC_OH_RPE || Recalculate the planned and packed RPE when an order is validated (Y/N). || COST_CENTRE
|-
| OMS_RESET_AUTO_PROC || Will the auto-processed flags of the order for the scheduling engine be reset when the early delivery date and time is changed? (Y/N) || COST_CENTRE
|-
| OMS_RE_BOOK_STATUS || Controls the status of re-book orders to DEL_FUTILE || SYSTEM
|-
| OMS_SEQ_CTL_ITEM_FORMAT || Add a prefix for the OMS reference for the order items as well as a sequential number (Y/N) || SYSTEM
|-
| OMS_SESSION_EARLY || Earliest arrival offset before the end of the handling time || SYSTEM
|-
| OMS_SESSION_HANDLING || Handling time associated with session collections || SYSTEM
|-
| OMS_SESSION_LATE || Latest arrival offset after the end of the handling time || SYSTEM
|-
| OMS_SESSION_WINDOW || Percentage value used to calculate the collection date and time window for transport orders generated from sessions || SYSTEM
|-
| OMS_SET_DATES || Change Delivery dates on Invalid Back orders || COST_CENTRE
|-
| OMS_SET_DELIVERY_TYPE || Order on/off/not in Schedule || COST_CENTRE
|-
| OMS_STD_ITEMS || Controls if Standard items are auto generated || COST_CENTRE
|-
| OMS_STD_RULE || Schedule rules applied excluding transport mode and delivery types || SYSTEM
|-
| OMS_TAG_TO_ASSET_TYPE || Order types to be validated in TAG to Asset Scanning || SYSTEM
|-
| OMS_TRACK_ITEMS || Indicates if the tracking references will be stored as order items. (Y/N) || CUSTOMER
|-
| OMS_TRACK_ITEMS || Indicates if the tracking references will be stored as order items. (Y/N) || COST_CENTRE
|-
| OMS_UNIQUE_EXT_REF || Controls if imports can load multiple order lines || CUSTOMER
|-
| OMS_UPDATE_SCHEDULE_TO_TRIP || Update the time windows for the orders that exist on a trip when the schedule of the trip is changed in the Planning screen. || SYSTEM
|-
| OMS_VALIDATE_INACTIVE_CODES || To validate orders with error condition for an invalid code for delivery type and service level || SYSTEM
|-
| OMS_VALIDATE_TEMPLATE || Controls whether the Template Id is populated with the associated Lane Id - LANE or NULL || SYSTEM
|-
| OPEN_FTP_DESTINATION_DIRECTORY || OPEN FTP destination Directory || SYSTEM
|-
| OPEN_FTP_DESTINATION_IP_ADDRESS || OPEN FTP destination IP Address || SYSTEM
|-
| OPEN_FTP_DESTINATION_IP_ADDRESS_COPY || OPEN FTP destination IP Address || SYSTEM
|-
| OPEN_FTP_DESTINATION_PASSWORD || OPEN FTP Password || SYSTEM
|-
| OPEN_FTP_DESTINATION_PORT || OPEN FTP destination Port || SYSTEM
|-
| OPEN_FTP_DESTINATION_USERNAME || OPEN FTP Username || SYSTEM
|-
| OP_SYS || Operating system || SYSTEM
|-
| OP_SYS_VER || Operating system version || SYSTEM
|-
| OR3_INTERFACE || Is the PR3 interface active || SYSTEM
|-
| ORDER_SEARCH_CONSOL || Include orders that have passed through a user's SCHED GROUP || SYSTEM
|-
| ORDER_WELL_HIGHLIGHT || Highlight Orders where matching trip found || COST_CENTRE
|-
| ORD_ALLOW_SHIPMENTS || Consolidate Orders on Shipments || COST_CENTRE
|-
| ORD_BOOKING_METHOD || CSV Import - Booking Method -HOME for home delivery, any other value for standard || COST_CENTRE
|-
| ORD_BOOKING_STATUS || Controls if Booking status is displayed || COST_CENTRE
|-
| ORD_CHANGE_BOOKING || Controls if a change to the booking ref is reflected on the payment || COST_CENTRE
|-
| ORD_CHECK_DUPLICATE_ORDERS || For orders where source system is IMPORTS check to see if order is a duplicate - Y or N || SYSTEM
|-
| ORD_CLEAR_DATES || Are dates cleared in the interface || SYSTEM
|-
| ORD_CONF_REPORT || Ord Conf report || COST_CENTRE
|-
| ORD_COPY_ALL_REFS || Are all references copied when items are split? || SYSTEM
|-
| ORD_CREATE_MANIFEST || Controls if a portal manifest record is created for Manual Orders || COST_CENTRE
|-
| ORD_CREATE_PORTAL_ITEM_IDS || Does C-TMS generate the item identifiers for Portal orders || SYSTEM
|-
| ORD_CREATTE_PORTAL_ITEM_IDS || Does C-TMS generate the item identifiers for Portal orders || SYSTEM
|-
| ORD_DEBRIEF_DAYS || Default number of days used to restrict Orders displayed by Order Debrief form. || SYSTEM
|-
| ORD_DEFAULT_AIR || Default Dimensional Weight Factor for Air Transport || SYSTEM
|-
| ORD_DEFAULT_CC || Order Default Cost Centre || SYSTEM
|-
| ORD_DEFAULT_CUST || Order Default Customer || SYSTEM
|-
| ORD_DEFAULT_DEL_TYPE || Order Default Delivery Type || SYSTEM
|-
| ORD_DEFAULT_ROAD || Default Dimensional Weight Factor for Road Transport || SYSTEM
|-
| ORD_DEFAULT_SEND_TO_MTM || Order Default Send to MTM Flag || SYSTEM
|-
| ORD_DEFAULT_SESSION_DU_TYPE || Standard delivery unit used to transport unprocessed blood from sessions || SYSTEM
|-
| ORD_DEFAULT_SESSION_PROD_TYPE || Standard product type used to transport unprocessed blood from sessions || SYSTEM
|-
| ORD_DEFAULT_TRANSCODE || Order Default Trans. Code || SYSTEM
|-
| ORD_DESP2_RESEND || Allow Desp2 message to be resent from orders screen || COST_CENTRE
|-
| ORD_DISPLAY_LIFTS || Display Lifts in preference to quantity || SYSTEM
|-
| ORD_EARLY_COLLECT_THRESHOLD || Number of Hours Early Collection Time can be before the Current Date/Time when creating an Order || SYSTEM
|-
| ORD_EDIT_RPE || Enable the RPE of an order line to be edited? (Y/N) || COST_CENTRE
|-
| ORD_EFFECTIVE_FUEL || Indicates if Fuel charges are fixed or based on effective dates || COST_CENTRE
|-
| ORD_END_TIME || The default late delivery time when a route is not provided for an API order (HH:MM) || SYSTEM
|-
| ORD_ENHANCED_REBOOK || Controls which rebook screen is displayed in the orders form || COST_CENTRE
|-
| ORD_EQUIPMENT_LOAD || Controls if equipment & equipment times are validated || SYSTEM
|-
| ORD_FIXED_SCHEDULE_CHECK || Check for existing fixed schedule generated orders || CUSTOMER
|-
| ORD_FUTURE_LIMIT_DAYS || Maximum Number of days in the future that an order can be created || SYSTEM
|-
| ORD_FUTURE_OFFSET || How far in the future can order offset be set || COST_CENTRE
|-
| ORD_IGNORE_LINE || Are some order lines ignored in the interface || SYSTEM
|-
| ORD_JUST_IN_TIME || Is the collection window set just in time || CUSTOMER
|-
| ORD_LATE_TIME || Late time windows for generated stack orders || SYSTEM
|-
| ORD_LINE_LENGTH || Store LENGTH i/o FOOTPRINT || COST_CENTRE
|-
| ORD_LINE_METHOD || Line Qty Calc Method || COST_CENTRE
|-
| ORD_LINK_CONTENTS || Link Items and contents in the interface || SYSTEM
|-
| ORD_NO_DEL_FOR_FAILS || Controls if DEL messages are generated for FAILED orders - Y to prevent, C to send as CAN || COST_CENTRE
|-
| ORD_OMIT_PACK_SCHEDULING || Omit the scheduling of the order and only print the label when pack confirming. || COST_CENTRE
|-
| ORD_ON_SCHED_DEL_LOC || Du category to be assessed for exclusion from parcel scheduling || CUSTOMER
|-
| ORD_POSTCODE_SEARCH || Determines whether he user can search for order addresses via a postcode (Y/N). || SYSTEM
|-
| ORD_PROCESSED_MSG || Ord Conf Processed Email Msg || COST_CENTRE
|-
| ORD_PROCESSED_SUBJECT || Ord Conf Processed Subject || COST_CENTRE
|-
| ORD_QUANTITY_DU_FIELDS_FORMAT_MASK || Default quantity and pallet fields format mask || SYSTEM
|-
| ORD_QUANTITY_PALLET_FIELDS_FORMAT_MASK || Default quantity and pallet fields format mask || SYSTEM
|-
| ORD_RBO_PREFIX || Is the rebook prefix stripped for LOTS? || SYSTEM
|-
| ORD_REASON_CODE_FILTER || Order Reason Code Filter || SYSTEM
|-
| ORD_REASON_SUP || Reason codes to be supressed in the web service || COST_CENTRE
|-
| ORD_RECEIVED_MSG || Ord Conf Received Email Msg || COST_CENTRE
|-
| ORD_RECEIVED_SUBJECT || Ord Conf Received Subject || COST_CENTRE
|-
| ORD_REMOVE_CANC || Controls if Orders Cancelled in C-TMS generate REM message to LOTS || COST_CENTRE
|-
| ORD_REPRINT_PACK_VISIBLE || Determines whether the Reprint Labels and Pack Confirm buttons are visible. (Y/N). || SYSTEM
|-
| ORD_RETAIN_PLANNED || Planned weight is retained on lines || COST_CENTRE
|-
| ORD_RPE_LM_FACTOR || The factor for loading meters to calculate the RPE of the orders. || COST_CENTRE
|-
| ORD_SET_BUSINESS_TYPE || Set Business Type on Orders || COST_CENTRE
|-
| ORD_SET_SERVICE || Controls if the service level is set to match the delivery type || SYSTEM
|-
| ORD_SPLIT_ALL_REFS || Are all references copied when items are split? || SYSTEM
|-
| ORD_SPLIT_REBOOK_ITEMS || Controls if items on the original order suffixed with X when the order is re-booked || COST_CENTRE
|-
| ORD_SPLI_ALL_REFS || Are all references copied when items are split? || SYSTEM
|-
| ORD_STACK_DEBRIEF || Order Stack Debrief || COST_CENTRE
|-
| ORD_START_TIME || The default early delivery time when a route is not provided for an API order (HH:MM) || SYSTEM
|-
| ORD_TARGET_SEND_TO_MTM || Order Target Send to MTM - Y or N || SYSTEM
|-
| ORD_TEMPERATURE_COMBO || Use Temperature Combo to determine if the customer reference should be highlighted. || COST_CENTRE
|-
| ORD_TEMPLATE_EDIT_UPDATE || Controls whether the user can edit the order template data during generation (Y/N). || SYSTEM
|-
| ORD_UNSCHEDULE_FAILS || Controls if Orders Cancelled in EPOD generate a CANC message to LOTS || COST_CENTRE
|-
| ORD_UNSCHED_COMP || Controls if Orders with 0 qty delivered be unscheduled from COMPLETED trips? || COST_CENTRE
|-
| ORD_UPDATE_LATE_COLL_DATE_TO_DEL || Controls if the Late Collection Date/Time is updated at Save to Match the Late Delivery Date/Time. || SYSTEM
|-
| ORD_VALIDATE_GROUP_NAME || Validate Group Name during order entry || COST_CENTRE
|-
| ORD_WRITE_NOTES || Write Order Notes. || SYSTEM
|-
| ORD_XDOCK_LOTS_DEL_MSG || Lots DEL msg is only sent on last trip for xdock orders (Y/N) || SYSTEM
|-
| ORS_DELIMITER || Oracle reporting suite data field delimiter || SYSTEM
|-
| ORS_SUMMARY || Allow the summarisation OF ORS reports || SYSTEM
|-
| ORS_TYPE_DEF_GROUP_BY || List of the ORS types to default group by fields || SYSTEM
|-
| ORS_TYPE_EXC_GROUP || Exclude ORS types from grouping fields || SYSTEM
|-
| OST_DEBRIEF_WARNING_DAYS || Number of days prior to current date for which orders not debriefed will included in warning message in Order Tracking form. || SYSTEM
|-
| OUTBOUND_3 || File path for Outbound Trips. || SYSTEM
|-
| P2 || users || SYSTEM
|-
| PALLET_BASED_RATING || Rate based on chargeable/non chargeable pallets || CUSTOMER
|-
| PARAGON_IMPORT_LAYOUT || Paragon Import Layout || COST_CENTRE
|-
| PARAGON_INSTALLED || Paragon Installed ? - YES or NO. Only one of MTM_INSTALLED or PARAGON_INSTALLED should be set to YES. || SYSTEM
|-
| PARAGON_INSTALLED || Paragon Installed ? - YES or NO. Only one of MTM_INSTALLED or PARAGON_INSTALLED should be set to YES. || COST_CENTRE
|-
| PARAGON_RUNNING || Paragon Import is currently running (to stop outbound XML jobs) || SYSTEM
|-
| PARAGON_SCHED_DAYS || Determines how many days back paragon should extract records || COST_CENTRE
|-
| PAR_ALLOW_IMPORT_UNDO || Used to indicate if the UNDO button is allowed to be pressed on the Paragon Trip Import? (Y/N) || COST_CENTRE
|-
| PAR_API || Create Control records for Paragon API || SYSTEM
|-
| PAR_AUDIT || Include auditing of the import process in the STP version of the Paragon API (Y/N) || SYSTEM
|-
| PAR_AUTO_RESET_NEW || Auto reset orders at status New after paragon run || COST_CENTRE
|-
| PAR_CHECKSUM_OFF || To indicate if the checksum validation code is required for paragon imports? (Y/N) || SYSTEM
|-
| PAR_DISPLAY_IMPORT_DETAILS || Used to indicate whether the additional message containing the imported details is displayed or not on the Paragon Trip Import? (Y/N) || COST_CENTRE
|-
| PAR_DUN_COL_END_OFFSET || Offset for Dunelm collection end time || SYSTEM
|-
| PAR_DUN_COL_START_OFFSET || Offset for Dunelm collection start time || SYSTEM
|-
| PAR_DUN_TRUNK_CUTOFF_TIME || Set a cut-off time in format HH24:MI to apply to trunk trips to use the current schedule for the day. || SYSTEM
|-
| PAR_DUN_TRUNK_OFFSET_DAYS || Set a number of days to assess the trunk trips for the DUN radial trips. || SYSTEM
|-
| PAR_ENDPOINT_URL || URL for paragon API || SYSTEM
|-
| PAR_EXPORT_FORECAST || Send forecast values to Paragon || COST_CENTRE
|-
| PAR_FREQUENCY || Frequency for PAR Master keys || SYSTEM
|-
| PAR_FTP_DESTINATION_DIRECTORY || Directory for FTP of Paragon Files || SYSTEM
|-
| PAR_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Paragon Files || SYSTEM
|-
| PAR_FTP_DESTINATION_IP_ADDRESS_OLD || IP for FTP of Paragon Files || SYSTEM
|-
| PAR_FTP_DESTINATION_PASSWORD || Password for FTP of Paragon Files || SYSTEM
|-
| PAR_FTP_DESTINATION_PORT || Port for FTP of Paragon Files || SYSTEM
|-
| PAR_FTP_DESTINATION_USERNAME || Username for FTP of Paragon Files || SYSTEM
|-
| PAR_GROUP_STAGING || Paragon Group Staging Level || SYSTEM
|-
| PAR_INBOUND_ARCH || Path for Paragon XML archiving || SYSTEM
|-
| PAR_INBOUND_FAIL || Path for Paragon XML failures || SYSTEM
|-
| PAR_INBOUND_IDENTIFIER || Pattern for Paragon Trip Inbound XML || SYSTEM
|-
| PAR_INBOUND_LISTING_NAME || Filename for list of files in directory for Paragon XML trip Inbound || SYSTEM
|-
| PAR_INBOUND_PATH || Path for yet to be processed XML files from Paragon || SYSTEM
|-
| PAR_INT_SCREEN_CLASSIC_LAYOUT || Removes/Renames fields in PAR_INT to traditional C-TMS system setup rather than those changed for industrial || SYSTEM
|-
| PAR_KEY_FORMAT || PAR Master key format WKXX, DDMM, DAYX || SYSTEM
|-
| PAR_KEY_PROJECT || PAR Project name || SYSTEM
|-
| PAR_LISTING_SCRIPT_NAME || Script name foe Paragon XML Trip Inbound || SYSTEM
|-
| PAR_OUTBOUND_ARCH || Path for archiving outbound Paragon XML interfaces || SYSTEM
|-
| PAR_OUTBOUND_FAIL || Path for failing outbound Paragon XML interfaces || SYSTEM
|-
| PAR_OUTBOUND_PATH || Path for outbound Paragon XML interfaces || SYSTEM
|-
| PAR_PLAN_DIRECT || Controls if Paragon will plan direct collections (Not to owning depot) || COST_CENTRE
|-
| PAR_PROXY || Paragon Proxy Server || SYSTEM
|-
| PAR_RUN_NUMBER || Is Paragon Planning based on Run Numbers? || SYSTEM
|-
| PAR_SEND_ALL_LOCATIONS || Are locations sent out via API || SYSTEM
|-
| PAR_SET_ALL_FROM_NEW || Should all orders and trips set as NEW be updated after Paragon Run || SYSTEM
|-
| PAR_SHUNT_TRUNK || Check if the shunt and trunk routing has been completed prior to exporting to Paragon (Y/N). || SYSTEM
|-
| PAR_SLOT_CUTOFF_TIME || Number of minutes before slot window start that it closes to new orders || SYSTEM
|-
| PAR_START_DATE || Start Date for Master Keys || SYSTEM
|-
| PAR_TENNANT || Tennant for paragon API || SYSTEM
|-
| PAR_TENNANT_KEY1 || Tennant KEY 1 for paragon API || SYSTEM
|-
| PAR_TENNANT_KEY2 || Tennant KEY 2 for paragon API || SYSTEM
|-
| PAR_TRIP_STATUS || Controls the status of any Trips that are created via the Paragon Interface. || SYSTEM
|-
| PAR_TRUNK_THRESHOLD_UOM || Controls the order qty measure used as a threshold when assigning orders to Trunk trips in the Paragon Import. Values are WEIGHT, RPE or VOLUME. || COST_CENTRE
|-
| PAR_TRUNK_TRIP || Are trunk trips generated from Paragon Plan || SYSTEM
|-
| PAR_USE_LOC || Paragon Use From location of order s depot || SYSTEM
|-
| PAR_USE_RPOXY || Paragon Use Proxy || SYSTEM
|-
| PAR_USE_SLOTS || Use slots when exporting to Paragon (DUN format) || SYSTEM
|-
| PAR_VIRTUAL_OUT_ARCH || Path for webshow of archiving outbound Paragon XML interfaces || SYSTEM
|-
| PAR_VIRTUAL_OUT_FAIL || Path for webshow of failing outbound Paragon XML interfaces || SYSTEM
|-
| PAR_XML_OLD_ORDERS || Number of days in the past to still be included for sending orders to paragon || SYSTEM
|-
| PERCENTAGE_MARGIN || Percentage Margin Value || SYSTEM
|-
| PETAL_STARTS_AT_ANY_DEPOT || Does a Petal start at a Depot ? || SYSTEM
|-
| PLANNING_AUTO_SCHED_INACTIVE_DEPOTS || List the inactive depots by commas and in single quotes to exclude their orders in the Planning screen. || SYSTEM
|-
| PLAN_REG_COUNTRY || Planning Region Country suffix || COST_CENTRE
|-
| POLAR_CUST_REF || Controls the source of cust ref in Polar Speed labels || CUSTOMER
|-
| POM_DATE_END || Number of days after Purchase Order dates || SYSTEM
|-
| POM_DATE_START || Number of days before Purchase Order dates || SYSTEM
|-
| POM_DEF_COST || Default Cost Centre for PO || SYSTEM
|-
| POM_DEF_CUST || Default Customer for PO || SYSTEM
|-
| POM_DEF_PROD_TYPE || Default Product Type for PO || SYSTEM
|-
| POM_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header || SYSTEM
|-
| POM_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header || SYSTEM
|-
| POM_INBOUND_PATH || Path for yet to be processed XML files || SYSTEM
|-
| POM_OUTBOUND_ARCH || Path for processed POM outbound XML files that have successfully completed processing || SYSTEM
|-
| POM_OUTBOUND_PATH || Path for PO outbound files || SYSTEM
|-
| PORSCHE_DOT_CODE || Tyre Age for PORSCHE || SYSTEM
|-
| PORTAL_AUTO_SCHED_RET_DAYS || Day range for auto allocation of return orders || SYSTEM
|-
| PORTAL_DEF_DEL_TYPE || Delivery Type for Return orders || SYSTEM
|-
| PORTAL_ORDERS || Portal Imports available || SYSTEM
|-
| POSTAL_STRINGS_TOWN || Is town compared in postal string zones || SYSTEM
|-
| POSTCODE_SHIPMENTS || Indicates if shipments are postcode based || COST_CENTRE
|-
| PO_OVERRIDE_DU_WITH_SUB || A comma-separated list of transit DU types for which the sub-transit DU type will be used instead to generate order lines for the PO || SYSTEM
|-
| PRD_ITEM_IMPORT_FILE || Name of Product Item Import file || SYSTEM
|-
| PRD_ITEM_IMPORT_PATH || Product Item Import path || SYSTEM
|-
| PREVENT_ORD_COL_AFTER_DEL || Stop any ORD or COL messages after a DEL message || COST_CENTRE
|-
| PRINT_ACCEPTED_LABEL || Controls if customer labels are printed when trip is Accepted || COST_CENTRE
|-
| PRINT_INBOUND_LABELS || Controls if labels are generated for inbound xml orders || SYSTEM
|-
| PRINT_LABEL || Controls if customer labels may be reprinted from Order screen || COST_CENTRE
|-
| PRINT_LABEL_PATH || File path for Parcel Carrier Labels to be printed || SYSTEM
|-
| PROJECT_LOCATIONS || Indicates which prefixes are used for project location ids || COST_CENTRE
|-
| PTV_RO_ARCH_DIR || Folder for archive of PTV RO files || SYSTEM
|-
| PTV_RO_AUTO || PTV Automatic Response from Import || SYSTEM
|-
| PTV_RO_DEL_PRIORITY_DAYS || Number of days before late delivery when prioritized in Route Optimiser || SYSTEM
|-
| PTV_RO_DIR || Folder for PTV RO files || SYSTEM
|-
| PTV_RO_EXTEND || PTV plan covers more than 1 week || SYSTEM
|-
| PTV_RO_FILE_API || Create File or send data via API || SYSTEM
|-
| PTV_RO_FIX_MINUS1 || Reduce fix time by 1 when sending to PTV RO || SYSTEM
|-
| PTV_RO_GROUP_NAME || Select PTV unscheduled orders by group name rather than depot || SYSTEM
|-
| PTV_RO_MASTER_PROFILE || Profile for PTV RO webservice || SYSTEM
|-
| PTV_RO_MASTER_PROFILE_DEPOT || Profile for PTV RO webservice || SYSTEM
|-
| PTV_RO_ORDER_PAIRS || PTV Send load and unload tasks combined || SYSTEM
|-
| PTV_RO_ORD_FUTURE_DAYS || PTV Orders Future Days || SYSTEM
|-
| PTV_RO_ORD_HISTORIC_DAYS || PTV Orders Historic Days || SYSTEM
|-
| PTV_RO_PASSWORD || Password for PTV RO webservice || SYSTEM
|-
| PTV_RO_PASSWORD_BETA || Password for PTV RO webservice || SYSTEM
|-
| PTV_RO_PROFILE || Profile for PTV RO webservice || SYSTEM
|-
| PTV_RO_PROFILE_DEPOT_SCHED || Profile for PTV RO webservice || SYSTEM
|-
| PTV_RO_PROJECT || Project for PTV RO webservice || SYSTEM
|-
| PTV_RO_PROXY || Proxy server name for PTV RO webservice || SYSTEM
|-
| PTV_RO_SEND_RETRO || Send retro orders || SYSTEM
|-
| PTV_RO_SET_ROUTE || Set route code on trips from PTV RO || SYSTEM
|-
| PTV_RO_SPLIT || PTV imported route returns to Start Depot || SYSTEM
|-
| PTV_RO_TIMEOUT || Timeout for PTV RO webservice || SYSTEM
|-
| PTV_RO_TRIPS_HISTORIC_DAYS || PTV Trips Historic Days || SYSTEM
|-
| PTV_RO_TRIP_FUTURE_DAYS || PTV Trips Future Days || SYSTEM
|-
| PTV_RO_URL || URL for PTV RO webservice || SYSTEM
|-
| PTV_RO_URL_BETA || URL for PTV RO webservice || SYSTEM
|-
| PTV_RO_URL_NHS || URL for PTV RO webservice || SYSTEM
|-
| PTV_RO_USERNAME || Username for PTV RO webservice || SYSTEM
|-
| PTV_RO_USERNAME_BETA || Username for PTV RO webservice || SYSTEM
|-
| PTV_RO_USERNAME_NHS || Username for PTV RO webservice || SYSTEM
|-
| PTV_RO_WAIT_TIMEOUT || Timeout for PTV RO webservice Response || SYSTEM
|-
| RADIO_DU || Radio active || COST_CENTRE
|-
| RDT_441_CHECK_DAYS || Set a number of days in which to assess the prior loading messages for WCS. || SYSTEM
|-
| REBOOK_ALT_STATUS || If set to Y when an order is rebooked the original orders status will not be changed || SYSTEM
|-
| REBOOK_COPY_SUB_REF_CONTACTS || Set as Y or N to copy Sub References on Rebook, contact details only i.e. SMS and Email details || COST_CENTRE
|-
| RECORD_LIMIT || Limitation of records to display on Customer Service Screen || SYSTEM
|-
| REFRESH_WHEN_CLOSE_ORDER_DETAILS || Refresh the order summary screen when you close the order details page in the Orders form || SYSTEM
|-
| REPORT_CONNECT_STRING || Report auto production - connect string (user/pass@database). || SYSTEM
|-
| REPORT_DIRECTORY || Report auto production - place report in directory. || SYSTEM
|-
| REPORT_FLOC || Report auto production - name of FLOC directory for reports. || SYSTEM
|-
| REPORT_IP_ADDRESS || Report auto production - IP address server. || SYSTEM
|-
| REPORT_PORT || Report auto production - Port || SYSTEM
|-
| REPORT_SERVER || Report auto production - name of report server. || SYSTEM
|-
| REP_DELIVERY_DOCS || Name of the Delivery report printed from trip tree || COST_CENTRE
|-
| REP_JAVA_PDF || Java Report Controller Script || SYSTEM
|-
| REP_JAVA_PDF_DIR || Java Report Folder || SYSTEM
|-
| REP_JAVA_PDF_SHOW || Java Report Webshow Folder || SYSTEM
|-
| REP_LOADING || Name of the loading report printed from trip tree || COST_CENTRE
|-
| REP_ORARRP_DEST_FILEPATH || Reports Destination Filepath || SYSTEM
|-
| REP_ORD_EXTRACT_DAYS || Number of days that the order extract can be run for || SYSTEM
|-
| REP_PDF_DEST_FILEPATH || Reports PDF File Path || SYSTEM
|-
| REP_PDF_FILE_LOC || Reports PDF file location || SYSTEM
|-
| REP_PDF_WEB_DEST_NAME || Reports PDF destination || SYSTEM
|-
| REP_PDF_WEB_SERVER_NAME || Reports PDF Wed Server Name || SYSTEM
|-
| REP_PDF_WEB_SERVER_URL || Reports PDF Web Server URL || SYSTEM
|-
| REP_SERVER_WEB || Reports Server || SYSTEM
|-
| REP_SHOW_CARRIER || Controls if Carrier id is included in the Unsched Orders report || SYSTEM
|-
| REP_SO_REF_FORMAT || Set as 1 or 0 to reformat Order Reference, extract all characters up to the first '-' or '_' || COST_CENTRE
|-
| REP_WEB_SERVER_NAME || Reports Web Server name || SYSTEM
|-
| REP_WEB_SERVER_URL || Reports Server URL || SYSTEM
|-
| RESEND_EFX_STATUS || Can users resend EFX at status Accepted and En-route || COST_CENTRE
|-
| RESOURCE_DIARY || Resource Diary for display of trip allocation || SYSTEM
|-
| RES_ALTERNATIVE_CARRIER || During MTM sync, if Carrier does not exist should MTS check for alternative carrier ? - Y or N || SYSTEM
|-
| RES_ALT_CARRIER || Controls access to Alternate carriers button on Resource form, these are used in TRIPSUM_JRL. - Y or N || SYSTEM
|-
| RES_AVAILABILITY_ALLOC || Determines how resources are allocated to a trip || COST_CENTRE
|-
| RES_CONTROL_ALLOC_RESOURCE || Controls whether a resource can be assigned to more than one Carrier / Carrier Group || SYSTEM
|-
| RES_DT_FUEL_UNITS || Current fuel unit - Litres or Gallons || SYSTEM
|-
| RES_EXTERNAL_DRIVER || Use External Drivers || SYSTEM
|-
| RES_TRACKING_SYSTEM_DISPLAYED || Null, Tractor, Trailer or Both to indicate if Tracking systems are enabled. || SYSTEM
|-
| RETAIN_INTERFACE_ERRORS || Number of days Interface Errors are retained || COST_CENTRE
|-
| RE_PLAN_ORDERS || Controls if the Planner splits order for planning || SYSTEM
|-
| RE_SEQUENCE_STOPS || Are trip stops validate || COST_CENTRE
|-
| RHA_INDEXES || Use RHA indexes || SYSTEM
|-
| RICO_ACCOUNT || Rico Account login to Star-Gate || SYSTEM
|-
| RICO_OUT_ARCH || Outbound archive folder for Rico XML files || SYSTEM
|-
| RICO_OUT_DIR || Outbound folder for Rico XML files || SYSTEM
|-
| RTE_CHECK_MISSING_STOPS || Determines which stops must be present on a Trip, either HIGHEST_OPTIONAL or ALL. || SYSTEM
|-
| RTE_DEF_CAPACITY_MEASURE || Fixed Routes, default capacity measure (RPE, WEIGHT or VOLUME) || SYSTEM
|-
| RTE_DISBAND_SEMI_HOURS || Sets the number of hours prior to departure when a SEMI_FIXED Trip should be disbanded || SYSTEM
|-
| RTE_LOG_DEL_DAYS || Number of days that Fixed Routes log messages should be kept for || SYSTEM
|-
| RTE_MAINT_RDC_ALL_USAGE || Allow the values for the fixed route locations to include an RDC location when the depot has not been assigned to a customer or a customer group (Y/N) || SYSTEM
|-
| RTE_ORDERS_ASC_OR_DESC || Should orders be orders in Ascending or Descending order (ASC or DESC) || SYSTEM
|-
| RTE_PLAN_BY_REGION || Allow Fixed Routes to plan by Postal Region or Planning Region, values are PL and PO. || SYSTEM
|-
| RTE_PRIORITISE_URG_LATE_ORDS || Controls whether urgent and late orders are to prioritised in the Fixed Route process. || SYSTEM
|-
| RTE_REGION_AND_ZONE || Will fixed routes crossdock by planning region and location zone? (Y/N) || SYSTEM
|-
| RTE_SCHED_OFFSET_HRS || Fixed Routes Schedule Offset in hours || SYSTEM
|-
| RTE_SEMI_FIXED_CAPACITY || Determines whether capacity is checked by FILL or TRAILER capacity. || SYSTEM
|-
| RTE_SEMI_FIXED_FUNCTION || Should trips go to SEMI_FIXED if they are not optimum, Y or N. || SYSTEM
|-
| RTE_STOPOVER_MINS || Default number of minutes for a stopover for the network route. || COST_CENTRE
|-
| RTE_TRIPS_DEL_DAYS || Fixed Route RTE Trips in status DELETED on schedules older than this value will be deleted || SYSTEM
|-
| RTE_TRIPS_FIN_STATUS || Fixed Routes final status || SYSTEM
|-
| RTE_TRIPS_TO_ACCEPTED || Defines if ACCEPTED or PLANNED Trips are deleted in Rev TI, if yes then ACCEPTED, otherwise PLANNED - Y or N || SYSTEM
|-
| RTE_USE_CROSSDOCK || Should Fixed Routes allow crossdocks to be used. || SYSTEM
|-
| SALES_EXPORT || Payments are to be exported || SYSTEM
|-
| SAP_DEFAULT_DU_QTY || Default DU Quantity for bookings received via the SAP Interface. || SYSTEM
|-
| SAP_DEFAULT_DU_TYPE || Default DU Type for bookings received via the SAP Interface. || SYSTEM
|-
| SAP_DEFAULT_PROD_TYPE || Default Product Type for bookings received via the SAP Interface. || SYSTEM
|-
| SAP_POD_MSG_RQD || Is SAP (POD) Messages Required to be Extracted out of MTS - Y or N. || SYSTEM
|-
| SCHEDULE_RULES_SERVICE || Is service level displayed in schedule rules || COST_CENTRE
|-
| SCHED_ENG_DEL_OFFSET || The number of days that the order will remain in the delivery depot before it can be assigned to its delivery trip || COST_CENTRE
|-
| SCHED_ENG_DEL_OFFSET_CUTOFF || The cut off time at the delivery depot before an order can be assigned to its delivery trip || COST_CENTRE
|-
| SCHED_ENG_EXC_DU_CATEGORY || Du category to be EXCLUDED from parcel scheduling || CUSTOMER
|-
| SCHED_ENG_PART_PLAN || Will the network scheduling engine allow orders to be partially planned?(Y/N) || COST_CENTRE
|-
| SCHED_EXC_SI || Exclude order with special instructions from engine || COST_CENTRE
|-
| SCHED_RULE_SHOW_ZONE || Display zones instead of master location on delivery schedules in Sched Rules form || SYSTEM
|-
| SCH_CSCS_EST_IMPORT_FILE || Name of CSCS Estimate Import file || SYSTEM
|-
| SCH_CSCS_FC_IMPORT_FILE || Name of CSCS Forecast Import file || SYSTEM
|-
| SCH_CSCS_IMPORT_PATH || CSCS Import path || SYSTEM
|-
| SCH_DEFAULT_FIXED_TEMPLATE || Default Fixed Template Name for Auto Generation || SYSTEM
|-
| SCH_DELETE_PROD_QUANT_DURATION || Number of days worth or Product Quantity data that gets deleted. || SYSTEM
|-
| SCH_MANUAL_CREATE_SCHED || Ability to manually create schedules - Y or N || SYSTEM
|-
| SCH_NAME_FORMAT || Schedule Name Format || SYSTEM
|-
| SCH_RECORD_ITEM_DU_USE || Determine whether to update avg used flag and DU data on product quantity. This might be switched off to improve performance - Y or N || SYSTEM
|-
| SCH_SCHEDULE_ADV_DAYS || Determines how many days in advance to generate fixed routes Schedule || SYSTEM
|-
| SCH_SCHED_DATE_RANGE || Range in days for displaying schedules || SYSTEM
|-
| SCH_SCHED_DURATION || Schedule Duration (Days) || SYSTEM
|-
| SCH_SCHED_ORD_DERIVE || Controls the Order Schedule Date. Acceptable values ECDT, LCDT, EDDT, LDDT. || SYSTEM
|-
| SCH_SCHED_ORD_IMP_IGGESUND_SCHED_DATE_OVERRIDE || When Importing IGGESUND data, can the sched_date be over-written by the SCH_SCHED_ORD_DERIVE rule? || SYSTEM
|-
| SCH_SCHED_ORD_IMP_TI_ORDER_SCHED_DATE_OVERRIDE || When Importing TI_ORDER data, can the sched_date be over-written by the SCH_SCHED_ORD_DERIVE rule? || SYSTEM
|-
| SCH_SCHED_START || Schedule Start time || SYSTEM
|-
| SCH_TRIP_ID_DEPOT || Controls if Trip ID is derived from Owning Depot || SYSTEM
|-
| SCH_TRIP_ID_FMT || SCH Trip Id FMT || SYSTEM
|-
| SCH_TRIP_ID_PREFIX || Prefix for Depot based Trip ID || SYSTEM
|-
| SCH_VLS_IMPORT_FILE || Name of VLS Import File || SYSTEM
|-
| SCH_VLS_IMPORT_PATH || VLS Import Path || SYSTEM
|-
| SCR_CURRENT_HIGHLIGHT_COLOUR || Controls colour of highlighted rows in tables || SYSTEM
|-
| SCR_HEADER_BKG_COLOUR || Colour for header toolbars on forms || SYSTEM
|-
| SCR_HEADER_BMP_PATH || Location of BMP to control the colour of the toolbar/header in forms. Leave a trailing slash. || SYSTEM
|-
| SCR_HEADER_TEXT_COLOUR || Colour of text in header toolbars on forms || SYSTEM
|-
| SEC_GROUP_OR_BASEDAT || Security - Lock Monitor, display Group or Based at || SYSTEM
|-
| SEND_CAN_WITHOUT_BOOKING || Allow CAN message to be sent without Booking Ref || SYSTEM
|-
| SEND_INTERFACE_FAIL_EMAIL || Send email for interface errors || COST_CENTRE
|-
| SEND_LINE_ITEM_TO_LOTS || Send Line Item To LOTS. Y - send both Order Line (D) and Item (S) records. N - Checks for Items and, if there are any, sends Item (S) records, else Order Line (D) records. || SYSTEM
|-
| SEND_MANF_TO_SUPP || Indicates if the supplier manifest report will be automatically generated when a trip is accepted for the cost centre of the trip being collected. || COST_CENTRE
|-
| SEND_MANF_TO_SUPP || Indicates if the supplier manifest report will be automatically generated when a trip is accepted for the cost centre of the trip being collected. || CUSTOMER
|-
| SEND_MIL_MESSAGES || Send Tracking Milestone Messages || CUSTOMER
|-
| SEND_PALLET_ID_XML || Send Pallet ID tag in xml || COST_CENTRE
|-
| SEND_SCP_MESSAGES || Send Supplier Collection Messages || CUSTOMER
|-
| SEND_SMS_EMAIL || Controls whether a SMS or an e-mail may be sent to the recipient of the order being delivered on the trip (Y/N). || COST_CENTRE
|-
| SEND_SMS_EMAIL_OLD || Controls whether a SMS or an e-mail may be sent to the recipient of the order being delivered on the trip (Y/N). || COST_CENTRE
|-
| SEND_TO_ISOTRAK || Send to ISOTRAK - ALL or NONE. || SYSTEM
|-
| SERVICES || Controls if service payments are generated || COST_CENTRE
|-
| SESSION_DEFAULT_LOAD_RATE || Session Default Load rate || COST_CENTRE
|-
| SESSION_DEFAULT_UNLOAD_RATE || Session Default Unload rate || COST_CENTRE
|-
| SET_FAST_ORD_WINDOWS || Call fast order windows in Import || SYSTEM
|-
| SET_MICROLISE_SLOTS || Determines if the delivery slot times are sent to Microlise instead of the planned delivery times. || SYSTEM
|-
| SET_TRUNKS_ACCEPTED || Are Trunk trips automatically set to ACCEPTED status? || SYSTEM
|-
| SFTP_LOG_LEVEL || SFTP Log level - numeric 0-3 || SYSTEM
|-
| SHA_EXCLUDE_AUDIT || Activity types that will be excluded from writing audit log records when they are activated. || SYSTEM
|-
| SHIFT_ADDITIONAL_HOURS || Threshold for charging additional shift hours || COST_CENTRE
|-
| SHIFT_DISTANCE || Shift Distance || COST_CENTRE
|-
| SHIPMENT_NO_QTY_RATING || Indicates if a shipment can be rated without quantities || COST_CENTRE
|-
| SHIPMENT_VOLUME || Maximum shipment volume || SYSTEM
|-
| SHIPMENT_WEIGHT || Maximum shipment weight || SYSTEM
|-
| SHOW_CAPPED_TONNAGE || Display Capped Tonnage Details || SYSTEM
|-
| SHOW_CARRIER_NAME || Is carrier name shown on Planning screen? || SYSTEM
|-
| SHOW_CONTACT || Show contact name and number on labels. || COST_CENTRE
|-
| SHOW_FULL_ADDRESS || Show full delivery address on labels. || COST_CENTRE
|-
| SHOW_SCANNED_ITEMS_BTN || Display Scanned Items Update Button || SYSTEM
|-
| SLOT_DFLT_TRAILER_TYPE || Default Trailer Type for Slots || SYSTEM
|-
| SLOT_EXP_DIR || Slot Export - FTP to directory || SYSTEM
|-
| SLOT_EXP_IP || Slot Export - FTP to IP address || SYSTEM
|-
| SLOT_EXP_LOGIN || Slot Export - FTP using login || SYSTEM
|-
| SLOT_EXP_PORT || Slot Export - FTP to Port || SYSTEM
|-
| SLOT_INC_ADD_CORE_TYPES || Set to Y if Slot are to be defined as type CORE or ADDITIONAL || SYSTEM
|-
| SMA_ALLOW_CREATE_ORDERS || Allow orders to be created || SYSTEM
|-
| SMA_FTP_DESTINATION_DIRECTORY || Directory for FTP of Smartphone Files || SYSTEM
|-
| SMA_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Smartphone Files || SYSTEM
|-
| SMA_FTP_DESTINATION_PASSWORD || Password for FTP of Smartphone Files || SYSTEM
|-
| SMA_FTP_DESTINATION_PORT || Port for FTP of Smartphone Files || SYSTEM
|-
| SMA_FTP_DESTINATION_USERNAME || Username for FTP of Smartphone Files || SYSTEM
|-
| SMA_INBOUND_ARCH || Path for Smartphone XML archiving || SYSTEM
|-
| SMA_INBOUND_FAIL || Path for Smartphone XML failure || SYSTEM
|-
| SMA_INBOUND_IDENTIFIER || Pattern for SMA Trip inbound XML || SYSTEM
|-
| SMA_INBOUND_LISTING_NAME || Filename for list of files in directory for SMA XML trip inbound || SYSTEM
|-
| SMA_INBOUND_PATH || Path for yet to be processed XML files from Smartphone || SYSTEM
|-
| SMA_LISTING_SCRIPT_NAME || Script name for SMA XML Trip inbound || SYSTEM
|-
| SMA_OUTBOUND_ARCH || Path for archiving outbound Smartphone XML interface || SYSTEM
|-
| SMA_OUTBOUND_FAIL || Path for failing outbound Smartphone XML interface || SYSTEM
|-
| SMA_OUTBOUND_PATH || Path for outbound Smartphone XML interface || SYSTEM
|-
| SMA_OWNING_DEPOT || Indicates if the Smartphone file is sent with Database or owing depot in the name || SYSTEM
|-
| SMA_RESOURCE_UPDATE || Update resources on receipt of Smartphone message || COST_CENTRE
|-
| SMA_SEND_ACCEPTED || Send ACCEPTED message to SMARTPHONE || SYSTEM
|-
| SMA_SET_TO_COMP_CONF || Update Trip Status once Smartphone has provided all quantities and times || SYSTEM
|-
| SMA_TO_DELIVER_IS_DELIVERED || Auto-Default the TO_DELIVER quantity from the DELIVERED quantity || COST_CENTRE
|-
| SMS_AUDITING || Will records be audited in ADM_LOG for the SMS_EMAIL messages (Y/N)? || SYSTEM
|-
| SMS_COL_DEL_BOTH || Send SMS for delivery/collection orders or both? (COL, DEL, BOTH) || COST_CENTRE
|-
| SMS_GATEWAY_PWD || SMS Gateway Password || SYSTEM
|-
| SMS_GATEWAY_URL || SMS Gateway URL || SYSTEM
|-
| SMS_GATEWAY_USER || SMS Gateway Username || SYSTEM
|-
| SMS_LANDLINE_EXCLUSION || Will SMS be excluded for landlines? (Y/N) || SYSTEM
|-
| SMS_LOC_TYPES || Limit SMS and EMAIL Notifications to this list of location types only. If blank messages are sent for all stops || COST_CENTRE
|-
| SMS_MULTI_MSG || Send multiple SMS message for each trip stop (Y/N) || COST_CENTRE
|-
| SMS_SENDER_NUM || SMS Sender number to stop replies || SYSTEM
|-
| SMS_SERVICE_BOX || Stores the e-mail address of the SMS service box. || SYSTEM
|-
| SMS_SERVICE_BOX_OLD || Stores the e-mail address of the SMS service box. || SYSTEM
|-
| SMTP_ORDER_SENDER || Order Email Sender address || SCHED_GROUP
|-
| SMTP_ORD_CONF_SENDER || Ord Conf Email Sender Address || COST_CENTRE
|-
| SMTP_ORD_CONF_SENDERXX || Ord Conf Email Sender Address || COST_CENTRE
|-
| SMTP_PASSWORD || SMTP password || SYSTEM
|-
| SMTP_PORT_NUMBER || SMTP Port Number || SYSTEM
|-
| SMTP_PRIMARY || Primary Mail Server || SYSTEM
|-
| SMTP_SECONDARY || Secondary Mail Server || SYSTEM
|-
| SMTP_SENDER || Email Sender address || SYSTEM
|-
| SMTP_SMS_PRIMARY || Primary mail server for SMS. || SYSTEM
|-
| SMTP_SMS_SECONDARY || Secondary mail server for SMS. || SYSTEM
|-
| SMTP_SMS_SENDER || Sender address for SMS. || SYSTEM
|-
| SMTP_TRIP_SENDER || Trip Email Sender address || CONTROL_TOWER
|-
| SMTP_USER || SMTP Username || SYSTEM
|-
| SOUTHERN_MANIFEST || Depot Linked to Southern Manifests || SYSTEM
|-
| STOP_PID || LOTS - is STOP_PID included in the extract || SYSTEM
|-
| SUBMIT_CARGOWISE_HEADER || Enter the number of minutes from FTP support files complete status to send header file? || SYSTEM
|-
| SUGGEST_TRIP || Suggest an appropriate trip for an order || COST_CENTRE
|-
| SUPPLIER_MANF || Indicates the name of the supplier manifest report to be automatically generated when a trip is accepted. || COST_CENTRE
|-
| SVC_USE_SERVICE_TYPES || Controls whether Service types are to be used which includes the use of transaction, manual, late and urgent order charging. || SYSTEM
|-
| T2A_ASSET_ARRIVED_OFFSET_DAYS || A number of offset days from the current date to select orders that have arrived at the depot for T2A Forward Items. || SYSTEM
|-
| T2A_ASSET_DUE_OFFSET_DAYS || A number of offset days from the current date to select orders that are due arrive at the depot for T2A Forward Items. || SYSTEM
|-
| TAG_TO_ASSET_SCANNING || Allow scanning and recording of Tags || SYSTEM
|-
| TA_EMAIL_SUBJECT || Email subject for automatically e-mailing manifest || COST_CENTRE
|-
| TA_EMAIL_SUBJECT || Trip accept. Email subject. || SYSTEM
|-
| TA_EMAIL_TEXT || Trip accept. Email message || SYSTEM
|-
| TA_EMAIL_TEXT || Email text for automatically e-mailing manifest || COST_CENTRE
|-
| TA_FILE_NAME || Trip accept. Name of output file. || SYSTEM
|-
| TA_FTP_DIRECTORY || Trip accept. FTP report to upload directory. || SYSTEM
|-
| TA_FTP_IP_ADDRESS || Trip accept. FTP report to IP address. || SYSTEM
|-
| TA_FTP_PASS || Trip accept. FTP report using password. || SYSTEM
|-
| TA_FTP_PORT || Trip accept. FTP port. || SYSTEM
|-
| TA_FTP_USER || Trip accept. FTP report using username. || SYSTEM
|-
| TA_PDF_TO_TIFF1 || Trip accept. Convert pdf to tiff. || SYSTEM
|-
| TA_PDF_TO_TIFF2 || Trip accept. Convert pdf to tiff. || SYSTEM
|-
| TA_PDF_TO_TIFF3 || Trip accept. Convert pdf to tiff stage 3. || COST_CENTRE
|-
| TA_PDF_TO_TIFF3 || Trip accept. Convert pdf to tiff. Rotation for landscape || SYSTEM
|-
| TA_REPORT_NAME || Trip accept. Name of report to be run. Please include the .rep extension. || COST_CENTRE
|-
| TA_REPORT_NAME || Trip accept. Name of report to be run. Please include the .rep extension. || SYSTEM
|-
| TA_SUB_FROM || Trip accept. Sub file from || COST_CENTRE
|-
| TA_SUB_FROM || Indicates Zetafax value in .sub file in FROM: || COST_CENTRE
|-
| TA_SUB_FROM || Trip accept. Sub file from || SYSTEM
|-
| TA_SUB_ORGANISATION || Trip accept. Sub file organisation || SYSTEM
|-
| TA_SUB_PRIORITY || Trip accept. Sub file priority || SYSTEM
|-
| TA_SUB_USER || Trip accept. Sub file user || COST_CENTRE
|-
| TA_SUB_USER || Trip accept. Sub file user || SYSTEM
|-
| TA_SUB_USER || Indicates Zetafax value in .sub file in USER: || COST_CENTRE
|-
| TDL_GEN_ITEMS || Allow order items to be generated from lines || SYSTEM
|-
| TDL_INBOUND_ARCH || Path for TDL XML archiving || SYSTEM
|-
| TDL_INBOUND_IDENTIFIER || Pattern for TDL Inbound XML || SYSTEM
|-
| TDL_INBOUND_PATH || Path for yet to be processed XML files from TDL || SYSTEM
|-
| TDL_ITEM_IN_PORTAL_FORMAT || Generate item identifier in portal format in order entry || SYSTEM
|-
| TEND_EMAIL || Different format for Tender invitation || SYSTEM
|-
| TEST || Controls whether certain testing functions are enabled - Y or N || SYSTEM
|-
| TIMES_LOADING_TIME || Default Loading Time used in Slots import when recalculating times || SYSTEM
|-
| TIME_ZONE_ACTIVE || Time Zone Active || SYSTEM
|-
| TMS_AUTO_DEFAULT_RESOURCE || Automatically default the Resource - Smartphone || COST_CENTRE
|-
| TMS_OTBOUND_SO_REF || Controls the outbound format for SO_REF in LOTSC || CUSTOMER
|-
| TOK_CNAME || Defines the Tokairo Customer Name. || CUSTOMER
|-
| TOK_CUSTOMERS || A comma-delimited list of customers to interface with Tokairo. || SYSTEM
|-
| TOK_FIELD || Defines the Tokairo field name. || CUSTOMER
|-
| TOK_OUTBOUND_ARCHIVE || Filepath for Tokairo Daily Extract archive || SYSTEM
|-
| TOK_OUTBOUND_PATH || Filepath for Tokairo Daily Extract || SYSTEM
|-
| TOK_POD_AVAIL || Is Tokairo being used to view POD documents - Y or N. || SYSTEM
|-
| TOK_SRCH_PAGE || Defines the Tokairo search page. || SYSTEM
|-
| TOK_URL_PREFIX || Defines the Tokairo URL prefix. || SYSTEM
|-
| TOK_VIRDIR || Defines the Tokairo virtual directory. || CUSTOMER
|-
| TOMTOM_CHECK_DEPOT || Check the depot to control data sent to depot || SYSTEM
|-
| TOMTOM_DRIP_FEED || Are stops sent to Webfleet by drip feed process || SYSTEM
|-
| TOMTOM_ORDER_TYPES || Are WEBFLEET order types derived || SYSTEM
|-
| TOMTOM_TIMES_ONLY || Do actual times on SU and CL set trip status || SYSTEM
|-
| TRANSPORT_MODE || Are Customer Transport Mode Factors Required || COST_CENTRE
|-
| TRIP_ALWAYS_SHOW_EMERGENCY_ORDERS || Emergency Deliveries are always displayed regardless of filter criterion || SYSTEM
|-
| TRIP_BRIEF_MAINTENANCE || Enable the Trailer Type, Rated Cost and Message Configuration to be maintained in Carrier Selection for trip planning (Y/N). || COST_CENTRE
|-
| TRIP_CHARGING_METHOD || Determines whether the calculation for the costs includes the trailer type of the trip: F is Fixed and includes the trailer type. || COST_CENTRE
|-
| TRIP_HAZARD_DISPLAYED || Show the Trip hazardous Totals or not. || SYSTEM
|-
| TRIP_HAZARD_LEVEL1_CODE || The colour code of the hazardous weight level 1. || SYSTEM
|-
| TRIP_HAZARD_LEVEL1_FROM || The lower value in the range of the hazardous weight level 1. || SYSTEM
|-
| TRIP_HAZARD_LEVEL1_TO || The upper value in the range of the hazardous weight level 1. || SYSTEM
|-
| TRIP_HAZARD_LEVEL2_CODE || The colour code of the hazardous weight level 2. || SYSTEM
|-
| TRIP_HAZARD_LEVEL2_FROM || The lower value in the range of the hazardous weight level 2. || SYSTEM
|-
| TRIP_HAZARD_LEVEL2_TO || The upper value in the range of the hazardous weight level 2. || SYSTEM
|-
| TRIP_HAZARD_LEVEL3_CODE || The colour code of the hazardous weight level 3. || SYSTEM
|-
| TRIP_HAZARD_LEVEL3_FROM || The lower value in the range of the hazardous weight level 3. || SYSTEM
|-
| TRIP_HAZARD_LEVEL3_TO || The upper value in the range of the hazardous weight level 3. || SYSTEM
|-
| TRIP_HAZARD_PRODUCTS || List the descriptions of the product types considered to be hazardous using a comma as a delimiter. || SYSTEM
|-
| TRIP_LABELS || Indicates the name of the report to be run from the Print Labels menu option in the trip tree in the Planning screen. || COST_CENTRE
|-
| TRIP_ORDER_XSD_VERS || Version of TRIP XSD being used. || SYSTEM
|-
| TRIP_ORD_LATE_FORMAT_MASK || Display the format of the late available and late delivery columns as time only (TIME) or date and time (DATETIME). || SYSTEM
|-
| TRIP_OVERVIEW_CURRENT_TYRES || Use the current quantity of tyres in the Trip Waterfall screen (Y/N) || SYSTEM
|-
| TRIP_PREVENT_PARCEL_CARRIER_ASSIGNMENT || Controls the manual assignment and cross-docking of transport orders to trips for parcels (Y to disable or N to enable). || COST_CENTRE
|-
| TRIP_SHEET || Trip Sheet Report || COST_CENTRE
|-
| TRIP_TRAMPS_ON_WATERFALL || Allow tramping trips to be shown in waterfall form by date not schedule || SYSTEM
|-
| TRIP_VALIDATE_PARCEL_ORDER_ASSIGNMENT || Controls validation of parcel orders to trips for parcel carriers (Y to disable or N to enable). || COST_CENTRE
|-
| TRLR_TYPE_RATE || Are trailer types included when estimating cost? || COST_CENTRE
|-
| TRM_3PL_SCHEDULE_NO_DROP || Enable orders without a drop number for the run to be pre-planned for Paragon (Y/N) || SYSTEM
|-
| TRM_ACTION_MITIGATION || Order Reason Actions requiring Mitigation || SYSTEM
|-
| TRM_ACTIVITY_QTY || Use Activity Quantity to determine when to create DEP control record || COST_CENTRE
|-
| TRM_ACT_PMTS_DEL_ORD_AT_CONF || Control whether Order_payments should be updated, and Orders set to DELIVERED when Trip is set to confirmed || SYSTEM
|-
| TRM_ADD_EDIT_ITEMS || Trip manipulation - display additional edit items. || SYSTEM
|-
| TRM_ALLOW_REJECTIONS || Allow trips to be rejected when they are not tendered (Y/N)? || SYSTEM
|-
| TRM_APPLY_DRIVER_BREAK_RULES || Switches Driver Breaks on or off - Y or N || SYSTEM
|-
| TRM_APPLY_POD_AFTER_ACTUALS || Apply the POD after the all actuals button is pressed (IIB) || SYSTEM
|-
| TRM_AUTO_DEL_TRIP_UNSCHED || Automatically delete trips when the last order is unscheduled from it || COST_CENTRE
|-
| TRM_AUTO_SET_ACCEPTED || Auto Set trip to accepted once all resources allocated || COST_CENTRE
|-
| TRM_BAXTER_ROUTES || Used to control when the process to populate trunk and radial routes is called || COST_CENTRE
|-
| TRM_BOL_PREFIX || Prefix that will be added to BOL when created in MTS. || COST_CENTRE
|-
| TRM_BOL_SUFFIX || Suffix that will be added to BOL when created in MTS. || COST_CENTRE
|-
| TRM_CANCEL_EMPTY_ORDER || Remove orders from trip going to Accepted if there are no items || COST_CENTRE
|-
| TRM_CARRIER_AUDIT || Controls whether audit records are written for Carrier CHANGES || COST_CENTRE
|-
| TRM_CHECK_CREW || Indicates if the Check_Crew functionality should be run. || COST_CENTRE
|-
| TRM_CHECK_LIMITS || Controls level at which Weight, RPE and Volume limits are checked - BY_STOP or NULL || SYSTEM
|-
| TRM_CHK_DRIVER_CARRIER || Use carrier hubs if driver hubs not set || COST_CENTRE
|-
| TRM_CL_DFLT_fixed_time || Default Close Down time (minutes) || SYSTEM
|-
| TRM_COMPLETED_SETTINGS || Indicates if CC/Customer Completed settings are in use || COST_CENTRE
|-
| TRM_CONSOLIDATE_STOPS || Allow consolidation of order on stops if time windows do not overlap || SYSTEM
|-
| TRM_CONSOL_ORDER_AFTER_XDOCK || Consolidate the available time windows for a collected order against the orders being loaded for delivery (Y/N) || SYSTEM
|-
| TRM_CROSSDOCK_TIME || Time offset for delivery into crossdock location || COST_CENTRE
|-
| TRM_DEBRIEF_SCREEN_TIME_VARIANCE_DISPLAYED || Is the Time Variance field displayed and updateable in the Trip Debrief screen. || SYSTEM
|-
| TRM_DEFAULT_DRIVER || Default Driver ID || COST_CENTRE
|-
| TRM_DEFAULT_TRACTOR || Default Tractor ID || COST_CENTRE
|-
| TRM_DEPOT_SCANS || Are trunk trip scans checked || SYSTEM
|-
| TRM_DESP_FOR_DEL || Maintain the Actual Despatched Quantity for a Delivery Trip in Trip Debrief (Y/N). || COST_CENTRE
|-
| TRM_DFLT_DRV_BREAK_MINS || Default Driver Break (minutes) || SYSTEM
|-
| TRM_DFLT_MAX_DRV_HRS_WO_BREAK || Default maximum drive hours without break || SYSTEM
|-
| TRM_DFLT_MAX_DRV_HRS_WO_STOPOVER || Default maximum drive hours without stopover. || SYSTEM
|-
| TRM_DFLT_MAX_WRK_HRS_WO_BREAK || Default maximum work hours without break || SYSTEM
|-
| TRM_DFLT_MAX_WRK_HRS_WO_STOPOVER || Default maximum work hours without stopover. || SYSTEM
|-
| TRM_DFLT_STOPOVER_BREAK_MINS || Default stopover duration (minutes). || SYSTEM
|-
| TRM_DFLT_WRK_BREAK_MINS || Default work break duration (minutes) || SYSTEM
|-
| TRM_DISPLAY_ERROR_MULTI_TRIP || Display Errors when changing multiple trips status || COST_CENTRE
|-
| TRM_DISP_ISOTRAK_OR_EFX || Controls whether the Isotrak Ref or EFX Ref is displayed in the TRIPSUM form - ISOTRAK or EFX || SYSTEM
|-
| TRM_DISP_OMS_OR_CUST_REF_OR_BOOK_OR_CONT_NO || Display OMS, Customer Ref, Booking Ref or Container No - OMS_REF, CUST_REF, CONT_NO or BOOKING_REF. || SYSTEM
|-
| TRM_DISP_REV_COLDEL || Display Revenue on collection or delivery trip || COST_CENTRE
|-
| TRM_DISP_RPE_DU_OR_WEIGHT || Controls whether RPE Qty, DU Qty or Total Weight is displayed in the TRIPSUM form - RPE, DU or WEIGHT. || SYSTEM
|-
| TRM_DISP_SCHED_ALL || Trip manipulation - display schedule all check box. || SYSTEM
|-
| TRM_DISP_VOL_OR_CASES || Controls whether Volume or Cases is displayed in Unscheduled Orders in TRIPSUM forms - VOLUME or CASES || SYSTEM
|-
| TRM_DISTRIBUTE_MAX_ORD_COST || Indicates if the cost centre will DISTRIBUTE revenue charges || COST_CENTRE
|-
| TRM_DO_NOT_UPDATE_ORD_DEL || Leave the order delivery type when the trip delivery type is different || COST_CENTRE
|-
| TRM_DRIVER_HUB || Drivers are aligned to a Hub Location || SYSTEM
|-
| TRM_DRIVER_RQD_FOR_ENROUTE_OR_ACC || Is a Driver required before a Trip can be set to EN_ROUTE or ACCEPTED || COST_CENTRE
|-
| TRM_EARLIEST_STOP_WINDOW || Toggle (Y/N) to specify whether consolidation uses the earliest stop || SYSTEM
|-
| TRM_ENFORCE_CARRIER_RULES || Enforce Carrier Hub Location Rules || COST_CENTRE
|-
| TRM_ENFORCE_TRIP_RECALC || Enforce Trip Recalculation - YES or NO || SYSTEM
|-
| TRM_EXCL_REG_AUTO || Planning Regions to be excluded from Auto Scheduling || COST_CENTRE
|-
| TRM_EXCL_TIME_VALIDATION || Indicates if the available time of an order is not compared to the cut-off time for TRUNK or LINEHAUL routes in the network scheduling engine (Y/N). || SYSTEM
|-
| TRM_FIXED_TRIP_STATUS || Determines status of trips created via Fixed Schedules. P for PLANNED or A for ACCEPTED. || SYSTEM
|-
| TRM_HIGHLIGHT_OVERDUE_FINISH || Trip Status used in Trip Overview screen to highlight overdue finish time || SYSTEM
|-
| TRM_HIGHLIGHT_OVERDUE_START || Trip Status used in Trip Overview screen to highlight overdue start time || SYSTEM
|-
| TRM_IGNORE_DUP_LOC_CHECK || Dunelm orders from a supplier in Scotland to a store in Scotland need to visit the trailer swap location twice so ignore standard checks in TRM || SYSTEM
|-
| TRM_INCL_TRUNK || Are trunk trips to be validated || SYSTEM
|-
| TRM_INC_BASED_AT_LOC_TRIPS || Allows viewing of other depots transiting || SYSTEM
|-
| TRM_LFS_PRINT_TRIP_POD_POC || Display LFS Trip Sheet POD POC report menu option (Y/N)? || SYSTEM
|-
| TRM_LOAD_DFLT_fixed_time || Default Loading Time (minutes) || SYSTEM
|-
| TRM_LOAD_dflt_mins_per_rpe || Default loading rate per RPE (minutes) || SYSTEM
|-
| TRM_LOAD_dflt_mins_per_weight || Default Loading rate per Weight (minutes) || SYSTEM
|-
| TRM_LOC_RADIAL_ROUTES || Indicates if a radial route that is stored for the location will be used in the scheduling engine instead of the location zones (Y/N). || SYSTEM
|-
| TRM_MANIFEST_DATES || Controls if the manifest is run based on dates || COST_CENTRE
|-
| TRM_MAX_DRIVING_HOURS || Maximum Driving Hours || SYSTEM
|-
| TRM_MAX_ORD_COST || Indicates if the cost centre will base revenue charges on the Maximum at a single stop || COST_CENTRE
|-
| TRM_MAX_SHIFT_HOURS || Maximum Shift Hours || SYSTEM
|-
| TRM_MAX_STOP_COST || Indicates if the cost centre will base cost charges on the Maximum at a single stop || COST_CENTRE
|-
| TRM_MAX_STOP_REVENUE || Indicates if the cost centre will base revenue charges on the Maximum at a single stop. || COST_CENTRE
|-
| TRM_MAX_WAIT_TIME || Maximum waiting time at Location (minutes) || COST_CENTRE
|-
| TRM_MERGE_END_OR_EXISTING_STOPS || Method-assigning orders to resulting trip in merge trips. Values: END or EXISTING. END adds orders to end. EXISTING adds orders to 1st available stop. || SYSTEM
|-
| TRM_MIC_DRIVER || Are driver minutes updated from Microlise debrief || COST_CENTRE
|-
| TRM_MODIFY_SCHED || Allow the stop times of the delivery trip to be updated to match the new delivery times of the scheduled order (Y/N). || COST_CENTRE
|-
| TRM_MOVE_ITEM_TO_DESP_BAY || Move an item from the grid to the despatch bay when added to the order on the trip or its order is assigned to the trip (Y/N) || SYSTEM
|-
| TRM_NETWORK_STOPS || Are trunk trip times set by the network table || COST_CENTRE
|-
| TRM_NEW_TRIP_STATUS_CHECKS || Control new restrictions on trip status change. || SYSTEM
|-
| TRM_NLP_SUMMARY || Request a summary by country in the NLP distance and time calculations(Y/N) || COST_CENTRE
|-
| TRM_NLP_SUMMARY || Request a summary by country in the NLP distance and time calculations(Y/N) || COST_CENTRE
|-
| TRM_NON_STD_INSTRUCTIONS || Calculate Planning Instructions on Carrier Trip Form || COST_CENTRE
|-
| TRM_NO_STOP_DELETE || Do not delete stops || COST_CENTRE
|-
| TRM_NO_TIME_VALIDATION || Trip prefix to prevent validation || COST_CENTRE
|-
| TRM_ODO_DISTANCE_LIMIT || Limit used to validate difference between odo start and end entries in debrief areas of Trip Forms || SYSTEM
|-
| TRM_OFFSET_PUBLIC_HOLIDAY || Indicates if the order time windows and the scheduling engine will be offset for the public holiday at the country, depot or route level (Y/N). || SYSTEM
|-
| TRM_ORD_OVERVIEW || Include Orders in Trip Overview screen || COST_CENTRE
|-
| TRM_ORD_SCHED_FROM || Number of days back for schedule range || COST_CENTRE
|-
| TRM_ORD_SCHED_FROM_PLANNING || Number of days back for schedule range in Planning screen || SYSTEM
|-
| TRM_ORD_SCHED_SEARCH || Maximum number of days for schedule range || COST_CENTRE
|-
| TRM_ORD_SCHED_SEARCH_PLANNING || Maximum number of days for schedule range in Planning screen || SYSTEM
|-
| TRM_ORD_SCHED_TO || Number of days forward for schedule range || COST_CENTRE
|-
| TRM_ORD_SCHED_TO_PLANNING || Number of days forward for schedule range in Planning screen || SYSTEM
|-
| TRM_OVERVIEW_AMBER_TIME || Time allowed before start and finish times are amber in TRIP OVERVIEW || SYSTEM
|-
| TRM_OVERVIEW_RED_TIME || Time allowed before start and finish times are red in TRIP OVERVIEW || SYSTEM
|-
| TRM_PLAN_ALL_RET_ORDERS || Plan all RET orders || COST_CENTRE
|-
| TRM_PLAN_INVALID || Are un-manifested orders set to invalid || SYSTEM
|-
| TRM_PREVENT_ALL_DEBRIEF || Prevent setting of actuals in trip debrief || SYSTEM
|-
| TRM_PREVENT_CONSOL_ACROSS_STOPS || Stop orders being added to shipments when not on same stops || COST_CENTRE
|-
| TRM_PREVENT_ORD_ON_COMP_STOP || Prevent Orders Being Planned on Completed stops || SYSTEM
|-
| TRM_PROSPERO_ADV_DAYS || Advance Scheduling days for Prospero || SYSTEM
|-
| TRM_PROTECT_SHUNTS || Protect the times from the order windows for the trip stops for shunt trips for collections (Y/N) || SYSTEM
|-
| TRM_RECALC_ELAPSED_TIME || Always recalculate elapsed time on trip || COST_CENTRE
|-
| TRM_RETAIN_CARRIER_NEW_SCHED || It is to retain a carrier when the schedule of the trip is updated. Otherwise, the carrier is reset to the carrier for the owning depot. || COST_CENTRE
|-
| TRM_RETAIN_EMPTY_STOPS || Retain empty stops when validating the trip. || COST_CENTRE
|-
| TRM_RETAIN_MTM || Retain MTM cost when set to Planned || SYSTEM
|-
| TRM_RETAIN_ORD_STATUS_TRIP_COMPLETE || Retain the current order status if trip status is set to COMPLETED (Y/N) || COST_CENTRE
|-
| TRM_RETAIN_PACK_DATA || Retain Pack Data either via Paragon or advise user to retain or delete pack data if manually unscheduling order. || COST_CENTRE
|-
| TRM_ROUND_RPE_AT_STOP || Round RPE at unload stop || SYSTEM
|-
| TRM_SCHEDULE_BY_DEL || Controls if orders are manually scheduled onto trips by del time || SYSTEM
|-
| TRM_SEND_PLUTO_ACTUALS || Actuals process for PLUTO || COST_CENTRE
|-
| TRM_SEND_PRE_DELIVERY_MSG || Activates email and SMS functionality || COST_CENTRE
|-
| TRM_SET_ACTUALS_AFTER_ENROUTE || Should Actuals (arrive/depart) be set for Trip stop 1 when trip is set to En-Route - Y or N || COST_CENTRE
|-
| TRM_SET_DESP_AFTER_ENROUTE || Should the actual despatched values for an order be set when the trip status is set to EN-ROUTE (Y to enable or N to disable). || COST_CENTRE
|-
| TRM_SET_NEW_STOP_TIMES || Trip prefix to set stop times based on trip duration || COST_CENTRE
|-
| TRM_SET_OWNING_DEPOT || Priority for assigning owning depot to a trip || COST_CENTRE
|-
| TRM_SET_TO_COMPLETED || Should trip be auto set to Completed. Values are N, ACTUAL (after actuals have been applied), POC/POD (when POC and POD applied to all Orders). || COST_CENTRE
|-
| TRM_SET_TO_COMP_AFTER_TIMES || Are trips set to completed when stop actuals have been set? || SYSTEM
|-
| TRM_SET_TO_CONFIRMED || Should trip be auto set to Confirmed. Values are N, ACTUAL (after actuals have been applied), POC/POD (when POC and POD applied to all Orders). || SYSTEM
|-
| TRM_SET_TO_ENROUTE_AFTER_ACTUALS || Should trip be set to En-Route after first order has been collected - Y or N || COST_CENTRE
|-
| TRM_SHIFT_TIMES_FOR_TRIP || Use Shift Times For Start And End Times Of Trip || SYSTEM
|-
| TRM_SHOW_LATE_BUTTON || Is the Show Late Reasons Button visible. || SYSTEM
|-
| TRM_SHOW_TIME_DEBRIEF_BTNS || Show time debrief buttons in trip debrief || SYSTEM
|-
| TRM_SHOW_TRIP_EXPORT_BTN || Show Export Button in TRIP screens. Specifically for Road Ops Report || SYSTEM
|-
| TRM_SOURCE_SYSTEM || Highlight the trip details when it contains an order without an OPEN status in the WMS source system (Y/N) || SYSTEM
|-
| TRM_STACK_DEBRIEF || Trip Stack Debrief || COST_CENTRE
|-
| TRM_STATUS_FOR_CONSOLIDATION || The trip status that controls the consolidation by customer or customer group, enter BOTH for ACCEPTED and PLANNED || SYSTEM
|-
| TRM_STOP_TIMES_FROM_ORDS || Will the trip stop times be inherited from the delivery time window of the order? (Y/N) || CUSTOMER
|-
| TRM_STORE_TRIP_MOVES || Determines whether audit of old and new trips is stored against orders || COST_CENTRE
|-
| TRM_SU_DFLT_fixed_time || Default Start Up time (minutes) || SYSTEM
|-
| TRM_SVC_TYPE || Is SVC_TYPE Editable on TRIP forms? || SYSTEM
|-
| TRM_TEMP_DEBRIEF || Display temperature on Trip debrief || SYSTEM
|-
| TRM_TRACTOR_RQD_FOR_ENROUTE_OR_ACC || Is a Tractor (Vehicle) required before a Trip can be set to EN_ROUTE or ACCEPTED || COST_CENTRE
|-
| TRM_TRAILER_RQD_FOR_ENROUTE_OR_ACC || Is a Trailer Id required on every stop before a Trip can be set to EN_ROUTE or ACCEPTED || COST_CENTRE
|-
| TRM_TRANSPORT_MODE_REQD || Is the transport mode on the trip screens a required field || COST_CENTRE
|-
| TRM_TREE_FORMAT || Determines trip tree display format || COST_CENTRE
|-
| TRM_TREE_ROUTE || Determines whether Route code is displayed in trip tree || COST_CENTRE
|-
| TRM_TRIP_STATUSES || List of Trip Statuses to control which trips displayed in Tripdtl/Trip Debrief form. || SYSTEM
|-
| TRM_TRUNK_TIME || Time in minutes for assessing Trunk Trips || COST_CENTRE
|-
| TRM_UNLOAD_DFLT_fixed_time || Default unloading time (minutes) || SYSTEM
|-
| TRM_UNLOAD_dflt_mins_per_rpe || Default unloading rate per RPE (minutes) || SYSTEM
|-
| TRM_UNLOAD_dflt_mins_per_weight || Default Unloading rate per RPE (minutes) || SYSTEM
|-
| TRM_UNSCHEDULE_TO_CANCEL || Controls if orders are Unscheduled when a cancellation is received || SYSTEM
|-
| TRM_UPDATE_ALL_ACTUALS || When a line actual is debriefed all actuals are set || COST_CENTRE
|-
| TRM_USE_ACTUALS_FOR_STOP_TIMES || Use Actual Times at stops to calculate times for next stop || SYSTEM
|-
| TRM_USE_MAX_RPE_OF_LARG_TRAILER || Controls whether MTS uses Max RPE of Largest Trailer Type when adding Orders to Trips - Y or N (N will use Current Trailer) || SYSTEM
|-
| TRM_VALIDATE_STOP_TIMES || Show Validation messages on stop times and prevent the user from going to accepted (Y/N) || SYSTEM
|-
| TRM_VALIDIDATE_DU_TEMP || Validate Du temp by product and DU || COST_CENTRE
|-
| TRM_VAL_CAR_VESSEL || Trip manipulation - validate carrier after vessel has been allocated. || SYSTEM
|-
| TRM_WASTE_SITE || Amend TO_LOC to a waste site in order well || COST_CENTRE
|-
| TRM_WEIGHTED_AVE_FILL_ACCEPT_PCENT || Defines the acceptable percentage for trip weighted average fill || SYSTEM
|-
| TRM_WEIGHTED_AVE_FILL_MIN_PCENT || Defines the minimum required percentage for trip weighted average fill || SYSTEM
|-
| TRM_WMS_STATUS || Controls if WMS status is calculated and if WMS status fields displayed in Trip forms. || COST_CENTRE
|-
| TRM_XDOCK_VALIDATION || Different Validation for the Cross dock process || COST_CENTRE
|-
| TRM_XDOCK_VIA_ROUTE || Display additional route information when selecting trip for XDOCK orders (Y/N) || SYSTEM
|-
| TRP_RED_TRUCK_ERRORS || Indicates if the truck icon is red to indicate an error || SYSTEM
|-
| TRP_SEND_ENABLE_MSG || Which enabling message is to be sent by Trip form || SYSTEM
|-
| TRP_SEND_WAREHOUSE_LOAD || Include Warehouse Loading Time in the outbound XML flow. || COST_CENTRE
|-
| TRP_STACK_DEBRIEF || Trip Stack Debrief || COST_CENTRE
|-
| TRUNK_LOAD || Time (minutes) to load an order on a trunk trip || SYSTEM
|-
| TRUNK_UNLOAD || Time (minutes) to unload an order on a trunk trip || SYSTEM
|-
| UKMAIL_ADD_INFO_LABEL || Additional information on UKMail Label || COST_CENTRE
|-
| UKMAIL_USE_CUST_REF_ON_LABEL || Controls if customer ref is displayed on UKMAIL label || CUSTOMER
|-
| UNISON_ORDER_INT_TYPE || EIH Interface Type (UNISON ORDER) || SYSTEM
|-
| UNI_DEFAULT_DU_TYPE || Default DU Type for Orders created via the UNISON interface. || SYSTEM
|-
| UNI_ENABLED || To enable the inbound and outbound file processing on this DB || SYSTEM
|-
| UNI_FTP_DESTINATION_DIRECTORY || Directory for FTP of Unilever Files || SYSTEM
|-
| UNI_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Unilever Files || SYSTEM
|-
| UNI_FTP_DESTINATION_PASSWORD || Password for FTP of Unilever Files || SYSTEM
|-
| UNI_FTP_DESTINATION_PORT || Port for FTP of Unilever Files || SYSTEM
|-
| UNI_FTP_DESTINATION_USERNAME || Username for FTP of Unilever Files || SYSTEM
|-
| UNI_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header (Unilever) || SYSTEM
|-
| UNI_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header (Unilever) || SYSTEM
|-
| UNI_INBOUND_PATH || Path for yet to be processed XML files (Unilever) || SYSTEM
|-
| UNI_LOCATION || Location for Unilever || SYSTEM
|-
| UNI_OUTBOUND_ARCH || Path for processed XML files for Unilever || SYSTEM
|-
| UNI_OUTBOUND_FAIL || Path for processed XML files for Unilever that have failed processing || SYSTEM
|-
| UNI_OUTBOUND_IDENTIFIER || Unilever outbound file identifier || SYSTEM
|-
| UNI_OUTBOUND_PATH || Path for yet to be processed XML files for Unilever || SYSTEM
|-
| UNSCHED_ORDERS_DEL_DAYS || Unscheduled orders on schedules older than this value will be deleted || SYSTEM
|-
| UPDATE_DIR || client Server Update directory || SYSTEM
|-
| UPDATE_IP_ADDR || Client Server Update IP Address || SYSTEM
|-
| UPDATE_IP_ADDR_CGEY || CGEY Client Server IP Address || SYSTEM
|-
| UPDATE_ORDERS_TO_TRIP || Update Order Windows to match selected trip || COST_CENTRE
|-
| UPDATE_ORDER_TIMES_TO_TRIP || Enable the current orders to have their time windows updated to match the stop time windows in the 'Confirm Update/Add' process (Y/N) || COST_CENTRE
|-
| UPDATE_PASSWORD || Client Server Update Password || SYSTEM
|-
| UPDATE_TO_DELIVER || update the To deliver quantity with the Ordered quantity for New order Items || SYSTEM
|-
| UPDATE_USER || Client Server Update User || SYSTEM
|-
| UPD_CUST_DATES || Default part Number || CUSTOMER
|-
| UPGRADE_PASSWORD || Client Server Upgrade Password || SYSTEM
|-
| UPGRADE_USER || Client Server Upgrade Username || SYSTEM
|-
| UPPERCASE_ASSET_ID || Asset id to be stored in upper case || SYSTEM
|-
| URGENT_ORDER || Controls if Urgent Notification emails are sent to planners || COST_CENTRE
|-
| URGENT_ORD_DELIVERY || Controls which delivery types trigger an urgent notification || COST_CENTRE
|-
| URGENT_ORD_RECIPIENT || Controls who receives an urgent notification || COST_CENTRE
|-
| USE_CHILD_LOCATIONS || Use any child locations in preference to the master locations of an order in the requested reports? (Y/Y) || COST_CENTRE
|-
| USE_ORDER_ADDRESSEE || Will the addressee name be used for the order? (Y/N) || COST_CENTRE
|-
| USE_PACK_QUANTITY || Use the current quantity of tyres in the Trip Waterfall screen (Y/N) || SYSTEM
|-
| USE_PALLET_ID_XML || Use Pallet ID instead of item identifier in XML Outbound files || COST_CENTRE
|-
| USE_SECURITY_PROFILES || Use Security Profiles for users || SYSTEM
|-
| USE_SMS_GATEWAY || Use SMS Gateway for SMS message sending || SYSTEM
|-
| USE_XML_ORDER_SUB_REFS || Print order sub refs on outbound XML || COST_CENTRE
|-
| USE_XML_ORDER_SUB_REFS || Print order sub-references in the outbound XML file? (Y/N) || COST_CENTRE
|-
| UTL_IMPORT_IGNORE_INVALID_OPERATION || The import process of files will suppress the auditing of messages when a file does not exist on the server to overwrite (Y/N) || SYSTEM
|-
| VALIDATE_LOCATION_ON_CLOSE || Validate address details if the close button is pressed within locations screen (Y/N)? || SYSTEM
|-
| VALIDATE_MASTER_LOC || Validate the collection and delivery location of the order against the decoded master locations (Y/N) || COST_CENTRE
|-
| VB_UPLOAD_APP_VERSION || Version number of the PC MTS Upload/Import Application written in Visual Basic || SYSTEM
|-
| WARN_MISSING_PO || Warn if No PO Allocated to a trip when status or carrier changed || CARRIER
|-
| WARN_OUTSTANDING4933 || Warn of unmatched 4933 orders on trip status change || CUSTOMER
|-
| WATERFALL_UPDATES || control updates on the waterfall screen || SYSTEM
|-
| WCS_441_CHECK_DAYS || Set a number of days in which to assess the prior loading messages for WCS. || SYSTEM
|-
| WCS_CALC_ITEM_WGT_VOL || Calculate the weight and volume for the DU in the 804 scan (Y/N). || COST_CENTRE
|-
| WCS_CALC_ITEM_WGT_VOL || Calculate the weight and volume for the DU in the 804 scan (Y/N). || CUSTOMER
|-
| WCS_CLEARDOWN_DAYS || Number of days after which WCS control records will be cancelled. || SYSTEM
|-
| WCS_COLLECTION_PREADVICE || Do we call collection pre-advice || NONE
|-
| WCS_COMBINED_ADD_LOAD || WCS add items and loading into a single scan || SYSTEM
|-
| WCS_DEFAULT_AGENT || Default agent for WCS messages || SYSTEM
|-
| WCS_DUAL_INSTANCE || Dual Instance WCS....***DUNELM ONLY*** || SYSTEM
|-
| WCS_ENABLED || Is the WCS system enabled? || SYSTEM
|-
| WCS_MIN_ITEM_LENGTH || Min length of WCS_ITEM to check for match in CTMS || SYSTEM
|-
| WCS_MULTI_DEPOTS || Pre-advise WCS when depot is different || SYSTEM
|-
| WCS_OLD_404_DAYS || Number of days to allow old 404 messages to be sent to WCS || SYSTEM
|-
| WCS_ORD_BUILD_ENABLED || Y to enable WCS Re-advice resend of Orders Overnight Processing || SYSTEM
|-
| WCS_RETAIN_EMPTY_LINES || Retain any empty order lines that have been created when their items have been deleted during the order confirmation process? (Y/N) || SYSTEM
|-
| WCS_SET_BAY_GRID_ITEMS_ONLY || Only update item locations that are on the grid || SYSTEM
|-
| WCS_SPLIT_LOAD_PLAN || Automatically plan the split load orders to final destination || SYSTEM
|-
| WCS_SPLIT_ORDER_BY_TRIP || Allow an order to be split when its items are loaded on different trips for delivery (Y/N)? || COST_CENTRE
|-
| WEB_SERVICE_STORE_REQ || Determines if the message request sent to the web server enquiry should be stored in the audit record - Y will store the message as a CLOB value. || SYSTEM
|-
| WEB_SERVICE_STORE_RESP || Determines if the message in response to the web server enquiry should be stored in the audit record - Y will store the message as a CLOB value. || SYSTEM
|-
| WEB_SERVICE_USER || User name for web service || SYSTEM
|-
| WMS_INBOUND_ARCH || Path for WMS XML archiving || SYSTEM
|-
| WMS_INBOUND_FAIL || Path for WMS XML failures || SYSTEM
|-
| WMS_INBOUND_LISTING_NAME || Filename for list of files in directory for WMS XML Order Inbound || SYSTEM
|-
| WMS_INBOUND_ORD_IDENTIFIER || Pattern for WMS Order Inbound XML || SYSTEM
|-
| WMS_INBOUND_PATH || Path for yet to be processed XML files from WMS || SYSTEM
|-
| WMS_LISTING_SCRIPT_NAME || Script name for WMS XML Order Inbound || SYSTEM
|-
| WOC_MSG_SEND_COUNT || Number of message per run sent to WCS via WOC || SYSTEM
|-
| WSA_ARCHIVE_DAYS || Determines the number of days that the web service messages will be retained in C-TMS prior to being archived. || SYSTEM
|-
| WS_COLLECT_LOCATION || Collection location to override one provided in web service to override collection depot in partnership || CUSTOMER
|-
| WS_COL_CUTOFF || Cut-off time for web service orders from an RDC to make the next days delivery. || SYSTEM
|-
| WS_DERIVE_COL_WINDOW || Derive Collection windows for Web Service Orders || COST_CENTRE
|-
| WS_DUMMY_DU_TYPE || Dummy DU Type used for Web Service order creation || SYSTEM
|-
| WS_EARLY_AVAIL_TIME || Early available time for Web Service Orders || COST_CENTRE
|-
| WS_MAX_MANF_RPE || Maximum RPE value for Web service || SYSTEM
|-
| WS_NUM_OF_RETRIES_ALLOWED || Max number of times a record will be sent to a web service endpoint || SYSTEM
|-
| WS_REASON_CODE || Default reason code for Web service || SYSTEM
|-
| WS_USE_TRIP_STATUS || Use Trip Status for Web Service || COST_CENTRE
|-
| XML_NO_DELAY_FILES || List of XML filenames that will require no delay in polling time (eg pack confirmation). || SYSTEM
|-
| XML_OUT_SUMM_LVL || Level to summarize XML outbound message || SYSTEM
|-
| ZERO_MANIFEST || Allow orders to be zero manifested and set to ABORTED || COST_CENTRE
|-
| ZERO_PACK_REASON || Zero packed reason code || COST_CENTRE
|-
| ZETES_INSTALLED || Zetes installed || SYSTEM
|-
| ZET_INBOUND_ARCH || Path for Microlise XML archiving || SYSTEM
|-
| ZET_INBOUND_FAIL || Path for Microlise XML failures || SYSTEM
|-
| ZET_INBOUND_IDENTIFIER || Pattern for MIC Trip Inbound XML || SYSTEM
|-
| ZET_INBOUND_LISTING_NAME || Filename for list of files in directory for MIC XML Trip Inbound || SYSTEM
|-
| ZET_INBOUND_PATH || Path for yet to be processed XML files from Microlise || SYSTEM
|-
| ZET_INC_SSCC_PREFIX || Include prefixes for SSCC formats for the Zetes interface (Y/N). || COST_CENTRE
|-
| ZET_LISTING_SCRIPT_NAME || Script name foe MIC XML Trip Inbound || SYSTEM
|-
| ZET_OUTBOUND_ARCH || Path for safe copy of XML files for Zetes || SYSTEM
|-
| ZET_OUTBOUND_PATH || Path for yet to be collected XML files for Zetes || SYSTEM
|-
| ZIP || Zip executable location on application server || SYSTEM
|-
| ZIP_SERVER || Application server folder for zipped Invoice files || SYSTEM
|-
| ZONE_POSTCODE_CHECK || Does Zone import check the postcode || SYSTEM
|-
| zip || Location of the zip executable on the application server || SYSTEM
|-
|API_CARRIER_PLAN ||The carrier for the API process which the customer will use with pre-packed labels ||CUSTOMER
|-
|DO_NOT_UPDATE_LOADING_RATES ||Do not update loading rates via customer onboarding ||SYSTEM
|-
|FLEXIPOD ||Set to Y to indicate the FlexiPod interface is active ||SYSTEM
|-
|FLEXIPOD_ACID ||Flexipod acid ||SYSTEM
|-
|FLEXIPOD_BREAK_DROPS ||Flexipod include breaks for the drops in the Add API call (Y/N) ||SYSTEM
|-
|FLEXIPOD_CARRIERS ||Set to Y indicates the Carrier can control if a trip is sent to FlexiPod ||SYSTEM
|-
|FLEXIPOD_CLIENTNUM ||FleXipod ClientNum sent in interface ||SYSTEM
|-
|FLEXIPOD_DEPOTS ||Set to Y indicates the Depot can control if a trip is sent to FlexiPod ||SYSTEM
|-
|FLEXIPOD_DIRECT ||Set to Y to indicate the FlexiPod interface is direct and not using Route Execution ||SYSTEM
|-
|FLEXIPOD_DROP ||Determines the Drop level STOP-OMS or ITEM ||SYSTEM
|-
|FLEXIPOD_EXPIRY ||Sets the expiry date for the manifest as a number of days after the end of the trip. ||SYSTEM
|-
|FLEXIPOD_EXTERNALSYSTEMUPDATE ||Flexipod process the External System Update messages in the API call (Y/N) ||SYSTEM
|-
|FLEXIPOD_FORCEITEMSCAN ||Force the items to be scanned separately: 0 to use the ScanLevel or 1 to force the scan by item. ||SYSTEM
|-
|FLEXIPOD_LISTPENDINGMANIFESTS ||Flexipod process the List Pending Manifest Update messages in the API call (Y/N) ||SYSTEM
|-
|FLEXIPOD_MERGE_DROPS ||Flexipod merge the orders on the drop in the Add API call (Y/N) ||SYSTEM
|-
|FLEXIPOD_PASSWORD ||FleXipod Webservice password ||SYSTEM
|-
|FLEXIPOD_PROXY ||Flexipod proxy server ||SYSTEM
|-
|FLEXIPOD_READDROP ||Flexipod process the Read Drop messages in the API call (Y/N) ||SYSTEM
|-
|FLEXIPOD_SCAN_LEVEL ||1,2 or 3 to indicate line or item level scanning ||SYSTEM
|-
|FLEXIPOD_SCAN_TYPE ||Contents and items ||SYSTEM
|-
|FLEXIPOD_SIGNATORY ||Set to Y to store the SignedByName as the actual signatory as information for the order at its collection of delivery location ||SYSTEM
|-
|FLEXIPOD_SPLIT ||Are orders to be split? ||SYSTEM
|-
|FLEXIPOD_SYSTEM ||FleXipod SYSTEM ID sent in interface ||SYSTEM
|-
|FLEXIPOD_TPCLIENTNUM ||FleXipod TPClientNum sent in interface ||SYSTEM
|-
|FLEXIPOD_USERCODE ||FleXipod webservice usercode ||SYSTEM
|-
|FLEXIPOD_USERNAME ||FleXipod webservice username ||SYSTEM
|-
|FLEXIPOD_WEBSERVICE ||Flexipod webservice endpoint URL ||SYSTEM
|-
|FLEXIPOD_WEBSERVICE_TASK ||Flexipod webservice endpoint URL for Tasks ||SYSTEM
|-
|FLEXIPOD_WEBSERVICE_UI ||Flexipod webservice endpoint URL ||SYSTEM
|-
|FLEXIPOD_WEBSERVICE_UI_EXEC ||Flexipod webservice endpoint URL for Route Execution ||SYSTEM
|-
|FLEXIPOD_X_API_KEY ||Flexipod x-api-key for External System Update messages ||SYSTEM
|-
|IMP_DERIVE_FROM_LOCATION ||Derive the collection location of an order. ||COST_CENTRE
|-
|IMP_DERIVE_ORDER_WINDOWS ||Derive the order windows. ||COST_CENTRE
|-
|IMP_SET_ORDER_TYPE ||Set the order type to RET, SLS or DIR. ||COST_CENTRE
|-
|IMP_SPLIT_CONTACT_NAME ||Split a contact name into Forename and Surname. ||COST_CENTRE
|-
|LIMIT_ADDRESS_MATCH ||Limit address matching to line1, line2 and postcode ||SYSTEM
|-
|LOOKUP_FOR_ROUTE_CODES ||Display lookup button in PLANNING beside Route Code ||SYSTEM
|-
|PSD_CONTACT_ADDRESS ||Polar Speed Distribution Ltd ||SYSTEM
|-
|PSD_CONTACT_TEL ||Tel: +44 (0) 1525 217666 ||SYSTEM
|-
|REBOOK_REQ_SUBREF ||Add Rebook Sub reference when CBR exception added to item ||SYSTEM
|-
|REBOOK_SERVICE_LEVEL ||Service Level For rebooked orders when set to copy use existing ||SYSTEM
|-
|RESET_MANUAL_SCHEDULE ||Reset manual schedule flag from the planning screen ||SYSTEM
|-
|TMP_ENG_TRIP_PREFIX ||Scheduling Engine Trip Prefix ||COST_CENTRE
|-
|TRM_3PL_REROUTE ||Reroute the order in the fixed-drop scheduling engine to the next available route for the day (Y/N) ||SYSTEM
|}

System Parameters List

2025-09-16T11:50:44Z

Anw: Added details of MCS Scanning changes

{| class="wikitable apt-searchable" border="1" id="systemparams"
|- bgcolor="silver"
!Parameter !! Description !! Level
|-
| ACC_ACTUAL_DISTANCE || Controls if the distance is rated using actual distance || SYSTEM
|-
| ACC_ADD_LINES || Does the user rate by lines and additional tariffs || COST_CENTRE
|-
| ACC_ALLOCATE_MANUAL_COST || Allow manual cost payments on orders || SYSTEM
|-
| ACC_ALLOW_MULTIPLE_CCY || Can multiple currencies be defined in the database? || SYSTEM
|-
| ACC_ALLOW_ZERO_RPE || Allow zero quantity to be returned from get charges (for RPE tier) || SYSTEM
|-
| ACC_ALWAYS_APPLY || There are tariffs that should always be applied || SYSTEM
|-
| ACC_CALC_SECURITY || Indicates if Security charges are applicable || SYSTEM
|-
| ACC_CALC_SERVICES || Service charges applicable || SYSTEM
|-
| ACC_CHECK_ORDER || Should order be assessed for rating || SYSTEM
|-
| ACC_CONSOL_RADIAL_COSTS || Indicates if radial charges are consolidated at delivery location || SYSTEM
|-
| ACC_CONTRACT_OWN || To control if the system looks at the contract or the existing table to identify the charges for own packaging || SYSTEM
|-
| ACC_CONTRACT_PICKPACK || To check the relevant contract for a PICKPACK tariff and generate a payment || SYSTEM
|-
| ACC_CONTRACT_SERVICES || To control a procedure that will check if there are any service records on the order || SYSTEM
|-
| ACC_CUST_FUEL || Apply Customer Fuel Charges || SYSTEM
|-
| ACC_Calc_Payment_Ord || Controls whether payment button is displayed on Orders forms - Y or N, Internal Charges are being applied to orders) || SYSTEM
|-
| ACC_Calc_Payment_Trip || Controls whether payment button is displayed on Trip forms - Y or N, Trip Cost method is defined against the Carrier Type || SYSTEM
|-
| ACC_Calc_Revenue_Ord || Control Order revenue calculation method - CONTRACT or CONTRACT-TPL || SYSTEM
|-
| ACC_Calc_Revenue_Trip || Controls whether revenue button is displayed on Trip forms - Y or N, Trip Cost method is defined against the Carrier Type) || SYSTEM
|-
| ACC_Calc_Saving_Ord || Controls whether the saving button is displayed on Orders forms - Y or N || SYSTEM
|-
| ACC_DEMURRAGE || Number of hours before demurrage charge start || SYSTEM
|-
| ACC_EDIT_ORD_CHARGE || Allow users to edit revenue charges || SYSTEM
|-
| ACC_FUELSURCH_EVENTDATE || Details whether Fuel Surcharges are calculated based on TENDERED or TRIPSTART date. || SYSTEM
|-
| ACC_FUEL_SEC_MODE || Are Fuel and security charges controlled by transport mode || SYSTEM
|-
| ACC_INC_ALL_ORDER_COST_PAYMENTS || Include all order cost payments (Y/N)? || COST_CENTRE
|-
| ACC_INDEXES || Use Acc indexes || SYSTEM
|-
| ACC_INT_CHRG_AT_TRUNK_LEG || Indicates if Internal Charges (trunk and radial) are generated by the trunk leg || SYSTEM
|-
| ACC_INVOICE_LOGO || Invoice Logo || COST_CENTRE
|-
| ACC_KNOWN_ZONE || Can rating Zone be predicted? || SYSTEM
|-
| ACC_LINES_OR_HEADER || Rate orders by line level only (Y), or by header level only or both levels (N) || CUSTOMER
|-
| ACC_OF_VERSION || Controls format of extract to OF || SYSTEM
|-
| ACC_ORD_STD_COST || Control Order standard cost calculation method - CONTRACT or CONTRACT-TPL || COST_CENTRE
|-
| ACC_PACKAGES || Are DU type charges separately || SYSTEM
|-
| ACC_PLAN_COSTS || Allows user to calc costs from Planned trips || COST_CENTRE
|-
| ACC_PROTECT_STATUS || Indicates if Payment status are protected from update to F || SYSTEM
|-
| ACC_RATE_BY_PARTY || To control if the rating process will look for a party contract when rating || SYSTEM
|-
| ACC_ROUND_AVG_DU_WEIGHT || Round Avg Du Weight to 3 decimal places for rating || COST_CENTRE
|-
| ACC_SCREENING_CHARGES || Are screening charges applied || SYSTEM
|-
| ACC_SERVICE_METHODS || Controls is services are allocated by methods || COST_CENTRE
|-
| ACC_SHOW_PROFIT || Controls the display of the Profit Field || COST_CENTRE
|-
| ACC_SUPPRESS_RATING || Should rating be prevented when validating orders || CUSTOMER
|-
| ACC_TRANSPORT_MODE || Is transport mode included in Contract charges || SYSTEM
|-
| ACC_USE_ORD_TRLR_TYPE || Should order revenue be calculated from the order trailer type even when scheduled || COST_CENTRE
|-
| ACC_ZERO_DESPATCHED || Controls if Zero despatched lines are ignored from rating || COST_CENTRE
|-
| ACTIVE_ROLE_DISPLAY || Indicates if the active role is displayed in the tool bar || SYSTEM
|-
| ADDITIONAL_ORDER_VALIDATION || Additional order validation required for product weight || COST_CENTRE
|-
| ADD_CSV_COL_FORMATTING || Add Column Formatting to CSV extracts || SYSTEM
|-
| ADM_EXCLUDE_AUDIT_LOG || Processes that will be excluded from writing audit log records. || SYSTEM
|-
| ADM_EXCLUDE_PACKAGE_MSG || Packages whose adm log messages are not to be written || SYSTEM
|-
| ADM_LOG_ARC_DEL_DAYS || Number of days that ADM_LOG_ARCHIVE messages should be kept for || SYSTEM
|-
| ADM_NO_DISPLAY_MENU || Enable the user to access the menu item || SYSTEM
|-
| ADM_UNKOWN_ORDERS || Identify amended/duplicate orders || SYSTEM
|-
| ADM_UPSHIFT_DU_TYPE || Upshifts the despatch unit type when Y. || SYSTEM
|-
| ADM_UPSHIFT_PRODUCT_TYPE || Upshifts the product type when Y || SYSTEM
|-
| ADM_WRITE_ERRORS || Store fatal form errors in FORM_ERROR_LOG || SYSTEM
|-
| ADR_REGS || Are ADR regulations displayed for trips || COST_CENTRE
|-
| ALLOC_RESOURCE || Are drivers and tractors allocated to own fleet carriers? || SYSTEM
|-
| ALLOC_TRIP_PMNTS || Allocate the trip payments as order costs || SYSTEM
|-
| ALLOW_DIRECT_BAY_MOVES || Should orders be moved directly from the receipt bay or to the despatch bay from the grid? || SYSTEM
|-
| ALLOW_DUPLICATE_CUST_REF || Allow orders with duplicate cust refs but different to locations. || SYSTEM
|-
| ALLOW_ETA_UPDATES || Determines whether the user can update ETA values || COST_CENTRE
|-
| ALLOW_HOLD_ORDERS || allow orders to be place don hold || SYSTEM
|-
| ALLOW_MANUAL_RPE || Allow RPE to be entered (via the inbound EDI) and do not overwrite. || SYSTEM
|-
| ALLOW_MISSING_DEL || Is unit weight sent in the items || SYSTEM
|-
| ALLOW_MULTIPLE_ADD_REFS || Allow multiple additional references for an order values will be (Y/N) || COST_CENTRE
|-
| ALLOW_POC_EDIT || Allow users to edit the POC Flag in Debrief || SYSTEM
|-
| ALLOW_TENDERED_PARAGON_TRIPS || Allow Tendered Trips in Paragon || COST_CENTRE
|-
| ALLOW_TENDERED_PARAGON_TRIPS || Allow Tendered Trips in Paragon || COST_CENTRE
|-
| ALLOW_TRP_DEL_TYPE_UPDATE || Allow Delivery type updates in the planning screen || CARRIER
|-
| ALLOW_UNLOAD_ASSET || Controls if asset records are created as part of unload || SYSTEM
|-
| ALLOW_UNSCHEDULE_SCHED_COLL || Controls if menu item Unschedule sched coll is displayed || SYSTEM
|-
| ALTERNATE_DB_NAME || Alternate DB Name || SYSTEM
|-
| ALTERNATE_ORDER_ENTRY || Validate item identifier field || COST_CENTRE
|-
| AMAZON_OWNER_CODE || Asset owner code to pass to Amazon || SYSTEM
|-
| API_CARRIER || Carrier ID for API || SYSTEM
|-
| API_EVENTS || Are events sent out via API || SYSTEM
|-
| API_TEXT_AUTHORISATION || authorisation code for API text || SYSTEM
|-
| API_TEXT_END || Time of day the system stops sending texts || SYSTEM
|-
| API_TEXT_ENDPOINT_URL || URL endpoint for API text || SYSTEM
|-
| API_TEXT_START || Time of day the system can start sending texts || SYSTEM
|-
| API_WS_ADDRESS || WebService endpoint for API events || SYSTEM
|-
| API_WS_ELUCID_ADDRESS || WebService endpoint for API events for Elucid || SYSTEM
|-
| API_WS_ELUCID_PASSWD || WebService password for API events for Elucid || SYSTEM
|-
| API_WS_ELUCID_USER || WebService username for API events for Elucid || SYSTEM
|-
| APPLY_ADDITIONAL_LOC_CHECKS || To enable additional validation checks for location entry. || SYSTEM
|-
| ARDO_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header (Unilever) || SYSTEM
|-
| ARDO_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header (Unilever) || SYSTEM
|-
| ARDO_INBOUND_PATH || Path for yet to be processed XML files (Ardo) || SYSTEM
|-
| ASSEMBLY_DU_TYPE || Assembly DU Type || COST_CENTRE
|-
| ASSET_AT_FIXED_ORIGIN || Asset At Fixed Origin || COST_CENTRE
|-
| ASSET_DEBRIEF || Indicates if assets debriefed with Items || COST_CENTRE
|-
| ASSET_FORMAT || Indicates which order item field will identify an asset || COST_CENTRE
|-
| AUTO_COMMIT_EMPTY_STOPS || Commit After Deletion of Empty Stops || COST_CENTRE
|-
| AUTO_PLAN_ORDERS || Auto Plan orders onto an existing trip || COST_CENTRE
|-
| AUTO_ROUTE_NEW_ORDERS || Automatically plan orders loaded || SYSTEM
|-
| AUTO_SCHEDULING || Auto Scheduling of orders || COST_CENTRE
|-
| AUTO_SCHED_INACTIVE_DEPOTS || List the inactive depots to exclude from the fixed drop scheduling engine. || SYSTEM
|-
| AUTO_SET_DELIVERY_TYPES || Automatically set delivery type rules || COST_CENTRE
|-
| BEIG2_FTP_DESTINATION_DIRECTORY || Directory for FTP of BirdsEye Files || SYSTEM
|-
| BEIG2_FTP_DESTINATION_IP_ADDRESS || IP for FTP of BirdsEye Files || SYSTEM
|-
| BEIG2_FTP_DESTINATION_PASSWORD || Password for FTP of BirdsEye Files || SYSTEM
|-
| BEIG2_FTP_DESTINATION_PORT || Port for FTP of BirdsEye Files || SYSTEM
|-
| BEIG2_FTP_DESTINATION_USERNAME || Username for FTP of BirdsEye Files || SYSTEM
|-
| BEIG2_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header || SYSTEM
|-
| BEIG2_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header || SYSTEM
|-
| BEIG2_INBOUND_PATH || Path for yet to be processed XML files || SYSTEM
|-
| BEIG2_OUTBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header || SYSTEM
|-
| BEIG2_OUTBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header || SYSTEM
|-
| BEIG2_OUTBOUND_PATH || Path for yet to be processed XML files || SYSTEM
|-
| BEIG_ENABLED || To enable the inbound and outbound file processing on this DB || SYSTEM
|-
| BEIG_FTP_DESTINATION_DIRECTORY || Directory for FTP of BirdsEye Files || SYSTEM
|-
| BEIG_FTP_DESTINATION_IP_ADDRESS || IP for FTP of BirdsEye Files || SYSTEM
|-
| BEIG_FTP_DESTINATION_PASSWORD || Password for FTP of BirdsEye Files || SYSTEM
|-
| BEIG_FTP_DESTINATION_PORT || Port for FTP of BirdsEye Files || SYSTEM
|-
| BEIG_FTP_DESTINATION_USERNAME || Username for FTP of BirdsEye Files || SYSTEM
|-
| BEIG_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header || SYSTEM
|-
| BEIG_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header || SYSTEM
|-
| BEIG_INBOUND_PATH || Path for yet to be processed XML files || SYSTEM
|-
| BEIG_OUTBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header || SYSTEM
|-
| BEIG_OUTBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header || SYSTEM
|-
| BEIG_OUTBOUND_PATH || Path for yet to be processed XML files || SYSTEM
|-
| BGW_AUTO_REBOOK || Indicates if auto rebook is switched on when non conformance is added || COST_CENTRE
|-
| BGW_DUMMY_WASTE || Defines Dummy waste location for BGW. || COST_CENTRE
|-
| BGW_TRAILER_SET || Defines which Trailer Types are allowed. || COST_CENTRE
|-
| BKG_APPEND_TO_ORDERS || Controls whether Bookings can append to an existing Order if the Slot is already used. || SYSTEM
|-
| BKG_AUTO_CREATE_SLOT || Creates slots if no slot exists || SYSTEM
|-
| BKG_DEF_COST || Default Cost Centre for Bookings || SYSTEM
|-
| BKG_DEF_CUST || Default Customer for Bookings || SYSTEM
|-
| BKG_DEF_DELIVERY_DEL_TYPE || Any order that are created via the interface, that are delivering to their final loc || SYSTEM
|-
| BKG_DEF_POPULATE_DEL || Any order that are created via bookings will have Del Type populated by system, specific to DSG || SYSTEM
|-
| BKG_DEF_TRUNK_DEL_TYPE || Defines the default booking trunk delivery type for any orders being delivered inti a x-dock location, default to null || SYSTEM
|-
| BKG_GEN_TI_METHOD || Defines whether Gen TI does standard, xdock of both processes, STANDARD, BOTH or XDOCK. || SYSTEM
|-
| BKG_INCREMENT || Increment exiting Bookings on import rather than overwriting || SYSTEM
|-
| BKG_REV_TI_DISBAND_INV_FIX_RTE || Should Reverse TIs disband Fixed Trips - Y or N || SYSTEM
|-
| BKG_SLOT_INACTIVATE || Controls whether existing Slots are updated to INACTIVE during a Slot Import. || SYSTEM
|-
| BKG_TYPE_9_DU_TYPE || Default DU Type for Type 9 Orders || SYSTEM
|-
| BKG_USE_BOOKING_STATUS || Defines whether booking status is being used, N, PROVISIONAL, PLANNED or CONFIRMED. || SYSTEM
|-
| BMW_DOT_CODE || Tyre Age for BMW || SYSTEM
|-
| BUF_OLD_ORD_CLEAR_DAYS || Number of days in the past to be checked by the Buffaload order clear down || SYSTEM
|-
| BWSC_GEO_ADD_NETWORK_LOV_LIMIT || When set to Y the LOV for adding network locations will only show SSS, BRANCH and PLANT locations || SYSTEM
|-
| CALCULATE_CONTRACTUAL_WEIGHT_TRG || Allow contractual weights to be re-calculated via database trigger (set to N for LFS testing) || SYSTEM
|-
| CALC_DIMEN || Calculate volume from dimensions || COST_CENTRE
|-
| CALIDUS_ASSIST_BASE_URL || URL for Calidus Assist Install || SYSTEM
|-
| CALIDUS_ASSIST_RELEASE_DB || The final part of the URL used to view the release notes, for this database, on Calidus assist. || SYSTEM
|-
| CALL_LOGGING_DATE_RANGE || Call Logging Date Range Days || SYSTEM
|-
| CAL_DEFAULT_TIME_OFFSET || Default time offset which gets added to times in Order tracking, for users viewing data in different timezone || SYSTEM
|-
| CAL_DEFAULT_TIME_ZONE || Description of timezone, used in Order Tracking form, freetext || SYSTEM
|-
| CAL_WORKING_DAY_MAP || Defines which days of the week are being worked - Sunday to Saturday, Y or N. || COST_CENTRE
|-
| CANCEL_STATUS_CHK || Only orders on Planned trips cn be cancelled || SYSTEM
|-
| CARGOWISE_BILLING_BRANCH_CODE || Billing Branch Code for Cargowise || COST_CENTRE
|-
| CARGOWISE_BRANCH || Branch for Cargowise || COST_CENTRE
|-
| CARGOWISE_CONSIGNEE || Consignee name for Cargowise || COST_CENTRE
|-
| CARGOWISE_DATABASE || Controls which cargowise database invoices are exported to || COST_CENTRE
|-
| CARGOWISE_DEPARTMENT || Department code || COST_CENTRE
|-
| CARGOWISE_DESTINATION_PORT || Destination Port || COST_CENTRE
|-
| CARGOWISE_EXPORT || Payments are exported to Cargowise || COST_CENTRE
|-
| CARGOWISE_ORIGIN_PORT || Origin Port for Cargowise || COST_CENTRE
|-
| CARRIER_API_CLIENT_CODE || Value sent across to LFE in API || SYSTEM
|-
| CARRIER_API_MANIFEST_READY_TIME || The cut-off time for the ready time for the carrier manifest (HH24:MI). || SYSTEM
|-
| CARRIER_API_WS || Endpoint for LFE API || SYSTEM
|-
| CARRIER_API_WS_AMEND || Endpoint for Carrier API updates || SYSTEM
|-
| CARRIER_API_WS_CANCEL || Endpoint for Carrier API cancellations || SYSTEM
|-
| CARRIER_INVOICE_TYPE || Carrier Invoice type || SYSTEM
|-
| CARRIER_RULES_ALL || Controls if all du types and products are checked || SYSTEM
|-
| CARRIER_WORK_REP_FOOTER_1 || The footing printed at the bottom of the CARRIER_WORK_CONF report (first part). || SYSTEM
|-
| CARRIER_WORK_REP_FOOTER_2 || The footing printed at the bottom of the CARRIER_WORK_CONF report (second part). || SYSTEM
|-
| CARR_GAZ_POSTCODE_FORMAT || For which carrier gazetteer formats will the postcode in the file exclude spaces. (List delimited with semi-colons) || SYSTEM
|-
| CARR_SRVCE_LEVEL_OFFSET_DAYS || The default minimum number of offset days to calculate the collection job date for UKMail. || COST_CENTRE
|-
| CC_FORMAT_PATTERN || Click and Collect Ext Ref format || SYSTEM
|-
| CD_DIR || Directory used for copying zipped files || SYSTEM
|-
| CFX_CARRIER || Stores the name of CFX Carrier || CARRIER
|-
| CFX_CONTROL || Is there control over which trips go to CFX || SYSTEM
|-
| CFX_CONTROL_CUSTOMER || Controls which customers are configured for CFX || CUSTOMER
|-
| CFX_EXT_LOCATION_NAME || Include the extra location name in the CFX messages (Y/N) || SYSTEM
|-
| CFX_LINES_AND_ITEMS || Are items and lines included in CFX file, S,D,B,N || SYSTEM
|-
| CFX_NEW_ORDERS || Does adding orders to a trip re-trigger the CFX file? || SYSTEM
|-
| CFX_ORDER_ADDRESSES || Are order addresses include in the CFX file || SYSTEM
|-
| CFX_ORDER_HEADER || Are orders included in CFX file || SYSTEM
|-
| CFX_ORDER_HEADER_TMS || Is the order header TMS section included in CFX file || SYSTEM
|-
| CFX_OWNING_DEPOT || Is the owning depot included in the filename? || SYSTEM
|-
| CFX_SEND || Are trips sent to CFX || SYSTEM
|-
| CFX_STATUS_CHECK || Are carriers checked at status change for CFX? || SYSTEM
|-
| CHANGE_DEBRIEF_LABELS || Controls the labels for certain items in the debrief and orders screen || SYSTEM
|-
| CHANGE_PRINTER || Is change printer displayed || COST_CENTRE
|-
| CHECK_ELUCID_IMBALANCE || Check for stock imbalance at Elucid || COST_CENTRE
|-
| CHECK_RESOURCES || Check Resource on existing trips before allocation || SYSTEM
|-
| CHG_SCHED_DATE_TRIP || A comma-separated list of trip status for which the schedule may be changed || SYSTEM
|-
| CIM_CONF_INBOUND_IDENTIFIER || Pattern for MIC Order Inbound XML || SYSTEM
|-
| CIM_CONF_INBOUND_LISTING_NAME || Filename for list of files in directory for MIC XML Order Inbound || SYSTEM
|-
| CIM_CONF_LISTING_SCRIPT_NAME || Script name for MIC XML Order Inbound || SYSTEM
|-
| CIM_ENABLED || XML Isotrak enabled for this database || SYSTEM
|-
| CIM_INBOUND_ARCH || Path for CIM XML archiving || SYSTEM
|-
| CIM_INBOUND_FAIL || Path for CIM XML failures || SYSTEM
|-
| CIM_INBOUND_IDENTIFIER || Pattern for MIC Order Inbound XML || SYSTEM
|-
| CIM_INBOUND_LISTING_NAME || Filename for list of files in directory for MIC XML Order Inbound || SYSTEM
|-
| CIM_INBOUND_MAR_IDENTIFIER || Pattern for CIM Order update XML || SYSTEM
|-
| CIM_INBOUND_PATH || Path for yet to be processed XML files from CIM || SYSTEM
|-
| CIM_LISTING_SCRIPT_NAME || Script name for MIC XML Order Inbound || SYSTEM
|-
| CIM_OUTBOUND_ARCH || Path for archiving outbound CIM XML interfaces || SYSTEM
|-
| CIM_OUTBOUND_FAIL || Path for failing outbound CIM XML interfaces || SYSTEM
|-
| CIM_OUTBOUND_PATH || Path for outbound CIM XML interfaces || SYSTEM
|-
| CLICK_CUST || Click and Collect Customer || SYSTEM
|-
| CLIENT_CODE_CHECK || Client code assessment for Location import || SYSTEM
|-
| CMD_MERGE_DOCUMENTS || The command to merge documents can be stored with any paths that need to be unset to allow the process to be performed. || SYSTEM
|-
| CMR_NOTE || Name of the CMR note report || COST_CENTRE
|-
| CMR_NOTE1 || Name of the CMR note report || COST_CENTRE
|-
| CNT_SERVICE_LEVEL_OFFSETS || Enable collection and delivery offsets for service levels (Y/N) || SYSTEM
|-
| CNT_SUMMER || Date Summer starts this current year || SYSTEM
|-
| CNT_WINTER || Date WINTER starts this current year || SYSTEM
|-
| CO2_EMMISIONS_LTR || Defines Amount of CO2 emissions per litre of fuel. || COST_CENTRE
|-
| COMBINED_DOCUMENTS_REPORT || Name of the Combined Documents report. || COST_CENTRE
|-
| CONSOLIDATE_TRIPS || Remove Duplicate lines when trip is ACCEPTED || SYSTEM
|-
| CONSOL_BY_SHIPMENT || Consolidation at Shipment level || COST_CENTRE
|-
| CONSOL_RUNNING || Indicates whether the order consolidation process is currently running. || SYSTEM
|-
| CONTINGENCY_IMPORT || Contingency Import setting || COST_CENTRE
|-
| CON_MAX_RPE || Max RPE per shipment || COST_CENTRE
|-
| COST_CENTRE_LOGO || Customer logo filename || COST_CENTRE
|-
| COST_CENTRE_POST_MATRIX || Does this cost centre use Post Matrix type charging? || COST_CENTRE
|-
| COST_CENTRE_SEGREGATION || Segregate data by cost centre || SYSTEM
|-
| CREATE_ORD_MANF || Controls if an order manifest record is created || COST_CENTRE
|-
| CSB_EXPORT_PATH || Directory where carrier self billing exports are stored. || SYSTEM
|-
| CSB_REPORT_PATH || Directory where carrier self billing reports are stored. || SYSTEM
|-
| CS_CLOSE_BY || Display trips in cust serv that are within x miles of order || SYSTEM
|-
| CS_DEFAULT_BOOKING_STATUS_OLD || Customer Services Default Booking Status || SYSTEM
|-
| CS_DEFAULT_ORDER_STATUS_OLD || Customer Services Default Order Status || SYSTEM
|-
| CTMS_CITD_FTP_DESTINATION_DIRECTORY || CITD Destination Directory || SYSTEM
|-
| CTMS_CITD_FTP_DESTINATION_IP_ADDRESS || CITD Destination IP Address || SYSTEM
|-
| CTMS_CITD_FTP_DESTINATION_PASSWORD || CITD Destination Directory Password || SYSTEM
|-
| CTMS_CITD_FTP_DESTINATION_PORT || CITD Destination Directory Port || SYSTEM
|-
| CTMS_CITD_FTP_DESTINATION_USERNAME || CITD Destination Directory username || SYSTEM
|-
| CTMS_ESI_FTP_DESTINATION_DIRECTORY || Directory for FTP of Outbound Trips Files. || SYSTEM
|-
| CTMS_ESI_FTP_DESTINATION_IP_ADDRESS || IP Address for FTP of Outbound Trips Files. || SYSTEM
|-
| CTMS_ESI_FTP_DESTINATION_PASSWORD || Password for FTP of Outbound Trips Files. || SYSTEM
|-
| CTMS_ESI_FTP_DESTINATION_PORT || Port for FTP of Outbound Trips Files. || SYSTEM
|-
| CTMS_ESI_FTP_DESTINATION_USERNAME || Username for FTP of Outbound Trips Files. || SYSTEM
|-
| CTMS_MANF_FTP_DESTINATION_DIRECTORY || Manifest Destination Directory || SYSTEM
|-
| CTMS_MANF_FTP_DESTINATION_IP_ADDRESS || Manifest Destination IP Address || SYSTEM
|-
| CTMS_MANF_FTP_DESTINATION_PASSWORD || Manifest Destination Directory Password || SYSTEM
|-
| CTMS_MANF_FTP_DESTINATION_PORT || Manifest Destination Directory Port || SYSTEM
|-
| CTMS_MANF_FTP_DESTINATION_USERNAME || Manifest Destination Directory username || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_ARCH || File path for Outbound Trips. || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_ARCH_TEST || File path for Outbound Trips archive. || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_FILENAME || Filename for Outbound Trips. || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_FLAG || Flag to permit the creation of Outbound Trips (Y/N). || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_MSG_TYPE || The Message Type of the Outbound Trips (Y/N). || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_OWNING_DEPOT || The owning depot of the Outbound Trips (Y/N). || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_PATH || File path for Outbound Trips. || SYSTEM
|-
| CTM_ACCEPT_TRIP_UPDATE_DATA || Should Trip data be entered when user Accepts a trip - Y or N || CARR_GROUP
|-
| CTM_ACCEPT_TRIP_UPDATE_DATA || Should Trip data be entered when user Accepts a trip - Y or N || CARRIER
|-
| CTM_DISP_SCHEDTRIP_OR_BOL || Display Sched/Trip or BOL in Carrier Trip Management - SCHEDTRIP or BOL || CARRIER
|-
| CTM_MSG_CHASE_AFTER || Time(mins) after which a message should be sent to a carrier after failure to respond || CARRIER
|-
| CTM_MSG_CHASE_AFTER || Time(mins) after which a message should be sent to a carrier after failure to respond || CARR_GROUP
|-
| CTM_REFRESH_TIMER_INTERVAL || Automatic Timer Refresh Interval for Carrier Trip Management - Enter value in mins || CARRIER
|-
| CTM_SHOW_TRIP_TIMES || Show trip times in Carrier Trip Management form - Value is Y or N || CARRIER
|-
| CUSTOMER_CONTROLLED_ORDER_REVENUE_ACTUALS || Y/N- greater of planned and actual quantity || SYSTEM
|-
| CUSTOMER_LOGO || Customer logo filename || CUSTOMER
|-
| CUSTOMER_SERVICE_LEVEL || Enable Customer Specific Service Levels || SYSTEM
|-
| CUST_DU_CONS_SCHED || Consolidate DU By Schedule || CUSTOMER
|-
| CUST_UPDATE_ORDER_LINES || Update Orders || CUSTOMER
|-
| DEBRIEF_DRIVERS_HOURS || Enter Drivers hours worked at debrief || COST_CENTRE
|-
| DEBUG || Debug enabled ? - Y or N || SYSTEM
|-
| DEFAULT_DEL_TYPE || Default Delivery Type || COST_CENTRE
|-
| DEFAULT_DU_TYPE || Default Du Type for NHS || SYSTEM
|-
| DEFAULT_ORACLE_DIRECTORY || Stores System directory for TMP_DIR in EXPORT production || SYSTEM
|-
| DEFAULT_PART_NO || Default part Number || CUSTOMER
|-
| DEFAULT_PAR_DEL_TYPE || Default Del type for paragon || COST_CENTRE
|-
| DEFAULT_PROD_TYPE || Default Product Type || COST_CENTRE
|-
| DEFAULT_REBOOK_DEL_TYPE || Default Del type for Rebook || COST_CENTRE
|-
| DEFAULT_SLOT_DELETION_DAYS || Number of days after which an inactive slot is deleted || SYSTEM
|-
| DEFAULT_TRAILER_TYPE || Default Trailer Type || COST_CENTRE
|-
| DEFAULT_UNSCHEDULED_CARRIER || Indicates a default carrier may be used to print labels for unscheduled orders during packing. || SYSTEM
|-
| DEF_AQ_SCHEMA || Schema for use when starting advanced queues || SYSTEM
|-
| DEF_CALLOUT_DEL_TYPE || Default Callout Delivery Type || SYSTEM
|-
| DEF_COST || Default Cost Centre for NHSBT || SYSTEM
|-
| DEF_INSPECT_DEL_TYPE || Default Inspection Delivery Type || SYSTEM
|-
| DEF_INSPECT_SERVICE || Default Inspection Service Level || SYSTEM
|-
| DEF_SERVICE_LEVEL || Default service level for orders when null || COST_CENTRE
|-
| DELCONF_FTP_DESTINATION_DIRECTORY || Directory for FTP of Microlise Files || SYSTEM
|-
| DELCONF_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Microlise Files || SYSTEM
|-
| DELCONF_FTP_DESTINATION_PASSWORD || Password for FTP of Microlise Files || SYSTEM
|-
| DELCONF_FTP_DESTINATION_PORT || Port for FTP of Microlise Files || SYSTEM
|-
| DELCONF_FTP_DESTINATION_USERNAME || Username for FTP of Microlise Files || SYSTEM
|-
| DELETE_ALL_PMTS_AT_PLANNED || Delete All payments for a trip at Planned Status || COST_CENTRE
|-
| DELIVERY_CUTOFF || Cost Centre Delivery Cut Off || COST_CENTRE
|-
| DELIVERY_NOTE || Name of the delivery note report || COST_CENTRE
|-
| DEL_LEVEL_PARAM || Level of data reported in the Delivery docs || COST_CENTRE
|-
| DEL_TIME_OFFSET || The earliest delivery time ahead of the requested delivery date and time sent from PULSE || COST_CENTRE
|-
| DESPATCH_EMAIL || Create Despatch email control record || SYSTEM
|-
| DESPATCH_REPORT || Name of the despatch note report printed from the trip tree || COST_CENTRE
|-
| DHL_INV_EMAIL || List of emails (sep with ;) for monthly DHL Invoicing data || SYSTEM
|-
| DIM_CHARGE_WEIGHT || Kg Value for dimensional weight calculation || CUSTOMER
|-
| DIRECT_CARRIER || Stores the carrier ID that will go direct and not via a location - the via routing code will not be displayed. || SYSTEM
|-
| DISABLE_ITEM_ID || Disable the item identifier in order entry || COST_CENTRE
|-
| DISPLAY_DESPATCHED_RPE || Display the Actual Despatched RPE Quantity in the Order Detail and Trip Debrief screens? || COST_CENTRE
|-
| DISPLAY_PARAGON_LOC_ID || Display Paragon ID and EXT Ref in Locations Screen || SYSTEM
|-
| DISPLAY_PO_REF_REPORT || PO Ref to be displayed in delivery note || CUSTOMER
|-
| DISPLAY_WIC_CODE || Determines if the delivery type of the order for the customer contains a WIC Code and whether the title will be displayed in the Order Details screen || CUSTOMER
|-
| DISTRIBUTION_OFF || Is revenue distributed as part of trip charges? || SYSTEM
|-
| DOM_DIMS || Domestic version of dimensions functionality || COST_CENTRE
|-
| DONT_SEND_PLANNED_TO_WEBFLEET || When the parameter is set control record is not sent for PLANNED status || COST_CENTRE
|-
| DSG_ALLOW_BKG_IN_PAST || Allow Bookings in the past from the Dixons Bookings interface - Y or N. || SYSTEM
|-
| DSG_DEF_DU_TYPE || Default DU Type for Orders created via the Dixons Bookings interface. || SYSTEM
|-
| DSG_DEF_PRD_TYPE || Default Product Type for Orders created via the Dixons Bookings interface. || SYSTEM
|-
| DSG_TRIP_DTL_PATH || File path for DSG Trip detail messages. || SYSTEM
|-
| DU_PARAMS || DUs may be used as charge parameters || SYSTEM
|-
| EARLY_ARR_REASON_CODE || Early reason code for trip deliveries || SYSTEM
|-
| EDI1214_DELIMITER || File delimiter in EDI1214 file || SYSTEM
|-
| EDI1214_ENDOFLINE || File end of line delimiter in EDI1214 file || SYSTEM
|-
| EDI1214_SYSTEM || T for test P for Prod || SYSTEM
|-
| EDI_CN_ENTITY_CODE || Consignment Entity code for Invoice XML || SYSTEM
|-
| EDI_INVOICE_MSG_TYPE || Invoice Message type for Invoice XML || SYSTEM
|-
| EDI_MESSAGE_VERSION || Message Version for Invoice XML || SYSTEM
|-
| EDI_SH_ENTITY_CODE || Shipment Entity code for Invoice XML || SYSTEM
|-
| EDI_STRUCTURE_VERSION || Structure version for Invoice XML || SYSTEM
|-
| EFX_CANC_ARCH || Archive folder for EFX cancellation requests || SYSTEM
|-
| EFX_CANC_FTP_DESTINATION_DIRECTORY || Directory for FTP of Microlise Files || SYSTEM
|-
| EFX_CANC_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Microlise Files || SYSTEM
|-
| EFX_CANC_FTP_DESTINATION_PASSWORD || Password for FTP of Microlise Files || SYSTEM
|-
| EFX_CANC_FTP_DESTINATION_PORT || Port for FTP of Microlise Files || SYSTEM
|-
| EFX_CANC_FTP_DESTINATION_USERNAME || Username for FTP of Microlise Files || SYSTEM
|-
| EFX_DEADLINE_HOURS || EFX Default Deadline Hours || SYSTEM
|-
| EFX_DEFAULT_CARRIER || EFX Default Carrier || SYSTEM
|-
| EFX_DEF_WEIGHT || Default EFX weight per RPE, used in calculation of trip weight for EFX export || SYSTEM
|-
| EFX_EXCLUDE_CARR_TYPE_DEB || EFX Exclude Carrier Type from Debrief Messages || COST_CENTRE
|-
| EFX_EXT_LOCATION_NAME || Include the extra location name in the EFX messages (Y/N) || SYSTEM
|-
| EFX_FAILURE_PATH || File path for failed EFX filed || SYSTEM
|-
| EFX_FORMAT || EFX Format || SYSTEM
|-
| EFX_FTP_DESTINATION_DIRECTORY || Directory for FTP of Microlise Files || SYSTEM
|-
| EFX_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Microlise Files || SYSTEM
|-
| EFX_FTP_DESTINATION_PASSWORD || Password for FTP of Microlise Files || SYSTEM
|-
| EFX_FTP_DESTINATION_PORT || Port for FTP of Microlise Files || SYSTEM
|-
| EFX_FTP_DESTINATION_USERNAME || Username for FTP of Microlise Files || SYSTEM
|-
| EFX_IDENTIFIER || EFX file identifier || SYSTEM
|-
| EFX_INBOUND_LISTING_NAME || Filename for list of files in directory for EFX XML Trip Inbound || SYSTEM
|-
| EFX_INC_TRIP_VEH_TYPE || Include the vehicle type for the trip stop from EFX (Y/N) || COST_CENTRE
|-
| EFX_LISTING_SCRIPT_NAME || Script name foe EFX XML Inbound || SYSTEM
|-
| EFX_PATH || File path for EFX Inbound messages || SYSTEM
|-
| EFX_PROCESSED_PATH || File path for processed EFX files || SYSTEM
|-
| EFX_SEND_SUB || Send Sub-Contracted Trips to EFX when they go to ACCEPTED status || SYSTEM
|-
| EFX_TRIP_ARCH || Archive folder for EFX requests || SYSTEM
|-
| EFX_TRIP_DTL_PATH || File path for EFX Trip detail messages. || SYSTEM
|-
| EFX_XML_DEB_DELAY || EFX XML Outbound second debrief message delay in minutes || SYSTEM
|-
| EFX_XML_DEB_TRIP_STATUS || Determine which trip status generates debrief messages to EFX || COST_CENTRE
|-
| EFX_XML_INC_COUNTRYCODE || Will XML messages for EFX include COUNTRYCODE for load and drop locations (Y/N). || COST_CENTRE
|-
| EFX_XML_SYSTEM || EFX XML Outbound System Name || COST_CENTRE
|-
| EFX_XML_TYPE || EFX Type || COST_CENTRE
|-
| EFX_XML_UOM || EFX XML Outbound UOM || COST_CENTRE
|-
| ELUCID_API_PROXY || Proxy Sever Elucid || SYSTEM
|-
| ELUCID_WS_ADDRESS || Elucid WS Address || SYSTEM
|-
| ELUCID_WS_PWD || Elucid WS User || SYSTEM
|-
| ELUCID_WS_USER || Elucid WS User || SYSTEM
|-
| EMAIL_ACTUALS_FAILURE || Email address for Actuals Failure Email || CUSTOMER
|-
| EMAIL_CUSTOMER_CARE || Customer Care email address || SYSTEM
|-
| EMAIL_CUST_SERVICES_RECIPIENT || The address for the recipient of the emails. || COST_CENTRE
|-
| EMAIL_OWN_PACKAGE || Is an e-mail required for an order that contains own packaging (Y/N)? || COST_CENTRE
|-
| ENABLE_SEND_BORDERO || Send Bordero Messages || CUSTOMER
|-
| ENGINE_RUNNING || Indicates whether the Scheduling Engine is running || SYSTEM
|-
| EPL_CUST_REF || VPF Test param for 317770 || SYSTEM
|-
| EPOD_COLLECT_STOCK || To exclude sending a loading stop to EPOD which does not have an order for van stock or to fit new tyres(Y/N) || SYSTEM
|-
| EPOD_COMPLETED_UPDATE || Are epod updates sent for COMPLETED trips? || SYSTEM
|-
| EPOD_COMPLETE_ON_LOAD_UPDATE || Complete Trip when RTD job sent back from C-ePOD for load updates || COST_CENTRE
|-
| EPOD_COMPLETE_ON_RTD || Complete Trip when RTD job sent back from C-ePOD || COST_CENTRE
|-
| EPOD_CONCATENATE_JOB_INSTR || Concatenate the special instructions and the order comments for the collection/delivery location as the job instructions (Y/N). || COST_CENTRE
|-
| EPOD_CONSOLIDATION_LEVEL || Level of job consolidation for C-ePOD || COST_CENTRE
|-
| EPOD_CONTACT_DELIMITER || EPOD contact delimiter || COST_CENTRE
|-
| EPOD_CONTAINER_CODE1 || What populates this field in EPOD DIMS for dimensions(default) or PARTS for the part numbers if present || COST_CENTRE
|-
| EPOD_CONTAINER_CODE2 || What populates this field in EPOD DIMS for dimensions or PARTS for the part numbers if present (default) || COST_CENTRE
|-
| EPOD_CONTAINER_CODE3 || What populates this field in EPOD DIMS for dimensions or PARTS (for the part numbers if present) default NULL || COST_CENTRE
|-
| EPOD_CONTAINER_DESCRIPTION || What populates this field in EPOD COMMODITY for the item commodity(default) DESCRIPTION for item desc or PROD_DESC for the prod AKA code and item desc || COST_CENTRE
|-
| EPOD_CUSTOMER_INVOICE || Include an EPOD_CUSTOMER_INVOICE section within the EPOD_CUSTOMERS section for the service jobs (Y/N) || SYSTEM
|-
| EPOD_CUSTOMER_INVOICE_SXU || To include the EPOD_CUSTOMER section || SYSTEM
|-
| EPOD_IGNORE_COL_SIG_DEPOT || Controls is signatures are ignored for cols at depots || COST_CENTRE
|-
| EPOD_IGNORE_COL_SIG_DEPOT || Controls is signatures are ignored for cols at depots || SYSTEM
|-
| EPOD_ITEM_LEVEL || Send Containers (IC for items or LC for lines) or Products (IP for item or LP for lines) to EPOD || SYSTEM
|-
| EPOD_JOB_GROUP_FORMAT || Indicates whether the value passed in the EPL Job Group to EPOD is the Cost Centre (CC), Carried ID (CI), Customer Group (CG) or Customer (CU). || SYSTEM
|-
| EPOD_JOB_RETAIN_TIMES || Retain the actual times for the trip stop for the job (Y/N). || COST_CENTRE
|-
| EPOD_OWNER_CONFIG || C-ePOD Owner Configuration || COST_CENTRE
|-
| EPOD_PREVENT_ASSET_TRACK || Prevents asset tracking through EPOD || COST_CENTRE
|-
| EPOD_SEND_CLOSING_TIME || Send Location closing time to C-ePOD || SYSTEM
|-
| EPOD_SEND_COD_NAME || Send COD Name to C-ePOD values will be (Y/N) || COST_CENTRE
|-
| EPOD_SEND_CONTACT_INFO || Send Contact information to C-ePOD || COST_CENTRE
|-
| EPOD_SEND_DRIVER || Is the driver username included? (Y/N) || SYSTEM
|-
| EPOD_SEND_EPL_LAT_LONG || Send EPL_LAT and EPL_LONG for job addresses (Y/N) || COST_CENTRE
|-
| EPOD_SEND_EQUIPMENT || Controls if equipment requirements are sent to EPOD || SYSTEM
|-
| EPOD_SEND_ITEM_AKA_CODE || Send EPL_PRODUCT_CODE with the item AKA code (Y/N) || COST_CENTRE
|-
| EPOD_SEND_LOADING_TYPE || Send Loading Type to C-ePOD || COST_CENTRE
|-
| EPOD_SEND_RVA_UNIT_TYPE || Send EPL_UNIT_TYPE as the vehicle configuration ID for the services (Y/N) || COST_CENTRE
|-
| EPOD_SET_ACTUAL_SIGNATORY_BLANK || Set C-ePOD actual signatory to blank (Y/N)? || SYSTEM
|-
| EPOD_SIGNATORY || Controls if signatory is stored from C-ePOD || COST_CENTRE
|-
| EPOD_SIGNATURE_STORAGE || Store signature received from C-ePOD || COST_CENTRE
|-
| EPOD_SITE_ID_FORMAT || Indicates whether the value passed in the EPL Site ID to C-ePOD is the Database Name(DB), Cost Centre (CC) or Carrier ID (CI). || SYSTEM
|-
| EPOD_TNC_STORAGE || Store TNC declaration from C-ePOD || COST_CENTRE
|-
| EPOD_UPDATE_ETA || Update Later stops ETA on receipt from C-ePOD || COST_CENTRE
|-
| EPOD_VIEW_POD_URL || URL for C-ePOD Documents || SYSTEM
|-
| EPOD_WS_ADDRESS || C-ePOD Web Service End Point || SYSTEM
|-
| EPOD_WS_ADDRESS_NHSPRD || C-ePOD Web Service End Point || SYSTEM
|-
| EPOD_WS_MESSAGE_FORMAT || C-ePOD message format - can either be PARCEL, BULK, RETAIL, MODE1, MODE2 or DELTYPE to define where fields are sent in the web service message || SYSTEM
|-
| EPOD_WS_PASSWORD || C-ePOD Web Service Login Password || SYSTEM
|-
| EPOD_WS_TIMEOUT || Number of minutes before a WS message will be set to Held || SYSTEM
|-
| EPOD_WS_USERNAME || C-ePOD Web Service Login Username || SYSTEM
|-
| ETA_LOAD_TIME || Load time in minutes to be used in ETA calculation || SYSTEM
|-
| EXE_ARCH_DIRECTORY || Destination directory EXE rcp || SYSTEM
|-
| EXE_DESTINATION_DIRECTORY || Destination directory EXE rcp || SYSTEM
|-
| EXE_DESTINATION_IP_ADDRESS || Destination for EXE rcp || SYSTEM
|-
| EXE_DESTINATION_PASSWORD || Password for EXE rcp || SYSTEM
|-
| EXE_DESTINATION_USERNAME || Username for EXE rcp || SYSTEM
|-
| EXE_SOURCE_DIRECTORY || Source directory for EXE rcp || SYSTEM
|-
| EXTERNAL_CALL_LOGGING || Call Logging External User || SYSTEM
|-
| FASTER_SCANNING || Controls if the Planner splits order for planning || SYSTEM
|-
| FC_ACCESS_TOKEN || The FleetCheck Access Token, provided by FleetCheck. || SYSTEM
|-
| FC_FLEET_KEY || The FleetCheck fleet being updated by C-TMS. || SYSTEM
|-
| FC_TIMEOUT || The amount of time to wait when trying to update FleetCheck. || SYSTEM
|-
| FC_URL || The base URL for the FleetCheck system. || SYSTEM
|-
| FILE_INTERFACE_DIR || File Interface Directory || SYSTEM
|-
| FINDTRIP_URL || Find trip webservice URL || SYSTEM
|-
| FIT_PRESSURE_HIGH || FIT Report: Pressure Analysis High || SYSTEM
|-
| FIT_PRESSURE_LOW || FIT Report: Pressure Analysis Low || SYSTEM
|-
| FIT_PRESSURE_VHIGH || FIT Report: Pressure Analysis Very High || SYSTEM
|-
| FIT_PRESSURE_VLOW || FIT Report: Pressure Analysis Very Low || SYSTEM
|-
| FIT_TREAD_REPLACE_NEXT || FIT Report: RTD in Next Month || SYSTEM
|-
| FIT_TREAD_REPLACE_NEXT2 || FIT Report: RTD in Next 2 Months || SYSTEM
|-
| FIT_TREAD_REPLACE_NOW || FIT Report: RTD in Current Month || SYSTEM
|-
| FIXED_IMPORT || Customer is using fixed order import || CUSTOMER
|-
| FIX_NULL_BOOKING_REF || Set booking Ref to Null for fixed schedules || COST_CENTRE
|-
| FLEXIPOD || Set to Y to indicate the FleXipod interface is active || SYSTEM
|-
| FLEXIPOD_CARRIERS || Set to Y indicates the Carrier can control if a trip is sent to FleXipod || SYSTEM
|-
| FLEXIPOD_CLIENTNUM || FleXipod ClientNum sent in interface || SYSTEM
|-
| FLEXIPOD_DEPOTS || Set to Y indicates the Depot can control if a trip is sent to FleXipod || SYSTEM
|-
| FLEXIPOD_DROP || Determines the Drop level STOP-OMS or ITEM || SYSTEM
|-
| FLEXIPOD_PASSWORD || FleXipod Webservice password || SYSTEM
|-
| FLEXIPOD_SCAN_LEVEL || 1,2 or 3 to indicate line or item level scanning || SYSTEM
|-
| FLEXIPOD_SCAN_TYPE || Contents and items || SYSTEM
|-
| FLEXIPOD_SPLIT || Are orders to be split? || SYSTEM
|-
| FLEXIPOD_SYSTEM || FleXipod SYSTEM ID sent in interface || SYSTEM
|-
| FLEXIPOD_USERCODE || FleXipod Webservice usercode || SYSTEM
|-
| FLEXIPOD_USERNAME || FleXipod Webservice username || SYSTEM
|-
| FLEXIPOD_WEBSERVICE || FleXipod webservice endpoint URL || SYSTEM
|-
| FLEXIPOD_WEBSERVICE_TASK || FleXipod webservice endpoint URL for Tasks || SYSTEM
|-
| FLEXIPOD_WEBSERVICE_UI || FleXipod webservice endpoint URL || SYSTEM
|-
| FORCE_ITEM_SCAN || Is driver required to scan at debrief? || SYSTEM
|-
| FORMS_ALERT_MESSAGE_MODULE || Alert Messages Form || SYSTEM
|-
| FORMS_CS_PATH || Forms Client Server Path || SYSTEM
|-
| FORMS_DEFAULT_MODULE || Default Module accessed when C-TMS is started - ORI_STATS, ORI_STATS_JRL or ORI_STATS_WATERFALL || SYSTEM
|-
| FORMS_DEFAULT_ORDERS_MODULE || Default Orders Form - ORDERS_WIDE, ORDERS or ORD_ENTRY_TARGET || SYSTEM
|-
| FORMS_DEFAULT_TRIP_MODULE || Default Trip Form - TRIPSUM or TRIPSUM_JRL || SYSTEM
|-
| FORMS_PASSWORD_MODULE || Password Change form. || SYSTEM
|-
| FORMS_PATH || Forms Path || SYSTEM
|-
| FORMS_WEB_PATH || Determines where on the server forms are being obtained from for this database || SYSTEM
|-
| FORMS_WEB_PATH_BLUE || Blue forms || SYSTEM
|-
| FTP_SERVER_LOG || Create server logs for FTP send to prove delivery || SYSTEM
|-
| FTP_TRANSMIT_TIME_LIMIT || Determines the time limit (in minutes) above which a file being transferred is considered to be failed instead of pending. || SYSTEM
|-
| FTP_WRITE_LOC || FTP Write location || SYSTEM
|-
| FULL_LOAD_GROUPAGE_FLAG || Controls whether Full load \ Groupage flag is checked when changing Trip status || SYSTEM
|-
| FULL_LOAD_THRESHOLD || Maximum weight threshold for any FTL || SYSTEM
|-
| GEL_DU || Identifies which du types include GEL || COST_CENTRE
|-
| GEO_ASKGEO_PROXY || Proxy server setting for AskGEO web server || SYSTEM
|-
| GEO_ASKGEO_TIMEOUT || AskGEO web server time out || SYSTEM
|-
| GEO_ASKGEO_URL || AskGEO web server URL || SYSTEM
|-
| GEO_DEFAULT_COUNTRY || Default country for new locations || SYSTEM
|-
| GEO_DEFAULT_DEPOT || Default depot for new locations || SYSTEM
|-
| GEO_DEFAULT_LOAD_RATE || Default Loading Rate for locations. || SYSTEM
|-
| GEO_DEFAULT_SESSION_COUNTRY || Default Country Code for locations created from sessions || SYSTEM
|-
| GEO_DEFAULT_UNLOAD_RATE || Default Unloading Rate for locations. || SYSTEM
|-
| GEO_DRIVE_TIME_DTL_ONLY || Allows TRANSIT DAYS to be be overridden by Drive Time in GEO_NET, YES or NO. || SYSTEM
|-
| GEO_DT_ADDR_FMT || Determines the format of the Address string passed to external Map application, e.g. MapPoint, for Address Location Matching || SYSTEM
|-
| GEO_DT_CALC || Determines the distance and time calculation methods - NET, NETR, LINE, PCMS || SYSTEM
|-
| GEO_DT_CALC_ORD || Determines distance calculation method for orders || COST_CENTRE
|-
| GEO_DT_CALC_PAR_INT || Override for dist/time method for Paragon Interface || SYSTEM
|-
| GEO_DT_DFLT_SPEED || Default truck speed assumed in approximation of driving time. || SYSTEM
|-
| GEO_DT_DISTANCE_FACTOR || "Wiggle" factor applied to straight-line distance to approximate Road distance. || SYSTEM
|-
| GEO_DT_DISTANCE_UNITS || Current distance unit - miles or kilometres || SYSTEM
|-
| GEO_DT_DISTANCE_UNITS || Current distance unit - miles or kilometres || COST_CENTRE
|-
| GEO_DT_PCMS_TIMEOUT || Number of seconds to wait for PCMS to calculate distance and time. || SYSTEM
|-
| GEO_DT_PCMS_TIMEOUT_ORD || Number of seconds to wait for NAVTEQ for order distance calculation || COST_CENTRE
|-
| GEO_HERE_DISTANCE_TYPE || Set to either miles or leave blank || COST_CENTRE
|-
| GEO_HIDE_SWAP_LOCATIONS || It is to exclude SWAP locations from list of Location_ID in location maintenance screen || SYSTEM
|-
| GEO_KEEP_LATLONG || Keep Lat-Long when entered || SYSTEM
|-
| GEO_LOCATION_STACK || Switch on stack specific location fields || SYSTEM
|-
| GEO_LOC_ADD1_MAND || Address Line 1 must be entered || SYSTEM
|-
| GEO_LOC_CUST_CTRY || Enable a customer to be specified for a location to be maintained for one of multiple countries? (‘Y/N) || SYSTEM
|-
| GEO_LOC_IMP_POST_PLAN || Populate the postal and planning regions using rules in country and static data when doing location import || SYSTEM
|-
| GEO_LOC_PCDE_MAND || Post code must be entered || SYSTEM
|-
| GEO_LOC_RADIAL_ROUTES || Indicates if a radial route will be stored for the location based on the fixed route stop for collection/delivery (Y/N). || SYSTEM
|-
| GEO_LOC_TOWN_MAND || Town must be entered || SYSTEM
|-
| GEO_MAX_INVENTORY || Maximum inventory threshold for warning || SYSTEM
|-
| GEO_MIN_INVENTORY || Minimum inventory threshold for warning || SYSTEM
|-
| GEO_NAVTEQ_AJAX_LOGIN || NAVTEQ Ajax Login || SYSTEM
|-
| GEO_NAVTEQ_CITY_SPEED || City Road Speed for NAVTEQ || SYSTEM
|-
| GEO_NAVTEQ_COUNTRY_SPEED || Country Road Speed for NAVTEQ || SYSTEM
|-
| GEO_NAVTEQ_FAST_SHORT || Fastest or Shortest Method for NAVTEQ Route calculation || SYSTEM
|-
| GEO_NAVTEQ_JAVA || NAVTEQ Java || SYSTEM
|-
| GEO_NAVTEQ_LOGIN || NAVTEQ Login || SYSTEM
|-
| GEO_NAVTEQ_MAP_DIR || NAVTEQ Maps Folder || SYSTEM
|-
| GEO_NAVTEQ_MAP_SHOW || NAVTEQ Maps Folder for WEBSHOW || SYSTEM
|-
| GEO_NAVTEQ_MOTOR_SPEED || Motorway Speed for NAVTEQ || SYSTEM
|-
| GEO_NAVTEQ_PROXY || Proxy Sever for NAVTEQ || SYSTEM
|-
| GEO_NAVTEQ_URL_LOC || NAVTEQ Location URL || SYSTEM
|-
| GEO_NAVTEQ_URL_MAP || NAVTEQ Map URL || SYSTEM
|-
| GEO_NAVTEQ_URL_MAP_ALL || NAVTEQ Map URL || SYSTEM
|-
| GEO_NAVTEQ_URL_ROUTE || NAVTEQ Route URL || SYSTEM
|-
| GEO_NET_TABLE || Network Table || SYSTEM
|-
| GEO_NLP_ALT_PROXY || Proxy Sever for NLP 11g || SYSTEM
|-
| GEO_NLP_ALT_URL_LOC || Alternative URL for Geocode service on NLP system || SYSTEM
|-
| GEO_NLP_ALT_URL_ROUTE || Alternative URL for Calculate Route service on NLP system || SYSTEM
|-
| GEO_NLP_API_KEY || API Key for NLP || SYSTEM
|-
| GEO_NLP_APP_LOC || App_ID for Geo Code call to NLP system || SYSTEM
|-
| GEO_NLP_APP_MAP || App for Map service on NLP system || SYSTEM
|-
| GEO_NLP_APP_ROUTE || App_ID for Route call to NLP system || SYSTEM
|-
| GEO_NLP_CAR_TRUCK || Nokia travel time calculations to be based on a truck or a car || SYSTEM
|-
| GEO_NLP_DISTRICT_PARAM || Control which field (TOWN/LINE3) is sent as district to Nokia || SYSTEM
|-
| GEO_NLP_FORMAT_FREETEXT || NLP Freetext Format || SYSTEM
|-
| GEO_NLP_FORMAT_QUALIFIED || NLP Qualified Format || SYSTEM
|-
| GEO_NLP_JAVA || Java for NLP to create PDF || SYSTEM
|-
| GEO_NLP_JS_MULTI || Location for the show map multiple map printout in JavaScript || SYSTEM
|-
| GEO_NLP_LATLONG_ACCURACY || NLP Geocode Accuracy || SYSTEM
|-
| GEO_NLP_MAP_DIR || Directory for PDF of maps || SYSTEM
|-
| GEO_NLP_MAP_SHOW || Directory for PDF of maps || SYSTEM
|-
| GEO_NLP_MOTORWAY || Motorway Preference for NLP distance calculations || COST_CENTRE
|-
| GEO_NLP_PROXY || Proxy Sever for NLP || SYSTEM
|-
| GEO_NLP_TOKEN_LOC || NLP Geocode Token || SYSTEM
|-
| GEO_NLP_TOKEN_MAP || Login token for Map service on NLP system || SYSTEM
|-
| GEO_NLP_TOKEN_ROUTE || Login token for Calculate Route service on NLP system || SYSTEM
|-
| GEO_NLP_URL_LOC || Nokia Location Platform Geocode URL || SYSTEM
|-
| GEO_NLP_URL_MAP || URL for Map service on NLP system || SYSTEM
|-
| GEO_NLP_URL_ROUTE || URL for Calculate Route service on NLP system || SYSTEM
|-
| GEO_NLP_USE_ALTERNATE || Use Alternative URLS and Proxy || SYSTEM
|-
| GEO_POP_PLANNING_REGION || Controls whether the Planning Region is populated from the look up table - Y or N. || SYSTEM
|-
| GEO_SLOT_IMPORT_FILE || Name of Slot Import file || SYSTEM
|-
| GEO_SLOT_IMPORT_PATH || Slot Import path || SYSTEM
|-
| GEO_SUBURB || Town must match a Zone || SYSTEM
|-
| GEO_TOMTOM_ACCOUNT || TomTom account || SYSTEM
|-
| GEO_TOMTOM_ARCH_DAYS || Number of days to keep the TomTom data before archiving || SYSTEM
|-
| GEO_TOMTOM_AUTO_AREA_RADIUS || Radius (m) of temporary TomTom areas || SYSTEM
|-
| GEO_TOMTOM_FENCE_CARR || List of carriers to test TomTom Geo-fence breaks || SYSTEM
|-
| GEO_TOMTOM_FENCE_VAR || Variation of time in hours from planned for TomTom Geo-fence breaks to update stop || SYSTEM
|-
| GEO_TOMTOM_FENCE_VEH || List of vehicles to test TomTom Geo-fence breaks || SYSTEM
|-
| GEO_TOMTOM_GETMSGS_URL || TomTom web service || SYSTEM
|-
| GEO_TOMTOM_LATE_MINS || TomTom Late Reason Variance Minutes || SYSTEM
|-
| GEO_TOMTOM_LATE_REASON || TomTom Late Reason Code || SYSTEM
|-
| GEO_TOMTOM_ORDER_DEBRIEF || List of Delivery types allowing change || CARRIER
|-
| GEO_TOMTOM_PASSWORD || TomTom password || SYSTEM
|-
| GEO_TOMTOM_PROXY || Proxy server setting for TomTom web server || SYSTEM
|-
| GEO_TOMTOM_SENDORD_URL || TomTom web service to send orders || SYSTEM
|-
| GEO_TOMTOM_SEND_CUST_REF || Send order customer ref to TomTom || SYSTEM
|-
| GEO_TOMTOM_TIMEOUT || TomTom web server time out || SYSTEM
|-
| GEO_TOMTOM_TRIP_COMPLETE || TomTom to automatically complete trips || SYSTEM
|-
| GEO_TOMTOM_TRIP_EN-ROUTE || Set trip status to EN-ROUTE from TomTom || SYSTEM
|-
| GEO_TOMTOM_USERNAME || TomTom username || SYSTEM
|-
| GEO_VALIDATE_LOCATION_NAME || Indicates whether the system should check for duplicate location names (as well as IDs) when creating/updating locations || SYSTEM
|-
| GLO_CUSTOMER || Customer for Unilever Gloucester || SYSTEM
|-
| GLO_FTP_DESTINATION_DIRECTORY || Directory for FTP of Unilever Files || SYSTEM
|-
| GLO_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Unilever Files || SYSTEM
|-
| GLO_FTP_DESTINATION_PASSWORD || Password for FTP of Unilever Files || SYSTEM
|-
| GLO_FTP_DESTINATION_PORT || Port for FTP of Unilever Files || SYSTEM
|-
| GLO_FTP_DESTINATION_USERNAME || Username for FTP of Unilever Files || SYSTEM
|-
| GLO_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header (Unilever) || SYSTEM
|-
| GLO_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header (Unilever) || SYSTEM
|-
| GLO_INBOUND_PATH || Path for yet to be processed XML files (Unilever) || SYSTEM
|-
| GLO_LOCATION || Location for Unilever Gloucester || SYSTEM
|-
| GLO_OUTBOUND_ARCH || Path for processed XML files for Unilever || SYSTEM
|-
| GLO_OUTBOUND_FAIL || Path for processed XML files for Unilever that have failed processing || SYSTEM
|-
| GLO_OUTBOUND_PATH || Path for yet to be processed XML files for Unilever || SYSTEM
|-
| HIGHLIGHT_SMS_EMAIL || Highlight order Green if SMS or email notification required || COST_CENTRE
|-
| HKP_Clear_Archive_Messages || Age of ARCHIVED messaging records that are to be cleared. || SYSTEM
|-
| HKP_Clear_Messages || Age of messaging records that are to be cleared. || SYSTEM
|-
| HTTPS_CALL || It is related to switching from HTTP to HTTPS || SYSTEM
|-
| HTTPS_PASSWORD || The password for URL commands in the database. || SYSTEM
|-
| HTTPS_WALLET_FILE || The wallet file for URL commands in the database. || SYSTEM
|-
| HTTP_WALLET_TOMTOM || Location of wallets for TOMTOM https || SYSTEM
|-
| ICE_DU || Identifies which du types include ICE || COST_CENTRE
|-
| IGGESUND_IDENTIFIER || Identifier for IGGESUND inbound order files || SYSTEM
|-
| IGGESUND_LISTING_NAME || List for IGGESUND files || SYSTEM
|-
| IGGESUND_LISTING_SCRIPT_NAME || KSH for IGGESUND files || SYSTEM
|-
| IMP_BWSC_DEF_CARRIER || Default Carrier for BWSC import for self delivery suppliers || COST_CENTRE
|-
| IMP_CARRIER_LANE_COUNTRY_CODE || Country code for each cost centre imported on Carrier_Lane - INDUSTRIAL || COST_CENTRE
|-
| IMP_CHANGE_DECIMALS || Correct commas and decimal points for Dimensions || CUSTOMER
|-
| IMP_COL_DATE_REQD || Collection Date must be specified for imports || COST_CENTRE
|-
| IMP_CREATE_ITEM_ID || Controls if Item identifiers are system generated in CSV || CUSTOMER
|-
| IMP_FULL_LOC_ADDR_MATCH || Check the addresses match for the location name, address line 1, postcode, country and type for imported orders before creating a new location (Y/N). || SYSTEM
|-
| IMP_LOC_ID_ONLY || Only validate the location id when importing orders not the address lines || SYSTEM
|-
| IMP_OVERRIDE_SOURCE_REF || Set source system and control additional functionality in ORD_LINE_ITM CSV order import || SYSTEM
|-
| IMP_RESET_ORD_WINDOWS || Reset Order windows during Import || COST_CENTRE
|-
| IMP_RESET_ORD_WINDOWS || Reset Order windows during Import || CUSTOMER
|-
| IMP_TI_ORDER_CALC_WEIGHTS || CSV Import - Calculate weights from dims(Y=X*Y*Z/6000) || COST_CENTRE
|-
| IMP_TI_ORDER_CHECK_SMS || CSV Import - Check contact numbers can be used as SMS numbers || COST_CENTRE
|-
| IMP_TI_ORDER_DEFAULT_DU || CSV Import - Default DU Type Method || COST_CENTRE
|-
| IMP_TI_ORDER_GEN_ITEMS || CSV Import - Generate order items from Qty || COST_CENTRE
|-
| IMP_TI_ORDER_GEN_LOC || CSV Import - Location Name generation by Post Code || COST_CENTRE
|-
| IMP_TI_ORDER_QTY_ADD || CSV Import - Add line qty || COST_CENTRE
|-
| IMP_TI_ORDER_REVENUE_LIMIT || CSV Import -Pre-call above revenue limit (Numeric Limit).0 means no pre-call || COST_CENTRE
|-
| IMP_TI_ORD_GEN_LOC_NAME || Send Supplier Collection Messages || CUSTOMER
|-
| IMP_USE_DEFAULT_DU || Use Default DU Type in import || CUSTOMER
|-
| IMP_USE_DEFAULT_DU || Use Default DU Type in import || CUSTOMER
|-
| IMP_USE_GERMAN_DECODE || Controls if location names are decoded from German || SYSTEM
|-
| INBOUND_ARDO_IDENTIFIER || Identifier for MTS PO Inbound Ardo files || SYSTEM
|-
| INBOUND_ARDO_LISTING_NAME || Listing file for Ardo inbound XML files || SYSTEM
|-
| INBOUND_ARDO_SCRIPT_NAME || Command file for Ardo inbound XML files || SYSTEM
|-
| INBOUND_BEIG2_IDENTIFIER || Identifier for MTS PO Inbound DAI_TMS_BEIG_ORD_YYYYMMDDHHMMSSII.XML || SYSTEM
|-
| INBOUND_BEIG2_LISTING_NAME || Listing file for BEIG inbound XML files || SYSTEM
|-
| INBOUND_BEIG2_SCRIPT_NAME || Command file for BEIG inbound XML files || SYSTEM
|-
| INBOUND_BEIG_IDENTIFIER || Identifier for MTS PO Inbound DAI_TMS_BEIG_ORD_YYYYMMDDHHMMSSII.XML || SYSTEM
|-
| INBOUND_BEIG_LISTING_NAME || Listing file for BEIG inbound XML files || SYSTEM
|-
| INBOUND_BEIG_SCRIPT_NAME || Command file for BEIG inbound XML files || SYSTEM
|-
| INBOUND_FAILURES_PATH || Path for failed inbound files || SYSTEM
|-
| INBOUND_GLO_IDENTIFIER || Identifier for MTS PO Inbound Unilever files || SYSTEM
|-
| INBOUND_GLO_LISTING_NAME || Listing file for GLO inbound XML files || SYSTEM
|-
| INBOUND_GLO_LOA_IDENTIFIER || Identifier for MTS PO Inbound Unilever LOA files || SYSTEM
|-
| INBOUND_GLO_SCRIPT_NAME || Command file for GLO inbound XML files || SYSTEM
|-
| INBOUND_POM_IDENTIFIER || Identifier for MTS PO Inbound MTS_POMI_<YYYYMMDDHH24MISS>_<10 DIGIT SEQ>.XML || SYSTEM
|-
| INBOUND_POM_LISTING_NAME || Listing file for POM inbound XML files || SYSTEM
|-
| INBOUND_POM_SCRIPT_NAME || Command file for POM inbound XML files || SYSTEM
|-
| INBOUND_PROCESSED_PATH || Path for processed inbound files || SYSTEM
|-
| INBOUND_UNI_IDENTIFIER || Identifier for MTS PO Inbound Unilever files || SYSTEM
|-
| INBOUND_UNI_LISTING_NAME || Listing file for UNI inbound XML files || SYSTEM
|-
| INBOUND_UNI_SCRIPT_NAME || Command file for UNI inbound XML files || SYSTEM
|-
| INCLUDE_CDATA_TAG || Use CDATA tag around XML tags values and allowed values will be (Y/N) which will be used to control escaping of special characters like & || SYSTEM
|-
| INCLUDE_FAILED_ORDERS || Include Failed Orders as CANCELLED for API || COST_CENTRE
|-
| INCL_ROUTE_CODE || Include Baxter Route code and delivery method || COST_CENTRE
|-
| INCOMPLETE_ORDERS_WARNING || Display warning message on trip status change if no order items exist || COST_CENTRE
|-
| INHERIT_LAT_LONG || Inherit Lat/Long details from parent address || CUSTOMER
|-
| INNER_OUTER_DU || Inner and outer du types for rating || COST_CENTRE
|-
| INTERFACE_FORMAT || Controls the interface format for inbound orders || SYSTEM
|-
| INTERFACE_INBOUND_PATH || Path for Inbound files || SYSTEM
|-
| INT_ADD_MOD43_CD || Store the Modulo 43 check digit as a suffix for the order item for the barcode label (Y/N). || COST_CENTRE
|-
| INT_ADD_MOD43_CD || Store the Modulo 43 check digit as a suffix for the order item for the barcode label (Y/N). || CUSTOMER
|-
| INT_ALTERNATE_DB || Determines if alternate_db is used as a condition in the INT_MSG code || SYSTEM
|-
| INT_CARRIER_DETS || Used to control which carrier details cursor is fetched in INT_MSG.PROCESS_TRIP_DTL_MSG || SYSTEM
|-
| INT_CHARGES || Determines whether internal charging is based on COST_CENTRE or GROUP_NAME || SYSTEM
|-
| INT_DECODE_UNISON || Used to control which DECODE_VALUE is used in INT_MSG || SYSTEM
|-
| INT_DROP_POSTCODE || Determines how v_string is built within INT_MSG.PROCESS_EFX_TRIP_DTL_MSG part of INT_MSG alignment || SYSTEM
|-
| INT_ERRNUM || Used to establish whether error numbers should be inserted into VALIDATION_ERROR in INT_MSG || SYSTEM
|-
| INT_IGNORE_DESP_QTY || Send despatch messages even when despatch quantity is not set || SYSTEM
|-
| INT_KEEP_FILE || Do not remove files from delivery folder || SYSTEM
|-
| INT_MSG_TYPE || Determines whether a cursor is fetched or a hard coded if IN the INT_MSG.READ_BBOKING_HEADER procedure. Part of Alignment process. || SYSTEM
|-
| INT_ORDER_COMMENT || Indicates if the order_comments in INT_MSG.PROCESS_UNSION_FILE is selected as a substring || SYSTEM
|-
| INT_ORDER_CORRECT || Indicates if interface files are corrected || SYSTEM
|-
| INT_READ_EFX_COMMENTED_OUT || Indicated if code is commented out in EFX procedure of INT_MSG part of alignment || SYSTEM
|-
| INT_READ_EFX_CURSOR || Indicates if C_EFX_TRIPS cursor is based on trip or load part of INT_MSG alignment || SYSTEM
|-
| INT_REVERSE_DECODE || Indicates if INT_MSG.PROCESS_EXE_OUTBOUND_FILE requires a call to IMP_REVERSE_DECODE in the current database || SYSTEM
|-
| INT_TRAILER_TYPE || DECODE or REVERSE to determine how trailer type is extracted in INT_MSG.PROCESS_EFX_TRIP_DTL_MSG || SYSTEM
|-
| INT_TRANSHIP_POS || Used to determine TRANSHIP_IND is in the incoming file for INT_MSG.READ_BOOKING_DETAIL || SYSTEM
|-
| INT_TRIP_STOP_DATE || Determines which date (LATE DEL or DEPART) is passed to the string in INT_MSG || SYSTEM
|-
| INT_UNISON_ERRNUM || Indicates if errnum should be included when inserting data into validation_error field in INT_MSG.PROCESS_UNISON_FILE || SYSTEM
|-
| INT_USE_NEW_DB || Determines which procedures within INT_MSG use the new database name || SYSTEM
|-
| INT_XML_DAYS_PAST || Used to set how many days into the past the dp_pulse package should look for locked records || SYSTEM
|-
| INVOICE_DIR || Directory for storing invoices when printed || SYSTEM
|-
| INV_ACT_PMNTS_DAYS || Process payments for a set number of days prior to the period end date or the current date for the next invoice. || SYSTEM
|-
| INV_SEARCH_FROM_OFFSET || Controls how many days in the past to default the from search in the INVOICES form. || SYSTEM
|-
| INV_SEARCH_TO_OFFSET || Controls how many days in the future to default the from search in the INVOICES form. || SYSTEM
|-
| INV_SET_PERIOD || Set the period for the invoice based on the current date (Y/N) || SYSTEM
|-
| ISOTRAK_BATCH_JOB_SIZE || Number of job records that are processed each minute via the ISOTRAK interface || SYSTEM
|-
| ISO_ENABLED || ISO enabled for this database || SYSTEM
|-
| ISO_FTP_DESTINATION_DIRECTORY || Directory for FTP of ISOTRAK Files || SYSTEM
|-
| ISO_FTP_DESTINATION_IP_ADDRESS || IP for FTP of ISOTRAK Files || SYSTEM
|-
| ISO_FTP_DESTINATION_PASSWORD || Password for FTP of ISOTRAK Files || SYSTEM
|-
| ISO_FTP_DESTINATION_PORT || Port for FTP of ISOTRAK Files || SYSTEM
|-
| ISO_FTP_DESTINATION_USERNAME || Username for FTP of ISOTRAK Files || SYSTEM
|-
| ISO_INBOUND_ARCH || Path for inbound ISO XML archiving || SYSTEM
|-
| ISO_INBOUND_FAIL || Path for ISO XML failures || SYSTEM
|-
| ISO_INBOUND_IDENTIFIER || Pattern for ISO Trip Inbound XML || SYSTEM
|-
| ISO_INBOUND_LISTING_NAME || Filename for list of files in directory for ISO XML Trip Inbound || SYSTEM
|-
| ISO_INBOUND_PATH || Path for yet to be processed XML files from ISO || SYSTEM
|-
| ISO_LISTING_SCRIPT_NAME || Script name for ISO XML Trip Inbound || SYSTEM
|-
| ISO_OUTBOUND_ARCH || Path for archiving outbound ISO XML interfaces || SYSTEM
|-
| ISO_OUTBOUND_FAIL || Path for failing outbound ISO XML interfaces || SYSTEM
|-
| ISO_OUTBOUND_PATH || Path for outbound ISO XML interfaces || SYSTEM
|-
| ISO_Queue_Name || ISOTRAK Queue Name || SYSTEM
|-
| ISO_RECON_MODE || Determine whether messages should be deleted or reconciled, then delete or update as appropriate, ARCHIVE or DELETE || SYSTEM
|-
| ISO_Sched_Prefix || ISOTRAK Schedule Prefix || SYSTEM
|-
| ISO_Signature || ISOTRAK Signature || SYSTEM
|-
| JAVAVM_PROFILE || javavm profile || SYSTEM
|-
| KCC_DEL_INFO_PATH || File path for KCC Delivery Information Export || SYSTEM
|-
| KER_LOADING_FTP_DIRECTORY || Specify the directory for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_FILENAME || Specify the Filename for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_IP_ADDRESS || Specify the IP Address for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_PASSWORD || Specify the Password for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_PATH || Specify the path for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_PORT || Specify the Port for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_USERNAME || Specify the Username for the Kerridge Loading file || COST_CENTRE
|-
| KER_WEB_PATH || URL for show web Kerridge Files || COST_CENTRE
|-
| LABEL_DIR || Directory for storing the labels when printed || COST_CENTRE
|-
| LABEL_FILE || Directory for storing the labels when printed || COST_CENTRE
|-
| LABEL_FILE_UNSCHEDULED || The label format for when the order is UNSCHEDULED. || COST_CENTRE
|-
| LABEL_FORMAT || Label format for Orders || COST_CENTRE
|-
| LABEL_GROUP || Delivery Type for which labels will be printed || COST_CENTRE
|-
| LABEL_LOGO_FILE || Set label logo file || SYSTEM
|-
| LANE_RATE_CHARGING || lane rates calc || COST_CENTRE
|-
| LAST_RELEASE_DATE || Last release for this database. NB. UPDATED_DATE (updated by trigger) stores the real value (see ORI_STATS). Change VALUE after each release. || SYSTEM
|-
| LBO_CUTOFF_TIME_DEFAULT || Latest time by which a Lane Based Order must be places if Cut-off functionality is switched on || SYSTEM
|-
| LBO_CUTOFF_TIME_ENABLE || LBO Cut-off times enabled - Y or N || SYSTEM
|-
| LBO_FUTURE_ORDER_LIMIT_DAYS || Maximum number of days in future that LB Order can be created || SYSTEM
|-
| LFE_API_AUTHORISATION || Client Ref for authorisation || SYSTEM
|-
| LFE_API_VERSION || 11 for 11g, 12 for 12c || SYSTEM
|-
| LICENCE_MONITOR_LEVEL || Licence monitor alert level || SYSTEM
|-
| LINE_ITEM_TOTALS || Controls if service payments are generated || COST_CENTRE
|-
| LOADING_REPORT || NON Cost centre Loading Report || SYSTEM
|-
| LOAD_LEVEL_PARAM || Level of data reported in the Load List || COST_CENTRE
|-
| LOCATION_DECODE_VALIDATION || Validate Addresses using decode values || COST_CENTRE
|-
| LOGINEXT_API_TOKEN || API Token for Loginext || SYSTEM
|-
| LOGINEXT_ENDPOINT || Endpoint address for Loginext || SYSTEM
|-
| LOGIX_ARCH_DIR || Folder for archive of Logix files || SYSTEM
|-
| LOGIX_CREATE_FILE || Create a file containing CLOB || SYSTEM
|-
| LOGIX_DEL_PRIORITY_DAYS || Number of days before late delivery when prioritized in Route Optimiser || SYSTEM
|-
| LOGIX_DIR || Folder for Logix files || SYSTEM
|-
| LOGIX_MASTER_PROFILE || Profile for Logix API webservice || SYSTEM
|-
| LOGIX_MASTER_WORK_AREA || LogiX Master Work area directory name || SYSTEM
|-
| LOGIX_PASSWORD || Password for Logix API webservice || SYSTEM
|-
| LOGIX_PROFILE || Profile for Logix API webservice || SYSTEM
|-
| LOGIX_PROJECT || Project for Logix API webservice || SYSTEM
|-
| LOGIX_PROXY || Proxy server name for Logix API webservice || SYSTEM
|-
| LOGIX_RANGE || Range of schedules to send || SYSTEM
|-
| LOGIX_RANGE_OLD || Range of schedules to send || SYSTEM
|-
| LOGIX_SCHEDULE_MATRIX || How Many Days in the future to Recalculate Planned Transport? || SYSTEM
|-
| LOGIX_SERVER_NAME || LogiX server name || SYSTEM
|-
| LOGIX_SLOT_CUTOFF_TIME || Cut-off time for planning trunks in LogiX import || SYSTEM
|-
| LOGIX_TIMEOUT || Timeout for Logix API webservice || SYSTEM
|-
| LOGIX_URL || URL for Logix API webservice || SYSTEM
|-
| LOGIX_USERNAME || Username for Logix API webservice || SYSTEM
|-
| LOGNET_INT_DIR || LOGNET file path. || SYSTEM
|-
| LOGO_FILE || Logo file || SYSTEM
|-
| LOGO_FILE_BW || Logo file in Black and White for system usage (e.g. on labels). || SYSTEM
|-
| LOGO_PATH || Site specific location of logo files || SYSTEM
|-
| LOTS_ADD_DEBRIEF || LOTS Additional Debrief Details || COST_CENTRE
|-
| LOTS_DEL_CUST_SIGNATORY || Controls if DEL messages for LOTS require an actual signatory - Y to hold messages. || COST_CENTRE
|-
| LOTS_DEL_MSG_TRIP_STATUS_COMPLETE || Send LOTS DEL Message if trip status set to COMPLETE (Y/N) || COST_CENTRE
|-
| LOTS_EXPORT_TYRE || LOTS export tyre || COST_CENTRE
|-
| LOTS_FTP_DESTINATION_DIRECTORY || Final Destination directory for FTP of LOTS Files || SYSTEM
|-
| LOTS_FTP_DESTINATION_IP_ADDRESS || IP for FTP of LOTS Files || SYSTEM
|-
| LOTS_FTP_DESTINATION_PASSWORD || Password for FTP of LOTS Files || SYSTEM
|-
| LOTS_FTP_DESTINATION_PORT || Port for FTP of LOTS Files || SYSTEM
|-
| LOTS_FTP_DESTINATION_USERNAME || Username for FTP of LOTS Files || SYSTEM
|-
| LOTS_FTP_PUT_DIRECTORY || Mid-Send directory for FTP of LOTS Files || SYSTEM
|-
| LOTS_INBOUND_ARCH || Path for archiving inbound LOTS XML interfaces || SYSTEM
|-
| LOTS_INBOUND_FAIL || Path for failing inbound LOTS XML interfaces || SYSTEM
|-
| LOTS_INBOUND_IDENTIFIER || Pattern for LOTS Trip Inbound XML || SYSTEM
|-
| LOTS_INBOUND_LISTING_NAME || Filename for list of files in directory for LOTS XML Trip Inbound || SYSTEM
|-
| LOTS_INBOUND_PATH || Path for inbound LOTS XML interfaces || SYSTEM
|-
| LOTS_INC_ORDER_HEADER_CONFIRM || Includes the ORDER_HEADER_CONFIRM section in the DEL file for LOTS. || SYSTEM
|-
| LOTS_INC_STOP_SIGNATURE || Indicates if the STOP_SIGNATURE section will be displayed in the DEL outbound files to LOTS. || SYSTEM
|-
| LOTS_INC_STOP_TYPE_DESC || Include STOP-TYPE_DESC tag in XML || SYSTEM
|-
| LOTS_LISTING_SCRIPT_NAME || Script name foe LOTS XML Trip Inbound || SYSTEM
|-
| LOTS_MINI_LODGMENT_FILE || Lodgements || SYSTEM
|-
| LOTS_OUTBOUND_ARCH || Path for archiving outbound LOTS XML interfaces || SYSTEM
|-
| LOTS_OUTBOUND_FAIL || Path for failing outbound LOTS XML interfaces || SYSTEM
|-
| LOTS_OUTBOUND_PATH || Path for outbound LOTS XML interfaces || SYSTEM
|-
| LOTS_PREVENT_MULTI_VLI_VUI || Prevent multiple VLI and VUI files being sent to LOTS (Y/N). || SYSTEM
|-
| LOTS_SEND_PLANNED || Allow TRP message to be sent to LOTS when trip is still at status Planned || SYSTEM
|-
| LOTS_SEND_WHEN_VEHICLE_SCANNED || List of LOTS message types that will be held until a vehicle scan is received for the order. || COST_CENTRE
|-
| LOTS_VERSION_NUMBER || LOTS Poller Version || SYSTEM
|-
| LOTS_XFER_EXTENSION || Sets the LOTS transfer file extension || COST_CENTRE
|-
| LOWERCASE_REF || Allow lowercase bill of lading || COST_CENTRE
|-
| MAINTAIN_SCHEDULE_DATES || Use wholesale schedule dates || COST_CENTRE
|-
| MANF_RECIPIENT || Indicates the recipient type of the manifest || COST_CENTRE
|-
| MANF_REPORT || Indicates the name of the manifest report to be automatically generated when a trip is accepted || COST_CENTRE
|-
| MANF_REPORT || Driver Manifest Name || COST_CENTRE
|-
| MANIFEST_AT_ENROUTE_ONLY || Only Send XML manifest at En-Route status || CARRIER
|-
| MANIFEST_ORDERS || Indicates that the cost centre allows parent and child shipments to be imported || COST_CENTRE
|-
| MAX_LOCATION_INACTIVE_DAYS || Maximum number of days a location can remain inactive before being set to inactive automatically. || SYSTEM
|-
| MAX_REPORT_PARAM_VALUES || Maximum number of multiple values that can be selected for extracts || SYSTEM
|-
| MAX_VOLUME || Maximum Volume for any FTL || SYSTEM
|-
| MAX_WEIGHT || Maximum weight for any FTL || SYSTEM
|-
| MCS_AWB_REQUIRED || This flag control whether the AWB (Air Way Bill) is requested during the pallet building and despatch processes in C-MCS. || SYSTEM
|-
| MCS_DESPATCH_DISPLAY_DROP || Display the Drop Number in the Despatch Screen || SYSTEM
|-
| MCS_DESPATCH_TO_PLAN || Enforce the despatch scanning of packages and pallets to the planned trips? (Y/N) || SYSTEM
|-
| MCS_DISPLAY_ADDITIONAL || Display items scanned from different trips in MCS despatch? (Y/N) || SYSTEM
|-
| MCS_DISPLAY_COMMTYPE_HAZ || This flag controls whether commodity code and hazardous information is displayed against items and pallets in C MCS pallet building. || SYSTEM
|-
| MCS_DISPLAY_PROD_TYPE || This flag controls whether the Product Type is displayed against items and pallets in C- MCS in receipt, despatch and pallet building. || SYSTEM
|-
| MCS_DYNAMIC_PALLET_BUILDING || This flag controls whether to allow pallet building to occur while scanning items for despatch in the items screen || SYSTEM
|-
| MCS_EXCEPTIONS_DAMAGED || MCS exceptions at Receipt (excluding FNR and LATE) and Despatch will be marked as damaged items and be removed from onward trips (Y/N). || SYSTEM
|-
| MCS_FAST || This parameter will control the level of validation performed during MCS scanning. || SYSTEM
|-
| MCS_FAST_VALIDATION || Is fast validation enabled || SYSTEM
|-
| MCS_ITEM_DISPLAY_DU || This flag controls whether the DU type is displayed instead of the item type on item lists in MCS. || SYSTEM
|-
| MCS_LOCATION_PROMPT || Prompt for Receipt Location at Receipt || SYSTEM
|-
| MCS_MOVE_FULL_CONSIGNMENT || Move all items for an order during MCS split scanning. || SYSTEM
|-
| MCS_NEW_DESPATCH_MODE || This flag controls whether the new Despatch screen is run || SYSTEM
|-
| MCS_PALLET_LABEL_FORMAT || The format of pallet label produced by the pallet building option when printing pallet labels. || SYSTEM
|-
| MCS_PREVENT_UNPLANNED || Prevent unplanned items being scanned for pallet building, despatch and receipt although expected for the route (Y/N)? || SYSTEM
|-
| MCS_RECEIVE_TO_PLAN || Enforce the receipt scanning of packages and pallets to the planned trips? (Y/N) || SYSTEM
|-
| MCS_SET_PALLET_ID || MCS set item Pallet Id || SYSTEM
|-
| MCS_TEMPERATURE_SCAN || Prompt for Temperature Type at MCS Despatch || SYSTEM
|-
| MCS_TENDERED_ITEMS || This flag controls whether MCS items are generated at the change to TENDERED status as well as at ACCEPTED status, or just ACCEPTED status. || SYSTEM
|-
| MCS_UPDATE_SCAN_IMMEDIATELY || Allow items to count as despatched immediately after scanning? (Y/N) || SYSTEM
|-
| MSC_STD_STATUS_CHANGES || Do trips go to EN-ROUTE and COMPLETED auto? Affects Despatch only. N means set to ACCEPTED if at PLANNED or TENDERED, otherwise EN-ROUTE. Any other value means set to EN-ROUTE status. || SYSTEM
|-
| MICD_DONT_SEND_DRVR_ID || Microlise Direct Don't send driver id || COST_CENTRE
|-
| MICD_EE_PATH_IN_IDENT || Pattern for MICD EventExport Inbound XML || SYSTEM
|-
| MICD_JSE_PATH_IN_IDENT || Pattern for MICD JourneySummaryExport Inbound XML || SYSTEM
|-
| MIC_3PL_TRIP_HOURS || The number of elapsed hours that Microlise requires a trip not to exceed. || SYSTEM
|-
| MIC_ACTUAL_DISTANCE || Will Microlise receive an actual distance from Paragon for a trip (Y/N)? || SYSTEM
|-
| MIC_ADD_STOP_BARCODE || Include new tag STOP_BARCODE on Microlise outbound xml || SYSTEM
|-
| MIC_ALLOW_CREATE_ORDERS || Allow orders to be created || SYSTEM
|-
| MIC_AUTO_CONFIRM_COLLECTION_ORDERS || Create Service Types via Microlise || COST_CENTRE
|-
| MIC_CALC_REASON_QTY || Set the item reason quantity to the despatched quantity if a reason code is provided with a quantity of 0 instead of an accurate quantity (Y/N). || COST_CENTRE
|-
| MIC_COLLECTION_ORDER_TASKS || Create ad hoc orders via Microlise || COST_CENTRE
|-
| MIC_CONSOL_ORDERS || Consolidate the orders for the Microlise outbound XML flow, if Y then the orders will be consolidated. || COST_CENTRE
|-
| MIC_CONSOL_STOPS || Consolidate the stops for the Microlise outbound XML flow, if Y then the stops will be consolidated. || COST_CENTRE
|-
| MIC_CREATE_CD || Microlise interface to create CD reason for successful deliveries when not provided || SYSTEM
|-
| MIC_CREATE_FAILED_ORDERS || Controls if orders be set to FAILED status on inbound Microlise flow || COST_CENTRE
|-
| MIC_DEBRIEF_POC || Allow the collection orders to set their POC flag when they are confirmed with actual delivered quantities and generate a ORD_COLL_XML file? (Y/N) || COST_CENTRE
|-
| MIC_DEFAULT_DELIVER || Should the actual times be set to the planned ones upon receipt of a STA or DEP message || COST_CENTRE
|-
| MIC_DEFAULT_PRODUCT_TYPE || Create Service Types via Microlise || COST_CENTRE
|-
| MIC_DEFINE_GROUP_NAME || Group Name For Microlise Collection Orders || COST_CENTRE
|-
| MIC_DEF_COST || Cost Centre default || SYSTEM
|-
| MIC_DEF_CUST || Customer ID default for Microlise || COST_CENTRE
|-
| MIC_DEF_DEL_TYPE || Default Del Type for empty orders || SYSTEM
|-
| MIC_DEF_DU_TYPE || Du Type || SYSTEM
|-
| MIC_DEF_PRODUCT || Product Type || SYSTEM
|-
| MIC_DELETE_REASONS || Delete Reason codes before adding new reason codes. || COST_CENTRE
|-
| MIC_DEL_DAY_OFFSET || Delivery Day Offset || SYSTEM
|-
| MIC_DIRECT_DEF_COST || Cost Centre default || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_DIRECTORY || Directory for FTP of Microlise Direct Files || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_IP_ADDRESS || IP for FTP of Microlise Files || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_PASSWORD || Password for FTP of Microlise Direct Files || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_PORT || Port for FTP of Microlise Direct Files || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_PROTOCOL || Protocol for FTP of Microlise Direct Files || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_USERNAME || Username for FTP of Microlise Direct Files || SYSTEM
|-
| MIC_DIRECT_PATH_IN || Inbound Directory for Direct Microlise XML || SYSTEM
|-
| MIC_DIRECT_PATH_IN_ARCH || Archive Directory for Inbound Direct Microlise XML || SYSTEM
|-
| MIC_DIRECT_PATH_IN_FAIL || Failure Directory for Inbound Direct Microlise XML || SYSTEM
|-
| MIC_DIRECT_PATH_IN_IDENT || Pattern for MIC Trip Inbound XML || SYSTEM
|-
| MIC_DIRECT_PATH_IN_LIST || Filename for list of files in directory for MIC Direct XML Trip Inbound || SYSTEM
|-
| MIC_DIRECT_PATH_IN_SCRIPT || Script name for MIC Direct XML Trip Inbound || SYSTEM
|-
| MIC_DIRECT_PATH_OUT || Outbound Directory for Direct Microlise XML || COST_CENTRE
|-
| MIC_DIRECT_PATH_OUT_ARCH || Outbound Archive Directory for Direct Microlise XML || SYSTEM
|-
| MIC_DIRECT_SEND_CUSTOMER || Microlise direct will send customer group instead of carrier || SYSTEM
|-
| MIC_DIRECT_SEND_ROUTE_CODE || Set Microlise direct to send route code in the Journey Alias field. || SYSTEM
|-
| MIC_DIRECT_UPDATE_PRIORITY || Flag indicating priority for del/arr updates Manual, EventExport, PodPoc updates || COST_CENTRE
|-
| MIC_DISABLE_EMPTY_ITEM_STOPS || Allows disabling of stops with no items on || SYSTEM
|-
| MIC_EXCLUDE_ASSET_ID || A comma-delimited list of prefixes that determines if the new asset ID will not be stored (e.g. for loose items). || SYSTEM
|-
| MIC_EXCLUDE_UNPACKED_LINES || Exclude any order lines that have not been packed from the Microlise files (Y/N). || COST_CENTRE
|-
| MIC_EXTENDED_INSTRUCTIONS || Are extended instructions sent to MICROLISE || COST_CENTRE
|-
| MIC_FTP_DESTINATION_DIRECTORY || Directory for FTP of Microlise Files || SYSTEM
|-
| MIC_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Microlise Files || SYSTEM
|-
| MIC_FTP_DESTINATION_PASSWORD || Password for FTP of Microlise Files || SYSTEM
|-
| MIC_FTP_DESTINATION_PORT || Port for FTP of Microlise Files || SYSTEM
|-
| MIC_FTP_DESTINATION_USERNAME || Username for FTP of Microlise Files || SYSTEM
|-
| MIC_INBOUND_ARCH || Path for Microlise XML archiving || SYSTEM
|-
| MIC_INBOUND_CONTINUE_ON_ERROR || Continue processing MICROLISE message if invalid items exist within the file? (Y/N) || COST_CENTRE
|-
| MIC_INBOUND_FAIL || Path for Microlise XML failures || SYSTEM
|-
| MIC_INBOUND_IDENTIFIER || Pattern for MIC Trip Inbound XML || SYSTEM
|-
| MIC_INBOUND_LISTING_NAME || Filename for list of files in directory for MIC XML Trip Inbound || SYSTEM
|-
| MIC_INBOUND_PATH || Path for yet to be processed XML files from Microlise || SYSTEM
|-
| MIC_INC_SERVICES || List of services to be sent out to Microlise || COST_CENTRE
|-
| MIC_LISTING_SCRIPT_NAME || Script name foe MIC XML Trip Inbound || SYSTEM
|-
| MIC_ORDER_FULFILLMENT || Send Additional Order Fulfillment values to Microlise. || COST_CENTRE
|-
| MIC_OUTBOUND_ARCH || Path for archiving outbound Microlise XML interfaces || SYSTEM
|-
| MIC_OUTBOUND_FAIL || Path for failing outbound Microlise XML interfaces || SYSTEM
|-
| MIC_OUTBOUND_PATH || Path for outbound Microlise XML interfaces || SYSTEM
|-
| MIC_OWNING_DEPOT || Indicates if the Microlise file is sent with Database or owning depot in the name || SYSTEM
|-
| MIC_PACKED_DESPATCHED || Only packed/despatched lines and items sent to Microlise || COST_CENTRE
|-
| MIC_POCPOD_NON_DEPOT || Microlise to set POC/POD for non depot orders || COST_CENTRE
|-
| MIC_REDUCED_EVENTS || Will Microlise receive a reduced number of defined events (Y/N)? || SYSTEM
|-
| MIC_RESOURCE_UPDATE || Update resources on recipt of Microlise message || COST_CENTRE
|-
| MIC_SEND_ACCEPTED || Send Microlise Trip message when status changed to ACCEPTED || SYSTEM
|-
| MIC_SEND_ADDR_CONTACTS || Send Contacts to Microlise (DEP/DEL/BOTH) || COST_CENTRE
|-
| MIC_SEND_ADD_REF || Send Address references in Mircolise XML flow || COST_CENTRE
|-
| MIC_SEND_ALL_CONTACTS || Send All Contacts to Microlise (Y/N) || COST_CENTRE
|-
| MIC_SEND_CHILDREN || Are child locations sent to Microlise || COST_CENTRE
|-
| MIC_SEND_COST || Send Costs in Mircolise XML flow || COST_CENTRE
|-
| MIC_SEND_DETAIL_ID || Send DETAIL_ID in the MIC XML flow || COST_CENTRE
|-
| MIC_SEND_DIRECT || Flag indicating needing to send direct message to Microlise or not || COST_CENTRE
|-
| MIC_SEND_EMPTY || Are empty resources sent to Microlise || SYSTEM
|-
| MIC_SEND_HAULIER_TYPE || Include Haulier Type in outbound microlise flow || COST_CENTRE
|-
| MIC_SEND_ORD_LINE_AND_ITEM || Send both Order Lines and Items to Microlise. || COST_CENTRE
|-
| MIC_SEND_ORD_REF || Send Order sub references in Mircolise XML flow || COST_CENTRE
|-
| MIC_SEND_SUB_TYPE || Are VAN carriers indicated || COST_CENTRE
|-
| MIC_SERVICE_TASKS || Create Service Types via Microlise || COST_CENTRE
|-
| MIC_SET_TO_COMP_CONF || Set trip to P-Completed, F-Confirmed, N-Neither once Microlise has finished its updates || SYSTEM
|-
| MIC_SHIPMENT_SO_REF || Is external ref included in the Shipment detail tag? || SYSTEM
|-
| MIC_SO_REF || So_ref sent to MICROLISE is oms_ref concatenated with external_ref || SYSTEM
|-
| MIC_SO_REF_FORMAT || Format for the SO_REF for Microlise for non-consolidated orders: 0 = Standard (Customer Ref), 1 = Type-SO_REF-Trip-Seq-Act (eg C-12345-MAN-1234-001-L) || SYSTEM
|-
| MIC_SO_REF_FORMAT || Format for the SO_REF for Microlise for non-consolidated orders: 0 = Standard (Customer Ref), 1 = Type-SO_REF-Trip-Seq-Act (eg C-12345-MAN-1234-001-L) || COST_CENTRE
|-
| MIC_SO_REF_FORMAT || Contingency Import setting || COST_CENTRE
|-
| MIC_SUPPRESS_ORDER_SEGMENT || Only show orders against the stop for the final delivery || COST_CENTRE
|-
| MIC_TRUNK_CONSOL || Are trunk trips consolidated to send to Microlise || COST_CENTRE
|-
| MIC_UPDATE_ACTUALS_FROM_PODPOC || Update Actuals based on POD/POC Message. || COST_CENTRE
|-
| MIC_UPDATE_TO_DELIVER || Update To Deliver based on Delivered Amount || COST_CENTRE
|-
| MIC_USE_ALT_STOP_ID || Prefix stop id with route code for first and last stops || COST_CENTRE
|-
| MIC_USE_PALLET_ID || Use Pallet ID in Microlise || COST_CENTRE
|-
| MIC_USE_STOP_ID || Determines if the stop ID or the stop sequence will be used by Microlise, if Y then the stop ID will be used. || COST_CENTRE
|-
| MIC_USE_STOP_ID || Determines if the stop ID or the stop sequence will be used by Microlise, if Y then the stop ID will be used. || SYSTEM
|-
| MILK_ROUND_ORDERS || Allow orders to be added to Milk round Routes based on delivery information || COST_CENTRE
|-
| MILK_ROUND_TRIP_GENERATION || Trips Generated using milk round processing || COST_CENTRE
|-
| MINIMUM_COLLECTION || Are Minimum collection charges applicable at each stop || SYSTEM
|-
| MINS_TRUNKS_ACCEPTED || How many minutes to auto accept trunk trips? || SYSTEM
|-
| MIN_COLLECTION_CHARGE || Minimum Collection charge per stop || SYSTEM
|-
| MIN_CONSIGNMENT_CHARGE || Minimum charge per consignment || SYSTEM
|-
| MIS_CHAR_SET || Character set for MIS extracts || SYSTEM
|-
| MIS_DELETED_DAYS || The number of days after which the data on the MIS_DELETED table will be removed. || SYSTEM
|-
| MIS_DELETE_REQUIRED || Determines whether MSI table needs to be updated || SYSTEM
|-
| MIS_FTP_ARCH_DIR || MIS FTP archive directory || SYSTEM
|-
| MIS_FTP_DESTINATION_DIRECTORY || MIS FTP Dir || SYSTEM
|-
| MIS_FTP_DESTINATION_IP_ADDRESS || MIS FTP IP || SYSTEM
|-
| MIS_FTP_DESTINATION_PASSWORD || MIS FTP Password || SYSTEM
|-
| MIS_FTP_DESTINATION_PORT || MIS FTP Port || SYSTEM
|-
| MIS_FTP_DESTINATION_USERNAME || MIS FTP User || SYSTEM
|-
| MIS_FTP_PROTOCOL || MIS FTP Protocol || SYSTEM
|-
| MIS_TAB_DELIMITER || Use a tab as a delimiter for the MIS files (Y/N)? || SYSTEM
|-
| MIXMOVE || Is MIMOVE interface enabled? || SYSTEM
|-
| ML_REQUIRED || Whether database is multi-lingual. || SYSTEM
|-
| MSC_STD_STATUS_CHANGES || Do trips go to EN-ROUTE and COMPLETED auto || SYSTEM
|-
| MSG_CONCAT_TIME_PERIOD || Message concatenation time period (minutes) || SYSTEM
|-
| MSG_LOC_ORD_DEL_BY_DELIVERY || Set to Y if message body for event LOC_ORD_DEL is to show delivery details || SYSTEM
|-
| MSG_NAKS || Send an email message for NAK responses (Y/N) || SYSTEM
|-
| MSG_NAKS_EMAIL || The email recipient for a message for NAK responses || SYSTEM
|-
| MSG_NAKS_TYPE || A list of NAK event types to send an email message || SYSTEM
|-
| MSG_SCHEMA_URL || XSD Schema URL Path || SYSTEM
|-
| MSG_SCHEMA_XSD || XSD Schema XSD Name || SYSTEM
|-
| MSG_SENDER_TRIP_ACCEPT || The sending email address for a the trip accept message. || COST_CENTRE
|-
| MSG_SEND_HOURS_THRESHOLD || Threshold in hours before current date when Trip messages will still be sent (using trip start date) || SYSTEM
|-
| MSG_SUBJECT_BKNG_DTL || Message Subject for Booking Detail message || SYSTEM
|-
| MSG_SUBJECT_BKNG_DTL_L || Message Subject for Lane Booking Detail message || SYSTEM
|-
| MSG_SUBJECT_CTM_AUTCHASE || Message Subject for Carrier Trip Management (CTM) Auto Chase Messages || SYSTEM
|-
| MSG_SUBJECT_CTM_MANCHASE || Message Subject for Carrier Trip Management (CTM) Manual Chase Messages || SYSTEM
|-
| MSG_SUBJECT_LANE_ACD_DTL || Message Subject for Lane Accepted Detail message || SYSTEM
|-
| MSG_SUBJECT_LANE_ACPTD || Message Subject for Lane Accepted message || SYSTEM
|-
| MSG_SUBJECT_LANE_ACPTD_A || Message Subject for Lane Accepted Amended message || SYSTEM
|-
| MSG_SUBJECT_LANE_A_DTL_A || Message Subject for Lane Accepted Amended Detail message || SYSTEM
|-
| MSG_SUBJECT_LOC_ORD_DEL || Message Subject for Pre-warning Order delivery message || SYSTEM
|-
| MSG_SUBJECT_MANIFEST || Message Subject for Network Rail Manifest message || COST_CENTRE
|-
| MSG_SUBJECT_MANIFEST || Message Subject for Manifest message || SYSTEM
|-
| MSG_SUBJECT_MANIFEST_A || Message Subject for Manifest Amended message || SYSTEM
|-
| MSG_SUBJECT_MANIFEST_DTL || Message Subject for Manifest Detail message || SYSTEM
|-
| MSG_SUBJECT_MANIFEST_SUM || Message Subject for Manifest Summary message || SYSTEM
|-
| MSG_SUBJECT_MANIFE_DTL_A || Message Subject for Manifest Detail Amended message || SYSTEM
|-
| MSG_SUBJECT_SELF_BIL_INV || Message Subject for Self bill Credit note || SYSTEM
|-
| MSG_SUBJECT_TENDER_INVT || Message Subject for Tender Invitation message || SYSTEM
|-
| MSG_SUBJECT_TENDER_INV_A || Message Subject for Tender Invitation Amended message || SYSTEM
|-
| MSG_SUBJECT_TENDER_SUM || Message Subject for Tender Invitation Summary message || SYSTEM
|-
| MSG_SUBJECT_TEND_INV_DTL || Message Subject for Tender Invitation Detail message || SYSTEM
|-
| MSG_SUBJECT_TND_INV_DT_A || Message Subject for Tender Invitation Detail Amended message || SYSTEM
|-
| MSG_SUBJECT_TRIP_COM_LST || Message Subject for Trip Completed List || SYSTEM
|-
| MSG_SUB_DEPOT || Identifies the depot to replace with the current depot of the order items in the emails to invite tenders. || SYSTEM
|-
| MSG_TRIP_CONTACT || Messaging Contact Details || COST_CENTRE
|-
| MTMIF_DEFAULT_CUR || Default value for DEFAULT_CUR in MTM LOCATION table. || SYSTEM
|-
| MTMIF_DELV_SRV_CLASS_ID || Default value for DELV_SRV_CLASS_ID in MTM LOCATION table. || SYSTEM
|-
| MTMIF_DEL_STOPTM || Default value for DEL_STOPTM in MTM LOCATION table. || SYSTEM
|-
| MTMIF_ITEM_SOURCE || Defines what item information is uploaded to MTM into item_id column, PROD_TYPE, TEMP_COMBO or DU_TYPE || SYSTEM
|-
| MTMIF_LOAD_CLASS_ID || Default value for LOAD_CLASS_ID in MTM LOCATION table. || SYSTEM
|-
| MTMIF_LOAD_TYPE_SOURCE || Defines what Load information is uploaded to MTM into load_type_id column, PROD_TYPE, TEMP_COMBO or DU_TYPE || SYSTEM
|-
| MTMIF_PICK_SRV_CLASS_ID || Default value for PICK_SRV_CLASS_ID in MTM LOCATION table. || SYSTEM
|-
| MTMIF_PRODUCT_SOURCE || Defines what Product information is uploaded to MTM into product_id column, PROD_TYPE or NULL || SYSTEM
|-
| MTMIF_PU_STOPTM || Default value for PU_STOPTM in MTM LOCATION table. || SYSTEM
|-
| MTMIF_SEND_DUS || MTM Interface Send DUs - Y, N or RPE (Y sends DU Qty, RPE sends RPE Qty). || SYSTEM
|-
| MTMIF_SEND_PIECES || MTM Interface Send Pieces - Y, N or RPE (Y sends DU Qty, RPE sends RPE Qty). || SYSTEM
|-
| MTMIF_SEND_VOLUME || MTM Interface Send Volume - Y or N || SYSTEM
|-
| MTMIF_SEND_WEIGHT || MTM Interface Send Weight - Y or N || SYSTEM
|-
| MTMIF_SPLIT_CUBE || Default value for SPLIT_CUBE in MTM LOCATION table. || SYSTEM
|-
| MTMIF_SPLIT_PALLET || Default value for SPLIT_PALLET in MTM LOCATION table. || SYSTEM
|-
| MTMIF_SPLIT_PIECES || Default value for SPLIT_PIECES in MTM LOCATION table. || SYSTEM
|-
| MTMIF_SPLIT_WEIGHT || Default value for SPLIT_WEIGHT in MTM LOCATION table. || SYSTEM
|-
| MTMIF_XDOCK_HANDLING_TIME || Default value for XDOCK_HANDLING_TIME in MTM LOCATION table. || SYSTEM
|-
| MTM_INSTALLED || MTM Installed ? - YES or NO || SYSTEM
|-
| MTM_OPTIMISE_WAIT_TIME || Should wait time incurred at a stop be moved to end of the preceding stop if the latter is an RDC. || SYSTEM
|-
| MTM_PATH || MTM Path || SYSTEM
|-
| MTM_UPDATE_ORDERS || MTM Interface Update Orders - Y or N || SYSTEM
|-
| MTM_VERSION || MTM Version || SYSTEM
|-
| MTS_CSV_EXPORT_PATH || First path that exports looks for when writing a csv to the file system || SYSTEM
|-
| MTS_CSV_EXPORT_PATH_ORS || First path that exports looks for when writing a csv to the file system for ORS || SYSTEM
|-
| MTS_CSV_FTP_PATH || used by EXPORTS Form to set the Client Server FTP Path || SYSTEM
|-
| MTS_CSV_IP_ADDR || CSV IP Address || SYSTEM
|-
| MTS_CSV_LOCAL_PATH || used by EXPORTS Form in Client Server mode - sets where on users PC exports will be written to || SYSTEM
|-
| MTS_CSV_PASSWORD || CSV Password || SYSTEM
|-
| MTS_CSV_USER || CSV User || SYSTEM
|-
| MTS_CSV_WEB_ADDR || CSV Web address || SYSTEM
|-
| MTS_CSV_WEB_PATH || forms part of the URL when generating an export, different value depending on environment || SYSTEM
|-
| MTS_CURRENT_VERSION || MTS Client Server current version || SYSTEM
|-
| MTS_ENABLE_SECURITY || Is Security Enabled - Y or N || SYSTEM
|-
| MTS_EXPORT_PATH || Second path that exports looks for when writing a csv to the file system || SYSTEM
|-
| MTS_FILE_UPLOAD_URL || URL for launching the MTS File Upload || SYSTEM
|-
| MTS_FTP_USER || Mts ftp user to be used within the stand-alone Upload/Import application. || SYSTEM
|-
| MTS_FTP_USER_PWORD || Mts ftp user account password. || SYSTEM
|-
| MTS_FTP_VBAPP_IMPORT_PATH || MTS Import Path for the VB ftp application || SYSTEM
|-
| MTS_IMPORT_PATH || MTS Import Path || SYSTEM
|-
| MTS_IMPORT_VIRTUAL_PATH || MTS Virtual Import Path || SYSTEM
|-
| MTS_INTERFACE || The standard file structure for interfacing || SYSTEM
|-
| MTS_LATEST_REVISION || Latest MTS Version || SYSTEM
|-
| MTS_LOCATION_USAGE || Controls how Locations are grouped, either via CUST_GROUP, CUSTOMER, used in Customer form to display correct tab || SYSTEM
|-
| MTS_LOG_DIR || Path where MTS application error logs are written to || SYSTEM
|-
| MTS_OUTBOUND_ORDER_PATH || File path for Outbound Orders . || SYSTEM
|-
| MTS_PRODUCT_RELEASE || MTS Product RELEASE || SYSTEM
|-
| MTS_PRODUCT_VERSION || MTS Product Version || SYSTEM
|-
| MTS_TRACKING_SYSTEM_1 || Stores the name of one of the tracking systems used in MTS || SYSTEM
|-
| MTS_TRACKING_SYSTEM_2 || Stores the name of one of the tracking systems used in MTS || SYSTEM
|-
| MTS_TRACKING_SYSTEM_3 || TomTom Tracking System || SYSTEM
|-
| MTS_UNQ_DEPOT_DEPARTS || Do departure times need to be unique ? - Y or N || COST_CENTRE
|-
| MTS_WIDE_SCREEN || Should Execution screen de available in Wide Screen || SYSTEM
|-
| NEW_ORDER_CONF || Controls if customers are emailed an order confirmation || COST_CENTRE
|-
| NORTHERN_MANIFEST || Depot Linked to Northern Manifests || SYSTEM
|-
| NO_RECALC_VOL || Controls volume is calculated from the system || COST_CENTRE
|-
| NO_VALID_ORDS_ACPT || When Y -setting trip to Accepted will not call validate order || SYSTEM
|-
| NULL_EXT_REF || Error if external ref is null on manual order || COST_CENTRE
|-
| OBS_BACKGROUND || Background Colour || SYSTEM
|-
| OF_CURRENCY_CODE || Oracle Financial Currency Code || SYSTEM
|-
| OF_FILE_ARCHIVE || Oracle financials archive file path. || SYSTEM
|-
| OF_FILE_NAME_SECTION2 || Stores the name of section 2 on the OF filename || SYSTEM
|-
| OF_FILE_PATH || Oracle financials file path. || SYSTEM
|-
| OF_FTP_DESTINATION_DIRECTORY || Oracle Financials FTP Dir || COST_CENTRE
|-
| OF_FTP_DESTINATION_DIRECTORY || Oracle Financials FTP Dir || SYSTEM
|-
| OF_FTP_DESTINATION_IP_ADDRESS || Oracle Financials FTP IP || SYSTEM
|-
| OF_FTP_DESTINATION_IP_ADDRESS || Oracle Financials FTP IP || COST_CENTRE
|-
| OF_FTP_DESTINATION_PASSWORD || Oracle Financials FTP Password || COST_CENTRE
|-
| OF_FTP_DESTINATION_PASSWORD || Oracle Financials FTP Password || SYSTEM
|-
| OF_FTP_DESTINATION_PORT || Oracle Financials FTP Port || SYSTEM
|-
| OF_FTP_DESTINATION_PORT || Oracle Financials FTP Port || COST_CENTRE
|-
| OF_FTP_DESTINATION_USERNAME || Oracle Financials FTP User || SYSTEM
|-
| OF_FTP_DESTINATION_USERNAME || Oracle Financials FTP User || COST_CENTRE
|-
| OF_FTP_DEST_DTL_DIRECTORY || Cargowise Details directory || COST_CENTRE
|-
| OF_FTP_DEST_DTL_PASSWORD || Cargowise Details password || COST_CENTRE
|-
| OF_FTP_DEST_DTL_USERNAME || Cargowise Details username || COST_CENTRE
|-
| OF_IF_DTL || Oracle Financial IF DTL || SYSTEM
|-
| OF_IF_FTR || Oracle Financial IF FTR || SYSTEM
|-
| OF_IF_HDR || Oracle Financial IF HDR || SYSTEM
|-
| OF_JRNL_ENTRY_SOURCE_NAME || Oracle Financial Journal Entry Source Name || SYSTEM
|-
| OF_ORIGID || Stores the name of ORIGID || SYSTEM
|-
| OF_SECTION2 || Stores the name of section 2 on the OF filename || SYSTEM
|-
| OF_SETTINGS || Controls if Oracle Financial settings are required for 11i and R12 || SYSTEM
|-
| OF_SOURCE_SYSTEM_CODE || Oracle Financial System Code || SYSTEM
|-
| OMS_ACTUALS_MANDATORY || Governs which ACTUAL_QUANTITY fields require mandatory population in Debrief forms. || SYSTEM
|-
| OMS_ADD_ORDER_TO_LOCS || Should orders added to a Trip be added to existing stops based on Location Id - YES or NO || SYSTEM
|-
| OMS_ADD_ORDER_TO_MILK || Allow orders to be added to Milk round Routes || COST_CENTRE
|-
| OMS_ADD_PACKED_LINE || Allow an order to be valid when it contains an order line with a planned qty of zero? (Y/N) || COST_CENTRE
|-
| OMS_ALLOW_DUPL_CUST_REF || This parameter when set will allow the duplicate customer references || SYSTEM
|-
| OMS_ALLOW_MANUAL_SCHEDULE || Display Manual Schedule Flag in orders screen || COST_CENTRE
|-
| OMS_ALTERNATE_REBOOK || Alternative Rebook Functionality || COST_CENTRE
|-
| OMS_AMEND_SVC_FLAGS || OMS_AMEND_SVC_FLAGS || SYSTEM
|-
| OMS_AVG_WEIGHT || Uses average weight to calculate the weight against an order || COST_CENTRE
|-
| OMS_CHANGE_DEL_TYPE || List of Delivery types allowing change || SYSTEM
|-
| OMS_CHECK_CUTOFF || Controls if cut of times for product and du are considered when creating orders || SYSTEM
|-
| OMS_CONSOLIDATE_DUPLICATE_LINES || Enables the consolidation of duplicate order lines during order entry (Y/N). || COST_CENTRE
|-
| OMS_CONSOL_ITEMS || Controls if items are consolidated in order xml || COST_CENTRE
|-
| OMS_CONTACT_TRACKING || To control the use of the order and location contacts for the contacts when they are sent to EPOD and Portal TTM. || SYSTEM
|-
| OMS_CREATE_DUMMY_SOL || Create dummy SOL records for Dunelm || SYSTEM
|-
| OMS_CREATE_POD || Create CSV POD files for the customer? (Y/N) || CUSTOMER
|-
| OMS_CUTOFF_TIME_DEFAULT || Sets the default cut-off time in format HH24:MI for the order time window calculation should a schedule rule not exist for the locations. || SYSTEM
|-
| OMS_DEFAULT_ORDER_CREATION || Controls dates needed when creating Orders in Orders form. ALL, COLLECTION, DELIVERY or STANDARD || SYSTEM
|-
| OMS_DEFAULT_SERVICE_LEVEL || Default service level for the derivation of the time windows for parcel orders. || COST_CENTRE
|-
| OMS_DEFAULT_TEMPLATE_METHOD || Default method for generating orders from order template screen (M for Multiple, S for Single) || SYSTEM
|-
| OMS_DEF_PROD_TYPE || Default Prod Type for Dunelm || SYSTEM
|-
| OMS_EXCLUDE_AUDIT || Exclude changes to field from audit || SYSTEM
|-
| OMS_FOOTPRINT_FOR_VOLUME || Will the footprint of the order line be include in the VOLUME item for the outbound XML file for the despatch units instead of the cubic volume (Y/N)? || COST_CENTRE
|-
| OMS_INCLUDE_X_ITEM_PREFIX || Allow items with a prefix of X to be included in the Load Management screen and Microlise files (Y/N)? || COST_CENTRE
|-
| OMS_INVALID_SAME_LOCS || Set the order status to INVALID when the from and to locations are the same (Y/N) || SYSTEM
|-
| OMS_ITEMS || Generate Item Identifier using OMS reference and count of items || COST_CENTRE
|-
| OMS_ITEM_AKA_DISPLAY || Controls the label on the AKA Code field || COST_CENTRE
|-
| OMS_LEAVE_AS_NEW || To indicate if orders currently at status NEW are to be left at that status after validation other than the paragon interface? (Y/N) || SYSTEM
|-
| OMS_MIC_DEL_DATE || Are MIC files generated when delivery windows are updated || SYSTEM
|-
| OMS_NO_LIFTS || Controls if lifts are included in order xml || COST_CENTRE
|-
| OMS_NO_TRIP_REF_TRG || Do not obtain trip information in order triggers || SYSTEM
|-
| OMS_OFFERED_EARLY_OFFSET || The number of hours (minus) to offset the early collection or delivery time for the order when its booking status is OFFERED. || COST_CENTRE
|-
| OMS_OFFERED_LATE_OFFSET || The number of hours (plus) to offset the late collection or delivery time for the order when its booking status is OFFERED. || COST_CENTRE
|-
| OMS_ORDER_ARCH_DEL_DAYS || Number of days that archived Order Audit messages will be retained for. || SYSTEM
|-
| OMS_ORDER_AUDIT_ARCH_DAYS || Number of days that Order Audit message should be retained in the main table before being archived. || SYSTEM
|-
| OMS_ORDER_ID || Use the OMS Ref for the Order ID || COST_CENTRE
|-
| OMS_RECALC_OH_RPE || Recalculate the planned and packed RPE when an order is validated (Y/N). || COST_CENTRE
|-
| OMS_RESET_AUTO_PROC || Will the auto-processed flags of the order for the scheduling engine be reset when the early delivery date and time is changed? (Y/N) || COST_CENTRE
|-
| OMS_RE_BOOK_STATUS || Controls the status of re-book orders to DEL_FUTILE || SYSTEM
|-
| OMS_SEQ_CTL_ITEM_FORMAT || Add a prefix for the OMS reference for the order items as well as a sequential number (Y/N) || SYSTEM
|-
| OMS_SESSION_EARLY || Earliest arrival offset before the end of the handling time || SYSTEM
|-
| OMS_SESSION_HANDLING || Handling time associated with session collections || SYSTEM
|-
| OMS_SESSION_LATE || Latest arrival offset after the end of the handling time || SYSTEM
|-
| OMS_SESSION_WINDOW || Percentage value used to calculate the collection date and time window for transport orders generated from sessions || SYSTEM
|-
| OMS_SET_DATES || Change Delivery dates on Invalid Back orders || COST_CENTRE
|-
| OMS_SET_DELIVERY_TYPE || Order on/off/not in Schedule || COST_CENTRE
|-
| OMS_STD_ITEMS || Controls if Standard items are auto generated || COST_CENTRE
|-
| OMS_STD_RULE || Schedule rules applied excluding transport mode and delivery types || SYSTEM
|-
| OMS_TAG_TO_ASSET_TYPE || Order types to be validated in TAG to Asset Scanning || SYSTEM
|-
| OMS_TRACK_ITEMS || Indicates if the tracking references will be stored as order items. (Y/N) || CUSTOMER
|-
| OMS_TRACK_ITEMS || Indicates if the tracking references will be stored as order items. (Y/N) || COST_CENTRE
|-
| OMS_UNIQUE_EXT_REF || Controls if imports can load multiple order lines || CUSTOMER
|-
| OMS_UPDATE_SCHEDULE_TO_TRIP || Update the time windows for the orders that exist on a trip when the schedule of the trip is changed in the Planning screen. || SYSTEM
|-
| OMS_VALIDATE_INACTIVE_CODES || To validate orders with error condition for an invalid code for delivery type and service level || SYSTEM
|-
| OMS_VALIDATE_TEMPLATE || Controls whether the Template Id is populated with the associated Lane Id - LANE or NULL || SYSTEM
|-
| OPEN_FTP_DESTINATION_DIRECTORY || OPEN FTP destination Directory || SYSTEM
|-
| OPEN_FTP_DESTINATION_IP_ADDRESS || OPEN FTP destination IP Address || SYSTEM
|-
| OPEN_FTP_DESTINATION_IP_ADDRESS_COPY || OPEN FTP destination IP Address || SYSTEM
|-
| OPEN_FTP_DESTINATION_PASSWORD || OPEN FTP Password || SYSTEM
|-
| OPEN_FTP_DESTINATION_PORT || OPEN FTP destination Port || SYSTEM
|-
| OPEN_FTP_DESTINATION_USERNAME || OPEN FTP Username || SYSTEM
|-
| OP_SYS || Operating system || SYSTEM
|-
| OP_SYS_VER || Operating system version || SYSTEM
|-
| OR3_INTERFACE || Is the PR3 interface active || SYSTEM
|-
| ORDER_SEARCH_CONSOL || Include orders that have passed through a user's SCHED GROUP || SYSTEM
|-
| ORDER_WELL_HIGHLIGHT || Highlight Orders where matching trip found || COST_CENTRE
|-
| ORD_ALLOW_SHIPMENTS || Consolidate Orders on Shipments || COST_CENTRE
|-
| ORD_BOOKING_METHOD || CSV Import - Booking Method -HOME for home delivery, any other value for standard || COST_CENTRE
|-
| ORD_BOOKING_STATUS || Controls if Booking status is displayed || COST_CENTRE
|-
| ORD_CHANGE_BOOKING || Controls if a change to the booking ref is reflected on the payment || COST_CENTRE
|-
| ORD_CHECK_DUPLICATE_ORDERS || For orders where source system is IMPORTS check to see if order is a duplicate - Y or N || SYSTEM
|-
| ORD_CLEAR_DATES || Are dates cleared in the interface || SYSTEM
|-
| ORD_CONF_REPORT || Ord Conf report || COST_CENTRE
|-
| ORD_COPY_ALL_REFS || Are all references copied when items are split? || SYSTEM
|-
| ORD_CREATE_MANIFEST || Controls if a portal manifest record is created for Manual Orders || COST_CENTRE
|-
| ORD_CREATE_PORTAL_ITEM_IDS || Does C-TMS generate the item identifiers for Portal orders || SYSTEM
|-
| ORD_CREATTE_PORTAL_ITEM_IDS || Does C-TMS generate the item identifiers for Portal orders || SYSTEM
|-
| ORD_DEBRIEF_DAYS || Default number of days used to restrict Orders displayed by Order Debrief form. || SYSTEM
|-
| ORD_DEFAULT_AIR || Default Dimensional Weight Factor for Air Transport || SYSTEM
|-
| ORD_DEFAULT_CC || Order Default Cost Centre || SYSTEM
|-
| ORD_DEFAULT_CUST || Order Default Customer || SYSTEM
|-
| ORD_DEFAULT_DEL_TYPE || Order Default Delivery Type || SYSTEM
|-
| ORD_DEFAULT_ROAD || Default Dimensional Weight Factor for Road Transport || SYSTEM
|-
| ORD_DEFAULT_SEND_TO_MTM || Order Default Send to MTM Flag || SYSTEM
|-
| ORD_DEFAULT_SESSION_DU_TYPE || Standard delivery unit used to transport unprocessed blood from sessions || SYSTEM
|-
| ORD_DEFAULT_SESSION_PROD_TYPE || Standard product type used to transport unprocessed blood from sessions || SYSTEM
|-
| ORD_DEFAULT_TRANSCODE || Order Default Trans. Code || SYSTEM
|-
| ORD_DESP2_RESEND || Allow Desp2 message to be resent from orders screen || COST_CENTRE
|-
| ORD_DISPLAY_LIFTS || Display Lifts in preference to quantity || SYSTEM
|-
| ORD_EARLY_COLLECT_THRESHOLD || Number of Hours Early Collection Time can be before the Current Date/Time when creating an Order || SYSTEM
|-
| ORD_EDIT_RPE || Enable the RPE of an order line to be edited? (Y/N) || COST_CENTRE
|-
| ORD_EFFECTIVE_FUEL || Indicates if Fuel charges are fixed or based on effective dates || COST_CENTRE
|-
| ORD_END_TIME || The default late delivery time when a route is not provided for an API order (HH:MM) || SYSTEM
|-
| ORD_ENHANCED_REBOOK || Controls which rebook screen is displayed in the orders form || COST_CENTRE
|-
| ORD_EQUIPMENT_LOAD || Controls if equipment & equipment times are validated || SYSTEM
|-
| ORD_FIXED_SCHEDULE_CHECK || Check for existing fixed schedule generated orders || CUSTOMER
|-
| ORD_FUTURE_LIMIT_DAYS || Maximum Number of days in the future that an order can be created || SYSTEM
|-
| ORD_FUTURE_OFFSET || How far in the future can order offset be set || COST_CENTRE
|-
| ORD_IGNORE_LINE || Are some order lines ignored in the interface || SYSTEM
|-
| ORD_JUST_IN_TIME || Is the collection window set just in time || CUSTOMER
|-
| ORD_LATE_TIME || Late time windows for generated stack orders || SYSTEM
|-
| ORD_LINE_LENGTH || Store LENGTH i/o FOOTPRINT || COST_CENTRE
|-
| ORD_LINE_METHOD || Line Qty Calc Method || COST_CENTRE
|-
| ORD_LINK_CONTENTS || Link Items and contents in the interface || SYSTEM
|-
| ORD_NO_DEL_FOR_FAILS || Controls if DEL messages are generated for FAILED orders - Y to prevent, C to send as CAN || COST_CENTRE
|-
| ORD_OMIT_PACK_SCHEDULING || Omit the scheduling of the order and only print the label when pack confirming. || COST_CENTRE
|-
| ORD_ON_SCHED_DEL_LOC || Du category to be assessed for exclusion from parcel scheduling || CUSTOMER
|-
| ORD_POSTCODE_SEARCH || Determines whether he user can search for order addresses via a postcode (Y/N). || SYSTEM
|-
| ORD_PROCESSED_MSG || Ord Conf Processed Email Msg || COST_CENTRE
|-
| ORD_PROCESSED_SUBJECT || Ord Conf Processed Subject || COST_CENTRE
|-
| ORD_QUANTITY_DU_FIELDS_FORMAT_MASK || Default quantity and pallet fields format mask || SYSTEM
|-
| ORD_QUANTITY_PALLET_FIELDS_FORMAT_MASK || Default quantity and pallet fields format mask || SYSTEM
|-
| ORD_RBO_PREFIX || Is the rebook prefix stripped for LOTS? || SYSTEM
|-
| ORD_REASON_CODE_FILTER || Order Reason Code Filter || SYSTEM
|-
| ORD_REASON_SUP || Reason codes to be supressed in the web service || COST_CENTRE
|-
| ORD_RECEIVED_MSG || Ord Conf Received Email Msg || COST_CENTRE
|-
| ORD_RECEIVED_SUBJECT || Ord Conf Received Subject || COST_CENTRE
|-
| ORD_REMOVE_CANC || Controls if Orders Cancelled in C-TMS generate REM message to LOTS || COST_CENTRE
|-
| ORD_REPRINT_PACK_VISIBLE || Determines whether the Reprint Labels and Pack Confirm buttons are visible. (Y/N). || SYSTEM
|-
| ORD_RETAIN_PLANNED || Planned weight is retained on lines || COST_CENTRE
|-
| ORD_RPE_LM_FACTOR || The factor for loading meters to calculate the RPE of the orders. || COST_CENTRE
|-
| ORD_SET_BUSINESS_TYPE || Set Business Type on Orders || COST_CENTRE
|-
| ORD_SET_SERVICE || Controls if the service level is set to match the delivery type || SYSTEM
|-
| ORD_SPLIT_ALL_REFS || Are all references copied when items are split? || SYSTEM
|-
| ORD_SPLIT_REBOOK_ITEMS || Controls if items on the original order suffixed with X when the order is re-booked || COST_CENTRE
|-
| ORD_SPLI_ALL_REFS || Are all references copied when items are split? || SYSTEM
|-
| ORD_STACK_DEBRIEF || Order Stack Debrief || COST_CENTRE
|-
| ORD_START_TIME || The default early delivery time when a route is not provided for an API order (HH:MM) || SYSTEM
|-
| ORD_TARGET_SEND_TO_MTM || Order Target Send to MTM - Y or N || SYSTEM
|-
| ORD_TEMPERATURE_COMBO || Use Temperature Combo to determine if the customer reference should be highlighted. || COST_CENTRE
|-
| ORD_TEMPLATE_EDIT_UPDATE || Controls whether the user can edit the order template data during generation (Y/N). || SYSTEM
|-
| ORD_UNSCHEDULE_FAILS || Controls if Orders Cancelled in EPOD generate a CANC message to LOTS || COST_CENTRE
|-
| ORD_UNSCHED_COMP || Controls if Orders with 0 qty delivered be unscheduled from COMPLETED trips? || COST_CENTRE
|-
| ORD_UPDATE_LATE_COLL_DATE_TO_DEL || Controls if the Late Collection Date/Time is updated at Save to Match the Late Delivery Date/Time. || SYSTEM
|-
| ORD_VALIDATE_GROUP_NAME || Validate Group Name during order entry || COST_CENTRE
|-
| ORD_WRITE_NOTES || Write Order Notes. || SYSTEM
|-
| ORD_XDOCK_LOTS_DEL_MSG || Lots DEL msg is only sent on last trip for xdock orders (Y/N) || SYSTEM
|-
| ORS_DELIMITER || Oracle reporting suite data field delimiter || SYSTEM
|-
| ORS_SUMMARY || Allow the summarisation OF ORS reports || SYSTEM
|-
| ORS_TYPE_DEF_GROUP_BY || List of the ORS types to default group by fields || SYSTEM
|-
| ORS_TYPE_EXC_GROUP || Exclude ORS types from grouping fields || SYSTEM
|-
| OST_DEBRIEF_WARNING_DAYS || Number of days prior to current date for which orders not debriefed will included in warning message in Order Tracking form. || SYSTEM
|-
| OUTBOUND_3 || File path for Outbound Trips. || SYSTEM
|-
| P2 || users || SYSTEM
|-
| PALLET_BASED_RATING || Rate based on chargeable/non chargeable pallets || CUSTOMER
|-
| PARAGON_IMPORT_LAYOUT || Paragon Import Layout || COST_CENTRE
|-
| PARAGON_INSTALLED || Paragon Installed ? - YES or NO. Only one of MTM_INSTALLED or PARAGON_INSTALLED should be set to YES. || SYSTEM
|-
| PARAGON_INSTALLED || Paragon Installed ? - YES or NO. Only one of MTM_INSTALLED or PARAGON_INSTALLED should be set to YES. || COST_CENTRE
|-
| PARAGON_RUNNING || Paragon Import is currently running (to stop outbound XML jobs) || SYSTEM
|-
| PARAGON_SCHED_DAYS || Determines how many days back paragon should extract records || COST_CENTRE
|-
| PAR_ALLOW_IMPORT_UNDO || Used to indicate if the UNDO button is allowed to be pressed on the Paragon Trip Import? (Y/N) || COST_CENTRE
|-
| PAR_API || Create Control records for Paragon API || SYSTEM
|-
| PAR_AUDIT || Include auditing of the import process in the STP version of the Paragon API (Y/N) || SYSTEM
|-
| PAR_AUTO_RESET_NEW || Auto reset orders at status New after paragon run || COST_CENTRE
|-
| PAR_CHECKSUM_OFF || To indicate if the checksum validation code is required for paragon imports? (Y/N) || SYSTEM
|-
| PAR_DISPLAY_IMPORT_DETAILS || Used to indicate whether the additional message containing the imported details is displayed or not on the Paragon Trip Import? (Y/N) || COST_CENTRE
|-
| PAR_DUN_COL_END_OFFSET || Offset for Dunelm collection end time || SYSTEM
|-
| PAR_DUN_COL_START_OFFSET || Offset for Dunelm collection start time || SYSTEM
|-
| PAR_DUN_TRUNK_CUTOFF_TIME || Set a cut-off time in format HH24:MI to apply to trunk trips to use the current schedule for the day. || SYSTEM
|-
| PAR_DUN_TRUNK_OFFSET_DAYS || Set a number of days to assess the trunk trips for the DUN radial trips. || SYSTEM
|-
| PAR_ENDPOINT_URL || URL for paragon API || SYSTEM
|-
| PAR_EXPORT_FORECAST || Send forecast values to Paragon || COST_CENTRE
|-
| PAR_FREQUENCY || Frequency for PAR Master keys || SYSTEM
|-
| PAR_FTP_DESTINATION_DIRECTORY || Directory for FTP of Paragon Files || SYSTEM
|-
| PAR_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Paragon Files || SYSTEM
|-
| PAR_FTP_DESTINATION_IP_ADDRESS_OLD || IP for FTP of Paragon Files || SYSTEM
|-
| PAR_FTP_DESTINATION_PASSWORD || Password for FTP of Paragon Files || SYSTEM
|-
| PAR_FTP_DESTINATION_PORT || Port for FTP of Paragon Files || SYSTEM
|-
| PAR_FTP_DESTINATION_USERNAME || Username for FTP of Paragon Files || SYSTEM
|-
| PAR_GROUP_STAGING || Paragon Group Staging Level || SYSTEM
|-
| PAR_INBOUND_ARCH || Path for Paragon XML archiving || SYSTEM
|-
| PAR_INBOUND_FAIL || Path for Paragon XML failures || SYSTEM
|-
| PAR_INBOUND_IDENTIFIER || Pattern for Paragon Trip Inbound XML || SYSTEM
|-
| PAR_INBOUND_LISTING_NAME || Filename for list of files in directory for Paragon XML trip Inbound || SYSTEM
|-
| PAR_INBOUND_PATH || Path for yet to be processed XML files from Paragon || SYSTEM
|-
| PAR_INT_SCREEN_CLASSIC_LAYOUT || Removes/Renames fields in PAR_INT to traditional C-TMS system setup rather than those changed for industrial || SYSTEM
|-
| PAR_KEY_FORMAT || PAR Master key format WKXX, DDMM, DAYX || SYSTEM
|-
| PAR_KEY_PROJECT || PAR Project name || SYSTEM
|-
| PAR_LISTING_SCRIPT_NAME || Script name foe Paragon XML Trip Inbound || SYSTEM
|-
| PAR_OUTBOUND_ARCH || Path for archiving outbound Paragon XML interfaces || SYSTEM
|-
| PAR_OUTBOUND_FAIL || Path for failing outbound Paragon XML interfaces || SYSTEM
|-
| PAR_OUTBOUND_PATH || Path for outbound Paragon XML interfaces || SYSTEM
|-
| PAR_PLAN_DIRECT || Controls if Paragon will plan direct collections (Not to owning depot) || COST_CENTRE
|-
| PAR_PROXY || Paragon Proxy Server || SYSTEM
|-
| PAR_RUN_NUMBER || Is Paragon Planning based on Run Numbers? || SYSTEM
|-
| PAR_SEND_ALL_LOCATIONS || Are locations sent out via API || SYSTEM
|-
| PAR_SET_ALL_FROM_NEW || Should all orders and trips set as NEW be updated after Paragon Run || SYSTEM
|-
| PAR_SHUNT_TRUNK || Check if the shunt and trunk routing has been completed prior to exporting to Paragon (Y/N). || SYSTEM
|-
| PAR_SLOT_CUTOFF_TIME || Number of minutes before slot window start that it closes to new orders || SYSTEM
|-
| PAR_START_DATE || Start Date for Master Keys || SYSTEM
|-
| PAR_TENNANT || Tennant for paragon API || SYSTEM
|-
| PAR_TENNANT_KEY1 || Tennant KEY 1 for paragon API || SYSTEM
|-
| PAR_TENNANT_KEY2 || Tennant KEY 2 for paragon API || SYSTEM
|-
| PAR_TRIP_STATUS || Controls the status of any Trips that are created via the Paragon Interface. || SYSTEM
|-
| PAR_TRUNK_THRESHOLD_UOM || Controls the order qty measure used as a threshold when assigning orders to Trunk trips in the Paragon Import. Values are WEIGHT, RPE or VOLUME. || COST_CENTRE
|-
| PAR_TRUNK_TRIP || Are trunk trips generated from Paragon Plan || SYSTEM
|-
| PAR_USE_LOC || Paragon Use From location of order s depot || SYSTEM
|-
| PAR_USE_RPOXY || Paragon Use Proxy || SYSTEM
|-
| PAR_USE_SLOTS || Use slots when exporting to Paragon (DUN format) || SYSTEM
|-
| PAR_VIRTUAL_OUT_ARCH || Path for webshow of archiving outbound Paragon XML interfaces || SYSTEM
|-
| PAR_VIRTUAL_OUT_FAIL || Path for webshow of failing outbound Paragon XML interfaces || SYSTEM
|-
| PAR_XML_OLD_ORDERS || Number of days in the past to still be included for sending orders to paragon || SYSTEM
|-
| PERCENTAGE_MARGIN || Percentage Margin Value || SYSTEM
|-
| PETAL_STARTS_AT_ANY_DEPOT || Does a Petal start at a Depot ? || SYSTEM
|-
| PLANNING_AUTO_SCHED_INACTIVE_DEPOTS || List the inactive depots by commas and in single quotes to exclude their orders in the Planning screen. || SYSTEM
|-
| PLAN_REG_COUNTRY || Planning Region Country suffix || COST_CENTRE
|-
| POLAR_CUST_REF || Controls the source of cust ref in Polar Speed labels || CUSTOMER
|-
| POM_DATE_END || Number of days after Purchase Order dates || SYSTEM
|-
| POM_DATE_START || Number of days before Purchase Order dates || SYSTEM
|-
| POM_DEF_COST || Default Cost Centre for PO || SYSTEM
|-
| POM_DEF_CUST || Default Customer for PO || SYSTEM
|-
| POM_DEF_PROD_TYPE || Default Product Type for PO || SYSTEM
|-
| POM_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header || SYSTEM
|-
| POM_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header || SYSTEM
|-
| POM_INBOUND_PATH || Path for yet to be processed XML files || SYSTEM
|-
| POM_OUTBOUND_ARCH || Path for processed POM outbound XML files that have successfully completed processing || SYSTEM
|-
| POM_OUTBOUND_PATH || Path for PO outbound files || SYSTEM
|-
| PORSCHE_DOT_CODE || Tyre Age for PORSCHE || SYSTEM
|-
| PORTAL_AUTO_SCHED_RET_DAYS || Day range for auto allocation of return orders || SYSTEM
|-
| PORTAL_DEF_DEL_TYPE || Delivery Type for Return orders || SYSTEM
|-
| PORTAL_ORDERS || Portal Imports available || SYSTEM
|-
| POSTAL_STRINGS_TOWN || Is town compared in postal string zones || SYSTEM
|-
| POSTCODE_SHIPMENTS || Indicates if shipments are postcode based || COST_CENTRE
|-
| PO_OVERRIDE_DU_WITH_SUB || A comma-separated list of transit DU types for which the sub-transit DU type will be used instead to generate order lines for the PO || SYSTEM
|-
| PRD_ITEM_IMPORT_FILE || Name of Product Item Import file || SYSTEM
|-
| PRD_ITEM_IMPORT_PATH || Product Item Import path || SYSTEM
|-
| PREVENT_ORD_COL_AFTER_DEL || Stop any ORD or COL messages after a DEL message || COST_CENTRE
|-
| PRINT_ACCEPTED_LABEL || Controls if customer labels are printed when trip is Accepted || COST_CENTRE
|-
| PRINT_INBOUND_LABELS || Controls if labels are generated for inbound xml orders || SYSTEM
|-
| PRINT_LABEL || Controls if customer labels may be reprinted from Order screen || COST_CENTRE
|-
| PRINT_LABEL_PATH || File path for Parcel Carrier Labels to be printed || SYSTEM
|-
| PROJECT_LOCATIONS || Indicates which prefixes are used for project location ids || COST_CENTRE
|-
| PTV_RO_ARCH_DIR || Folder for archive of PTV RO files || SYSTEM
|-
| PTV_RO_AUTO || PTV Automatic Response from Import || SYSTEM
|-
| PTV_RO_DEL_PRIORITY_DAYS || Number of days before late delivery when prioritized in Route Optimiser || SYSTEM
|-
| PTV_RO_DIR || Folder for PTV RO files || SYSTEM
|-
| PTV_RO_EXTEND || PTV plan covers more than 1 week || SYSTEM
|-
| PTV_RO_FILE_API || Create File or send data via API || SYSTEM
|-
| PTV_RO_FIX_MINUS1 || Reduce fix time by 1 when sending to PTV RO || SYSTEM
|-
| PTV_RO_GROUP_NAME || Select PTV unscheduled orders by group name rather than depot || SYSTEM
|-
| PTV_RO_MASTER_PROFILE || Profile for PTV RO webservice || SYSTEM
|-
| PTV_RO_MASTER_PROFILE_DEPOT || Profile for PTV RO webservice || SYSTEM
|-
| PTV_RO_ORDER_PAIRS || PTV Send load and unload tasks combined || SYSTEM
|-
| PTV_RO_ORD_FUTURE_DAYS || PTV Orders Future Days || SYSTEM
|-
| PTV_RO_ORD_HISTORIC_DAYS || PTV Orders Historic Days || SYSTEM
|-
| PTV_RO_PASSWORD || Password for PTV RO webservice || SYSTEM
|-
| PTV_RO_PASSWORD_BETA || Password for PTV RO webservice || SYSTEM
|-
| PTV_RO_PROFILE || Profile for PTV RO webservice || SYSTEM
|-
| PTV_RO_PROFILE_DEPOT_SCHED || Profile for PTV RO webservice || SYSTEM
|-
| PTV_RO_PROJECT || Project for PTV RO webservice || SYSTEM
|-
| PTV_RO_PROXY || Proxy server name for PTV RO webservice || SYSTEM
|-
| PTV_RO_SEND_RETRO || Send retro orders || SYSTEM
|-
| PTV_RO_SET_ROUTE || Set route code on trips from PTV RO || SYSTEM
|-
| PTV_RO_SPLIT || PTV imported route returns to Start Depot || SYSTEM
|-
| PTV_RO_TIMEOUT || Timeout for PTV RO webservice || SYSTEM
|-
| PTV_RO_TRIPS_HISTORIC_DAYS || PTV Trips Historic Days || SYSTEM
|-
| PTV_RO_TRIP_FUTURE_DAYS || PTV Trips Future Days || SYSTEM
|-
| PTV_RO_URL || URL for PTV RO webservice || SYSTEM
|-
| PTV_RO_URL_BETA || URL for PTV RO webservice || SYSTEM
|-
| PTV_RO_URL_NHS || URL for PTV RO webservice || SYSTEM
|-
| PTV_RO_USERNAME || Username for PTV RO webservice || SYSTEM
|-
| PTV_RO_USERNAME_BETA || Username for PTV RO webservice || SYSTEM
|-
| PTV_RO_USERNAME_NHS || Username for PTV RO webservice || SYSTEM
|-
| PTV_RO_WAIT_TIMEOUT || Timeout for PTV RO webservice Response || SYSTEM
|-
| RADIO_DU || Radio active || COST_CENTRE
|-
| RDT_441_CHECK_DAYS || Set a number of days in which to assess the prior loading messages for WCS. || SYSTEM
|-
| REBOOK_ALT_STATUS || If set to Y when an order is rebooked the original orders status will not be changed || SYSTEM
|-
| REBOOK_COPY_SUB_REF_CONTACTS || Set as Y or N to copy Sub References on Rebook, contact details only i.e. SMS and Email details || COST_CENTRE
|-
| RECORD_LIMIT || Limitation of records to display on Customer Service Screen || SYSTEM
|-
| REFRESH_WHEN_CLOSE_ORDER_DETAILS || Refresh the order summary screen when you close the order details page in the Orders form || SYSTEM
|-
| REPORT_CONNECT_STRING || Report auto production - connect string (user/pass@database). || SYSTEM
|-
| REPORT_DIRECTORY || Report auto production - place report in directory. || SYSTEM
|-
| REPORT_FLOC || Report auto production - name of FLOC directory for reports. || SYSTEM
|-
| REPORT_IP_ADDRESS || Report auto production - IP address server. || SYSTEM
|-
| REPORT_PORT || Report auto production - Port || SYSTEM
|-
| REPORT_SERVER || Report auto production - name of report server. || SYSTEM
|-
| REP_DELIVERY_DOCS || Name of the Delivery report printed from trip tree || COST_CENTRE
|-
| REP_JAVA_PDF || Java Report Controller Script || SYSTEM
|-
| REP_JAVA_PDF_DIR || Java Report Folder || SYSTEM
|-
| REP_JAVA_PDF_SHOW || Java Report Webshow Folder || SYSTEM
|-
| REP_LOADING || Name of the loading report printed from trip tree || COST_CENTRE
|-
| REP_ORARRP_DEST_FILEPATH || Reports Destination Filepath || SYSTEM
|-
| REP_ORD_EXTRACT_DAYS || Number of days that the order extract can be run for || SYSTEM
|-
| REP_PDF_DEST_FILEPATH || Reports PDF File Path || SYSTEM
|-
| REP_PDF_FILE_LOC || Reports PDF file location || SYSTEM
|-
| REP_PDF_WEB_DEST_NAME || Reports PDF destination || SYSTEM
|-
| REP_PDF_WEB_SERVER_NAME || Reports PDF Wed Server Name || SYSTEM
|-
| REP_PDF_WEB_SERVER_URL || Reports PDF Web Server URL || SYSTEM
|-
| REP_SERVER_WEB || Reports Server || SYSTEM
|-
| REP_SHOW_CARRIER || Controls if Carrier id is included in the Unsched Orders report || SYSTEM
|-
| REP_SO_REF_FORMAT || Set as 1 or 0 to reformat Order Reference, extract all characters up to the first '-' or '_' || COST_CENTRE
|-
| REP_WEB_SERVER_NAME || Reports Web Server name || SYSTEM
|-
| REP_WEB_SERVER_URL || Reports Server URL || SYSTEM
|-
| RESEND_EFX_STATUS || Can users resend EFX at status Accepted and En-route || COST_CENTRE
|-
| RESOURCE_DIARY || Resource Diary for display of trip allocation || SYSTEM
|-
| RES_ALTERNATIVE_CARRIER || During MTM sync, if Carrier does not exist should MTS check for alternative carrier ? - Y or N || SYSTEM
|-
| RES_ALT_CARRIER || Controls access to Alternate carriers button on Resource form, these are used in TRIPSUM_JRL. - Y or N || SYSTEM
|-
| RES_AVAILABILITY_ALLOC || Determines how resources are allocated to a trip || COST_CENTRE
|-
| RES_CONTROL_ALLOC_RESOURCE || Controls whether a resource can be assigned to more than one Carrier / Carrier Group || SYSTEM
|-
| RES_DT_FUEL_UNITS || Current fuel unit - Litres or Gallons || SYSTEM
|-
| RES_EXTERNAL_DRIVER || Use External Drivers || SYSTEM
|-
| RES_TRACKING_SYSTEM_DISPLAYED || Null, Tractor, Trailer or Both to indicate if Tracking systems are enabled. || SYSTEM
|-
| RETAIN_INTERFACE_ERRORS || Number of days Interface Errors are retained || COST_CENTRE
|-
| RE_PLAN_ORDERS || Controls if the Planner splits order for planning || SYSTEM
|-
| RE_SEQUENCE_STOPS || Are trip stops validate || COST_CENTRE
|-
| RHA_INDEXES || Use RHA indexes || SYSTEM
|-
| RICO_ACCOUNT || Rico Account login to Star-Gate || SYSTEM
|-
| RICO_OUT_ARCH || Outbound archive folder for Rico XML files || SYSTEM
|-
| RICO_OUT_DIR || Outbound folder for Rico XML files || SYSTEM
|-
| RTE_CHECK_MISSING_STOPS || Determines which stops must be present on a Trip, either HIGHEST_OPTIONAL or ALL. || SYSTEM
|-
| RTE_DEF_CAPACITY_MEASURE || Fixed Routes, default capacity measure (RPE, WEIGHT or VOLUME) || SYSTEM
|-
| RTE_DISBAND_SEMI_HOURS || Sets the number of hours prior to departure when a SEMI_FIXED Trip should be disbanded || SYSTEM
|-
| RTE_LOG_DEL_DAYS || Number of days that Fixed Routes log messages should be kept for || SYSTEM
|-
| RTE_MAINT_RDC_ALL_USAGE || Allow the values for the fixed route locations to include an RDC location when the depot has not been assigned to a customer or a customer group (Y/N) || SYSTEM
|-
| RTE_ORDERS_ASC_OR_DESC || Should orders be orders in Ascending or Descending order (ASC or DESC) || SYSTEM
|-
| RTE_PLAN_BY_REGION || Allow Fixed Routes to plan by Postal Region or Planning Region, values are PL and PO. || SYSTEM
|-
| RTE_PRIORITISE_URG_LATE_ORDS || Controls whether urgent and late orders are to prioritised in the Fixed Route process. || SYSTEM
|-
| RTE_REGION_AND_ZONE || Will fixed routes crossdock by planning region and location zone? (Y/N) || SYSTEM
|-
| RTE_SCHED_OFFSET_HRS || Fixed Routes Schedule Offset in hours || SYSTEM
|-
| RTE_SEMI_FIXED_CAPACITY || Determines whether capacity is checked by FILL or TRAILER capacity. || SYSTEM
|-
| RTE_SEMI_FIXED_FUNCTION || Should trips go to SEMI_FIXED if they are not optimum, Y or N. || SYSTEM
|-
| RTE_STOPOVER_MINS || Default number of minutes for a stopover for the network route. || COST_CENTRE
|-
| RTE_TRIPS_DEL_DAYS || Fixed Route RTE Trips in status DELETED on schedules older than this value will be deleted || SYSTEM
|-
| RTE_TRIPS_FIN_STATUS || Fixed Routes final status || SYSTEM
|-
| RTE_TRIPS_TO_ACCEPTED || Defines if ACCEPTED or PLANNED Trips are deleted in Rev TI, if yes then ACCEPTED, otherwise PLANNED - Y or N || SYSTEM
|-
| RTE_USE_CROSSDOCK || Should Fixed Routes allow crossdocks to be used. || SYSTEM
|-
| SALES_EXPORT || Payments are to be exported || SYSTEM
|-
| SAP_DEFAULT_DU_QTY || Default DU Quantity for bookings received via the SAP Interface. || SYSTEM
|-
| SAP_DEFAULT_DU_TYPE || Default DU Type for bookings received via the SAP Interface. || SYSTEM
|-
| SAP_DEFAULT_PROD_TYPE || Default Product Type for bookings received via the SAP Interface. || SYSTEM
|-
| SAP_POD_MSG_RQD || Is SAP (POD) Messages Required to be Extracted out of MTS - Y or N. || SYSTEM
|-
| SCHEDULE_RULES_SERVICE || Is service level displayed in schedule rules || COST_CENTRE
|-
| SCHED_ENG_DEL_OFFSET || The number of days that the order will remain in the delivery depot before it can be assigned to its delivery trip || COST_CENTRE
|-
| SCHED_ENG_DEL_OFFSET_CUTOFF || The cut off time at the delivery depot before an order can be assigned to its delivery trip || COST_CENTRE
|-
| SCHED_ENG_EXC_DU_CATEGORY || Du category to be EXCLUDED from parcel scheduling || CUSTOMER
|-
| SCHED_ENG_PART_PLAN || Will the network scheduling engine allow orders to be partially planned?(Y/N) || COST_CENTRE
|-
| SCHED_EXC_SI || Exclude order with special instructions from engine || COST_CENTRE
|-
| SCHED_RULE_SHOW_ZONE || Display zones instead of master location on delivery schedules in Sched Rules form || SYSTEM
|-
| SCH_CSCS_EST_IMPORT_FILE || Name of CSCS Estimate Import file || SYSTEM
|-
| SCH_CSCS_FC_IMPORT_FILE || Name of CSCS Forecast Import file || SYSTEM
|-
| SCH_CSCS_IMPORT_PATH || CSCS Import path || SYSTEM
|-
| SCH_DEFAULT_FIXED_TEMPLATE || Default Fixed Template Name for Auto Generation || SYSTEM
|-
| SCH_DELETE_PROD_QUANT_DURATION || Number of days worth or Product Quantity data that gets deleted. || SYSTEM
|-
| SCH_MANUAL_CREATE_SCHED || Ability to manually create schedules - Y or N || SYSTEM
|-
| SCH_NAME_FORMAT || Schedule Name Format || SYSTEM
|-
| SCH_RECORD_ITEM_DU_USE || Determine whether to update avg used flag and DU data on product quantity. This might be switched off to improve performance - Y or N || SYSTEM
|-
| SCH_SCHEDULE_ADV_DAYS || Determines how many days in advance to generate fixed routes Schedule || SYSTEM
|-
| SCH_SCHED_DATE_RANGE || Range in days for displaying schedules || SYSTEM
|-
| SCH_SCHED_DURATION || Schedule Duration (Days) || SYSTEM
|-
| SCH_SCHED_ORD_DERIVE || Controls the Order Schedule Date. Acceptable values ECDT, LCDT, EDDT, LDDT. || SYSTEM
|-
| SCH_SCHED_ORD_IMP_IGGESUND_SCHED_DATE_OVERRIDE || When Importing IGGESUND data, can the sched_date be over-written by the SCH_SCHED_ORD_DERIVE rule? || SYSTEM
|-
| SCH_SCHED_ORD_IMP_TI_ORDER_SCHED_DATE_OVERRIDE || When Importing TI_ORDER data, can the sched_date be over-written by the SCH_SCHED_ORD_DERIVE rule? || SYSTEM
|-
| SCH_SCHED_START || Schedule Start time || SYSTEM
|-
| SCH_TRIP_ID_DEPOT || Controls if Trip ID is derived from Owning Depot || SYSTEM
|-
| SCH_TRIP_ID_FMT || SCH Trip Id FMT || SYSTEM
|-
| SCH_TRIP_ID_PREFIX || Prefix for Depot based Trip ID || SYSTEM
|-
| SCH_VLS_IMPORT_FILE || Name of VLS Import File || SYSTEM
|-
| SCH_VLS_IMPORT_PATH || VLS Import Path || SYSTEM
|-
| SCR_CURRENT_HIGHLIGHT_COLOUR || Controls colour of highlighted rows in tables || SYSTEM
|-
| SCR_HEADER_BKG_COLOUR || Colour for header toolbars on forms || SYSTEM
|-
| SCR_HEADER_BMP_PATH || Location of BMP to control the colour of the toolbar/header in forms. Leave a trailing slash. || SYSTEM
|-
| SCR_HEADER_TEXT_COLOUR || Colour of text in header toolbars on forms || SYSTEM
|-
| SEC_GROUP_OR_BASEDAT || Security - Lock Monitor, display Group or Based at || SYSTEM
|-
| SEND_CAN_WITHOUT_BOOKING || Allow CAN message to be sent without Booking Ref || SYSTEM
|-
| SEND_INTERFACE_FAIL_EMAIL || Send email for interface errors || COST_CENTRE
|-
| SEND_LINE_ITEM_TO_LOTS || Send Line Item To LOTS. Y - send both Order Line (D) and Item (S) records. N - Checks for Items and, if there are any, sends Item (S) records, else Order Line (D) records. || SYSTEM
|-
| SEND_MANF_TO_SUPP || Indicates if the supplier manifest report will be automatically generated when a trip is accepted for the cost centre of the trip being collected. || COST_CENTRE
|-
| SEND_MANF_TO_SUPP || Indicates if the supplier manifest report will be automatically generated when a trip is accepted for the cost centre of the trip being collected. || CUSTOMER
|-
| SEND_MIL_MESSAGES || Send Tracking Milestone Messages || CUSTOMER
|-
| SEND_PALLET_ID_XML || Send Pallet ID tag in xml || COST_CENTRE
|-
| SEND_SCP_MESSAGES || Send Supplier Collection Messages || CUSTOMER
|-
| SEND_SMS_EMAIL || Controls whether a SMS or an e-mail may be sent to the recipient of the order being delivered on the trip (Y/N). || COST_CENTRE
|-
| SEND_SMS_EMAIL_OLD || Controls whether a SMS or an e-mail may be sent to the recipient of the order being delivered on the trip (Y/N). || COST_CENTRE
|-
| SEND_TO_ISOTRAK || Send to ISOTRAK - ALL or NONE. || SYSTEM
|-
| SERVICES || Controls if service payments are generated || COST_CENTRE
|-
| SESSION_DEFAULT_LOAD_RATE || Session Default Load rate || COST_CENTRE
|-
| SESSION_DEFAULT_UNLOAD_RATE || Session Default Unload rate || COST_CENTRE
|-
| SET_FAST_ORD_WINDOWS || Call fast order windows in Import || SYSTEM
|-
| SET_MICROLISE_SLOTS || Determines if the delivery slot times are sent to Microlise instead of the planned delivery times. || SYSTEM
|-
| SET_TRUNKS_ACCEPTED || Are Trunk trips automatically set to ACCEPTED status? || SYSTEM
|-
| SFTP_LOG_LEVEL || SFTP Log level - numeric 0-3 || SYSTEM
|-
| SHA_EXCLUDE_AUDIT || Activity types that will be excluded from writing audit log records when they are activated. || SYSTEM
|-
| SHIFT_ADDITIONAL_HOURS || Threshold for charging additional shift hours || COST_CENTRE
|-
| SHIFT_DISTANCE || Shift Distance || COST_CENTRE
|-
| SHIPMENT_NO_QTY_RATING || Indicates if a shipment can be rated without quantities || COST_CENTRE
|-
| SHIPMENT_VOLUME || Maximum shipment volume || SYSTEM
|-
| SHIPMENT_WEIGHT || Maximum shipment weight || SYSTEM
|-
| SHOW_CAPPED_TONNAGE || Display Capped Tonnage Details || SYSTEM
|-
| SHOW_CARRIER_NAME || Is carrier name shown on Planning screen? || SYSTEM
|-
| SHOW_CONTACT || Show contact name and number on labels. || COST_CENTRE
|-
| SHOW_FULL_ADDRESS || Show full delivery address on labels. || COST_CENTRE
|-
| SHOW_SCANNED_ITEMS_BTN || Display Scanned Items Update Button || SYSTEM
|-
| SLOT_DFLT_TRAILER_TYPE || Default Trailer Type for Slots || SYSTEM
|-
| SLOT_EXP_DIR || Slot Export - FTP to directory || SYSTEM
|-
| SLOT_EXP_IP || Slot Export - FTP to IP address || SYSTEM
|-
| SLOT_EXP_LOGIN || Slot Export - FTP using login || SYSTEM
|-
| SLOT_EXP_PORT || Slot Export - FTP to Port || SYSTEM
|-
| SLOT_INC_ADD_CORE_TYPES || Set to Y if Slot are to be defined as type CORE or ADDITIONAL || SYSTEM
|-
| SMA_ALLOW_CREATE_ORDERS || Allow orders to be created || SYSTEM
|-
| SMA_FTP_DESTINATION_DIRECTORY || Directory for FTP of Smartphone Files || SYSTEM
|-
| SMA_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Smartphone Files || SYSTEM
|-
| SMA_FTP_DESTINATION_PASSWORD || Password for FTP of Smartphone Files || SYSTEM
|-
| SMA_FTP_DESTINATION_PORT || Port for FTP of Smartphone Files || SYSTEM
|-
| SMA_FTP_DESTINATION_USERNAME || Username for FTP of Smartphone Files || SYSTEM
|-
| SMA_INBOUND_ARCH || Path for Smartphone XML archiving || SYSTEM
|-
| SMA_INBOUND_FAIL || Path for Smartphone XML failure || SYSTEM
|-
| SMA_INBOUND_IDENTIFIER || Pattern for SMA Trip inbound XML || SYSTEM
|-
| SMA_INBOUND_LISTING_NAME || Filename for list of files in directory for SMA XML trip inbound || SYSTEM
|-
| SMA_INBOUND_PATH || Path for yet to be processed XML files from Smartphone || SYSTEM
|-
| SMA_LISTING_SCRIPT_NAME || Script name for SMA XML Trip inbound || SYSTEM
|-
| SMA_OUTBOUND_ARCH || Path for archiving outbound Smartphone XML interface || SYSTEM
|-
| SMA_OUTBOUND_FAIL || Path for failing outbound Smartphone XML interface || SYSTEM
|-
| SMA_OUTBOUND_PATH || Path for outbound Smartphone XML interface || SYSTEM
|-
| SMA_OWNING_DEPOT || Indicates if the Smartphone file is sent with Database or owing depot in the name || SYSTEM
|-
| SMA_RESOURCE_UPDATE || Update resources on receipt of Smartphone message || COST_CENTRE
|-
| SMA_SEND_ACCEPTED || Send ACCEPTED message to SMARTPHONE || SYSTEM
|-
| SMA_SET_TO_COMP_CONF || Update Trip Status once Smartphone has provided all quantities and times || SYSTEM
|-
| SMA_TO_DELIVER_IS_DELIVERED || Auto-Default the TO_DELIVER quantity from the DELIVERED quantity || COST_CENTRE
|-
| SMS_AUDITING || Will records be audited in ADM_LOG for the SMS_EMAIL messages (Y/N)? || SYSTEM
|-
| SMS_COL_DEL_BOTH || Send SMS for delivery/collection orders or both? (COL, DEL, BOTH) || COST_CENTRE
|-
| SMS_GATEWAY_PWD || SMS Gateway Password || SYSTEM
|-
| SMS_GATEWAY_URL || SMS Gateway URL || SYSTEM
|-
| SMS_GATEWAY_USER || SMS Gateway Username || SYSTEM
|-
| SMS_LANDLINE_EXCLUSION || Will SMS be excluded for landlines? (Y/N) || SYSTEM
|-
| SMS_LOC_TYPES || Limit SMS and EMAIL Notifications to this list of location types only. If blank messages are sent for all stops || COST_CENTRE
|-
| SMS_MULTI_MSG || Send multiple SMS message for each trip stop (Y/N) || COST_CENTRE
|-
| SMS_SENDER_NUM || SMS Sender number to stop replies || SYSTEM
|-
| SMS_SERVICE_BOX || Stores the e-mail address of the SMS service box. || SYSTEM
|-
| SMS_SERVICE_BOX_OLD || Stores the e-mail address of the SMS service box. || SYSTEM
|-
| SMTP_ORDER_SENDER || Order Email Sender address || SCHED_GROUP
|-
| SMTP_ORD_CONF_SENDER || Ord Conf Email Sender Address || COST_CENTRE
|-
| SMTP_ORD_CONF_SENDERXX || Ord Conf Email Sender Address || COST_CENTRE
|-
| SMTP_PASSWORD || SMTP password || SYSTEM
|-
| SMTP_PORT_NUMBER || SMTP Port Number || SYSTEM
|-
| SMTP_PRIMARY || Primary Mail Server || SYSTEM
|-
| SMTP_SECONDARY || Secondary Mail Server || SYSTEM
|-
| SMTP_SENDER || Email Sender address || SYSTEM
|-
| SMTP_SMS_PRIMARY || Primary mail server for SMS. || SYSTEM
|-
| SMTP_SMS_SECONDARY || Secondary mail server for SMS. || SYSTEM
|-
| SMTP_SMS_SENDER || Sender address for SMS. || SYSTEM
|-
| SMTP_TRIP_SENDER || Trip Email Sender address || CONTROL_TOWER
|-
| SMTP_USER || STMP Username || SYSTEM
|-
| SOUTHERN_MANIFEST || Depot Linked to Southern Manifests || SYSTEM
|-
| STOP_PID || LOTS - is STOP_PID included in the extract || SYSTEM
|-
| SUBMIT_CARGOWISE_HEADER || Enter the number of minutes from FTP support files complete status to send header file? || SYSTEM
|-
| SUGGEST_TRIP || Suggest an appropriate trip for an order || COST_CENTRE
|-
| SUPPLIER_MANF || Indicates the name of the supplier manifest report to be automatically generated when a trip is accepted. || COST_CENTRE
|-
| SVC_USE_SERVICE_TYPES || Controls whether Service types are to be used which includes the use of transaction, manual, late and urgent order charging. || SYSTEM
|-
| T2A_ASSET_ARRIVED_OFFSET_DAYS || A number of offset days from the current date to select orders that have arrived at the depot for T2A Forward Items. || SYSTEM
|-
| T2A_ASSET_DUE_OFFSET_DAYS || A number of offset days from the current date to select orders that are due arrive at the depot for T2A Forward Items. || SYSTEM
|-
| TAG_TO_ASSET_SCANNING || Allow scanning and recording of Tags || SYSTEM
|-
| TA_EMAIL_SUBJECT || Email subject for automatically e-mailing manifest || COST_CENTRE
|-
| TA_EMAIL_SUBJECT || Trip accept. Email subject. || SYSTEM
|-
| TA_EMAIL_TEXT || Trip accept. Email message || SYSTEM
|-
| TA_EMAIL_TEXT || Email text for automatically e-mailing manifest || COST_CENTRE
|-
| TA_FILE_NAME || Trip accept. Name of output file. || SYSTEM
|-
| TA_FTP_DIRECTORY || Trip accept. FTP report to upload directory. || SYSTEM
|-
| TA_FTP_IP_ADDRESS || Trip accept. FTP report to IP address. || SYSTEM
|-
| TA_FTP_PASS || Trip accept. FTP report using password. || SYSTEM
|-
| TA_FTP_PORT || Trip accept. FTP port. || SYSTEM
|-
| TA_FTP_USER || Trip accept. FTP report using username. || SYSTEM
|-
| TA_PDF_TO_TIFF1 || Trip accept. Convert pdf to tiff. || SYSTEM
|-
| TA_PDF_TO_TIFF2 || Trip accept. Convert pdf to tiff. || SYSTEM
|-
| TA_PDF_TO_TIFF3 || Trip accept. Convert pdf to tiff stage 3. || COST_CENTRE
|-
| TA_PDF_TO_TIFF3 || Trip accept. Convert pdf to tiff. Rotation for landscape || SYSTEM
|-
| TA_REPORT_NAME || Trip accept. Name of report to be run. Please include the .rep extension. || COST_CENTRE
|-
| TA_REPORT_NAME || Trip accept. Name of report to be run. Please include the .rep extension. || SYSTEM
|-
| TA_SUB_FROM || Trip accept. Sub file from || COST_CENTRE
|-
| TA_SUB_FROM || Indicates Zetafax value in .sub file in FROM: || COST_CENTRE
|-
| TA_SUB_FROM || Trip accept. Sub file from || SYSTEM
|-
| TA_SUB_ORGANISATION || Trip accept. Sub file organisation || SYSTEM
|-
| TA_SUB_PRIORITY || Trip accept. Sub file priority || SYSTEM
|-
| TA_SUB_USER || Trip accept. Sub file user || COST_CENTRE
|-
| TA_SUB_USER || Trip accept. Sub file user || SYSTEM
|-
| TA_SUB_USER || Indicates Zetafax value in .sub file in USER: || COST_CENTRE
|-
| TDL_GEN_ITEMS || Allow order items to be generated from lines || SYSTEM
|-
| TDL_INBOUND_ARCH || Path for TDL XML archiving || SYSTEM
|-
| TDL_INBOUND_IDENTIFIER || Pattern for TDL Inbound XML || SYSTEM
|-
| TDL_INBOUND_PATH || Path for yet to be processed XML files from TDL || SYSTEM
|-
| TDL_ITEM_IN_PORTAL_FORMAT || Generate item identifier in portal format in order entry || SYSTEM
|-
| TEND_EMAIL || Different format for Tender invitation || SYSTEM
|-
| TEST || Controls whether certain testing functions are enabled - Y or N || SYSTEM
|-
| TIMES_LOADING_TIME || Default Loading Time used in Slots import when recalculating times || SYSTEM
|-
| TIME_ZONE_ACTIVE || Time Zone Active || SYSTEM
|-
| TMS_AUTO_DEFAULT_RESOURCE || Automatically default the Resource - Smartphone || COST_CENTRE
|-
| TMS_OTBOUND_SO_REF || Controls the outbound format for SO_REF in LOTSC || CUSTOMER
|-
| TOK_CNAME || Defines the Tokairo Customer Name. || CUSTOMER
|-
| TOK_CUSTOMERS || A comma-delimited list of customers to interface with Tokairo. || SYSTEM
|-
| TOK_FIELD || Defines the Tokairo field name. || CUSTOMER
|-
| TOK_OUTBOUND_ARCHIVE || Filepath for Tokairo Daily Extract archive || SYSTEM
|-
| TOK_OUTBOUND_PATH || Filepath for Tokairo Daily Extract || SYSTEM
|-
| TOK_POD_AVAIL || Is Tokairo being used to view POD documents - Y or N. || SYSTEM
|-
| TOK_SRCH_PAGE || Defines the Tokairo search page. || SYSTEM
|-
| TOK_URL_PREFIX || Defines the Tokairo URL prefix. || SYSTEM
|-
| TOK_VIRDIR || Defines the Tokairo virtual directory. || CUSTOMER
|-
| TOMTOM_CHECK_DEPOT || Check the depot to control data sent to depot || SYSTEM
|-
| TOMTOM_DRIP_FEED || Are stops sent to Webfleet by drip feed process || SYSTEM
|-
| TOMTOM_ORDER_TYPES || Are WEBFLEET order types derived || SYSTEM
|-
| TOMTOM_TIMES_ONLY || Do actual times on SU and CL set trip status || SYSTEM
|-
| TRANSPORT_MODE || Are Customer Transport Mode Factors Required || COST_CENTRE
|-
| TRIP_ALWAYS_SHOW_EMERGENCY_ORDERS || Emergency Deliveries are always displayed regardless of filter criterion || SYSTEM
|-
| TRIP_BRIEF_MAINTENANCE || Enable the Trailer Type, Rated Cost and Message Configuration to be maintained in Carrier Selection for trip planning (Y/N). || COST_CENTRE
|-
| TRIP_CHARGING_METHOD || Determines whether the calculation for the costs includes the trailer type of the trip: F is Fixed and includes the trailer type. || COST_CENTRE
|-
| TRIP_HAZARD_DISPLAYED || Show the Trip hazardous Totals or not. || SYSTEM
|-
| TRIP_HAZARD_LEVEL1_CODE || The colour code of the hazardous weight level 1. || SYSTEM
|-
| TRIP_HAZARD_LEVEL1_FROM || The lower value in the range of the hazardous weight level 1. || SYSTEM
|-
| TRIP_HAZARD_LEVEL1_TO || The upper value in the range of the hazardous weight level 1. || SYSTEM
|-
| TRIP_HAZARD_LEVEL2_CODE || The colour code of the hazardous weight level 2. || SYSTEM
|-
| TRIP_HAZARD_LEVEL2_FROM || The lower value in the range of the hazardous weight level 2. || SYSTEM
|-
| TRIP_HAZARD_LEVEL2_TO || The upper value in the range of the hazardous weight level 2. || SYSTEM
|-
| TRIP_HAZARD_LEVEL3_CODE || The colour code of the hazardous weight level 3. || SYSTEM
|-
| TRIP_HAZARD_LEVEL3_FROM || The lower value in the range of the hazardous weight level 3. || SYSTEM
|-
| TRIP_HAZARD_LEVEL3_TO || The upper value in the range of the hazardous weight level 3. || SYSTEM
|-
| TRIP_HAZARD_PRODUCTS || List the descriptions of the product types considered to be hazardous using a comma as a delimiter. || SYSTEM
|-
| TRIP_LABELS || Indicates the name of the report to be run from the Print Labels menu option in the trip tree in the Planning screen. || COST_CENTRE
|-
| TRIP_ORDER_XSD_VERS || Version of TRIP XSD being used. || SYSTEM
|-
| TRIP_ORD_LATE_FORMAT_MASK || Display the format of the late available and late delivery columns as time only (TIME) or date and time (DATETIME). || SYSTEM
|-
| TRIP_OVERVIEW_CURRENT_TYRES || Use the current quantity of tyres in the Trip Waterfall screen (Y/N) || SYSTEM
|-
| TRIP_PREVENT_PARCEL_CARRIER_ASSIGNMENT || Controls the manual assignment and cross-docking of transport orders to trips for parcels (Y to disable or N to enable). || COST_CENTRE
|-
| TRIP_SHEET || Trip Sheet Report || COST_CENTRE
|-
| TRIP_TRAMPS_ON_WATERFALL || Allow tramping trips to be shown in waterfall form by date not schedule || SYSTEM
|-
| TRIP_VALIDATE_PARCEL_ORDER_ASSIGNMENT || Controls validation of parcel orders to trips for parcel carriers (Y to disable or N to enable). || COST_CENTRE
|-
| TRLR_TYPE_RATE || Are trailer types included when estimating cost? || COST_CENTRE
|-
| TRM_3PL_SCHEDULE_NO_DROP || Enable orders without a drop number for the run to be pre-planned for Paragon (Y/N) || SYSTEM
|-
| TRM_ACTION_MITIGATION || Order Reason Actions requiring Mitigation || SYSTEM
|-
| TRM_ACTIVITY_QTY || Use Activity Quantity to determine when to create DEP control record || COST_CENTRE
|-
| TRM_ACT_PMTS_DEL_ORD_AT_CONF || Control whether Order_payments should be updated, and Orders set to DELIVERED when Trip is set to confirmed || SYSTEM
|-
| TRM_ADD_EDIT_ITEMS || Trip manipulation - display additional edit items. || SYSTEM
|-
| TRM_ALLOW_REJECTIONS || Allow trips to be rejected when they are not tendered (Y/N)? || SYSTEM
|-
| TRM_APPLY_DRIVER_BREAK_RULES || Switches Driver Breaks on or off - Y or N || SYSTEM
|-
| TRM_APPLY_POD_AFTER_ACTUALS || Apply the POD after the all actuals button is pressed (IIB) || SYSTEM
|-
| TRM_AUTO_DEL_TRIP_UNSCHED || Automatically delete trips when the last order is unscheduled from it || COST_CENTRE
|-
| TRM_AUTO_SET_ACCEPTED || Auto Set trip to accepted once all resources allocated || COST_CENTRE
|-
| TRM_BAXTER_ROUTES || Used to control when the process to populate trunk and radial routes is called || COST_CENTRE
|-
| TRM_BOL_PREFIX || Prefix that will be added to BOL when created in MTS. || COST_CENTRE
|-
| TRM_BOL_SUFFIX || Suffix that will be added to BOL when created in MTS. || COST_CENTRE
|-
| TRM_CANCEL_EMPTY_ORDER || Remove orders from trip going to Accepted if there are no items || COST_CENTRE
|-
| TRM_CARRIER_AUDIT || Controls whether audit records are written for Carrier CHANGES || COST_CENTRE
|-
| TRM_CHECK_CREW || Indicates if the Check_Crew functionality should be run. || COST_CENTRE
|-
| TRM_CHECK_LIMITS || Controls level at which Weight, RPE and Volume limits are checked - BY_STOP or NULL || SYSTEM
|-
| TRM_CHK_DRIVER_CARRIER || Use carrier hubs if driver hubs not set || COST_CENTRE
|-
| TRM_CL_DFLT_fixed_time || Default Close Down time (minutes) || SYSTEM
|-
| TRM_COMPLETED_SETTINGS || Indicates if CC/Customer Completed settings are in use || COST_CENTRE
|-
| TRM_CONSOLIDATE_STOPS || Allow consolidation of order on stops if time windows do not overlap || SYSTEM
|-
| TRM_CONSOL_ORDER_AFTER_XDOCK || Consolidate the available time windows for a collected order against the orders being loaded for delivery (Y/N) || SYSTEM
|-
| TRM_CROSSDOCK_TIME || Time offset for delivery into crossdock location || COST_CENTRE
|-
| TRM_DEBRIEF_SCREEN_TIME_VARIANCE_DISPLAYED || Is the Time Variance field displayed and updateable in the Trip Debrief screen. || SYSTEM
|-
| TRM_DEFAULT_DRIVER || Default Driver ID || COST_CENTRE
|-
| TRM_DEFAULT_TRACTOR || Default Tractor ID || COST_CENTRE
|-
| TRM_DEPOT_SCANS || Are trunk trip scans checked || SYSTEM
|-
| TRM_DESP_FOR_DEL || Maintain the Actual Despatched Quantity for a Delivery Trip in Trip Debrief (Y/N). || COST_CENTRE
|-
| TRM_DFLT_DRV_BREAK_MINS || Default Driver Break (minutes) || SYSTEM
|-
| TRM_DFLT_MAX_DRV_HRS_WO_BREAK || Default maximum drive hours without break || SYSTEM
|-
| TRM_DFLT_MAX_DRV_HRS_WO_STOPOVER || Default maximum drive hours without stopover. || SYSTEM
|-
| TRM_DFLT_MAX_WRK_HRS_WO_BREAK || Default maximum work hours without break || SYSTEM
|-
| TRM_DFLT_MAX_WRK_HRS_WO_STOPOVER || Default maximum work hours without stopover. || SYSTEM
|-
| TRM_DFLT_STOPOVER_BREAK_MINS || Default stopover duration (minutes). || SYSTEM
|-
| TRM_DFLT_WRK_BREAK_MINS || Default work break duration (minutes) || SYSTEM
|-
| TRM_DISPLAY_ERROR_MULTI_TRIP || Display Errors when changing multiple trips status || COST_CENTRE
|-
| TRM_DISP_ISOTRAK_OR_EFX || Controls whether the Isotrak Ref or EFX Ref is displayed in the TRIPSUM form - ISOTRAK or EFX || SYSTEM
|-
| TRM_DISP_OMS_OR_CUST_REF_OR_BOOK_OR_CONT_NO || Display OMS, Customer Ref, Booking Ref or Container No - OMS_REF, CUST_REF, CONT_NO or BOOKING_REF. || SYSTEM
|-
| TRM_DISP_REV_COLDEL || Display Revenue on collection or delivery trip || COST_CENTRE
|-
| TRM_DISP_RPE_DU_OR_WEIGHT || Controls whether RPE Qty, DU Qty or Total Weight is displayed in the TRIPSUM form - RPE, DU or WEIGHT. || SYSTEM
|-
| TRM_DISP_SCHED_ALL || Trip manipulation - display schedule all check box. || SYSTEM
|-
| TRM_DISP_VOL_OR_CASES || Controls whether Volume or Cases is displayed in Unscheduled Orders in TRIPSUM forms - VOLUME or CASES || SYSTEM
|-
| TRM_DISTRIBUTE_MAX_ORD_COST || Indicates if the cost centre will DISTRIBUTE revenue charges || COST_CENTRE
|-
| TRM_DO_NOT_UPDATE_ORD_DEL || Leave the order delivery type when the trip delivery type is different || COST_CENTRE
|-
| TRM_DRIVER_HUB || Drivers are aligned to a Hub Location || SYSTEM
|-
| TRM_DRIVER_RQD_FOR_ENROUTE_OR_ACC || Is a Driver required before a Trip can be set to EN_ROUTE or ACCEPTED || COST_CENTRE
|-
| TRM_EARLIEST_STOP_WINDOW || Toggle (Y/N) to specify whether consolidation uses the earliest stop || SYSTEM
|-
| TRM_ENFORCE_CARRIER_RULES || Enforce Carrier Hub Location Rules || COST_CENTRE
|-
| TRM_ENFORCE_TRIP_RECALC || Enforce Trip Recalculation - YES or NO || SYSTEM
|-
| TRM_EXCL_REG_AUTO || Planning Regions to be excluded from Auto Scheduling || COST_CENTRE
|-
| TRM_EXCL_TIME_VALIDATION || Indicates if the available time of an order is not compared to the cut-off time for TRUNK or LINEHAUL routes in the network scheduling engine (Y/N). || SYSTEM
|-
| TRM_FIXED_TRIP_STATUS || Determines status of trips created via Fixed Schedules. P for PLANNED or A for ACCEPTED. || SYSTEM
|-
| TRM_HIGHLIGHT_OVERDUE_FINISH || Trip Status used in Trip Overview screen to highlight overdue finish time || SYSTEM
|-
| TRM_HIGHLIGHT_OVERDUE_START || Trip Status used in Trip Overview screen to highlight overdue start time || SYSTEM
|-
| TRM_IGNORE_DUP_LOC_CHECK || Dunelm orders from a supplier in Scotland to a store in Scotland need to visit the trailer swap location twice so ignore standard checks in TRM || SYSTEM
|-
| TRM_INCL_TRUNK || Are trunk trips to be validated || SYSTEM
|-
| TRM_INC_BASED_AT_LOC_TRIPS || Allows viewing of other depots transiting || SYSTEM
|-
| TRM_LFS_PRINT_TRIP_POD_POC || Display LFS Trip Sheet POD POC report menu option (Y/N)? || SYSTEM
|-
| TRM_LOAD_DFLT_fixed_time || Default Loading Time (minutes) || SYSTEM
|-
| TRM_LOAD_dflt_mins_per_rpe || Default loading rate per RPE (minutes) || SYSTEM
|-
| TRM_LOAD_dflt_mins_per_weight || Default Loading rate per Weight (minutes) || SYSTEM
|-
| TRM_LOC_RADIAL_ROUTES || Indicates if a radial route that is stored for the location will be used in the scheduling engine instead of the location zones (Y/N). || SYSTEM
|-
| TRM_MANIFEST_DATES || Controls if the manifest is run based on dates || COST_CENTRE
|-
| TRM_MAX_DRIVING_HOURS || Maximum Driving Hours || SYSTEM
|-
| TRM_MAX_ORD_COST || Indicates if the cost centre will base revenue charges on the Maximum at a single stop || COST_CENTRE
|-
| TRM_MAX_SHIFT_HOURS || Maximum Shift Hours || SYSTEM
|-
| TRM_MAX_STOP_COST || Indicates if the cost centre will base cost charges on the Maximum at a single stop || COST_CENTRE
|-
| TRM_MAX_STOP_REVENUE || Indicates if the cost centre will base revenue charges on the Maximum at a single stop. || COST_CENTRE
|-
| TRM_MAX_WAIT_TIME || Maximum waiting time at Location (minutes) || COST_CENTRE
|-
| TRM_MERGE_END_OR_EXISTING_STOPS || Method-assigning orders to resulting trip in merge trips. Values: END or EXISTING. END adds orders to end. EXISTING adds orders to 1st available stop. || SYSTEM
|-
| TRM_MIC_DRIVER || Are driver minutes updated from Microlise debrief || COST_CENTRE
|-
| TRM_MODIFY_SCHED || Allow the stop times of the delivery trip to be updated to match the new delivery times of the scheduled order (Y/N). || COST_CENTRE
|-
| TRM_MOVE_ITEM_TO_DESP_BAY || Move an item from the grid to the despatch bay when added to the order on the trip or its order is assigned to the trip (Y/N) || SYSTEM
|-
| TRM_NETWORK_STOPS || Are trunk trip times set by the network table || COST_CENTRE
|-
| TRM_NEW_TRIP_STATUS_CHECKS || Control new restrictions on trip status change. || SYSTEM
|-
| TRM_NLP_SUMMARY || Request a summary by country in the NLP distance and time calculations(Y/N) || COST_CENTRE
|-
| TRM_NLP_SUMMARY || Request a summary by country in the NLP distance and time calculations(Y/N) || COST_CENTRE
|-
| TRM_NON_STD_INSTRUCTIONS || Calculate Planning Instructions on Carrier Trip Form || COST_CENTRE
|-
| TRM_NO_STOP_DELETE || Do not delete stops || COST_CENTRE
|-
| TRM_NO_TIME_VALIDATION || Trip prefix to prevent validation || COST_CENTRE
|-
| TRM_ODO_DISTANCE_LIMIT || Limit used to validate difference between odo start and end entries in debrief areas of Trip Forms || SYSTEM
|-
| TRM_OFFSET_PUBLIC_HOLIDAY || Indicates if the order time windows and the scheduling engine will be offset for the public holiday at the country, depot or route level (Y/N). || SYSTEM
|-
| TRM_ORD_OVERVIEW || Include Orders in Trip Overview screen || COST_CENTRE
|-
| TRM_ORD_SCHED_FROM || Number of days back for schedule range || COST_CENTRE
|-
| TRM_ORD_SCHED_FROM_PLANNING || Number of days back for schedule range in Planning screen || SYSTEM
|-
| TRM_ORD_SCHED_SEARCH || Maximum number of days for schedule range || COST_CENTRE
|-
| TRM_ORD_SCHED_SEARCH_PLANNING || Maximum number of days for schedule range in Planning screen || SYSTEM
|-
| TRM_ORD_SCHED_TO || Number of days forward for schedule range || COST_CENTRE
|-
| TRM_ORD_SCHED_TO_PLANNING || Number of days forward for schedule range in Planning screen || SYSTEM
|-
| TRM_OVERVIEW_AMBER_TIME || Time allowed before start and finish times are amber in TRIP OVERVIEW || SYSTEM
|-
| TRM_OVERVIEW_RED_TIME || Time allowed before start and finish times are red in TRIP OVERVIEW || SYSTEM
|-
| TRM_PLAN_ALL_RET_ORDERS || Plan all RET orders || COST_CENTRE
|-
| TRM_PLAN_INVALID || Are un-manifested orders set to invalid || SYSTEM
|-
| TRM_PREVENT_ALL_DEBRIEF || Prevent setting of actuals in trip debrief || SYSTEM
|-
| TRM_PREVENT_CONSOL_ACROSS_STOPS || Stop orders being added to shipments when not on same stops || COST_CENTRE
|-
| TRM_PREVENT_ORD_ON_COMP_STOP || Prevent Orders Being Planned on Completed stops || SYSTEM
|-
| TRM_PROSPERO_ADV_DAYS || Advance Scheduling days for Prospero || SYSTEM
|-
| TRM_PROTECT_SHUNTS || Protect the times from the order windows for the trip stops for shunt trips for collections (Y/N) || SYSTEM
|-
| TRM_RECALC_ELAPSED_TIME || Always recalculate elapsed time on trip || COST_CENTRE
|-
| TRM_RETAIN_CARRIER_NEW_SCHED || It is to retain a carrier when the schedule of the trip is updated. Otherwise, the carrier is reset to the carrier for the owning depot. || COST_CENTRE
|-
| TRM_RETAIN_EMPTY_STOPS || Retain empty stops when validating the trip. || COST_CENTRE
|-
| TRM_RETAIN_MTM || Retain MTM cost when set to Planned || SYSTEM
|-
| TRM_RETAIN_ORD_STATUS_TRIP_COMPLETE || Retain the current order status if trip status is set to COMPLETED (Y/N) || COST_CENTRE
|-
| TRM_RETAIN_PACK_DATA || Retain Pack Data either via Paragon or advise user to retain or delete pack data if manually unscheduling order. || COST_CENTRE
|-
| TRM_ROUND_RPE_AT_STOP || Round RPE at unload stop || SYSTEM
|-
| TRM_SCHEDULE_BY_DEL || Controls if orders are manually scheduled onto trips by del time || SYSTEM
|-
| TRM_SEND_PLUTO_ACTUALS || Actuals process for PLUTO || COST_CENTRE
|-
| TRM_SEND_PRE_DELIVERY_MSG || Activates email and SMS functionality || COST_CENTRE
|-
| TRM_SET_ACTUALS_AFTER_ENROUTE || Should Actuals (arrive/depart) be set for Trip stop 1 when trip is set to En-Route - Y or N || COST_CENTRE
|-
| TRM_SET_DESP_AFTER_ENROUTE || Should the actual despatched values for an order be set when the trip status is set to EN-ROUTE (Y to enable or N to disable). || COST_CENTRE
|-
| TRM_SET_NEW_STOP_TIMES || Trip prefix to set stop times based on trip duration || COST_CENTRE
|-
| TRM_SET_OWNING_DEPOT || Priority for assigning owning depot to a trip || COST_CENTRE
|-
| TRM_SET_TO_COMPLETED || Should trip be auto set to Completed. Values are N, ACTUAL (after actuals have been applied), POC/POD (when POC and POD applied to all Orders). || COST_CENTRE
|-
| TRM_SET_TO_COMP_AFTER_TIMES || Are trips set to completed when stop actuals have been set? || SYSTEM
|-
| TRM_SET_TO_CONFIRMED || Should trip be auto set to Confirmed. Values are N, ACTUAL (after actuals have been applied), POC/POD (when POC and POD applied to all Orders). || SYSTEM
|-
| TRM_SET_TO_ENROUTE_AFTER_ACTUALS || Should trip be set to En-Route after first order has been collected - Y or N || COST_CENTRE
|-
| TRM_SHIFT_TIMES_FOR_TRIP || Use Shift Times For Start And End Times Of Trip || SYSTEM
|-
| TRM_SHOW_LATE_BUTTON || Is the Show Late Reasons Button visible. || SYSTEM
|-
| TRM_SHOW_TIME_DEBRIEF_BTNS || Show time debrief buttons in trip debrief || SYSTEM
|-
| TRM_SHOW_TRIP_EXPORT_BTN || Show Export Button in TRIP screens. Specifically for Road Ops Report || SYSTEM
|-
| TRM_SOURCE_SYSTEM || Highlight the trip details when it contains an order without an OPEN status in the WMS source system (Y/N) || SYSTEM
|-
| TRM_STACK_DEBRIEF || Trip Stack Debrief || COST_CENTRE
|-
| TRM_STATUS_FOR_CONSOLIDATION || The trip status that controls the consolidation by customer or customer group, enter BOTH for ACCEPTED and PLANNED || SYSTEM
|-
| TRM_STOP_TIMES_FROM_ORDS || Will the trip stop times be inherited from the delivery time window of the order? (Y/N) || CUSTOMER
|-
| TRM_STORE_TRIP_MOVES || Determines whether audit of old and new trips is stored against orders || COST_CENTRE
|-
| TRM_SU_DFLT_fixed_time || Default Start Up time (minutes) || SYSTEM
|-
| TRM_SVC_TYPE || Is SVC_TYPE Editable on TRIP forms? || SYSTEM
|-
| TRM_TEMP_DEBRIEF || Display temperature on Trip debrief || SYSTEM
|-
| TRM_TRACTOR_RQD_FOR_ENROUTE_OR_ACC || Is a Tractor (Vehicle) required before a Trip can be set to EN_ROUTE or ACCEPTED || COST_CENTRE
|-
| TRM_TRAILER_RQD_FOR_ENROUTE_OR_ACC || Is a Trailer Id required on every stop before a Trip can be set to EN_ROUTE or ACCEPTED || COST_CENTRE
|-
| TRM_TRANSPORT_MODE_REQD || Is the transport mode on the trip screens a required field || COST_CENTRE
|-
| TRM_TREE_FORMAT || Determines trip tree display format || COST_CENTRE
|-
| TRM_TREE_ROUTE || Determines whether Route code is displayed in trip tree || COST_CENTRE
|-
| TRM_TRIP_STATUSES || List of Trip Statuses to control which trips displayed in Tripdtl/Trip Debrief form. || SYSTEM
|-
| TRM_TRUNK_TIME || Time in minutes for assessing Trunk Trips || COST_CENTRE
|-
| TRM_UNLOAD_DFLT_fixed_time || Default unloading time (minutes) || SYSTEM
|-
| TRM_UNLOAD_dflt_mins_per_rpe || Default unloading rate per RPE (minutes) || SYSTEM
|-
| TRM_UNLOAD_dflt_mins_per_weight || Default Unloading rate per RPE (minutes) || SYSTEM
|-
| TRM_UNSCHEDULE_TO_CANCEL || Controls if orders are Unscheduled when a cancellation is received || SYSTEM
|-
| TRM_UPDATE_ALL_ACTUALS || When a line actual is debriefed all actuals are set || COST_CENTRE
|-
| TRM_USE_ACTUALS_FOR_STOP_TIMES || Use Actual Times at stops to calculate times for next stop || SYSTEM
|-
| TRM_USE_MAX_RPE_OF_LARG_TRAILER || Controls whether MTS uses Max RPE of Largest Trailer Type when adding Orders to Trips - Y or N (N will use Current Trailer) || SYSTEM
|-
| TRM_VALIDATE_STOP_TIMES || Show Validation messages on stop times and prevent the user from going to accepted (Y/N) || SYSTEM
|-
| TRM_VALIDIDATE_DU_TEMP || Validate Du temp by product and DU || COST_CENTRE
|-
| TRM_VAL_CAR_VESSEL || Trip manipulation - validate carrier after vessel has been allocated. || SYSTEM
|-
| TRM_WASTE_SITE || Amend TO_LOC to a waste site in order well || COST_CENTRE
|-
| TRM_WEIGHTED_AVE_FILL_ACCEPT_PCENT || Defines the acceptable percentage for trip weighted average fill || SYSTEM
|-
| TRM_WEIGHTED_AVE_FILL_MIN_PCENT || Defines the minimum required percentage for trip weighted average fill || SYSTEM
|-
| TRM_WMS_STATUS || Controls if WMS status is calculated and if WMS status fields displayed in Trip forms. || COST_CENTRE
|-
| TRM_XDOCK_VALIDATION || Different Validation for the Cross dock process || COST_CENTRE
|-
| TRM_XDOCK_VIA_ROUTE || Display additional route information when selecting trip for XDOCK orders (Y/N) || SYSTEM
|-
| TRP_RED_TRUCK_ERRORS || Indicates if the truck icon is red to indicate an error || SYSTEM
|-
| TRP_SEND_ENABLE_MSG || Which enabling message is to be sent by Trip form || SYSTEM
|-
| TRP_SEND_WAREHOUSE_LOAD || Include Warehouse Loading Time in the outbound XML flow. || COST_CENTRE
|-
| TRP_STACK_DEBRIEF || Trip Stack Debrief || COST_CENTRE
|-
| TRUNK_LOAD || Time (minutes) to load an order on a trunk trip || SYSTEM
|-
| TRUNK_UNLOAD || Time (minutes) to unload an order on a trunk trip || SYSTEM
|-
| UKMAIL_ADD_INFO_LABEL || Additional information on UKMail Label || COST_CENTRE
|-
| UKMAIL_USE_CUST_REF_ON_LABEL || Controls if customer ref is displayed on UKMAIL label || CUSTOMER
|-
| UNISON_ORDER_INT_TYPE || EIH Interface Type (UNISON ORDER) || SYSTEM
|-
| UNI_DEFAULT_DU_TYPE || Default DU Type for Orders created via the UNISON interface. || SYSTEM
|-
| UNI_ENABLED || To enable the inbound and outbound file processing on this DB || SYSTEM
|-
| UNI_FTP_DESTINATION_DIRECTORY || Directory for FTP of Unilever Files || SYSTEM
|-
| UNI_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Unilever Files || SYSTEM
|-
| UNI_FTP_DESTINATION_PASSWORD || Password for FTP of Unilever Files || SYSTEM
|-
| UNI_FTP_DESTINATION_PORT || Port for FTP of Unilever Files || SYSTEM
|-
| UNI_FTP_DESTINATION_USERNAME || Username for FTP of Unilever Files || SYSTEM
|-
| UNI_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header (Unilever) || SYSTEM
|-
| UNI_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header (Unilever) || SYSTEM
|-
| UNI_INBOUND_PATH || Path for yet to be processed XML files (Unilever) || SYSTEM
|-
| UNI_LOCATION || Location for Unilever || SYSTEM
|-
| UNI_OUTBOUND_ARCH || Path for processed XML files for Unilever || SYSTEM
|-
| UNI_OUTBOUND_FAIL || Path for processed XML files for Unilever that have failed processing || SYSTEM
|-
| UNI_OUTBOUND_IDENTIFIER || Unilever outbound file identifier || SYSTEM
|-
| UNI_OUTBOUND_PATH || Path for yet to be processed XML files for Unilever || SYSTEM
|-
| UNSCHED_ORDERS_DEL_DAYS || Unscheduled orders on schedules older than this value will be deleted || SYSTEM
|-
| UPDATE_DIR || client Server Update directory || SYSTEM
|-
| UPDATE_IP_ADDR || Client Server Update IP Address || SYSTEM
|-
| UPDATE_IP_ADDR_CGEY || CGEY Client Server IP Address || SYSTEM
|-
| UPDATE_ORDERS_TO_TRIP || Update Order Windows to match selected trip || COST_CENTRE
|-
| UPDATE_ORDER_TIMES_TO_TRIP || Enable the current orders to have their time windows updated to match the stop time windows in the 'Confirm Update/Add' process (Y/N) || COST_CENTRE
|-
| UPDATE_PASSWORD || Client Server Update Password || SYSTEM
|-
| UPDATE_TO_DELIVER || update the To deliver quantity with the Ordered quantity for New order Items || SYSTEM
|-
| UPDATE_USER || Client Server Update User || SYSTEM
|-
| UPD_CUST_DATES || Default part Number || CUSTOMER
|-
| UPGRADE_PASSWORD || Client Server Upgrade Password || SYSTEM
|-
| UPGRADE_USER || Client Server Upgrade Username || SYSTEM
|-
| UPPERCASE_ASSET_ID || Asset id to be stored in upper case || SYSTEM
|-
| URGENT_ORDER || Controls if Urgent Notification emails are sent to planners || COST_CENTRE
|-
| URGENT_ORD_DELIVERY || Controls which delivery types trigger an urgent notification || COST_CENTRE
|-
| URGENT_ORD_RECIPIENT || Controls who receives an urgent notification || COST_CENTRE
|-
| USE_CHILD_LOCATIONS || Use any child locations in preference to the master locations of an order in the requested reports? (Y/Y) || COST_CENTRE
|-
| USE_ORDER_ADDRESSEE || Will the addressee name be used for the order? (Y/N) || COST_CENTRE
|-
| USE_PACK_QUANTITY || Use the current quantity of tyres in the Trip Waterfall screen (Y/N) || SYSTEM
|-
| USE_PALLET_ID_XML || Use Pallet ID instead of item identifier in XML Outbound files || COST_CENTRE
|-
| USE_SECURITY_PROFILES || Use Security Profiles for users || SYSTEM
|-
| USE_SMS_GATEWAY || Use SMS Gateway for SMS message sending || SYSTEM
|-
| USE_XML_ORDER_SUB_REFS || Print order sub refs on outbound XML || COST_CENTRE
|-
| USE_XML_ORDER_SUB_REFS || Print order sub-references in the outbound XML file? (Y/N) || COST_CENTRE
|-
| UTL_IMPORT_IGNORE_INVALID_OPERATION || The import process of files will suppress the auditing of messages when a file does not exist on the server to overwrite (Y/N) || SYSTEM
|-
| VALIDATE_LOCATION_ON_CLOSE || Validate address details if the close button is pressed within locations screen (Y/N)? || SYSTEM
|-
| VALIDATE_MASTER_LOC || Validate the collection and delivery location of the order against the decoded master locations (Y/N) || COST_CENTRE
|-
| VB_UPLOAD_APP_VERSION || Version number of the PC MTS Upload/Import Application written in Visual Basic || SYSTEM
|-
| WARN_MISSING_PO || Warn if No PO Allocated to a trip when status or carrier changed || CARRIER
|-
| WARN_OUTSTANDING4933 || Warn of unmatched 4933 orders on trip status change || CUSTOMER
|-
| WATERFALL_UPDATES || control updates on the waterfall screen || SYSTEM
|-
| WCS_441_CHECK_DAYS || Set a number of days in which to assess the prior loading messages for WCS. || SYSTEM
|-
| WCS_CALC_ITEM_WGT_VOL || Calculate the weight and volume for the DU in the 804 scan (Y/N). || COST_CENTRE
|-
| WCS_CALC_ITEM_WGT_VOL || Calculate the weight and volume for the DU in the 804 scan (Y/N). || CUSTOMER
|-
| WCS_CLEARDOWN_DAYS || Number of days after which WCS control records will be cancelled. || SYSTEM
|-
| WCS_COLLECTION_PREADVICE || Do we call collection pre-advice || NONE
|-
| WCS_COMBINED_ADD_LOAD || WCS add items and loading into a single scan || SYSTEM
|-
| WCS_DEFAULT_AGENT || Default agent for WCS messages || SYSTEM
|-
| WCS_DUAL_INSTANCE || Dual Instance WCS....***DUNELM ONLY*** || SYSTEM
|-
| WCS_ENABLED || Is the WCS system enabled? || SYSTEM
|-
| WCS_MIN_ITEM_LENGTH || Min length of WCS_ITEM to check for match in CTMS || SYSTEM
|-
| WCS_MULTI_DEPOTS || Pre-advise WCS when depot is different || SYSTEM
|-
| WCS_OLD_404_DAYS || Number of days to allow old 404 messages to be sent to WCS || SYSTEM
|-
| WCS_ORD_BUILD_ENABLED || Y to enable WCS Re-advice resend of Orders Overnight Processing || SYSTEM
|-
| WCS_RETAIN_EMPTY_LINES || Retain any empty order lines that have been created when their items have been deleted during the order confirmation process? (Y/N) || SYSTEM
|-
| WCS_SET_BAY_GRID_ITEMS_ONLY || Only update item locations that are on the grid || SYSTEM
|-
| WCS_SPLIT_LOAD_PLAN || Automatically plan the split load orders to final destination || SYSTEM
|-
| WCS_SPLIT_ORDER_BY_TRIP || Allow an order to be split when its items are loaded on different trips for delivery (Y/N)? || COST_CENTRE
|-
| WEB_SERVICE_STORE_REQ || Determines if the message request sent to the web server enquiry should be stored in the audit record - Y will store the message as a CLOB value. || SYSTEM
|-
| WEB_SERVICE_STORE_RESP || Determines if the message in response to the web server enquiry should be stored in the audit record - Y will store the message as a CLOB value. || SYSTEM
|-
| WEB_SERVICE_USER || User name for web service || SYSTEM
|-
| WMS_INBOUND_ARCH || Path for WMS XML archiving || SYSTEM
|-
| WMS_INBOUND_FAIL || Path for WMS XML failures || SYSTEM
|-
| WMS_INBOUND_LISTING_NAME || Filename for list of files in directory for WMS XML Order Inbound || SYSTEM
|-
| WMS_INBOUND_ORD_IDENTIFIER || Pattern for WMS Order Inbound XML || SYSTEM
|-
| WMS_INBOUND_PATH || Path for yet to be processed XML files from WMS || SYSTEM
|-
| WMS_LISTING_SCRIPT_NAME || Script name for WMS XML Order Inbound || SYSTEM
|-
| WOC_MSG_SEND_COUNT || Number of message per run sent to WCS via WOC || SYSTEM
|-
| WSA_ARCHIVE_DAYS || Determines the number of days that the web service messages will be retained in C-TMS prior to being archived. || SYSTEM
|-
| WS_COLLECT_LOCATION || Collection location to override one provided in web service to override collection depot in partnership || CUSTOMER
|-
| WS_COL_CUTOFF || Cut-off time for web service orders from an RDC to make the next days delivery. || SYSTEM
|-
| WS_DERIVE_COL_WINDOW || Derive Collection windows for Web Service Orders || COST_CENTRE
|-
| WS_DUMMY_DU_TYPE || Dummy DU Type used for Web Service order creation || SYSTEM
|-
| WS_EARLY_AVAIL_TIME || Early available time for Web Service Orders || COST_CENTRE
|-
| WS_MAX_MANF_RPE || Maximum RPE value for Web service || SYSTEM
|-
| WS_NUM_OF_RETRIES_ALLOWED || Max number of times a record will be sent to a web service endpoint || SYSTEM
|-
| WS_REASON_CODE || Default reason code for Web service || SYSTEM
|-
| WS_USE_TRIP_STATUS || Use Trip Status for Web Service || COST_CENTRE
|-
| XML_NO_DELAY_FILES || List of XML filenames that will require no delay in polling time (eg pack confirmation). || SYSTEM
|-
| XML_OUT_SUMM_LVL || Level to summarize XML outbound message || SYSTEM
|-
| ZERO_MANIFEST || Allow orders to be zero manifested and set to ABORTED || COST_CENTRE
|-
| ZERO_PACK_REASON || Zero packed reason code || COST_CENTRE
|-
| ZETES_INSTALLED || Zetes installed || SYSTEM
|-
| ZET_INBOUND_ARCH || Path for Microlise XML archiving || SYSTEM
|-
| ZET_INBOUND_FAIL || Path for Microlise XML failures || SYSTEM
|-
| ZET_INBOUND_IDENTIFIER || Pattern for MIC Trip Inbound XML || SYSTEM
|-
| ZET_INBOUND_LISTING_NAME || Filename for list of files in directory for MIC XML Trip Inbound || SYSTEM
|-
| ZET_INBOUND_PATH || Path for yet to be processed XML files from Microlise || SYSTEM
|-
| ZET_INC_SSCC_PREFIX || Include prefixes for SSCC formats for the Zetes interface (Y/N). || COST_CENTRE
|-
| ZET_LISTING_SCRIPT_NAME || Script name foe MIC XML Trip Inbound || SYSTEM
|-
| ZET_OUTBOUND_ARCH || Path for safe copy of XML files for Zetes || SYSTEM
|-
| ZET_OUTBOUND_PATH || Path for yet to be collected XML files for Zetes || SYSTEM
|-
| ZIP || Zip executable location on application server || SYSTEM
|-
| ZIP_SERVER || Application server folder for zipped Invoice files || SYSTEM
|-
| ZONE_POSTCODE_CHECK || Does Zone import check the postcode || SYSTEM
|-
| zip || Location of the zip executable on the application server || SYSTEM
|-
|API_CARRIER_PLAN ||The carrier for the API process which the customer will use with pre-packed labels ||CUSTOMER
|-
|DO_NOT_UPDATE_LOADING_RATES ||Do not update loading rates via customer onboarding ||SYSTEM
|-
|FLEXIPOD ||Set to Y to indicate the FlexiPod interface is active ||SYSTEM
|-
|FLEXIPOD_ACID ||Flexipod acid ||SYSTEM
|-
|FLEXIPOD_BREAK_DROPS ||Flexipod include breaks for the drops in the Add API call (Y/N) ||SYSTEM
|-
|FLEXIPOD_CARRIERS ||Set to Y indicates the Carrier can control if a trip is sent to FlexiPod ||SYSTEM
|-
|FLEXIPOD_CLIENTNUM ||FleXipod ClientNum sent in interface ||SYSTEM
|-
|FLEXIPOD_DEPOTS ||Set to Y indicates the Depot can control if a trip is sent to FlexiPod ||SYSTEM
|-
|FLEXIPOD_DIRECT ||Set to Y to indicate the FlexiPod interface is direct and not using Route Execution ||SYSTEM
|-
|FLEXIPOD_DROP ||Determines the Drop level STOP-OMS or ITEM ||SYSTEM
|-
|FLEXIPOD_EXPIRY ||Sets the expiry date for the manifest as a number of days after the end of the trip. ||SYSTEM
|-
|FLEXIPOD_EXTERNALSYSTEMUPDATE ||Flexipod process the External System Update messages in the API call (Y/N) ||SYSTEM
|-
|FLEXIPOD_FORCEITEMSCAN ||Force the items to be scanned separately: 0 to use the ScanLevel or 1 to force the scan by item. ||SYSTEM
|-
|FLEXIPOD_LISTPENDINGMANIFESTS ||Flexipod process the List Pending Manifest Update messages in the API call (Y/N) ||SYSTEM
|-
|FLEXIPOD_MERGE_DROPS ||Flexipod merge the orders on the drop in the Add API call (Y/N) ||SYSTEM
|-
|FLEXIPOD_PASSWORD ||FleXipod Webservice password ||SYSTEM
|-
|FLEXIPOD_PROXY ||Flexipod proxy server ||SYSTEM
|-
|FLEXIPOD_READDROP ||Flexipod process the Read Drop messages in the API call (Y/N) ||SYSTEM
|-
|FLEXIPOD_SCAN_LEVEL ||1,2 or 3 to indicate line or item level scanning ||SYSTEM
|-
|FLEXIPOD_SCAN_TYPE ||Contents and items ||SYSTEM
|-
|FLEXIPOD_SIGNATORY ||Set to Y to store the SignedByName as the actual signatory as information for the order at its collection of delivery location ||SYSTEM
|-
|FLEXIPOD_SPLIT ||Are orders to be split? ||SYSTEM
|-
|FLEXIPOD_SYSTEM ||FleXipod SYSTEM ID sent in interface ||SYSTEM
|-
|FLEXIPOD_TPCLIENTNUM ||FleXipod TPClientNum sent in interface ||SYSTEM
|-
|FLEXIPOD_USERCODE ||FleXipod webservice usercode ||SYSTEM
|-
|FLEXIPOD_USERNAME ||FleXipod webservice username ||SYSTEM
|-
|FLEXIPOD_WEBSERVICE ||Flexipod webservice endpoint URL ||SYSTEM
|-
|FLEXIPOD_WEBSERVICE_TASK ||Flexipod webservice endpoint URL for Tasks ||SYSTEM
|-
|FLEXIPOD_WEBSERVICE_UI ||Flexipod webservice endpoint URL ||SYSTEM
|-
|FLEXIPOD_WEBSERVICE_UI_EXEC ||Flexipod webservice endpoint URL for Route Execution ||SYSTEM
|-
|FLEXIPOD_X_API_KEY ||Flexipod x-api-key for External System Update messages ||SYSTEM
|-
|IMP_DERIVE_FROM_LOCATION ||Derive the collection location of an order. ||COST_CENTRE
|-
|IMP_DERIVE_ORDER_WINDOWS ||Derive the order windows. ||COST_CENTRE
|-
|IMP_SET_ORDER_TYPE ||Set the order type to RET, SLS or DIR. ||COST_CENTRE
|-
|IMP_SPLIT_CONTACT_NAME ||Split a contact name into Forename and Surname. ||COST_CENTRE
|-
|LIMIT_ADDRESS_MATCH ||Limit address matching to line1, line2 and postcode ||SYSTEM
|-
|LOOKUP_FOR_ROUTE_CODES ||Display lookup button in PLANNING beside Route Code ||SYSTEM
|-
|PSD_CONTACT_ADDRESS ||Polar Speed Distribution Ltd ||SYSTEM
|-
|PSD_CONTACT_TEL ||Tel: +44 (0) 1525 217666 ||SYSTEM
|-
|REBOOK_REQ_SUBREF ||Add Rebook Sub reference when CBR exception added to item ||SYSTEM
|-
|REBOOK_SERVICE_LEVEL ||Service Level For rebooked orders when set to copy use existing ||SYSTEM
|-
|RESET_MANUAL_SCHEDULE ||Reset manual schedule flag from the planning screen ||SYSTEM
|-
|TMP_ENG_TRIP_PREFIX ||Scheduling Engine Trip Prefix ||COST_CENTRE
|-
|TRM_3PL_REROUTE ||Reroute the order in the fixed-drop scheduling engine to the next available route for the day (Y/N) ||SYSTEM
|}

Business Data Maintenance

2025-09-16T10:41:23Z

Anw: Added details of MCS Scanning changes

Within the C-TMS system there is a large amount of Static or Reference data, Locations, Resources, Products, Customers, Cost Centres, Lane Based Orders and Messaging have been discussed separately but there are several other areas of static data that exist, namely Business Data, System Parameters and System Configuration.

Maintenance of business data functionality is used within C-TMS software to maintain data related to the business. The business data maintenance form can be accessed from the Maintenance Menu.

There are many tabs covering the different business data requirements.

== Group Names ==
This displays valid Order Groups that exist in C-TMS system. Order groups are used to group orders together, for example all orders from a location could be grouped together.

<center>[[Image:bdm_group_names.jpg|600px]]</center>

== CrossDock Paths ==
[[Crossdock]]s are used within C-TMS system to configure deliveries from A to B via C. This approach is commonly used for long distance deliveries and helps provide a better utilisation of resources. A Crossdock is created for a To Location, From Location, Product Type and Via Location, for example Non Perishable deliveries from Rugby to Crosby should be delivered via Haydock.

<center>[[Image:bdm_crossdock_paths.jpg|600px]]</center>

== Adjustment Reason Codes ==
Provides a list of valid adjustment reason codes, an adjustment reason code can be selected when performing a Manual Advance.

<center>[[Image:bdm_adjustment_reason_codes.jpg|600px]]</center>

== Reason Codes ==
This tab displays a list of valid Reason Codes and their usage.

<center>[[Image:bdm_reason_codes.jpg|600px]]</center>

These codes can be used to record why a user has opted to perform a certain action, an example of this is when a user Reverses TI's they can enter the reason for the reversal. This table is now used to maintain non conformance codes for collections and deliveries.

If using Quarantine processing, you may set the action of new reason codes to "QUAR". This indicates that the reason code will add the item to quarantine, which may then be handled through the the [[Quarantine Maintenance]] screen.

== Order Reason Codes ==
Displays a list of valid Order Reason Codes. These codes can be used in Trip Debrief to record a general order reason code e.g. for lateness.

<center>[[Image:bdm_order_reasons.jpg|600px]]</center>

== Min Ti RPE Quantity ==
Defines the minimum number of RPE's that should be placed on an order during Create TI's processing.

<center>[[Image:bdm_min_ti_rpe_quantity.jpg|600px]]</center>

== Trip Statuses ==
Displays a read only list of Trip status that are used within C-TMS, it also shows which options are set against a particular status, for example whether a carrier is required to set a Trip to a particular status.

<center>[[Image:bdm_trip_status.jpg|600px]]</center>

== Order Statuses ==
Displays a read only list of Order status that are used within C-TMS, it also shows which options are set against a particular status, for example Orders in that status can be Re-booked.

<center>[[Image:bdm_order_status.jpg|600px]]</center>

The CSTM checkbox is ticked if orders of the status can be sent to MTM.

The CBR checkbox is ticked if orders of the status can be rebooked.

== Service Types ==
{{Incomplete}}

== Surcharges ==
Fuel Surcharges are created on the Business Data Form's Surcharge tab. They specify a percentage surcharge to be calculated against all valid payments on a trip for an associated carrier whose fuel surcharge parameter date falls between the validity dates of the surcharge.

<center>[[Image:bdm_surcharges.jpg|600px]]</center>

Trip level payments are flagged as subject to fuel surcharges on the Accounts Maintenance Form's Payments tab. Fuel Surcharges are viewed on the Payments Form and are calculated automatically by the ACC package at time of trip payment creation (either automatically from fixed routes etc, at time of status change or as Payments are raised manually (via Trip Summary / Finance tab etc)) regardless of whether or not there are manually rated payments on the trip (the other payments are not re-calculated if manual rating is detected).

{{Note|
* Access permissions to the Business Data Form have not changed. Only users with new function ACC_AMEND_FUELSURCHAR_PYTTYPE_STATUS are able to set payments to be surcharged.
* New adm_system_parameter ACC_FUELSURCH_EVENTDATE is used to indicate the trip date that will be used to check for a valid surcharge (either TRIPSTART or TENDERED date).
* The new fuel surcharging payment types are FUELSurch (trip level) and Fuel-Charge (order level).
}}

== Location Types ==
You can use this tab to maintain the location types associated with the business in the system. These are used when creating new locations in the Locations maintenance screen.

<center>[[Image:bdm_location_types.jpg|600px]]</center>

You can create the location type with a description.

You can then maintain some default criteria against the location type:
* ''General''
** Use as Xdock
** Enable Trailer Swap
** Inventory Managed
** Optional Loc Usage
* ''EPOD'' - for use with the Aptean POD Calidus Edition system
** Send Jobs Load/Unload - whether these jobs are sent to C-ePOD on this activity.
** Consol Jobs Load/Unload - whether these jobs are automatically consolidated when sent to C-ePOD on this activity.
** Send Dets Load/Unload - whether these jobs are sent with details (items) to C-ePOD on this activity.
** EPOD Job Group Load/Unload - a specific job group to use when sending these jobs to C-ePOD on this activity.

== XDock Paths ==
{{Incomplete}}

== Paragon Staging Posts ==
Displays specified routes from/to with (via) Staging Post locations as supplied via a CSV data file from Paragon Data. The [[IMPORTS_EXEC|imported]] data from Paragon, may be supplimented, edited, or deleted via the use of the named buttons within the tab.

== Delivery Method ==
{{Incomplete}}

== Route Codes ==
Superseded by Fixed Route Maintenance.

== Location Zones ==
You can use this to maintain zones in the system.

<center>[[Image:bdm_location_zones.png|600px]]</center>

Zones may be used by various areas of the system (e.g. fixed routes) to determine where the location is grouped together, and therefore how to route to it from another location.

A zone can be maintained here with the following information:
* Zone ID - a unique ID for this zone.
* Type - Defines what the range is of - one of:
** Postcode
** Planning Region
** Postal Region
** Country
** Zone - a zone already defined in the system.
** Postal String
** Suburb
* Country
* Town/Suburb
* From Range
* To Range
* Inactive
* Inc/Exc - this flag indicates if the type of zone is being included or excluded from the location zone to enable greater flexibility to specify the delivery locations that are valid for the particular location zone.
* Customer
* Routing Code
* Cost Centre

{{Note}} When using Zones in the standard journeys for contracts, the system would have to look through all zones created on the system for other purposes like scheduling engine. Rather than consider zones that have not been defined for Finance, you may set up zones based on the areas for charging and click the "Rating" flag - the contracts function only looks at these zones.

Location Zones may also be imported through [[Imports]]:
* [[Imports_Details#LOC_ZONES|LOC_ZONES]]

== Asset Origins ==
This tab allows you to define the default location of assets belonging to customers.

<center>[[Image:bdm_asset_origins.jpg|600px]]</center>

This is used only when using permanent asset tracking.

You can specify the customer (through a lookup), the location (through a lookup) and whether it is the default location for that customer.

== Time Zones ==
This tab can be used to specify time zones used by the system to convert system dates and times into local dates and times. The business will need these to deal when planning and executing trips.

<center>[[Image:bdm_time_zones.jpg|600px]]</center>

You can specify:
* TZ Name - the name e.g. Greenwich Mean Time
* Abbrev - an abbreviation e.g. GMT
* DST Abbrev - an abbreviation of the daylight saving time for this time zone e.g. BST
* UTL Offset - the number of hours or minutes offset.
* Daylight Saving - whether daylight saving time is implemented in this time zone.
* Cost Centre - a lookup is provided.

For each time zone with daylight saving, you can also specify the start or end of the daylight saving time.

== Order Types ==
This screen is used to maintain the different order types that exist within the business.

<center>[[Image:bdm_order_types.jpg|600px]]</center>

== Service Levels ==
You can maintain service levels here.

<center>[[Image:bdm_order_types.jpg|600px]]</center>

You can enter:
* Inactive
* Level
* Description
* Coll Offset
* Del Offset
* Early Col
* Late Col
* Early Del
* Late Del

These service levels settings will be used to default collection and delivery windows when orders are created with that service level.

== Delivery Type ==
You can maintain delivery types here.

<center>[[Image:bdm_delivery_types.jpg|600px]]</center>

Delivery types are used against orders to group them, and are a critical part of order revenue generation from tariffs.

You can enter:
* Type
* Code
* Inactive
* Auto-Schec
* Do Not Rate
* Collect Saturday/Sunday
* Deliver Saturday/Sunday
* EPOD Mode - when using Aptean POD Calidus Edition (C-ePOD), and when configured to send different data by delivery type, this controls what mode to use i.e. how to map the data. A [[C-ePOD_Interface|List]] of the mapping per type is available on Assist.

== Transport Mode ==
You can maintain transport modes here. Transport modes are used by fixed route scheduling to determine wehther an order should be scheduled onto a route (defined by the transport mode on the order and route)

You can enter the transport mode and description here.

== Shift Patterns ==
{{:Shift Patterns}}

== Team Details ==
{{Note}} This is specific to session collection functionality.

<center>[[Image:bdm_team_details.jpg|600px]]</center>

Team master data will be created to link a team to a home depot for creating collection orders. The Team data including attributes to control the type of session that each team operates, whether the end session collection is required from transport, which depot the mid-session and end session collections should be delivered to and an optional validation period in minutes that that will control the planning for cold, normal and hot weather conditions.

If the related Team master data for a session record does not exist in C-TMS, the session record will be rejected by the interface validation functionality and not uploaded.

Session teams can be organised to run two or more different sessions concurrently. The team attributes controlling whether mid and end session collections and the depot (SHU or Manufacturing Centre) location derived from the team will apply to each and every session the team is assigned to.

As an optional entry, the Team Maintenance screen will allow an override validation period to be setup for cold, normal and hot ambient weather conditions. This will allow specific validation times for each team associated with sessions and will give NHSBT the flexibility to setup various operational scenarios, for example equipment at the sessions allows longer validation periods, or manufacturing needs a more regular 'trickle' of blood from sessions so the validation time is decreased.

You can use this tab to create Session teams.

You can select by Depot.

You can enter:
* Team ID
* Team Name
* Post Code
* Team Centre
* Location Type
* Mid Session details
** Transport
** Receiving Depot
* End Session details
** Transport
** Receiving Depot
* Validation Time
** Cold
** Normal
** Hot

== Storage Types ==
{{Incomplete}}

== Note Types ==
You can maintain location note types in this tab. You can then use these to add notes against a location.

== Fixed Costs By Route ==
You can use this tab to enter a fixed cost against a route for a particular customer.

== Booking Status ==
This tab allows you to maintain the booking types in the system. These are predominantly used by the CTL Customer Services screen.

== Route Priority ==
{{Note}} This is specific to the Paragon Route Master (Strategic) interface.

You can use this tab to enter rout codes, priorities and cust off times.

== Paragon Keys ==
This tab allows you to maintain Paragon Run Keys.
{{Note}} This is required when and specific to using the Paragon Routing and Scheduling system through an API.

<center>[[Image:bdm_par_keys.png|800px]]</center>

<noinclude>
[[Category:Maintenance|140]]
[[Category:C-TMS Modules|D-140]]
[[Category:C-TMS User Guide|BD-140]]
</noinclude>

WCS Maintenance

2025-09-16T10:28:08Z

Anw: Minor change

The WCS Maintenance screen is used predominantly for the control of the MCS or WCS RF scanning system and the interface to that system.

== Main Functions ==

=== WCS Location ===
On this tab you can maintain the locations of each type for each depot.

<center>[[Image:wcs_location.png|800px]]</center>

{{Note}} If you are using location scanning in MCS, then locations must be set up here per depot, per product type.

=== WCS Location Type ===
<center>[[Image:wcs_location_type.png|800px]]</center>

These define the locations in the depots for storage of the different products, for example:
* Quarantine Locations
* Inbound Locations
* Outbound Locations

=== Queue Maintenance ===
{{Warning}} This system configuration will be preconfigured. If changed without appropriate knowledge, this will make the WCS system inaccessible.

Here, you can see the queues created for communication with the WCS. These can be configured per depot. You can start or stop the interface with the provided buttons.

=== WCS Messages In ===
On this tab you can view any messages coming in from WCS, plus the success.

=== WCS Messages Out ===
On this tab you can view any messages going out to WCS, plus the success.

=== WCS Exception ===
On this tab you can view any exceptions, debug messages, warnings, information or errors when processing messages coming in from WCS.

=== Update Locations ===
Here, you can remove the current location of all DUs in the Sin Bin.

=== WCS Readvice ===
Here, you can resend a manifest preadvice to WCS.

<noinclude>
[[Category:Maintenance|220]]
[[Category:C-TMS Modules|D-220]]
[[Category:C-TMS User Guide|BD-220]]
</noinclude>

WCS Maintenance

2025-09-16T10:27:25Z

Anw: Updated with new MCS development

The WCS Maintenance screen is used predominantly for the control of the WCS RF scanning system and the interface to that system.

== Main Functions ==

=== WCS Location ===
On this tab you can maintain the locations of each type for each depot.

<center>[[Image:wcs_location.png|800px]]</center>

{{Note}} If you are using location scanning in MCS, then locations must be set up here per depot, per product type.

=== WCS Location Type ===
<center>[[Image:wcs_location_type.png|800px]]</center>

These define the locations in the depots for storage of the different products, for example:
* Quarantine Locations
* Inbound Locations
* Outbound Locations

=== Queue Maintenance ===
{{Warning}} This system configuration will be preconfigured. If changed without appropriate knowledge, this will make the WCS system inaccessible.

Here, you can see the queues created for communication with the WCS. These can be configured per depot. You can start or stop the interface with the provided buttons.

=== WCS Messages In ===
On this tab you can view any messages coming in from WCS, plus the success.

=== WCS Messages Out ===
On this tab you can view any messages going out to WCS, plus the success.

=== WCS Exception ===
On this tab you can view any exceptions, debug messages, warnings, information or errors when processing messages coming in from WCS.

=== Update Locations ===
Here, you can remove the current location of all DUs in the Sin Bin.

=== WCS Readvice ===
Here, you can resend a manifest preadvice to WCS.

<noinclude>
[[Category:Maintenance|220]]
[[Category:C-TMS Modules|D-220]]
[[Category:C-TMS User Guide|BD-220]]
</noinclude>

File:Wcs location.png

2025-09-16T10:26:23Z

Anw: Anw uploaded a new version of File:Wcs location.png

System Parameters List

2025-09-16T10:15:21Z

Anw: Added new MCS Parameters

{| class="wikitable apt-searchable" border="1" id="systemparams"
|- bgcolor="silver"
!Parameter !! Description !! Level
|-
| ACC_ACTUAL_DISTANCE || Controls if the distance is rated using actual distance || SYSTEM
|-
| ACC_ADD_LINES || Does the user rate by lines and additional tariffs || COST_CENTRE
|-
| ACC_ALLOCATE_MANUAL_COST || Allow manual cost payments on orders || SYSTEM
|-
| ACC_ALLOW_MULTIPLE_CCY || Can multiple currencies be defined in the database? || SYSTEM
|-
| ACC_ALLOW_ZERO_RPE || Allow zero quantity to be returned from get charges (for RPE tier) || SYSTEM
|-
| ACC_ALWAYS_APPLY || There are tariffs that should always be applied || SYSTEM
|-
| ACC_CALC_SECURITY || Indicates if Security charges are applicable || SYSTEM
|-
| ACC_CALC_SERVICES || Service charges applicable || SYSTEM
|-
| ACC_CHECK_ORDER || Should order be assessed for rating || SYSTEM
|-
| ACC_CONSOL_RADIAL_COSTS || Indicates if radial charges are consolidated at delivery location || SYSTEM
|-
| ACC_CONTRACT_OWN || To control if the system looks at the contract or the existing table to identify the charges for own packaging || SYSTEM
|-
| ACC_CONTRACT_PICKPACK || To check the relevant contract for a PICKPACK tariff and generate a payment || SYSTEM
|-
| ACC_CONTRACT_SERVICES || To control a procedure that will check if there are any service records on the order || SYSTEM
|-
| ACC_CUST_FUEL || Apply Customer Fuel Charges || SYSTEM
|-
| ACC_Calc_Payment_Ord || Controls whether payment button is displayed on Orders forms - Y or N, Internal Charges are being applied to orders) || SYSTEM
|-
| ACC_Calc_Payment_Trip || Controls whether payment button is displayed on Trip forms - Y or N, Trip Cost method is defined against the Carrier Type || SYSTEM
|-
| ACC_Calc_Revenue_Ord || Control Order revenue calculation method - CONTRACT or CONTRACT-TPL || SYSTEM
|-
| ACC_Calc_Revenue_Trip || Controls whether revenue button is displayed on Trip forms - Y or N, Trip Cost method is defined against the Carrier Type) || SYSTEM
|-
| ACC_Calc_Saving_Ord || Controls whether the saving button is displayed on Orders forms - Y or N || SYSTEM
|-
| ACC_DEMURRAGE || Number of hours before demurrage charge start || SYSTEM
|-
| ACC_EDIT_ORD_CHARGE || Allow users to edit revenue charges || SYSTEM
|-
| ACC_FUELSURCH_EVENTDATE || Details whether Fuel Surcharges are calculated based on TENDERED or TRIPSTART date. || SYSTEM
|-
| ACC_FUEL_SEC_MODE || Are Fuel and security charges controlled by transport mode || SYSTEM
|-
| ACC_INC_ALL_ORDER_COST_PAYMENTS || Include all order cost payments (Y/N)? || COST_CENTRE
|-
| ACC_INDEXES || Use Acc indexes || SYSTEM
|-
| ACC_INT_CHRG_AT_TRUNK_LEG || Indicates if Internal Charges (trunk and radial) are generated by the trunk leg || SYSTEM
|-
| ACC_INVOICE_LOGO || Invoice Logo || COST_CENTRE
|-
| ACC_KNOWN_ZONE || Can rating Zone be predicted? || SYSTEM
|-
| ACC_LINES_OR_HEADER || Rate orders by line level only (Y), or by header level only or both levels (N) || CUSTOMER
|-
| ACC_OF_VERSION || Controls format of extract to OF || SYSTEM
|-
| ACC_ORD_STD_COST || Control Order standard cost calculation method - CONTRACT or CONTRACT-TPL || COST_CENTRE
|-
| ACC_PACKAGES || Are DU type charges separately || SYSTEM
|-
| ACC_PLAN_COSTS || Allows user to calc costs from Planned trips || COST_CENTRE
|-
| ACC_PROTECT_STATUS || Indicates if Payment status are protected from update to F || SYSTEM
|-
| ACC_RATE_BY_PARTY || To control if the rating process will look for a party contract when rating || SYSTEM
|-
| ACC_ROUND_AVG_DU_WEIGHT || Round Avg Du Weight to 3 decimal places for rating || COST_CENTRE
|-
| ACC_SCREENING_CHARGES || Are screening charges applied || SYSTEM
|-
| ACC_SERVICE_METHODS || Controls is services are allocated by methods || COST_CENTRE
|-
| ACC_SHOW_PROFIT || Controls the display of the Profit Field || COST_CENTRE
|-
| ACC_SUPPRESS_RATING || Should rating be prevented when validating orders || CUSTOMER
|-
| ACC_TRANSPORT_MODE || Is transport mode included in Contract charges || SYSTEM
|-
| ACC_USE_ORD_TRLR_TYPE || Should order revenue be calculated from the order trailer type even when scheduled || COST_CENTRE
|-
| ACC_ZERO_DESPATCHED || Controls if Zero despatched lines are ignored from rating || COST_CENTRE
|-
| ACTIVE_ROLE_DISPLAY || Indicates if the active role is displayed in the tool bar || SYSTEM
|-
| ADDITIONAL_ORDER_VALIDATION || Additional order validation required for product weight || COST_CENTRE
|-
| ADD_CSV_COL_FORMATTING || Add Column Formatting to CSV extracts || SYSTEM
|-
| ADM_EXCLUDE_AUDIT_LOG || Processes that will be excluded from writing audit log records. || SYSTEM
|-
| ADM_EXCLUDE_PACKAGE_MSG || Packages whose adm log messages are not to be written || SYSTEM
|-
| ADM_LOG_ARC_DEL_DAYS || Number of days that ADM_LOG_ARCHIVE messages should be kept for || SYSTEM
|-
| ADM_NO_DISPLAY_MENU || Enable the user to access the menu item || SYSTEM
|-
| ADM_UNKOWN_ORDERS || Identify amended/duplicate orders || SYSTEM
|-
| ADM_UPSHIFT_DU_TYPE || Upshifts the despatch unit type when Y. || SYSTEM
|-
| ADM_UPSHIFT_PRODUCT_TYPE || Upshifts the product type when Y || SYSTEM
|-
| ADM_WRITE_ERRORS || Store fatal form errors in FORM_ERROR_LOG || SYSTEM
|-
| ADR_REGS || Are ADR regulations displayed for trips || COST_CENTRE
|-
| ALLOC_RESOURCE || Are drivers and tractors allocated to own fleet carriers? || SYSTEM
|-
| ALLOC_TRIP_PMNTS || Allocate the trip payments as order costs || SYSTEM
|-
| ALLOW_DIRECT_BAY_MOVES || Should orders be moved directly from the receipt bay or to the despatch bay from the grid? || SYSTEM
|-
| ALLOW_DUPLICATE_CUST_REF || Allow orders with duplicate cust refs but different to locations. || SYSTEM
|-
| ALLOW_ETA_UPDATES || Determines whether the user can update ETA values || COST_CENTRE
|-
| ALLOW_HOLD_ORDERS || allow orders to be place don hold || SYSTEM
|-
| ALLOW_MANUAL_RPE || Allow RPE to be entered (via the inbound EDI) and do not overwrite. || SYSTEM
|-
| ALLOW_MISSING_DEL || Is unit weight sent in the items || SYSTEM
|-
| ALLOW_MULTIPLE_ADD_REFS || Allow multiple additional references for an order values will be (Y/N) || COST_CENTRE
|-
| ALLOW_POC_EDIT || Allow users to edit the POC Flag in Debrief || SYSTEM
|-
| ALLOW_TENDERED_PARAGON_TRIPS || Allow Tendered Trips in Paragon || COST_CENTRE
|-
| ALLOW_TENDERED_PARAGON_TRIPS || Allow Tendered Trips in Paragon || COST_CENTRE
|-
| ALLOW_TRP_DEL_TYPE_UPDATE || Allow Delivery type updates in the planning screen || CARRIER
|-
| ALLOW_UNLOAD_ASSET || Controls if asset records are created as part of unload || SYSTEM
|-
| ALLOW_UNSCHEDULE_SCHED_COLL || Controls if menu item Unschedule sched coll is displayed || SYSTEM
|-
| ALTERNATE_DB_NAME || Alternate DB Name || SYSTEM
|-
| ALTERNATE_ORDER_ENTRY || Validate item identifier field || COST_CENTRE
|-
| AMAZON_OWNER_CODE || Asset owner code to pass to Amazon || SYSTEM
|-
| API_CARRIER || Carrier ID for API || SYSTEM
|-
| API_EVENTS || Are events sent out via API || SYSTEM
|-
| API_TEXT_AUTHORISATION || authorisation code for API text || SYSTEM
|-
| API_TEXT_END || Time of day the system stops sending texts || SYSTEM
|-
| API_TEXT_ENDPOINT_URL || URL endpoint for API text || SYSTEM
|-
| API_TEXT_START || Time of day the system can start sending texts || SYSTEM
|-
| API_WS_ADDRESS || WebService endpoint for API events || SYSTEM
|-
| API_WS_ELUCID_ADDRESS || WebService endpoint for API events for Elucid || SYSTEM
|-
| API_WS_ELUCID_PASSWD || WebService password for API events for Elucid || SYSTEM
|-
| API_WS_ELUCID_USER || WebService username for API events for Elucid || SYSTEM
|-
| APPLY_ADDITIONAL_LOC_CHECKS || To enable additional validation checks for location entry. || SYSTEM
|-
| ARDO_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header (Unilever) || SYSTEM
|-
| ARDO_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header (Unilever) || SYSTEM
|-
| ARDO_INBOUND_PATH || Path for yet to be processed XML files (Ardo) || SYSTEM
|-
| ASSEMBLY_DU_TYPE || Assembly DU Type || COST_CENTRE
|-
| ASSET_AT_FIXED_ORIGIN || Asset At Fixed Origin || COST_CENTRE
|-
| ASSET_DEBRIEF || Indicates if assets debriefed with Items || COST_CENTRE
|-
| ASSET_FORMAT || Indicates which order item field will identify an asset || COST_CENTRE
|-
| AUTO_COMMIT_EMPTY_STOPS || Commit After Deletion of Empty Stops || COST_CENTRE
|-
| AUTO_PLAN_ORDERS || Auto Plan orders onto an existing trip || COST_CENTRE
|-
| AUTO_ROUTE_NEW_ORDERS || Automatically plan orders loaded || SYSTEM
|-
| AUTO_SCHEDULING || Auto Scheduling of orders || COST_CENTRE
|-
| AUTO_SCHED_INACTIVE_DEPOTS || List the inactive depots to exclude from the fixed drop scheduling engine. || SYSTEM
|-
| AUTO_SET_DELIVERY_TYPES || Automatically set delivery type rules || COST_CENTRE
|-
| BEIG2_FTP_DESTINATION_DIRECTORY || Directory for FTP of BirdsEye Files || SYSTEM
|-
| BEIG2_FTP_DESTINATION_IP_ADDRESS || IP for FTP of BirdsEye Files || SYSTEM
|-
| BEIG2_FTP_DESTINATION_PASSWORD || Password for FTP of BirdsEye Files || SYSTEM
|-
| BEIG2_FTP_DESTINATION_PORT || Port for FTP of BirdsEye Files || SYSTEM
|-
| BEIG2_FTP_DESTINATION_USERNAME || Username for FTP of BirdsEye Files || SYSTEM
|-
| BEIG2_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header || SYSTEM
|-
| BEIG2_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header || SYSTEM
|-
| BEIG2_INBOUND_PATH || Path for yet to be processed XML files || SYSTEM
|-
| BEIG2_OUTBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header || SYSTEM
|-
| BEIG2_OUTBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header || SYSTEM
|-
| BEIG2_OUTBOUND_PATH || Path for yet to be processed XML files || SYSTEM
|-
| BEIG_ENABLED || To enable the inbound and outbound file processing on this DB || SYSTEM
|-
| BEIG_FTP_DESTINATION_DIRECTORY || Directory for FTP of BirdsEye Files || SYSTEM
|-
| BEIG_FTP_DESTINATION_IP_ADDRESS || IP for FTP of BirdsEye Files || SYSTEM
|-
| BEIG_FTP_DESTINATION_PASSWORD || Password for FTP of BirdsEye Files || SYSTEM
|-
| BEIG_FTP_DESTINATION_PORT || Port for FTP of BirdsEye Files || SYSTEM
|-
| BEIG_FTP_DESTINATION_USERNAME || Username for FTP of BirdsEye Files || SYSTEM
|-
| BEIG_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header || SYSTEM
|-
| BEIG_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header || SYSTEM
|-
| BEIG_INBOUND_PATH || Path for yet to be processed XML files || SYSTEM
|-
| BEIG_OUTBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header || SYSTEM
|-
| BEIG_OUTBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header || SYSTEM
|-
| BEIG_OUTBOUND_PATH || Path for yet to be processed XML files || SYSTEM
|-
| BGW_AUTO_REBOOK || Indicates if auto rebook is switched on when non conformance is added || COST_CENTRE
|-
| BGW_DUMMY_WASTE || Defines Dummy waste location for BGW. || COST_CENTRE
|-
| BGW_TRAILER_SET || Defines which Trailer Types are allowed. || COST_CENTRE
|-
| BKG_APPEND_TO_ORDERS || Controls whether Bookings can append to an existing Order if the Slot is already used. || SYSTEM
|-
| BKG_AUTO_CREATE_SLOT || Creates slots if no slot exists || SYSTEM
|-
| BKG_DEF_COST || Default Cost Centre for Bookings || SYSTEM
|-
| BKG_DEF_CUST || Default Customer for Bookings || SYSTEM
|-
| BKG_DEF_DELIVERY_DEL_TYPE || Any order that are created via the interface, that are delivering to their final loc || SYSTEM
|-
| BKG_DEF_POPULATE_DEL || Any order that are created via bookings will have Del Type populated by system, specific to DSG || SYSTEM
|-
| BKG_DEF_TRUNK_DEL_TYPE || Defines the default booking trunk delivery type for any orders being delivered inti a x-dock location, default to null || SYSTEM
|-
| BKG_GEN_TI_METHOD || Defines whether Gen TI does standard, xdock of both processes, STANDARD, BOTH or XDOCK. || SYSTEM
|-
| BKG_INCREMENT || Increment exiting Bookings on import rather than overwriting || SYSTEM
|-
| BKG_REV_TI_DISBAND_INV_FIX_RTE || Should Reverse TIs disband Fixed Trips - Y or N || SYSTEM
|-
| BKG_SLOT_INACTIVATE || Controls whether existing Slots are updated to INACTIVE during a Slot Import. || SYSTEM
|-
| BKG_TYPE_9_DU_TYPE || Default DU Type for Type 9 Orders || SYSTEM
|-
| BKG_USE_BOOKING_STATUS || Defines whether booking status is being used, N, PROVISIONAL, PLANNED or CONFIRMED. || SYSTEM
|-
| BMW_DOT_CODE || Tyre Age for BMW || SYSTEM
|-
| BUF_OLD_ORD_CLEAR_DAYS || Number of days in the past to be checked by the Buffaload order clear down || SYSTEM
|-
| BWSC_GEO_ADD_NETWORK_LOV_LIMIT || When set to Y the LOV for adding network locations will only show SSS, BRANCH and PLANT locations || SYSTEM
|-
| CALCULATE_CONTRACTUAL_WEIGHT_TRG || Allow contractual weights to be re-calculated via database trigger (set to N for LFS testing) || SYSTEM
|-
| CALC_DIMEN || Calculate volume from dimensions || COST_CENTRE
|-
| CALIDUS_ASSIST_BASE_URL || URL for Calidus Assist Install || SYSTEM
|-
| CALIDUS_ASSIST_RELEASE_DB || The final part of the URL used to view the release notes, for this database, on Calidus assist. || SYSTEM
|-
| CALL_LOGGING_DATE_RANGE || Call Logging Date Range Days || SYSTEM
|-
| CAL_DEFAULT_TIME_OFFSET || Default time offset which gets added to times in Order tracking, for users viewing data in different timezone || SYSTEM
|-
| CAL_DEFAULT_TIME_ZONE || Description of timezone, used in Order Tracking form, freetext || SYSTEM
|-
| CAL_WORKING_DAY_MAP || Defines which days of the week are being worked - Sunday to Saturday, Y or N. || COST_CENTRE
|-
| CANCEL_STATUS_CHK || Only orders on Planned trips cn be cancelled || SYSTEM
|-
| CARGOWISE_BILLING_BRANCH_CODE || Billing Branch Code for Cargowise || COST_CENTRE
|-
| CARGOWISE_BRANCH || Branch for Cargowise || COST_CENTRE
|-
| CARGOWISE_CONSIGNEE || Consignee name for Cargowise || COST_CENTRE
|-
| CARGOWISE_DATABASE || Controls which cargowise database invoices are exported to || COST_CENTRE
|-
| CARGOWISE_DEPARTMENT || Department code || COST_CENTRE
|-
| CARGOWISE_DESTINATION_PORT || Destination Port || COST_CENTRE
|-
| CARGOWISE_EXPORT || Payments are exported to Cargowise || COST_CENTRE
|-
| CARGOWISE_ORIGIN_PORT || Origin Port for Cargowise || COST_CENTRE
|-
| CARRIER_API_CLIENT_CODE || Value sent across to LFE in API || SYSTEM
|-
| CARRIER_API_MANIFEST_READY_TIME || The cut-off time for the ready time for the carrier manifest (HH24:MI). || SYSTEM
|-
| CARRIER_API_WS || Endpoint for LFE API || SYSTEM
|-
| CARRIER_API_WS_AMEND || Endpoint for Carrier API updates || SYSTEM
|-
| CARRIER_API_WS_CANCEL || Endpoint for Carrier API cancellations || SYSTEM
|-
| CARRIER_INVOICE_TYPE || Carrier Invoice type || SYSTEM
|-
| CARRIER_RULES_ALL || Controls if all du types and products are checked || SYSTEM
|-
| CARRIER_WORK_REP_FOOTER_1 || The footing printed at the bottom of the CARRIER_WORK_CONF report (first part). || SYSTEM
|-
| CARRIER_WORK_REP_FOOTER_2 || The footing printed at the bottom of the CARRIER_WORK_CONF report (second part). || SYSTEM
|-
| CARR_GAZ_POSTCODE_FORMAT || For which carrier gazetteer formats will the postcode in the file exclude spaces. (List delimited with semi-colons) || SYSTEM
|-
| CARR_SRVCE_LEVEL_OFFSET_DAYS || The default minimum number of offset days to calculate the collection job date for UKMail. || COST_CENTRE
|-
| CC_FORMAT_PATTERN || Click and Collect Ext Ref format || SYSTEM
|-
| CD_DIR || Directory used for copying zipped files || SYSTEM
|-
| CFX_CARRIER || Stores the name of CFX Carrier || CARRIER
|-
| CFX_CONTROL || Is there control over which trips go to CFX || SYSTEM
|-
| CFX_CONTROL_CUSTOMER || Controls which customers are configured for CFX || CUSTOMER
|-
| CFX_EXT_LOCATION_NAME || Include the extra location name in the CFX messages (Y/N) || SYSTEM
|-
| CFX_LINES_AND_ITEMS || Are items and lines included in CFX file, S,D,B,N || SYSTEM
|-
| CFX_NEW_ORDERS || Does adding orders to a trip re-trigger the CFX file? || SYSTEM
|-
| CFX_ORDER_ADDRESSES || Are order addresses include in the CFX file || SYSTEM
|-
| CFX_ORDER_HEADER || Are orders included in CFX file || SYSTEM
|-
| CFX_ORDER_HEADER_TMS || Is the order header TMS section included in CFX file || SYSTEM
|-
| CFX_OWNING_DEPOT || Is the owning depot included in the filename? || SYSTEM
|-
| CFX_SEND || Are trips sent to CFX || SYSTEM
|-
| CFX_STATUS_CHECK || Are carriers checked at status change for CFX? || SYSTEM
|-
| CHANGE_DEBRIEF_LABELS || Controls the labels for certain items in the debrief and orders screen || SYSTEM
|-
| CHANGE_PRINTER || Is change printer displayed || COST_CENTRE
|-
| CHECK_ELUCID_IMBALANCE || Check for stock imbalance at Elucid || COST_CENTRE
|-
| CHECK_RESOURCES || Check Resource on existing trips before allocation || SYSTEM
|-
| CHG_SCHED_DATE_TRIP || A comma-separated list of trip status for which the schedule may be changed || SYSTEM
|-
| CIM_CONF_INBOUND_IDENTIFIER || Pattern for MIC Order Inbound XML || SYSTEM
|-
| CIM_CONF_INBOUND_LISTING_NAME || Filename for list of files in directory for MIC XML Order Inbound || SYSTEM
|-
| CIM_CONF_LISTING_SCRIPT_NAME || Script name for MIC XML Order Inbound || SYSTEM
|-
| CIM_ENABLED || XML Isotrak enabled for this database || SYSTEM
|-
| CIM_INBOUND_ARCH || Path for CIM XML archiving || SYSTEM
|-
| CIM_INBOUND_FAIL || Path for CIM XML failures || SYSTEM
|-
| CIM_INBOUND_IDENTIFIER || Pattern for MIC Order Inbound XML || SYSTEM
|-
| CIM_INBOUND_LISTING_NAME || Filename for list of files in directory for MIC XML Order Inbound || SYSTEM
|-
| CIM_INBOUND_MAR_IDENTIFIER || Pattern for CIM Order update XML || SYSTEM
|-
| CIM_INBOUND_PATH || Path for yet to be processed XML files from CIM || SYSTEM
|-
| CIM_LISTING_SCRIPT_NAME || Script name for MIC XML Order Inbound || SYSTEM
|-
| CIM_OUTBOUND_ARCH || Path for archiving outbound CIM XML interfaces || SYSTEM
|-
| CIM_OUTBOUND_FAIL || Path for failing outbound CIM XML interfaces || SYSTEM
|-
| CIM_OUTBOUND_PATH || Path for outbound CIM XML interfaces || SYSTEM
|-
| CLICK_CUST || Click and Collect Customer || SYSTEM
|-
| CLIENT_CODE_CHECK || Client code assessment for Location import || SYSTEM
|-
| CMD_MERGE_DOCUMENTS || The command to merge documents can be stored with any paths that need to be unset to allow the process to be performed. || SYSTEM
|-
| CMR_NOTE || Name of the CMR note report || COST_CENTRE
|-
| CMR_NOTE1 || Name of the CMR note report || COST_CENTRE
|-
| CNT_SERVICE_LEVEL_OFFSETS || Enable collection and delivery offsets for service levels (Y/N) || SYSTEM
|-
| CNT_SUMMER || Date Summer starts this current year || SYSTEM
|-
| CNT_WINTER || Date WINTER starts this current year || SYSTEM
|-
| CO2_EMMISIONS_LTR || Defines Amount of CO2 emissions per litre of fuel. || COST_CENTRE
|-
| COMBINED_DOCUMENTS_REPORT || Name of the Combined Documents report. || COST_CENTRE
|-
| CONSOLIDATE_TRIPS || Remove Duplicate lines when trip is ACCEPTED || SYSTEM
|-
| CONSOL_BY_SHIPMENT || Consolidation at Shipment level || COST_CENTRE
|-
| CONSOL_RUNNING || Indicates whether the order consolidation process is currently running. || SYSTEM
|-
| CONTINGENCY_IMPORT || Contingency Import setting || COST_CENTRE
|-
| CON_MAX_RPE || Max RPE per shipment || COST_CENTRE
|-
| COST_CENTRE_LOGO || Customer logo filename || COST_CENTRE
|-
| COST_CENTRE_POST_MATRIX || Does this cost centre use Post Matrix type charging? || COST_CENTRE
|-
| COST_CENTRE_SEGREGATION || Segregate data by cost centre || SYSTEM
|-
| CREATE_ORD_MANF || Controls if an order manifest record is created || COST_CENTRE
|-
| CSB_EXPORT_PATH || Directory where carrier self billing exports are stored. || SYSTEM
|-
| CSB_REPORT_PATH || Directory where carrier self billing reports are stored. || SYSTEM
|-
| CS_CLOSE_BY || Display trips in cust serv that are within x miles of order || SYSTEM
|-
| CS_DEFAULT_BOOKING_STATUS_OLD || Customer Services Default Booking Status || SYSTEM
|-
| CS_DEFAULT_ORDER_STATUS_OLD || Customer Services Default Order Status || SYSTEM
|-
| CTMS_CITD_FTP_DESTINATION_DIRECTORY || CITD Destination Directory || SYSTEM
|-
| CTMS_CITD_FTP_DESTINATION_IP_ADDRESS || CITD Destination IP Address || SYSTEM
|-
| CTMS_CITD_FTP_DESTINATION_PASSWORD || CITD Destination Directory Password || SYSTEM
|-
| CTMS_CITD_FTP_DESTINATION_PORT || CITD Destination Directory Port || SYSTEM
|-
| CTMS_CITD_FTP_DESTINATION_USERNAME || CITD Destination Directory username || SYSTEM
|-
| CTMS_ESI_FTP_DESTINATION_DIRECTORY || Directory for FTP of Outbound Trips Files. || SYSTEM
|-
| CTMS_ESI_FTP_DESTINATION_IP_ADDRESS || IP Address for FTP of Outbound Trips Files. || SYSTEM
|-
| CTMS_ESI_FTP_DESTINATION_PASSWORD || Password for FTP of Outbound Trips Files. || SYSTEM
|-
| CTMS_ESI_FTP_DESTINATION_PORT || Port for FTP of Outbound Trips Files. || SYSTEM
|-
| CTMS_ESI_FTP_DESTINATION_USERNAME || Username for FTP of Outbound Trips Files. || SYSTEM
|-
| CTMS_MANF_FTP_DESTINATION_DIRECTORY || Manifest Destination Directory || SYSTEM
|-
| CTMS_MANF_FTP_DESTINATION_IP_ADDRESS || Manifest Destination IP Address || SYSTEM
|-
| CTMS_MANF_FTP_DESTINATION_PASSWORD || Manifest Destination Directory Password || SYSTEM
|-
| CTMS_MANF_FTP_DESTINATION_PORT || Manifest Destination Directory Port || SYSTEM
|-
| CTMS_MANF_FTP_DESTINATION_USERNAME || Manifest Destination Directory username || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_ARCH || File path for Outbound Trips. || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_ARCH_TEST || File path for Outbound Trips archive. || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_FILENAME || Filename for Outbound Trips. || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_FLAG || Flag to permit the creation of Outbound Trips (Y/N). || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_MSG_TYPE || The Message Type of the Outbound Trips (Y/N). || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_OWNING_DEPOT || The owning depot of the Outbound Trips (Y/N). || SYSTEM
|-
| CTMS_OUTBOUND_TRIP_PATH || File path for Outbound Trips. || SYSTEM
|-
| CTM_ACCEPT_TRIP_UPDATE_DATA || Should Trip data be entered when user Accepts a trip - Y or N || CARR_GROUP
|-
| CTM_ACCEPT_TRIP_UPDATE_DATA || Should Trip data be entered when user Accepts a trip - Y or N || CARRIER
|-
| CTM_DISP_SCHEDTRIP_OR_BOL || Display Sched/Trip or BOL in Carrier Trip Management - SCHEDTRIP or BOL || CARRIER
|-
| CTM_MSG_CHASE_AFTER || Time(mins) after which a message should be sent to a carrier after failure to respond || CARRIER
|-
| CTM_MSG_CHASE_AFTER || Time(mins) after which a message should be sent to a carrier after failure to respond || CARR_GROUP
|-
| CTM_REFRESH_TIMER_INTERVAL || Automatic Timer Refresh Interval for Carrier Trip Management - Enter value in mins || CARRIER
|-
| CTM_SHOW_TRIP_TIMES || Show trip times in Carrier Trip Management form - Value is Y or N || CARRIER
|-
| CUSTOMER_CONTROLLED_ORDER_REVENUE_ACTUALS || Y/N- greater of planned and actual quantity || SYSTEM
|-
| CUSTOMER_LOGO || Customer logo filename || CUSTOMER
|-
| CUSTOMER_SERVICE_LEVEL || Enable Customer Specific Service Levels || SYSTEM
|-
| CUST_DU_CONS_SCHED || Consolidate DU By Schedule || CUSTOMER
|-
| CUST_UPDATE_ORDER_LINES || Update Orders || CUSTOMER
|-
| DEBRIEF_DRIVERS_HOURS || Enter Drivers hours worked at debrief || COST_CENTRE
|-
| DEBUG || Debug enabled ? - Y or N || SYSTEM
|-
| DEFAULT_DEL_TYPE || Default Delivery Type || COST_CENTRE
|-
| DEFAULT_DU_TYPE || Default Du Type for NHS || SYSTEM
|-
| DEFAULT_ORACLE_DIRECTORY || Stores System directory for TMP_DIR in EXPORT production || SYSTEM
|-
| DEFAULT_PART_NO || Default part Number || CUSTOMER
|-
| DEFAULT_PAR_DEL_TYPE || Default Del type for paragon || COST_CENTRE
|-
| DEFAULT_PROD_TYPE || Default Product Type || COST_CENTRE
|-
| DEFAULT_REBOOK_DEL_TYPE || Default Del type for Rebook || COST_CENTRE
|-
| DEFAULT_SLOT_DELETION_DAYS || Number of days after which an inactive slot is deleted || SYSTEM
|-
| DEFAULT_TRAILER_TYPE || Default Trailer Type || COST_CENTRE
|-
| DEFAULT_UNSCHEDULED_CARRIER || Indicates a default carrier may be used to print labels for unscheduled orders during packing. || SYSTEM
|-
| DEF_AQ_SCHEMA || Schema for use when starting advanced queues || SYSTEM
|-
| DEF_CALLOUT_DEL_TYPE || Default Callout Delivery Type || SYSTEM
|-
| DEF_COST || Default Cost Centre for NHSBT || SYSTEM
|-
| DEF_INSPECT_DEL_TYPE || Default Inspection Delivery Type || SYSTEM
|-
| DEF_INSPECT_SERVICE || Default Inspection Service Level || SYSTEM
|-
| DEF_SERVICE_LEVEL || Default service level for orders when null || COST_CENTRE
|-
| DELCONF_FTP_DESTINATION_DIRECTORY || Directory for FTP of Microlise Files || SYSTEM
|-
| DELCONF_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Microlise Files || SYSTEM
|-
| DELCONF_FTP_DESTINATION_PASSWORD || Password for FTP of Microlise Files || SYSTEM
|-
| DELCONF_FTP_DESTINATION_PORT || Port for FTP of Microlise Files || SYSTEM
|-
| DELCONF_FTP_DESTINATION_USERNAME || Username for FTP of Microlise Files || SYSTEM
|-
| DELETE_ALL_PMTS_AT_PLANNED || Delete All payments for a trip at Planned Status || COST_CENTRE
|-
| DELIVERY_CUTOFF || Cost Centre Delivery Cut Off || COST_CENTRE
|-
| DELIVERY_NOTE || Name of the delivery note report || COST_CENTRE
|-
| DEL_LEVEL_PARAM || Level of data reported in the Delivery docs || COST_CENTRE
|-
| DEL_TIME_OFFSET || The earliest delivery time ahead of the requested delivery date and time sent from PULSE || COST_CENTRE
|-
| DESPATCH_EMAIL || Create Despatch email control record || SYSTEM
|-
| DESPATCH_REPORT || Name of the despatch note report printed from the trip tree || COST_CENTRE
|-
| DHL_INV_EMAIL || List of emails (sep with ;) for monthly DHL Invoicing data || SYSTEM
|-
| DIM_CHARGE_WEIGHT || Kg Value for dimensional weight calculation || CUSTOMER
|-
| DIRECT_CARRIER || Stores the carrier ID that will go direct and not via a location - the via routing code will not be displayed. || SYSTEM
|-
| DISABLE_ITEM_ID || Disable the item identifier in order entry || COST_CENTRE
|-
| DISPLAY_DESPATCHED_RPE || Display the Actual Despatched RPE Quantity in the Order Detail and Trip Debrief screens? || COST_CENTRE
|-
| DISPLAY_PARAGON_LOC_ID || Display Paragon ID and EXT Ref in Locations Screen || SYSTEM
|-
| DISPLAY_PO_REF_REPORT || PO Ref to be displayed in delivery note || CUSTOMER
|-
| DISPLAY_WIC_CODE || Determines if the delivery type of the order for the customer contains a WIC Code and whether the title will be displayed in the Order Details screen || CUSTOMER
|-
| DISTRIBUTION_OFF || Is revenue distributed as part of trip charges? || SYSTEM
|-
| DOM_DIMS || Domestic version of dimensions functionality || COST_CENTRE
|-
| DONT_SEND_PLANNED_TO_WEBFLEET || When the parameter is set control record is not sent for PLANNED status || COST_CENTRE
|-
| DSG_ALLOW_BKG_IN_PAST || Allow Bookings in the past from the Dixons Bookings interface - Y or N. || SYSTEM
|-
| DSG_DEF_DU_TYPE || Default DU Type for Orders created via the Dixons Bookings interface. || SYSTEM
|-
| DSG_DEF_PRD_TYPE || Default Product Type for Orders created via the Dixons Bookings interface. || SYSTEM
|-
| DSG_TRIP_DTL_PATH || File path for DSG Trip detail messages. || SYSTEM
|-
| DU_PARAMS || DUs may be used as charge parameters || SYSTEM
|-
| EARLY_ARR_REASON_CODE || Early reason code for trip deliveries || SYSTEM
|-
| EDI1214_DELIMITER || File delimiter in EDI1214 file || SYSTEM
|-
| EDI1214_ENDOFLINE || File end of line delimiter in EDI1214 file || SYSTEM
|-
| EDI1214_SYSTEM || T for test P for Prod || SYSTEM
|-
| EDI_CN_ENTITY_CODE || Consignment Entity code for Invoice XML || SYSTEM
|-
| EDI_INVOICE_MSG_TYPE || Invoice Message type for Invoice XML || SYSTEM
|-
| EDI_MESSAGE_VERSION || Message Version for Invoice XML || SYSTEM
|-
| EDI_SH_ENTITY_CODE || Shipment Entity code for Invoice XML || SYSTEM
|-
| EDI_STRUCTURE_VERSION || Structure version for Invoice XML || SYSTEM
|-
| EFX_CANC_ARCH || Archive folder for EFX cancellation requests || SYSTEM
|-
| EFX_CANC_FTP_DESTINATION_DIRECTORY || Directory for FTP of Microlise Files || SYSTEM
|-
| EFX_CANC_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Microlise Files || SYSTEM
|-
| EFX_CANC_FTP_DESTINATION_PASSWORD || Password for FTP of Microlise Files || SYSTEM
|-
| EFX_CANC_FTP_DESTINATION_PORT || Port for FTP of Microlise Files || SYSTEM
|-
| EFX_CANC_FTP_DESTINATION_USERNAME || Username for FTP of Microlise Files || SYSTEM
|-
| EFX_DEADLINE_HOURS || EFX Default Deadline Hours || SYSTEM
|-
| EFX_DEFAULT_CARRIER || EFX Default Carrier || SYSTEM
|-
| EFX_DEF_WEIGHT || Default EFX weight per RPE, used in calculation of trip weight for EFX export || SYSTEM
|-
| EFX_EXCLUDE_CARR_TYPE_DEB || EFX Exclude Carrier Type from Debrief Messages || COST_CENTRE
|-
| EFX_EXT_LOCATION_NAME || Include the extra location name in the EFX messages (Y/N) || SYSTEM
|-
| EFX_FAILURE_PATH || File path for failed EFX filed || SYSTEM
|-
| EFX_FORMAT || EFX Format || SYSTEM
|-
| EFX_FTP_DESTINATION_DIRECTORY || Directory for FTP of Microlise Files || SYSTEM
|-
| EFX_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Microlise Files || SYSTEM
|-
| EFX_FTP_DESTINATION_PASSWORD || Password for FTP of Microlise Files || SYSTEM
|-
| EFX_FTP_DESTINATION_PORT || Port for FTP of Microlise Files || SYSTEM
|-
| EFX_FTP_DESTINATION_USERNAME || Username for FTP of Microlise Files || SYSTEM
|-
| EFX_IDENTIFIER || EFX file identifier || SYSTEM
|-
| EFX_INBOUND_LISTING_NAME || Filename for list of files in directory for EFX XML Trip Inbound || SYSTEM
|-
| EFX_INC_TRIP_VEH_TYPE || Include the vehicle type for the trip stop from EFX (Y/N) || COST_CENTRE
|-
| EFX_LISTING_SCRIPT_NAME || Script name foe EFX XML Inbound || SYSTEM
|-
| EFX_PATH || File path for EFX Inbound messages || SYSTEM
|-
| EFX_PROCESSED_PATH || File path for processed EFX files || SYSTEM
|-
| EFX_SEND_SUB || Send Sub-Contracted Trips to EFX when they go to ACCEPTED status || SYSTEM
|-
| EFX_TRIP_ARCH || Archive folder for EFX requests || SYSTEM
|-
| EFX_TRIP_DTL_PATH || File path for EFX Trip detail messages. || SYSTEM
|-
| EFX_XML_DEB_DELAY || EFX XML Outbound second debrief message delay in minutes || SYSTEM
|-
| EFX_XML_DEB_TRIP_STATUS || Determine which trip status generates debrief messages to EFX || COST_CENTRE
|-
| EFX_XML_INC_COUNTRYCODE || Will XML messages for EFX include COUNTRYCODE for load and drop locations (Y/N). || COST_CENTRE
|-
| EFX_XML_SYSTEM || EFX XML Outbound System Name || COST_CENTRE
|-
| EFX_XML_TYPE || EFX Type || COST_CENTRE
|-
| EFX_XML_UOM || EFX XML Outbound UOM || COST_CENTRE
|-
| ELUCID_API_PROXY || Proxy Sever Elucid || SYSTEM
|-
| ELUCID_WS_ADDRESS || Elucid WS Address || SYSTEM
|-
| ELUCID_WS_PWD || Elucid WS User || SYSTEM
|-
| ELUCID_WS_USER || Elucid WS User || SYSTEM
|-
| EMAIL_ACTUALS_FAILURE || Email address for Actuals Failure Email || CUSTOMER
|-
| EMAIL_CUSTOMER_CARE || Customer Care email address || SYSTEM
|-
| EMAIL_CUST_SERVICES_RECIPIENT || The address for the recipient of the emails. || COST_CENTRE
|-
| EMAIL_OWN_PACKAGE || Is an e-mail required for an order that contains own packaging (Y/N)? || COST_CENTRE
|-
| ENABLE_SEND_BORDERO || Send Bordero Messages || CUSTOMER
|-
| ENGINE_RUNNING || Indicates whether the Scheduling Engine is running || SYSTEM
|-
| EPL_CUST_REF || VPF Test param for 317770 || SYSTEM
|-
| EPOD_COLLECT_STOCK || To exclude sending a loading stop to EPOD which does not have an order for van stock or to fit new tyres(Y/N) || SYSTEM
|-
| EPOD_COMPLETED_UPDATE || Are epod updates sent for COMPLETED trips? || SYSTEM
|-
| EPOD_COMPLETE_ON_LOAD_UPDATE || Complete Trip when RTD job sent back from C-ePOD for load updates || COST_CENTRE
|-
| EPOD_COMPLETE_ON_RTD || Complete Trip when RTD job sent back from C-ePOD || COST_CENTRE
|-
| EPOD_CONCATENATE_JOB_INSTR || Concatenate the special instructions and the order comments for the collection/delivery location as the job instructions (Y/N). || COST_CENTRE
|-
| EPOD_CONSOLIDATION_LEVEL || Level of job consolidation for C-ePOD || COST_CENTRE
|-
| EPOD_CONTACT_DELIMITER || EPOD contact delimiter || COST_CENTRE
|-
| EPOD_CONTAINER_CODE1 || What populates this field in EPOD DIMS for dimensions(default) or PARTS for the part numbers if present || COST_CENTRE
|-
| EPOD_CONTAINER_CODE2 || What populates this field in EPOD DIMS for dimensions or PARTS for the part numbers if present (default) || COST_CENTRE
|-
| EPOD_CONTAINER_CODE3 || What populates this field in EPOD DIMS for dimensions or PARTS (for the part numbers if present) default NULL || COST_CENTRE
|-
| EPOD_CONTAINER_DESCRIPTION || What populates this field in EPOD COMMODITY for the item commodity(default) DESCRIPTION for item desc or PROD_DESC for the prod AKA code and item desc || COST_CENTRE
|-
| EPOD_CUSTOMER_INVOICE || Include an EPOD_CUSTOMER_INVOICE section within the EPOD_CUSTOMERS section for the service jobs (Y/N) || SYSTEM
|-
| EPOD_CUSTOMER_INVOICE_SXU || To include the EPOD_CUSTOMER section || SYSTEM
|-
| EPOD_IGNORE_COL_SIG_DEPOT || Controls is signatures are ignored for cols at depots || COST_CENTRE
|-
| EPOD_IGNORE_COL_SIG_DEPOT || Controls is signatures are ignored for cols at depots || SYSTEM
|-
| EPOD_ITEM_LEVEL || Send Containers (IC for items or LC for lines) or Products (IP for item or LP for lines) to EPOD || SYSTEM
|-
| EPOD_JOB_GROUP_FORMAT || Indicates whether the value passed in the EPL Job Group to EPOD is the Cost Centre (CC), Carried ID (CI), Customer Group (CG) or Customer (CU). || SYSTEM
|-
| EPOD_JOB_RETAIN_TIMES || Retain the actual times for the trip stop for the job (Y/N). || COST_CENTRE
|-
| EPOD_OWNER_CONFIG || C-ePOD Owner Configuration || COST_CENTRE
|-
| EPOD_PREVENT_ASSET_TRACK || Prevents asset tracking through EPOD || COST_CENTRE
|-
| EPOD_SEND_CLOSING_TIME || Send Location closing time to C-ePOD || SYSTEM
|-
| EPOD_SEND_COD_NAME || Send COD Name to C-ePOD values will be (Y/N) || COST_CENTRE
|-
| EPOD_SEND_CONTACT_INFO || Send Contact information to C-ePOD || COST_CENTRE
|-
| EPOD_SEND_DRIVER || Is the driver username included? (Y/N) || SYSTEM
|-
| EPOD_SEND_EPL_LAT_LONG || Send EPL_LAT and EPL_LONG for job addresses (Y/N) || COST_CENTRE
|-
| EPOD_SEND_EQUIPMENT || Controls if equipment requirements are sent to EPOD || SYSTEM
|-
| EPOD_SEND_ITEM_AKA_CODE || Send EPL_PRODUCT_CODE with the item AKA code (Y/N) || COST_CENTRE
|-
| EPOD_SEND_LOADING_TYPE || Send Loading Type to C-ePOD || COST_CENTRE
|-
| EPOD_SEND_RVA_UNIT_TYPE || Send EPL_UNIT_TYPE as the vehicle configuration ID for the services (Y/N) || COST_CENTRE
|-
| EPOD_SET_ACTUAL_SIGNATORY_BLANK || Set C-ePOD actual signatory to blank (Y/N)? || SYSTEM
|-
| EPOD_SIGNATORY || Controls if signatory is stored from C-ePOD || COST_CENTRE
|-
| EPOD_SIGNATURE_STORAGE || Store signature received from C-ePOD || COST_CENTRE
|-
| EPOD_SITE_ID_FORMAT || Indicates whether the value passed in the EPL Site ID to C-ePOD is the Database Name(DB), Cost Centre (CC) or Carrier ID (CI). || SYSTEM
|-
| EPOD_TNC_STORAGE || Store TNC declaration from C-ePOD || COST_CENTRE
|-
| EPOD_UPDATE_ETA || Update Later stops ETA on receipt from C-ePOD || COST_CENTRE
|-
| EPOD_VIEW_POD_URL || URL for C-ePOD Documents || SYSTEM
|-
| EPOD_WS_ADDRESS || C-ePOD Web Service End Point || SYSTEM
|-
| EPOD_WS_ADDRESS_NHSPRD || C-ePOD Web Service End Point || SYSTEM
|-
| EPOD_WS_MESSAGE_FORMAT || C-ePOD message format - can either be PARCEL, BULK, RETAIL, MODE1, MODE2 or DELTYPE to define where fields are sent in the web service message || SYSTEM
|-
| EPOD_WS_PASSWORD || C-ePOD Web Service Login Password || SYSTEM
|-
| EPOD_WS_TIMEOUT || Number of minutes before a WS message will be set to Held || SYSTEM
|-
| EPOD_WS_USERNAME || C-ePOD Web Service Login Username || SYSTEM
|-
| ETA_LOAD_TIME || Load time in minutes to be used in ETA calculation || SYSTEM
|-
| EXE_ARCH_DIRECTORY || Destination directory EXE rcp || SYSTEM
|-
| EXE_DESTINATION_DIRECTORY || Destination directory EXE rcp || SYSTEM
|-
| EXE_DESTINATION_IP_ADDRESS || Destination for EXE rcp || SYSTEM
|-
| EXE_DESTINATION_PASSWORD || Password for EXE rcp || SYSTEM
|-
| EXE_DESTINATION_USERNAME || Username for EXE rcp || SYSTEM
|-
| EXE_SOURCE_DIRECTORY || Source directory for EXE rcp || SYSTEM
|-
| EXTERNAL_CALL_LOGGING || Call Logging External User || SYSTEM
|-
| FASTER_SCANNING || Controls if the Planner splits order for planning || SYSTEM
|-
| FC_ACCESS_TOKEN || The FleetCheck Access Token, provided by FleetCheck. || SYSTEM
|-
| FC_FLEET_KEY || The FleetCheck fleet being updated by C-TMS. || SYSTEM
|-
| FC_TIMEOUT || The amount of time to wait when trying to update FleetCheck. || SYSTEM
|-
| FC_URL || The base URL for the FleetCheck system. || SYSTEM
|-
| FILE_INTERFACE_DIR || File Interface Directory || SYSTEM
|-
| FINDTRIP_URL || Find trip webservice URL || SYSTEM
|-
| FIT_PRESSURE_HIGH || FIT Report: Pressure Analysis High || SYSTEM
|-
| FIT_PRESSURE_LOW || FIT Report: Pressure Analysis Low || SYSTEM
|-
| FIT_PRESSURE_VHIGH || FIT Report: Pressure Analysis Very High || SYSTEM
|-
| FIT_PRESSURE_VLOW || FIT Report: Pressure Analysis Very Low || SYSTEM
|-
| FIT_TREAD_REPLACE_NEXT || FIT Report: RTD in Next Month || SYSTEM
|-
| FIT_TREAD_REPLACE_NEXT2 || FIT Report: RTD in Next 2 Months || SYSTEM
|-
| FIT_TREAD_REPLACE_NOW || FIT Report: RTD in Current Month || SYSTEM
|-
| FIXED_IMPORT || Customer is using fixed order import || CUSTOMER
|-
| FIX_NULL_BOOKING_REF || Set booking Ref to Null for fixed schedules || COST_CENTRE
|-
| FLEXIPOD || Set to Y to indicate the FleXipod interface is active || SYSTEM
|-
| FLEXIPOD_CARRIERS || Set to Y indicates the Carrier can control if a trip is sent to FleXipod || SYSTEM
|-
| FLEXIPOD_CLIENTNUM || FleXipod ClientNum sent in interface || SYSTEM
|-
| FLEXIPOD_DEPOTS || Set to Y indicates the Depot can control if a trip is sent to FleXipod || SYSTEM
|-
| FLEXIPOD_DROP || Determines the Drop level STOP-OMS or ITEM || SYSTEM
|-
| FLEXIPOD_PASSWORD || FleXipod Webservice password || SYSTEM
|-
| FLEXIPOD_SCAN_LEVEL || 1,2 or 3 to indicate line or item level scanning || SYSTEM
|-
| FLEXIPOD_SCAN_TYPE || Contents and items || SYSTEM
|-
| FLEXIPOD_SPLIT || Are orders to be split? || SYSTEM
|-
| FLEXIPOD_SYSTEM || FleXipod SYSTEM ID sent in interface || SYSTEM
|-
| FLEXIPOD_USERCODE || FleXipod Webservice usercode || SYSTEM
|-
| FLEXIPOD_USERNAME || FleXipod Webservice username || SYSTEM
|-
| FLEXIPOD_WEBSERVICE || FleXipod webservice endpoint URL || SYSTEM
|-
| FLEXIPOD_WEBSERVICE_TASK || FleXipod webservice endpoint URL for Tasks || SYSTEM
|-
| FLEXIPOD_WEBSERVICE_UI || FleXipod webservice endpoint URL || SYSTEM
|-
| FORCE_ITEM_SCAN || Is driver required to scan at debrief? || SYSTEM
|-
| FORMS_ALERT_MESSAGE_MODULE || Alert Messages Form || SYSTEM
|-
| FORMS_CS_PATH || Forms Client Server Path || SYSTEM
|-
| FORMS_DEFAULT_MODULE || Default Module accessed when C-TMS is started - ORI_STATS, ORI_STATS_JRL or ORI_STATS_WATERFALL || SYSTEM
|-
| FORMS_DEFAULT_ORDERS_MODULE || Default Orders Form - ORDERS_WIDE, ORDERS or ORD_ENTRY_TARGET || SYSTEM
|-
| FORMS_DEFAULT_TRIP_MODULE || Default Trip Form - TRIPSUM or TRIPSUM_JRL || SYSTEM
|-
| FORMS_PASSWORD_MODULE || Password Change form. || SYSTEM
|-
| FORMS_PATH || Forms Path || SYSTEM
|-
| FORMS_WEB_PATH || Determines where on the server forms are being obtained from for this database || SYSTEM
|-
| FORMS_WEB_PATH_BLUE || Blue forms || SYSTEM
|-
| FTP_SERVER_LOG || Create server logs for FTP send to prove delivery || SYSTEM
|-
| FTP_TRANSMIT_TIME_LIMIT || Determines the time limit (in minutes) above which a file being transferred is considered to be failed instead of pending. || SYSTEM
|-
| FTP_WRITE_LOC || FTP Write location || SYSTEM
|-
| FULL_LOAD_GROUPAGE_FLAG || Controls whether Full load \ Groupage flag is checked when changing Trip status || SYSTEM
|-
| FULL_LOAD_THRESHOLD || Maximum weight threshold for any FTL || SYSTEM
|-
| GEL_DU || Identifies which du types include GEL || COST_CENTRE
|-
| GEO_ASKGEO_PROXY || Proxy server setting for AskGEO web server || SYSTEM
|-
| GEO_ASKGEO_TIMEOUT || AskGEO web server time out || SYSTEM
|-
| GEO_ASKGEO_URL || AskGEO web server URL || SYSTEM
|-
| GEO_DEFAULT_COUNTRY || Default country for new locations || SYSTEM
|-
| GEO_DEFAULT_DEPOT || Default depot for new locations || SYSTEM
|-
| GEO_DEFAULT_LOAD_RATE || Default Loading Rate for locations. || SYSTEM
|-
| GEO_DEFAULT_SESSION_COUNTRY || Default Country Code for locations created from sessions || SYSTEM
|-
| GEO_DEFAULT_UNLOAD_RATE || Default Unloading Rate for locations. || SYSTEM
|-
| GEO_DRIVE_TIME_DTL_ONLY || Allows TRANSIT DAYS to be be overridden by Drive Time in GEO_NET, YES or NO. || SYSTEM
|-
| GEO_DT_ADDR_FMT || Determines the format of the Address string passed to external Map application, e.g. MapPoint, for Address Location Matching || SYSTEM
|-
| GEO_DT_CALC || Determines the distance and time calculation methods - NET, NETR, LINE, PCMS || SYSTEM
|-
| GEO_DT_CALC_ORD || Determines distance calculation method for orders || COST_CENTRE
|-
| GEO_DT_CALC_PAR_INT || Override for dist/time method for Paragon Interface || SYSTEM
|-
| GEO_DT_DFLT_SPEED || Default truck speed assumed in approximation of driving time. || SYSTEM
|-
| GEO_DT_DISTANCE_FACTOR || "Wiggle" factor applied to straight-line distance to approximate Road distance. || SYSTEM
|-
| GEO_DT_DISTANCE_UNITS || Current distance unit - miles or kilometres || SYSTEM
|-
| GEO_DT_DISTANCE_UNITS || Current distance unit - miles or kilometres || COST_CENTRE
|-
| GEO_DT_PCMS_TIMEOUT || Number of seconds to wait for PCMS to calculate distance and time. || SYSTEM
|-
| GEO_DT_PCMS_TIMEOUT_ORD || Number of seconds to wait for NAVTEQ for order distance calculation || COST_CENTRE
|-
| GEO_HERE_DISTANCE_TYPE || Set to either miles or leave blank || COST_CENTRE
|-
| GEO_HIDE_SWAP_LOCATIONS || It is to exclude SWAP locations from list of Location_ID in location maintenance screen || SYSTEM
|-
| GEO_KEEP_LATLONG || Keep Lat-Long when entered || SYSTEM
|-
| GEO_LOCATION_STACK || Switch on stack specific location fields || SYSTEM
|-
| GEO_LOC_ADD1_MAND || Address Line 1 must be entered || SYSTEM
|-
| GEO_LOC_CUST_CTRY || Enable a customer to be specified for a location to be maintained for one of multiple countries? (‘Y/N) || SYSTEM
|-
| GEO_LOC_IMP_POST_PLAN || Populate the postal and planning regions using rules in country and static data when doing location import || SYSTEM
|-
| GEO_LOC_PCDE_MAND || Post code must be entered || SYSTEM
|-
| GEO_LOC_RADIAL_ROUTES || Indicates if a radial route will be stored for the location based on the fixed route stop for collection/delivery (Y/N). || SYSTEM
|-
| GEO_LOC_TOWN_MAND || Town must be entered || SYSTEM
|-
| GEO_MAX_INVENTORY || Maximum inventory threshold for warning || SYSTEM
|-
| GEO_MIN_INVENTORY || Minimum inventory threshold for warning || SYSTEM
|-
| GEO_NAVTEQ_AJAX_LOGIN || NAVTEQ Ajax Login || SYSTEM
|-
| GEO_NAVTEQ_CITY_SPEED || City Road Speed for NAVTEQ || SYSTEM
|-
| GEO_NAVTEQ_COUNTRY_SPEED || Country Road Speed for NAVTEQ || SYSTEM
|-
| GEO_NAVTEQ_FAST_SHORT || Fastest or Shortest Method for NAVTEQ Route calculation || SYSTEM
|-
| GEO_NAVTEQ_JAVA || NAVTEQ Java || SYSTEM
|-
| GEO_NAVTEQ_LOGIN || NAVTEQ Login || SYSTEM
|-
| GEO_NAVTEQ_MAP_DIR || NAVTEQ Maps Folder || SYSTEM
|-
| GEO_NAVTEQ_MAP_SHOW || NAVTEQ Maps Folder for WEBSHOW || SYSTEM
|-
| GEO_NAVTEQ_MOTOR_SPEED || Motorway Speed for NAVTEQ || SYSTEM
|-
| GEO_NAVTEQ_PROXY || Proxy Sever for NAVTEQ || SYSTEM
|-
| GEO_NAVTEQ_URL_LOC || NAVTEQ Location URL || SYSTEM
|-
| GEO_NAVTEQ_URL_MAP || NAVTEQ Map URL || SYSTEM
|-
| GEO_NAVTEQ_URL_MAP_ALL || NAVTEQ Map URL || SYSTEM
|-
| GEO_NAVTEQ_URL_ROUTE || NAVTEQ Route URL || SYSTEM
|-
| GEO_NET_TABLE || Network Table || SYSTEM
|-
| GEO_NLP_ALT_PROXY || Proxy Sever for NLP 11g || SYSTEM
|-
| GEO_NLP_ALT_URL_LOC || Alternative URL for Geocode service on NLP system || SYSTEM
|-
| GEO_NLP_ALT_URL_ROUTE || Alternative URL for Calculate Route service on NLP system || SYSTEM
|-
| GEO_NLP_API_KEY || API Key for NLP || SYSTEM
|-
| GEO_NLP_APP_LOC || App_ID for Geo Code call to NLP system || SYSTEM
|-
| GEO_NLP_APP_MAP || App for Map service on NLP system || SYSTEM
|-
| GEO_NLP_APP_ROUTE || App_ID for Route call to NLP system || SYSTEM
|-
| GEO_NLP_CAR_TRUCK || Nokia travel time calculations to be based on a truck or a car || SYSTEM
|-
| GEO_NLP_DISTRICT_PARAM || Control which field (TOWN/LINE3) is sent as district to Nokia || SYSTEM
|-
| GEO_NLP_FORMAT_FREETEXT || NLP Freetext Format || SYSTEM
|-
| GEO_NLP_FORMAT_QUALIFIED || NLP Qualified Format || SYSTEM
|-
| GEO_NLP_JAVA || Java for NLP to create PDF || SYSTEM
|-
| GEO_NLP_JS_MULTI || Location for the show map multiple map printout in JavaScript || SYSTEM
|-
| GEO_NLP_LATLONG_ACCURACY || NLP Geocode Accuracy || SYSTEM
|-
| GEO_NLP_MAP_DIR || Directory for PDF of maps || SYSTEM
|-
| GEO_NLP_MAP_SHOW || Directory for PDF of maps || SYSTEM
|-
| GEO_NLP_MOTORWAY || Motorway Preference for NLP distance calculations || COST_CENTRE
|-
| GEO_NLP_PROXY || Proxy Sever for NLP || SYSTEM
|-
| GEO_NLP_TOKEN_LOC || NLP Geocode Token || SYSTEM
|-
| GEO_NLP_TOKEN_MAP || Login token for Map service on NLP system || SYSTEM
|-
| GEO_NLP_TOKEN_ROUTE || Login token for Calculate Route service on NLP system || SYSTEM
|-
| GEO_NLP_URL_LOC || Nokia Location Platform Geocode URL || SYSTEM
|-
| GEO_NLP_URL_MAP || URL for Map service on NLP system || SYSTEM
|-
| GEO_NLP_URL_ROUTE || URL for Calculate Route service on NLP system || SYSTEM
|-
| GEO_NLP_USE_ALTERNATE || Use Alternative URLS and Proxy || SYSTEM
|-
| GEO_POP_PLANNING_REGION || Controls whether the Planning Region is populated from the look up table - Y or N. || SYSTEM
|-
| GEO_SLOT_IMPORT_FILE || Name of Slot Import file || SYSTEM
|-
| GEO_SLOT_IMPORT_PATH || Slot Import path || SYSTEM
|-
| GEO_SUBURB || Town must match a Zone || SYSTEM
|-
| GEO_TOMTOM_ACCOUNT || TomTom account || SYSTEM
|-
| GEO_TOMTOM_ARCH_DAYS || Number of days to keep the TomTom data before archiving || SYSTEM
|-
| GEO_TOMTOM_AUTO_AREA_RADIUS || Radius (m) of temporary TomTom areas || SYSTEM
|-
| GEO_TOMTOM_FENCE_CARR || List of carriers to test TomTom Geo-fence breaks || SYSTEM
|-
| GEO_TOMTOM_FENCE_VAR || Variation of time in hours from planned for TomTom Geo-fence breaks to update stop || SYSTEM
|-
| GEO_TOMTOM_FENCE_VEH || List of vehicles to test TomTom Geo-fence breaks || SYSTEM
|-
| GEO_TOMTOM_GETMSGS_URL || TomTom web service || SYSTEM
|-
| GEO_TOMTOM_LATE_MINS || TomTom Late Reason Variance Minutes || SYSTEM
|-
| GEO_TOMTOM_LATE_REASON || TomTom Late Reason Code || SYSTEM
|-
| GEO_TOMTOM_ORDER_DEBRIEF || List of Delivery types allowing change || CARRIER
|-
| GEO_TOMTOM_PASSWORD || TomTom password || SYSTEM
|-
| GEO_TOMTOM_PROXY || Proxy server setting for TomTom web server || SYSTEM
|-
| GEO_TOMTOM_SENDORD_URL || TomTom web service to send orders || SYSTEM
|-
| GEO_TOMTOM_SEND_CUST_REF || Send order customer ref to TomTom || SYSTEM
|-
| GEO_TOMTOM_TIMEOUT || TomTom web server time out || SYSTEM
|-
| GEO_TOMTOM_TRIP_COMPLETE || TomTom to automatically complete trips || SYSTEM
|-
| GEO_TOMTOM_TRIP_EN-ROUTE || Set trip status to EN-ROUTE from TomTom || SYSTEM
|-
| GEO_TOMTOM_USERNAME || TomTom username || SYSTEM
|-
| GEO_VALIDATE_LOCATION_NAME || Indicates whether the system should check for duplicate location names (as well as IDs) when creating/updating locations || SYSTEM
|-
| GLO_CUSTOMER || Customer for Unilever Gloucester || SYSTEM
|-
| GLO_FTP_DESTINATION_DIRECTORY || Directory for FTP of Unilever Files || SYSTEM
|-
| GLO_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Unilever Files || SYSTEM
|-
| GLO_FTP_DESTINATION_PASSWORD || Password for FTP of Unilever Files || SYSTEM
|-
| GLO_FTP_DESTINATION_PORT || Port for FTP of Unilever Files || SYSTEM
|-
| GLO_FTP_DESTINATION_USERNAME || Username for FTP of Unilever Files || SYSTEM
|-
| GLO_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header (Unilever) || SYSTEM
|-
| GLO_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header (Unilever) || SYSTEM
|-
| GLO_INBOUND_PATH || Path for yet to be processed XML files (Unilever) || SYSTEM
|-
| GLO_LOCATION || Location for Unilever Gloucester || SYSTEM
|-
| GLO_OUTBOUND_ARCH || Path for processed XML files for Unilever || SYSTEM
|-
| GLO_OUTBOUND_FAIL || Path for processed XML files for Unilever that have failed processing || SYSTEM
|-
| GLO_OUTBOUND_PATH || Path for yet to be processed XML files for Unilever || SYSTEM
|-
| HIGHLIGHT_SMS_EMAIL || Highlight order Green if SMS or email notification required || COST_CENTRE
|-
| HKP_Clear_Archive_Messages || Age of ARCHIVED messaging records that are to be cleared. || SYSTEM
|-
| HKP_Clear_Messages || Age of messaging records that are to be cleared. || SYSTEM
|-
| HTTPS_CALL || It is related to switching from HTTP to HTTPS || SYSTEM
|-
| HTTPS_PASSWORD || The password for URL commands in the database. || SYSTEM
|-
| HTTPS_WALLET_FILE || The wallet file for URL commands in the database. || SYSTEM
|-
| HTTP_WALLET_TOMTOM || Location of wallets for TOMTOM https || SYSTEM
|-
| ICE_DU || Identifies which du types include ICE || COST_CENTRE
|-
| IGGESUND_IDENTIFIER || Identifier for IGGESUND inbound order files || SYSTEM
|-
| IGGESUND_LISTING_NAME || List for IGGESUND files || SYSTEM
|-
| IGGESUND_LISTING_SCRIPT_NAME || KSH for IGGESUND files || SYSTEM
|-
| IMP_BWSC_DEF_CARRIER || Default Carrier for BWSC import for self delivery suppliers || COST_CENTRE
|-
| IMP_CARRIER_LANE_COUNTRY_CODE || Country code for each cost centre imported on Carrier_Lane - INDUSTRIAL || COST_CENTRE
|-
| IMP_CHANGE_DECIMALS || Correct commas and decimal points for Dimensions || CUSTOMER
|-
| IMP_COL_DATE_REQD || Collection Date must be specified for imports || COST_CENTRE
|-
| IMP_CREATE_ITEM_ID || Controls if Item identifiers are system generated in CSV || CUSTOMER
|-
| IMP_FULL_LOC_ADDR_MATCH || Check the addresses match for the location name, address line 1, postcode, country and type for imported orders before creating a new location (Y/N). || SYSTEM
|-
| IMP_LOC_ID_ONLY || Only validate the location id when importing orders not the address lines || SYSTEM
|-
| IMP_OVERRIDE_SOURCE_REF || Set source system and control additional functionality in ORD_LINE_ITM CSV order import || SYSTEM
|-
| IMP_RESET_ORD_WINDOWS || Reset Order windows during Import || COST_CENTRE
|-
| IMP_RESET_ORD_WINDOWS || Reset Order windows during Import || CUSTOMER
|-
| IMP_TI_ORDER_CALC_WEIGHTS || CSV Import - Calculate weights from dims(Y=X*Y*Z/6000) || COST_CENTRE
|-
| IMP_TI_ORDER_CHECK_SMS || CSV Import - Check contact numbers can be used as SMS numbers || COST_CENTRE
|-
| IMP_TI_ORDER_DEFAULT_DU || CSV Import - Default DU Type Method || COST_CENTRE
|-
| IMP_TI_ORDER_GEN_ITEMS || CSV Import - Generate order items from Qty || COST_CENTRE
|-
| IMP_TI_ORDER_GEN_LOC || CSV Import - Location Name generation by Post Code || COST_CENTRE
|-
| IMP_TI_ORDER_QTY_ADD || CSV Import - Add line qty || COST_CENTRE
|-
| IMP_TI_ORDER_REVENUE_LIMIT || CSV Import -Pre-call above revenue limit (Numeric Limit).0 means no pre-call || COST_CENTRE
|-
| IMP_TI_ORD_GEN_LOC_NAME || Send Supplier Collection Messages || CUSTOMER
|-
| IMP_USE_DEFAULT_DU || Use Default DU Type in import || CUSTOMER
|-
| IMP_USE_DEFAULT_DU || Use Default DU Type in import || CUSTOMER
|-
| IMP_USE_GERMAN_DECODE || Controls if location names are decoded from German || SYSTEM
|-
| INBOUND_ARDO_IDENTIFIER || Identifier for MTS PO Inbound Ardo files || SYSTEM
|-
| INBOUND_ARDO_LISTING_NAME || Listing file for Ardo inbound XML files || SYSTEM
|-
| INBOUND_ARDO_SCRIPT_NAME || Command file for Ardo inbound XML files || SYSTEM
|-
| INBOUND_BEIG2_IDENTIFIER || Identifier for MTS PO Inbound DAI_TMS_BEIG_ORD_YYYYMMDDHHMMSSII.XML || SYSTEM
|-
| INBOUND_BEIG2_LISTING_NAME || Listing file for BEIG inbound XML files || SYSTEM
|-
| INBOUND_BEIG2_SCRIPT_NAME || Command file for BEIG inbound XML files || SYSTEM
|-
| INBOUND_BEIG_IDENTIFIER || Identifier for MTS PO Inbound DAI_TMS_BEIG_ORD_YYYYMMDDHHMMSSII.XML || SYSTEM
|-
| INBOUND_BEIG_LISTING_NAME || Listing file for BEIG inbound XML files || SYSTEM
|-
| INBOUND_BEIG_SCRIPT_NAME || Command file for BEIG inbound XML files || SYSTEM
|-
| INBOUND_FAILURES_PATH || Path for failed inbound files || SYSTEM
|-
| INBOUND_GLO_IDENTIFIER || Identifier for MTS PO Inbound Unilever files || SYSTEM
|-
| INBOUND_GLO_LISTING_NAME || Listing file for GLO inbound XML files || SYSTEM
|-
| INBOUND_GLO_LOA_IDENTIFIER || Identifier for MTS PO Inbound Unilever LOA files || SYSTEM
|-
| INBOUND_GLO_SCRIPT_NAME || Command file for GLO inbound XML files || SYSTEM
|-
| INBOUND_POM_IDENTIFIER || Identifier for MTS PO Inbound MTS_POMI_<YYYYMMDDHH24MISS>_<10 DIGIT SEQ>.XML || SYSTEM
|-
| INBOUND_POM_LISTING_NAME || Listing file for POM inbound XML files || SYSTEM
|-
| INBOUND_POM_SCRIPT_NAME || Command file for POM inbound XML files || SYSTEM
|-
| INBOUND_PROCESSED_PATH || Path for processed inbound files || SYSTEM
|-
| INBOUND_UNI_IDENTIFIER || Identifier for MTS PO Inbound Unilever files || SYSTEM
|-
| INBOUND_UNI_LISTING_NAME || Listing file for UNI inbound XML files || SYSTEM
|-
| INBOUND_UNI_SCRIPT_NAME || Command file for UNI inbound XML files || SYSTEM
|-
| INCLUDE_CDATA_TAG || Use CDATA tag around XML tags values and allowed values will be (Y/N) which will be used to control escaping of special characters like & || SYSTEM
|-
| INCLUDE_FAILED_ORDERS || Include Failed Orders as CANCELLED for API || COST_CENTRE
|-
| INCL_ROUTE_CODE || Include Baxter Route code and delivery method || COST_CENTRE
|-
| INCOMPLETE_ORDERS_WARNING || Display warning message on trip status change if no order items exist || COST_CENTRE
|-
| INHERIT_LAT_LONG || Inherit Lat/Long details from parent address || CUSTOMER
|-
| INNER_OUTER_DU || Inner and outer du types for rating || COST_CENTRE
|-
| INTERFACE_FORMAT || Controls the interface format for inbound orders || SYSTEM
|-
| INTERFACE_INBOUND_PATH || Path for Inbound files || SYSTEM
|-
| INT_ADD_MOD43_CD || Store the Modulo 43 check digit as a suffix for the order item for the barcode label (Y/N). || COST_CENTRE
|-
| INT_ADD_MOD43_CD || Store the Modulo 43 check digit as a suffix for the order item for the barcode label (Y/N). || CUSTOMER
|-
| INT_ALTERNATE_DB || Determines if alternate_db is used as a condition in the INT_MSG code || SYSTEM
|-
| INT_CARRIER_DETS || Used to control which carrier details cursor is fetched in INT_MSG.PROCESS_TRIP_DTL_MSG || SYSTEM
|-
| INT_CHARGES || Determines whether internal charging is based on COST_CENTRE or GROUP_NAME || SYSTEM
|-
| INT_DECODE_UNISON || Used to control which DECODE_VALUE is used in INT_MSG || SYSTEM
|-
| INT_DROP_POSTCODE || Determines how v_string is built within INT_MSG.PROCESS_EFX_TRIP_DTL_MSG part of INT_MSG alignment || SYSTEM
|-
| INT_ERRNUM || Used to establish whether error numbers should be inserted into VALIDATION_ERROR in INT_MSG || SYSTEM
|-
| INT_IGNORE_DESP_QTY || Send despatch messages even when despatch quantity is not set || SYSTEM
|-
| INT_KEEP_FILE || Do not remove files from delivery folder || SYSTEM
|-
| INT_MSG_TYPE || Determines whether a cursor is fetched or a hard coded if IN the INT_MSG.READ_BBOKING_HEADER procedure. Part of Alignment process. || SYSTEM
|-
| INT_ORDER_COMMENT || Indicates if the order_comments in INT_MSG.PROCESS_UNSION_FILE is selected as a substring || SYSTEM
|-
| INT_ORDER_CORRECT || Indicates if interface files are corrected || SYSTEM
|-
| INT_READ_EFX_COMMENTED_OUT || Indicated if code is commented out in EFX procedure of INT_MSG part of alignment || SYSTEM
|-
| INT_READ_EFX_CURSOR || Indicates if C_EFX_TRIPS cursor is based on trip or load part of INT_MSG alignment || SYSTEM
|-
| INT_REVERSE_DECODE || Indicates if INT_MSG.PROCESS_EXE_OUTBOUND_FILE requires a call to IMP_REVERSE_DECODE in the current database || SYSTEM
|-
| INT_TRAILER_TYPE || DECODE or REVERSE to determine how trailer type is extracted in INT_MSG.PROCESS_EFX_TRIP_DTL_MSG || SYSTEM
|-
| INT_TRANSHIP_POS || Used to determine TRANSHIP_IND is in the incoming file for INT_MSG.READ_BOOKING_DETAIL || SYSTEM
|-
| INT_TRIP_STOP_DATE || Determines which date (LATE DEL or DEPART) is passed to the string in INT_MSG || SYSTEM
|-
| INT_UNISON_ERRNUM || Indicates if errnum should be included when inserting data into validation_error field in INT_MSG.PROCESS_UNISON_FILE || SYSTEM
|-
| INT_USE_NEW_DB || Determines which procedures within INT_MSG use the new database name || SYSTEM
|-
| INT_XML_DAYS_PAST || Used to set how many days into the past the dp_pulse package should look for locked records || SYSTEM
|-
| INVOICE_DIR || Directory for storing invoices when printed || SYSTEM
|-
| INV_ACT_PMNTS_DAYS || Process payments for a set number of days prior to the period end date or the current date for the next invoice. || SYSTEM
|-
| INV_SEARCH_FROM_OFFSET || Controls how many days in the past to default the from search in the INVOICES form. || SYSTEM
|-
| INV_SEARCH_TO_OFFSET || Controls how many days in the future to default the from search in the INVOICES form. || SYSTEM
|-
| INV_SET_PERIOD || Set the period for the invoice based on the current date (Y/N) || SYSTEM
|-
| ISOTRAK_BATCH_JOB_SIZE || Number of job records that are processed each minute via the ISOTRAK interface || SYSTEM
|-
| ISO_ENABLED || ISO enabled for this database || SYSTEM
|-
| ISO_FTP_DESTINATION_DIRECTORY || Directory for FTP of ISOTRAK Files || SYSTEM
|-
| ISO_FTP_DESTINATION_IP_ADDRESS || IP for FTP of ISOTRAK Files || SYSTEM
|-
| ISO_FTP_DESTINATION_PASSWORD || Password for FTP of ISOTRAK Files || SYSTEM
|-
| ISO_FTP_DESTINATION_PORT || Port for FTP of ISOTRAK Files || SYSTEM
|-
| ISO_FTP_DESTINATION_USERNAME || Username for FTP of ISOTRAK Files || SYSTEM
|-
| ISO_INBOUND_ARCH || Path for inbound ISO XML archiving || SYSTEM
|-
| ISO_INBOUND_FAIL || Path for ISO XML failures || SYSTEM
|-
| ISO_INBOUND_IDENTIFIER || Pattern for ISO Trip Inbound XML || SYSTEM
|-
| ISO_INBOUND_LISTING_NAME || Filename for list of files in directory for ISO XML Trip Inbound || SYSTEM
|-
| ISO_INBOUND_PATH || Path for yet to be processed XML files from ISO || SYSTEM
|-
| ISO_LISTING_SCRIPT_NAME || Script name for ISO XML Trip Inbound || SYSTEM
|-
| ISO_OUTBOUND_ARCH || Path for archiving outbound ISO XML interfaces || SYSTEM
|-
| ISO_OUTBOUND_FAIL || Path for failing outbound ISO XML interfaces || SYSTEM
|-
| ISO_OUTBOUND_PATH || Path for outbound ISO XML interfaces || SYSTEM
|-
| ISO_Queue_Name || ISOTRAK Queue Name || SYSTEM
|-
| ISO_RECON_MODE || Determine whether messages should be deleted or reconciled, then delete or update as appropriate, ARCHIVE or DELETE || SYSTEM
|-
| ISO_Sched_Prefix || ISOTRAK Schedule Prefix || SYSTEM
|-
| ISO_Signature || ISOTRAK Signature || SYSTEM
|-
| JAVAVM_PROFILE || javavm profile || SYSTEM
|-
| KCC_DEL_INFO_PATH || File path for KCC Delivery Information Export || SYSTEM
|-
| KER_LOADING_FTP_DIRECTORY || Specify the directory for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_FILENAME || Specify the Filename for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_IP_ADDRESS || Specify the IP Address for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_PASSWORD || Specify the Password for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_PATH || Specify the path for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_PORT || Specify the Port for the Kerridge Loading file || COST_CENTRE
|-
| KER_LOADING_FTP_USERNAME || Specify the Username for the Kerridge Loading file || COST_CENTRE
|-
| KER_WEB_PATH || URL for show web Kerridge Files || COST_CENTRE
|-
| LABEL_DIR || Directory for storing the labels when printed || COST_CENTRE
|-
| LABEL_FILE || Directory for storing the labels when printed || COST_CENTRE
|-
| LABEL_FILE_UNSCHEDULED || The label format for when the order is UNSCHEDULED. || COST_CENTRE
|-
| LABEL_FORMAT || Label format for Orders || COST_CENTRE
|-
| LABEL_GROUP || Delivery Type for which labels will be printed || COST_CENTRE
|-
| LABEL_LOGO_FILE || Set label logo file || SYSTEM
|-
| LANE_RATE_CHARGING || lane rates calc || COST_CENTRE
|-
| LAST_RELEASE_DATE || Last release for this database. NB. UPDATED_DATE (updated by trigger) stores the real value (see ORI_STATS). Change VALUE after each release. || SYSTEM
|-
| LBO_CUTOFF_TIME_DEFAULT || Latest time by which a Lane Based Order must be places if Cut-off functionality is switched on || SYSTEM
|-
| LBO_CUTOFF_TIME_ENABLE || LBO Cut-off times enabled - Y or N || SYSTEM
|-
| LBO_FUTURE_ORDER_LIMIT_DAYS || Maximum number of days in future that LB Order can be created || SYSTEM
|-
| LFE_API_AUTHORISATION || Client Ref for authorisation || SYSTEM
|-
| LFE_API_VERSION || 11 for 11g, 12 for 12c || SYSTEM
|-
| LICENCE_MONITOR_LEVEL || Licence monitor alert level || SYSTEM
|-
| LINE_ITEM_TOTALS || Controls if service payments are generated || COST_CENTRE
|-
| LOADING_REPORT || NON Cost centre Loading Report || SYSTEM
|-
| LOAD_LEVEL_PARAM || Level of data reported in the Load List || COST_CENTRE
|-
| LOCATION_DECODE_VALIDATION || Validate Addresses using decode values || COST_CENTRE
|-
| LOGINEXT_API_TOKEN || API Token for Loginext || SYSTEM
|-
| LOGINEXT_ENDPOINT || Endpoint address for Loginext || SYSTEM
|-
| LOGIX_ARCH_DIR || Folder for archive of Logix files || SYSTEM
|-
| LOGIX_CREATE_FILE || Create a file containing CLOB || SYSTEM
|-
| LOGIX_DEL_PRIORITY_DAYS || Number of days before late delivery when prioritized in Route Optimiser || SYSTEM
|-
| LOGIX_DIR || Folder for Logix files || SYSTEM
|-
| LOGIX_MASTER_PROFILE || Profile for Logix API webservice || SYSTEM
|-
| LOGIX_MASTER_WORK_AREA || LogiX Master Work area directory name || SYSTEM
|-
| LOGIX_PASSWORD || Password for Logix API webservice || SYSTEM
|-
| LOGIX_PROFILE || Profile for Logix API webservice || SYSTEM
|-
| LOGIX_PROJECT || Project for Logix API webservice || SYSTEM
|-
| LOGIX_PROXY || Proxy server name for Logix API webservice || SYSTEM
|-
| LOGIX_RANGE || Range of schedules to send || SYSTEM
|-
| LOGIX_RANGE_OLD || Range of schedules to send || SYSTEM
|-
| LOGIX_SCHEDULE_MATRIX || How Many Days in the future to Recalculate Planned Transport? || SYSTEM
|-
| LOGIX_SERVER_NAME || LogiX server name || SYSTEM
|-
| LOGIX_SLOT_CUTOFF_TIME || Cut-off time for planning trunks in LogiX import || SYSTEM
|-
| LOGIX_TIMEOUT || Timeout for Logix API webservice || SYSTEM
|-
| LOGIX_URL || URL for Logix API webservice || SYSTEM
|-
| LOGIX_USERNAME || Username for Logix API webservice || SYSTEM
|-
| LOGNET_INT_DIR || LOGNET file path. || SYSTEM
|-
| LOGO_FILE || Logo file || SYSTEM
|-
| LOGO_FILE_BW || Logo file in Black and White for system usage (e.g. on labels). || SYSTEM
|-
| LOGO_PATH || Site specific location of logo files || SYSTEM
|-
| LOTS_ADD_DEBRIEF || LOTS Additional Debrief Details || COST_CENTRE
|-
| LOTS_DEL_CUST_SIGNATORY || Controls if DEL messages for LOTS require an actual signatory - Y to hold messages. || COST_CENTRE
|-
| LOTS_DEL_MSG_TRIP_STATUS_COMPLETE || Send LOTS DEL Message if trip status set to COMPLETE (Y/N) || COST_CENTRE
|-
| LOTS_EXPORT_TYRE || LOTS export tyre || COST_CENTRE
|-
| LOTS_FTP_DESTINATION_DIRECTORY || Final Destination directory for FTP of LOTS Files || SYSTEM
|-
| LOTS_FTP_DESTINATION_IP_ADDRESS || IP for FTP of LOTS Files || SYSTEM
|-
| LOTS_FTP_DESTINATION_PASSWORD || Password for FTP of LOTS Files || SYSTEM
|-
| LOTS_FTP_DESTINATION_PORT || Port for FTP of LOTS Files || SYSTEM
|-
| LOTS_FTP_DESTINATION_USERNAME || Username for FTP of LOTS Files || SYSTEM
|-
| LOTS_FTP_PUT_DIRECTORY || Mid-Send directory for FTP of LOTS Files || SYSTEM
|-
| LOTS_INBOUND_ARCH || Path for archiving inbound LOTS XML interfaces || SYSTEM
|-
| LOTS_INBOUND_FAIL || Path for failing inbound LOTS XML interfaces || SYSTEM
|-
| LOTS_INBOUND_IDENTIFIER || Pattern for LOTS Trip Inbound XML || SYSTEM
|-
| LOTS_INBOUND_LISTING_NAME || Filename for list of files in directory for LOTS XML Trip Inbound || SYSTEM
|-
| LOTS_INBOUND_PATH || Path for inbound LOTS XML interfaces || SYSTEM
|-
| LOTS_INC_ORDER_HEADER_CONFIRM || Includes the ORDER_HEADER_CONFIRM section in the DEL file for LOTS. || SYSTEM
|-
| LOTS_INC_STOP_SIGNATURE || Indicates if the STOP_SIGNATURE section will be displayed in the DEL outbound files to LOTS. || SYSTEM
|-
| LOTS_INC_STOP_TYPE_DESC || Include STOP-TYPE_DESC tag in XML || SYSTEM
|-
| LOTS_LISTING_SCRIPT_NAME || Script name foe LOTS XML Trip Inbound || SYSTEM
|-
| LOTS_MINI_LODGMENT_FILE || Lodgements || SYSTEM
|-
| LOTS_OUTBOUND_ARCH || Path for archiving outbound LOTS XML interfaces || SYSTEM
|-
| LOTS_OUTBOUND_FAIL || Path for failing outbound LOTS XML interfaces || SYSTEM
|-
| LOTS_OUTBOUND_PATH || Path for outbound LOTS XML interfaces || SYSTEM
|-
| LOTS_PREVENT_MULTI_VLI_VUI || Prevent multiple VLI and VUI files being sent to LOTS (Y/N). || SYSTEM
|-
| LOTS_SEND_PLANNED || Allow TRP message to be sent to LOTS when trip is still at status Planned || SYSTEM
|-
| LOTS_SEND_WHEN_VEHICLE_SCANNED || List of LOTS message types that will be held until a vehicle scan is received for the order. || COST_CENTRE
|-
| LOTS_VERSION_NUMBER || LOTS Poller Version || SYSTEM
|-
| LOTS_XFER_EXTENSION || Sets the LOTS transfer file extension || COST_CENTRE
|-
| LOWERCASE_REF || Allow lowercase bill of lading || COST_CENTRE
|-
| MAINTAIN_SCHEDULE_DATES || Use wholesale schedule dates || COST_CENTRE
|-
| MANF_RECIPIENT || Indicates the recipient type of the manifest || COST_CENTRE
|-
| MANF_REPORT || Indicates the name of the manifest report to be automatically generated when a trip is accepted || COST_CENTRE
|-
| MANF_REPORT || Driver Manifest Name || COST_CENTRE
|-
| MANIFEST_AT_ENROUTE_ONLY || Only Send XML manifest at En-Route status || CARRIER
|-
| MANIFEST_ORDERS || Indicates that the cost centre allows parent and child shipments to be imported || COST_CENTRE
|-
| MAX_LOCATION_INACTIVE_DAYS || Maximum number of days a location can remain inactive before being set to inactive automatically. || SYSTEM
|-
| MAX_REPORT_PARAM_VALUES || Maximum number of multiple values that can be selected for extracts || SYSTEM
|-
| MAX_VOLUME || Maximum Volume for any FTL || SYSTEM
|-
| MAX_WEIGHT || Maximum weight for any FTL || SYSTEM
|-
| MCS_AWB_REQUIRED || This flag control whether the AWB (Air Way Bill) is requested during the pallet building and despatch processes in C-MCS. || SYSTEM
|-
| MCS_DESPATCH_DISPLAY_DROP || Display the Drop Number in the Despatch Screen || SYSTEM
|-
| MCS_DESPATCH_TO_PLAN || Enforce the despatch scanning of packages and pallets to the planned trips? (Y/N) || SYSTEM
|-
| MCS_DISPLAY_ADDITIONAL || Display items scanned from different trips in MCS despatch? (Y/N) || SYSTEM
|-
| MCS_DISPLAY_COMMTYPE_HAZ || This flag controls whether commodity code and hazardous information is displayed against items and pallets in C MCS pallet building. || SYSTEM
|-
| MCS_DISPLAY_PROD_TYPE || This flag controls whether the Product Type is displayed against items and pallets in C- MCS in receipt, despatch and pallet building. || SYSTEM
|-
| MCS_DYNAMIC_PALLET_BUILDING || This flag controls whether to allow pallet building to occur while scanning items for despatch in the items screen || SYSTEM
|-
| MCS_EXCEPTIONS_DAMAGED || MCS exceptions at Receipt (excluding FNR and LATE) and Despatch will be marked as damaged items and be removed from onward trips (Y/N). || SYSTEM
|-
| MCS_FAST || This parameter will control the level of validation performed during MCS scanning. || SYSTEM
|-
| MCS_FAST_VALIDATION || Is fast validation enabled || SYSTEM
|-
| MCS_ITEM_DISPLAY_DU || This flag controls whether the DU type is displayed instead of the item type on item lists in MCS. || SYSTEM
|-
| MCS_LOCATION_PROMPT || Prompt for Receipt Location at Receipt || SYSTEM
|-
| MCS_MOVE_FULL_CONSIGNMENT || Move all items for an order during MCS split scanning. || SYSTEM
|-
| MCS_NEW_DESPATCH_MODE || This flag controls whether the new Despatch screen is run || SYSTEM
|-
| MCS_PALLET_LABEL_FORMAT || The format of pallet label produced by the pallet building option when printing pallet labels. || SYSTEM
|-
| MCS_PREVENT_UNPLANNED || Prevent unplanned items being scanned for pallet building, despatch and receipt although expected for the route (Y/N)? || SYSTEM
|-
| MCS_RECEIVE_TO_PLAN || Enforce the receipt scanning of packages and pallets to the planned trips? (Y/N) || SYSTEM
|-
| MCS_SET_PALLET_ID || MCS set item Pallet Id || SYSTEM
|-
| MCS_TEMPERATURE_SCAN || Prompt for Temperature Type at MCS Despatch || SYSTEM
|-
| MCS_TENDERED_ITEMS || This flag controls whether MCS items are generated at the change to TENDERED status as well as at ACCEPTED status, or just ACCEPTED status. || SYSTEM
|-
| MCS_UPDATE_SCAN_IMMEDIATELY || Allow items to count as despatched immediately after scanning? (Y/N) || SYSTEM
|-
| MICD_DONT_SEND_DRVR_ID || Microlise Direct Don't send driver id || COST_CENTRE
|-
| MICD_EE_PATH_IN_IDENT || Pattern for MICD EventExport Inbound XML || SYSTEM
|-
| MICD_JSE_PATH_IN_IDENT || Pattern for MICD JourneySummaryExport Inbound XML || SYSTEM
|-
| MIC_3PL_TRIP_HOURS || The number of elapsed hours that Microlise requires a trip not to exceed. || SYSTEM
|-
| MIC_ACTUAL_DISTANCE || Will Microlise receive an actual distance from Paragon for a trip (Y/N)? || SYSTEM
|-
| MIC_ADD_STOP_BARCODE || Include new tag STOP_BARCODE on Microlise outbound xml || SYSTEM
|-
| MIC_ALLOW_CREATE_ORDERS || Allow orders to be created || SYSTEM
|-
| MIC_AUTO_CONFIRM_COLLECTION_ORDERS || Create Service Types via Microlise || COST_CENTRE
|-
| MIC_CALC_REASON_QTY || Set the item reason quantity to the despatched quantity if a reason code is provided with a quantity of 0 instead of an accurate quantity (Y/N). || COST_CENTRE
|-
| MIC_COLLECTION_ORDER_TASKS || Create ad hoc orders via Microlise || COST_CENTRE
|-
| MIC_CONSOL_ORDERS || Consolidate the orders for the Microlise outbound XML flow, if Y then the orders will be consolidated. || COST_CENTRE
|-
| MIC_CONSOL_STOPS || Consolidate the stops for the Microlise outbound XML flow, if Y then the stops will be consolidated. || COST_CENTRE
|-
| MIC_CREATE_CD || Microlise interface to create CD reason for successful deliveries when not provided || SYSTEM
|-
| MIC_CREATE_FAILED_ORDERS || Controls if orders be set to FAILED status on inbound Microlise flow || COST_CENTRE
|-
| MIC_DEBRIEF_POC || Allow the collection orders to set their POC flag when they are confirmed with actual delivered quantities and generate a ORD_COLL_XML file? (Y/N) || COST_CENTRE
|-
| MIC_DEFAULT_DELIVER || Should the actual times be set to the planned ones upon receipt of a STA or DEP message || COST_CENTRE
|-
| MIC_DEFAULT_PRODUCT_TYPE || Create Service Types via Microlise || COST_CENTRE
|-
| MIC_DEFINE_GROUP_NAME || Group Name For Microlise Collection Orders || COST_CENTRE
|-
| MIC_DEF_COST || Cost Centre default || SYSTEM
|-
| MIC_DEF_CUST || Customer ID default for Microlise || COST_CENTRE
|-
| MIC_DEF_DEL_TYPE || Default Del Type for empty orders || SYSTEM
|-
| MIC_DEF_DU_TYPE || Du Type || SYSTEM
|-
| MIC_DEF_PRODUCT || Product Type || SYSTEM
|-
| MIC_DELETE_REASONS || Delete Reason codes before adding new reason codes. || COST_CENTRE
|-
| MIC_DEL_DAY_OFFSET || Delivery Day Offset || SYSTEM
|-
| MIC_DIRECT_DEF_COST || Cost Centre default || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_DIRECTORY || Directory for FTP of Microlise Direct Files || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_IP_ADDRESS || IP for FTP of Microlise Files || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_PASSWORD || Password for FTP of Microlise Direct Files || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_PORT || Port for FTP of Microlise Direct Files || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_PROTOCOL || Protocol for FTP of Microlise Direct Files || SYSTEM
|-
| MIC_DIRECT_FTP_DEST_USERNAME || Username for FTP of Microlise Direct Files || SYSTEM
|-
| MIC_DIRECT_PATH_IN || Inbound Directory for Direct Microlise XML || SYSTEM
|-
| MIC_DIRECT_PATH_IN_ARCH || Archive Directory for Inbound Direct Microlise XML || SYSTEM
|-
| MIC_DIRECT_PATH_IN_FAIL || Failure Directory for Inbound Direct Microlise XML || SYSTEM
|-
| MIC_DIRECT_PATH_IN_IDENT || Pattern for MIC Trip Inbound XML || SYSTEM
|-
| MIC_DIRECT_PATH_IN_LIST || Filename for list of files in directory for MIC Direct XML Trip Inbound || SYSTEM
|-
| MIC_DIRECT_PATH_IN_SCRIPT || Script name for MIC Direct XML Trip Inbound || SYSTEM
|-
| MIC_DIRECT_PATH_OUT || Outbound Directory for Direct Microlise XML || COST_CENTRE
|-
| MIC_DIRECT_PATH_OUT_ARCH || Outbound Archive Directory for Direct Microlise XML || SYSTEM
|-
| MIC_DIRECT_SEND_CUSTOMER || Microlise direct will send customer group instead of carrier || SYSTEM
|-
| MIC_DIRECT_SEND_ROUTE_CODE || Set Microlise direct to send route code in the Journey Alias field. || SYSTEM
|-
| MIC_DIRECT_UPDATE_PRIORITY || Flag indicating priority for del/arr updates Manual, EventExport, PodPoc updates || COST_CENTRE
|-
| MIC_DISABLE_EMPTY_ITEM_STOPS || Allows disabling of stops with no items on || SYSTEM
|-
| MIC_EXCLUDE_ASSET_ID || A comma-delimited list of prefixes that determines if the new asset ID will not be stored (e.g. for loose items). || SYSTEM
|-
| MIC_EXCLUDE_UNPACKED_LINES || Exclude any order lines that have not been packed from the Microlise files (Y/N). || COST_CENTRE
|-
| MIC_EXTENDED_INSTRUCTIONS || Are extended instructions sent to MICROLISE || COST_CENTRE
|-
| MIC_FTP_DESTINATION_DIRECTORY || Directory for FTP of Microlise Files || SYSTEM
|-
| MIC_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Microlise Files || SYSTEM
|-
| MIC_FTP_DESTINATION_PASSWORD || Password for FTP of Microlise Files || SYSTEM
|-
| MIC_FTP_DESTINATION_PORT || Port for FTP of Microlise Files || SYSTEM
|-
| MIC_FTP_DESTINATION_USERNAME || Username for FTP of Microlise Files || SYSTEM
|-
| MIC_INBOUND_ARCH || Path for Microlise XML archiving || SYSTEM
|-
| MIC_INBOUND_CONTINUE_ON_ERROR || Continue processing MICROLISE message if invalid items exist within the file? (Y/N) || COST_CENTRE
|-
| MIC_INBOUND_FAIL || Path for Microlise XML failures || SYSTEM
|-
| MIC_INBOUND_IDENTIFIER || Pattern for MIC Trip Inbound XML || SYSTEM
|-
| MIC_INBOUND_LISTING_NAME || Filename for list of files in directory for MIC XML Trip Inbound || SYSTEM
|-
| MIC_INBOUND_PATH || Path for yet to be processed XML files from Microlise || SYSTEM
|-
| MIC_INC_SERVICES || List of services to be sent out to Microlise || COST_CENTRE
|-
| MIC_LISTING_SCRIPT_NAME || Script name foe MIC XML Trip Inbound || SYSTEM
|-
| MIC_ORDER_FULFILLMENT || Send Additional Order Fulfillment values to Microlise. || COST_CENTRE
|-
| MIC_OUTBOUND_ARCH || Path for archiving outbound Microlise XML interfaces || SYSTEM
|-
| MIC_OUTBOUND_FAIL || Path for failing outbound Microlise XML interfaces || SYSTEM
|-
| MIC_OUTBOUND_PATH || Path for outbound Microlise XML interfaces || SYSTEM
|-
| MIC_OWNING_DEPOT || Indicates if the Microlise file is sent with Database or owning depot in the name || SYSTEM
|-
| MIC_PACKED_DESPATCHED || Only packed/despatched lines and items sent to Microlise || COST_CENTRE
|-
| MIC_POCPOD_NON_DEPOT || Microlise to set POC/POD for non depot orders || COST_CENTRE
|-
| MIC_REDUCED_EVENTS || Will Microlise receive a reduced number of defined events (Y/N)? || SYSTEM
|-
| MIC_RESOURCE_UPDATE || Update resources on recipt of Microlise message || COST_CENTRE
|-
| MIC_SEND_ACCEPTED || Send Microlise Trip message when status changed to ACCEPTED || SYSTEM
|-
| MIC_SEND_ADDR_CONTACTS || Send Contacts to Microlise (DEP/DEL/BOTH) || COST_CENTRE
|-
| MIC_SEND_ADD_REF || Send Address references in Mircolise XML flow || COST_CENTRE
|-
| MIC_SEND_ALL_CONTACTS || Send All Contacts to Microlise (Y/N) || COST_CENTRE
|-
| MIC_SEND_CHILDREN || Are child locations sent to Microlise || COST_CENTRE
|-
| MIC_SEND_COST || Send Costs in Mircolise XML flow || COST_CENTRE
|-
| MIC_SEND_DETAIL_ID || Send DETAIL_ID in the MIC XML flow || COST_CENTRE
|-
| MIC_SEND_DIRECT || Flag indicating needing to send direct message to Microlise or not || COST_CENTRE
|-
| MIC_SEND_EMPTY || Are empty resources sent to Microlise || SYSTEM
|-
| MIC_SEND_HAULIER_TYPE || Include Haulier Type in outbound microlise flow || COST_CENTRE
|-
| MIC_SEND_ORD_LINE_AND_ITEM || Send both Order Lines and Items to Microlise. || COST_CENTRE
|-
| MIC_SEND_ORD_REF || Send Order sub references in Mircolise XML flow || COST_CENTRE
|-
| MIC_SEND_SUB_TYPE || Are VAN carriers indicated || COST_CENTRE
|-
| MIC_SERVICE_TASKS || Create Service Types via Microlise || COST_CENTRE
|-
| MIC_SET_TO_COMP_CONF || Set trip to P-Completed, F-Confirmed, N-Neither once Microlise has finished its updates || SYSTEM
|-
| MIC_SHIPMENT_SO_REF || Is external ref included in the Shipment detail tag? || SYSTEM
|-
| MIC_SO_REF || So_ref sent to MICROLISE is oms_ref concatenated with external_ref || SYSTEM
|-
| MIC_SO_REF_FORMAT || Format for the SO_REF for Microlise for non-consolidated orders: 0 = Standard (Customer Ref), 1 = Type-SO_REF-Trip-Seq-Act (eg C-12345-MAN-1234-001-L) || SYSTEM
|-
| MIC_SO_REF_FORMAT || Format for the SO_REF for Microlise for non-consolidated orders: 0 = Standard (Customer Ref), 1 = Type-SO_REF-Trip-Seq-Act (eg C-12345-MAN-1234-001-L) || COST_CENTRE
|-
| MIC_SO_REF_FORMAT || Contingency Import setting || COST_CENTRE
|-
| MIC_SUPPRESS_ORDER_SEGMENT || Only show orders against the stop for the final delivery || COST_CENTRE
|-
| MIC_TRUNK_CONSOL || Are trunk trips consolidated to send to Microlise || COST_CENTRE
|-
| MIC_UPDATE_ACTUALS_FROM_PODPOC || Update Actuals based on POD/POC Message. || COST_CENTRE
|-
| MIC_UPDATE_TO_DELIVER || Update To Deliver based on Delivered Amount || COST_CENTRE
|-
| MIC_USE_ALT_STOP_ID || Prefix stop id with route code for first and last stops || COST_CENTRE
|-
| MIC_USE_PALLET_ID || Use Pallet ID in Microlise || COST_CENTRE
|-
| MIC_USE_STOP_ID || Determines if the stop ID or the stop sequence will be used by Microlise, if Y then the stop ID will be used. || COST_CENTRE
|-
| MIC_USE_STOP_ID || Determines if the stop ID or the stop sequence will be used by Microlise, if Y then the stop ID will be used. || SYSTEM
|-
| MILK_ROUND_ORDERS || Allow orders to be added to Milk round Routes based on delivery information || COST_CENTRE
|-
| MILK_ROUND_TRIP_GENERATION || Trips Generated using milk round processing || COST_CENTRE
|-
| MINIMUM_COLLECTION || Are Minimum collection charges applicable at each stop || SYSTEM
|-
| MINS_TRUNKS_ACCEPTED || How many minutes to auto accept trunk trips? || SYSTEM
|-
| MIN_COLLECTION_CHARGE || Minimum Collection charge per stop || SYSTEM
|-
| MIN_CONSIGNMENT_CHARGE || Minimum charge per consignment || SYSTEM
|-
| MIS_CHAR_SET || Character set for MIS extracts || SYSTEM
|-
| MIS_DELETED_DAYS || The number of days after which the data on the MIS_DELETED table will be removed. || SYSTEM
|-
| MIS_DELETE_REQUIRED || Determines whether MSI table needs to be updated || SYSTEM
|-
| MIS_FTP_ARCH_DIR || MIS FTP archive directory || SYSTEM
|-
| MIS_FTP_DESTINATION_DIRECTORY || MIS FTP Dir || SYSTEM
|-
| MIS_FTP_DESTINATION_IP_ADDRESS || MIS FTP IP || SYSTEM
|-
| MIS_FTP_DESTINATION_PASSWORD || MIS FTP Password || SYSTEM
|-
| MIS_FTP_DESTINATION_PORT || MIS FTP Port || SYSTEM
|-
| MIS_FTP_DESTINATION_USERNAME || MIS FTP User || SYSTEM
|-
| MIS_FTP_PROTOCOL || MIS FTP Protocol || SYSTEM
|-
| MIS_TAB_DELIMITER || Use a tab as a delimiter for the MIS files (Y/N)? || SYSTEM
|-
| MIXMOVE || Is MIMOVE interface enabled? || SYSTEM
|-
| ML_REQUIRED || Whether database is multi-lingual. || SYSTEM
|-
| MSC_STD_STATUS_CHANGES || Do trips go to EN-ROUTE and COMPLETED auto || SYSTEM
|-
| MSG_CONCAT_TIME_PERIOD || Message concatenation time period (minutes) || SYSTEM
|-
| MSG_LOC_ORD_DEL_BY_DELIVERY || Set to Y if message body for event LOC_ORD_DEL is to show delivery details || SYSTEM
|-
| MSG_NAKS || Send an email message for NAK responses (Y/N) || SYSTEM
|-
| MSG_NAKS_EMAIL || The email recipient for a message for NAK responses || SYSTEM
|-
| MSG_NAKS_TYPE || A list of NAK event types to send an email message || SYSTEM
|-
| MSG_SCHEMA_URL || XSD Schema URL Path || SYSTEM
|-
| MSG_SCHEMA_XSD || XSD Schema XSD Name || SYSTEM
|-
| MSG_SENDER_TRIP_ACCEPT || The sending email address for a the trip accept message. || COST_CENTRE
|-
| MSG_SEND_HOURS_THRESHOLD || Threshold in hours before current date when Trip messages will still be sent (using trip start date) || SYSTEM
|-
| MSG_SUBJECT_BKNG_DTL || Message Subject for Booking Detail message || SYSTEM
|-
| MSG_SUBJECT_BKNG_DTL_L || Message Subject for Lane Booking Detail message || SYSTEM
|-
| MSG_SUBJECT_CTM_AUTCHASE || Message Subject for Carrier Trip Management (CTM) Auto Chase Messages || SYSTEM
|-
| MSG_SUBJECT_CTM_MANCHASE || Message Subject for Carrier Trip Management (CTM) Manual Chase Messages || SYSTEM
|-
| MSG_SUBJECT_LANE_ACD_DTL || Message Subject for Lane Accepted Detail message || SYSTEM
|-
| MSG_SUBJECT_LANE_ACPTD || Message Subject for Lane Accepted message || SYSTEM
|-
| MSG_SUBJECT_LANE_ACPTD_A || Message Subject for Lane Accepted Amended message || SYSTEM
|-
| MSG_SUBJECT_LANE_A_DTL_A || Message Subject for Lane Accepted Amended Detail message || SYSTEM
|-
| MSG_SUBJECT_LOC_ORD_DEL || Message Subject for Pre-warning Order delivery message || SYSTEM
|-
| MSG_SUBJECT_MANIFEST || Message Subject for Network Rail Manifest message || COST_CENTRE
|-
| MSG_SUBJECT_MANIFEST || Message Subject for Manifest message || SYSTEM
|-
| MSG_SUBJECT_MANIFEST_A || Message Subject for Manifest Amended message || SYSTEM
|-
| MSG_SUBJECT_MANIFEST_DTL || Message Subject for Manifest Detail message || SYSTEM
|-
| MSG_SUBJECT_MANIFEST_SUM || Message Subject for Manifest Summary message || SYSTEM
|-
| MSG_SUBJECT_MANIFE_DTL_A || Message Subject for Manifest Detail Amended message || SYSTEM
|-
| MSG_SUBJECT_SELF_BIL_INV || Message Subject for Self bill Credit note || SYSTEM
|-
| MSG_SUBJECT_TENDER_INVT || Message Subject for Tender Invitation message || SYSTEM
|-
| MSG_SUBJECT_TENDER_INV_A || Message Subject for Tender Invitation Amended message || SYSTEM
|-
| MSG_SUBJECT_TENDER_SUM || Message Subject for Tender Invitation Summary message || SYSTEM
|-
| MSG_SUBJECT_TEND_INV_DTL || Message Subject for Tender Invitation Detail message || SYSTEM
|-
| MSG_SUBJECT_TND_INV_DT_A || Message Subject for Tender Invitation Detail Amended message || SYSTEM
|-
| MSG_SUBJECT_TRIP_COM_LST || Message Subject for Trip Completed List || SYSTEM
|-
| MSG_SUB_DEPOT || Identifies the depot to replace with the current depot of the order items in the emails to invite tenders. || SYSTEM
|-
| MSG_TRIP_CONTACT || Messaging Contact Details || COST_CENTRE
|-
| MTMIF_DEFAULT_CUR || Default value for DEFAULT_CUR in MTM LOCATION table. || SYSTEM
|-
| MTMIF_DELV_SRV_CLASS_ID || Default value for DELV_SRV_CLASS_ID in MTM LOCATION table. || SYSTEM
|-
| MTMIF_DEL_STOPTM || Default value for DEL_STOPTM in MTM LOCATION table. || SYSTEM
|-
| MTMIF_ITEM_SOURCE || Defines what item information is uploaded to MTM into item_id column, PROD_TYPE, TEMP_COMBO or DU_TYPE || SYSTEM
|-
| MTMIF_LOAD_CLASS_ID || Default value for LOAD_CLASS_ID in MTM LOCATION table. || SYSTEM
|-
| MTMIF_LOAD_TYPE_SOURCE || Defines what Load information is uploaded to MTM into load_type_id column, PROD_TYPE, TEMP_COMBO or DU_TYPE || SYSTEM
|-
| MTMIF_PICK_SRV_CLASS_ID || Default value for PICK_SRV_CLASS_ID in MTM LOCATION table. || SYSTEM
|-
| MTMIF_PRODUCT_SOURCE || Defines what Product information is uploaded to MTM into product_id column, PROD_TYPE or NULL || SYSTEM
|-
| MTMIF_PU_STOPTM || Default value for PU_STOPTM in MTM LOCATION table. || SYSTEM
|-
| MTMIF_SEND_DUS || MTM Interface Send DUs - Y, N or RPE (Y sends DU Qty, RPE sends RPE Qty). || SYSTEM
|-
| MTMIF_SEND_PIECES || MTM Interface Send Pieces - Y, N or RPE (Y sends DU Qty, RPE sends RPE Qty). || SYSTEM
|-
| MTMIF_SEND_VOLUME || MTM Interface Send Volume - Y or N || SYSTEM
|-
| MTMIF_SEND_WEIGHT || MTM Interface Send Weight - Y or N || SYSTEM
|-
| MTMIF_SPLIT_CUBE || Default value for SPLIT_CUBE in MTM LOCATION table. || SYSTEM
|-
| MTMIF_SPLIT_PALLET || Default value for SPLIT_PALLET in MTM LOCATION table. || SYSTEM
|-
| MTMIF_SPLIT_PIECES || Default value for SPLIT_PIECES in MTM LOCATION table. || SYSTEM
|-
| MTMIF_SPLIT_WEIGHT || Default value for SPLIT_WEIGHT in MTM LOCATION table. || SYSTEM
|-
| MTMIF_XDOCK_HANDLING_TIME || Default value for XDOCK_HANDLING_TIME in MTM LOCATION table. || SYSTEM
|-
| MTM_INSTALLED || MTM Installed ? - YES or NO || SYSTEM
|-
| MTM_OPTIMISE_WAIT_TIME || Should wait time incurred at a stop be moved to end of the preceding stop if the latter is an RDC. || SYSTEM
|-
| MTM_PATH || MTM Path || SYSTEM
|-
| MTM_UPDATE_ORDERS || MTM Interface Update Orders - Y or N || SYSTEM
|-
| MTM_VERSION || MTM Version || SYSTEM
|-
| MTS_CSV_EXPORT_PATH || First path that exports looks for when writing a csv to the file system || SYSTEM
|-
| MTS_CSV_EXPORT_PATH_ORS || First path that exports looks for when writing a csv to the file system for ORS || SYSTEM
|-
| MTS_CSV_FTP_PATH || used by EXPORTS Form to set the Client Server FTP Path || SYSTEM
|-
| MTS_CSV_IP_ADDR || CSV IP Address || SYSTEM
|-
| MTS_CSV_LOCAL_PATH || used by EXPORTS Form in Client Server mode - sets where on users PC exports will be written to || SYSTEM
|-
| MTS_CSV_PASSWORD || CSV Password || SYSTEM
|-
| MTS_CSV_USER || CSV User || SYSTEM
|-
| MTS_CSV_WEB_ADDR || CSV Web address || SYSTEM
|-
| MTS_CSV_WEB_PATH || forms part of the URL when generating an export, different value depending on environment || SYSTEM
|-
| MTS_CURRENT_VERSION || MTS Client Server current version || SYSTEM
|-
| MTS_ENABLE_SECURITY || Is Security Enabled - Y or N || SYSTEM
|-
| MTS_EXPORT_PATH || Second path that exports looks for when writing a csv to the file system || SYSTEM
|-
| MTS_FILE_UPLOAD_URL || URL for launching the MTS File Upload || SYSTEM
|-
| MTS_FTP_USER || Mts ftp user to be used within the stand-alone Upload/Import application. || SYSTEM
|-
| MTS_FTP_USER_PWORD || Mts ftp user account password. || SYSTEM
|-
| MTS_FTP_VBAPP_IMPORT_PATH || MTS Import Path for the VB ftp application || SYSTEM
|-
| MTS_IMPORT_PATH || MTS Import Path || SYSTEM
|-
| MTS_IMPORT_VIRTUAL_PATH || MTS Virtual Import Path || SYSTEM
|-
| MTS_INTERFACE || The standard file structure for interfacing || SYSTEM
|-
| MTS_LATEST_REVISION || Latest MTS Version || SYSTEM
|-
| MTS_LOCATION_USAGE || Controls how Locations are grouped, either via CUST_GROUP, CUSTOMER, used in Customer form to display correct tab || SYSTEM
|-
| MTS_LOG_DIR || Path where MTS application error logs are written to || SYSTEM
|-
| MTS_OUTBOUND_ORDER_PATH || File path for Outbound Orders . || SYSTEM
|-
| MTS_PRODUCT_RELEASE || MTS Product RELEASE || SYSTEM
|-
| MTS_PRODUCT_VERSION || MTS Product Version || SYSTEM
|-
| MTS_TRACKING_SYSTEM_1 || Stores the name of one of the tracking systems used in MTS || SYSTEM
|-
| MTS_TRACKING_SYSTEM_2 || Stores the name of one of the tracking systems used in MTS || SYSTEM
|-
| MTS_TRACKING_SYSTEM_3 || TomTom Tracking System || SYSTEM
|-
| MTS_UNQ_DEPOT_DEPARTS || Do departure times need to be unique ? - Y or N || COST_CENTRE
|-
| MTS_WIDE_SCREEN || Should Execution screen de available in Wide Screen || SYSTEM
|-
| NEW_ORDER_CONF || Controls if customers are emailed an order confirmation || COST_CENTRE
|-
| NORTHERN_MANIFEST || Depot Linked to Northern Manifests || SYSTEM
|-
| NO_RECALC_VOL || Controls volume is calculated from the system || COST_CENTRE
|-
| NO_VALID_ORDS_ACPT || When Y -setting trip to Accepted will not call validate order || SYSTEM
|-
| NULL_EXT_REF || Error if external ref is null on manual order || COST_CENTRE
|-
| OBS_BACKGROUND || Background Colour || SYSTEM
|-
| OF_CURRENCY_CODE || Oracle Financial Currency Code || SYSTEM
|-
| OF_FILE_ARCHIVE || Oracle financials archive file path. || SYSTEM
|-
| OF_FILE_NAME_SECTION2 || Stores the name of section 2 on the OF filename || SYSTEM
|-
| OF_FILE_PATH || Oracle financials file path. || SYSTEM
|-
| OF_FTP_DESTINATION_DIRECTORY || Oracle Financials FTP Dir || COST_CENTRE
|-
| OF_FTP_DESTINATION_DIRECTORY || Oracle Financials FTP Dir || SYSTEM
|-
| OF_FTP_DESTINATION_IP_ADDRESS || Oracle Financials FTP IP || SYSTEM
|-
| OF_FTP_DESTINATION_IP_ADDRESS || Oracle Financials FTP IP || COST_CENTRE
|-
| OF_FTP_DESTINATION_PASSWORD || Oracle Financials FTP Password || COST_CENTRE
|-
| OF_FTP_DESTINATION_PASSWORD || Oracle Financials FTP Password || SYSTEM
|-
| OF_FTP_DESTINATION_PORT || Oracle Financials FTP Port || SYSTEM
|-
| OF_FTP_DESTINATION_PORT || Oracle Financials FTP Port || COST_CENTRE
|-
| OF_FTP_DESTINATION_USERNAME || Oracle Financials FTP User || SYSTEM
|-
| OF_FTP_DESTINATION_USERNAME || Oracle Financials FTP User || COST_CENTRE
|-
| OF_FTP_DEST_DTL_DIRECTORY || Cargowise Details directory || COST_CENTRE
|-
| OF_FTP_DEST_DTL_PASSWORD || Cargowise Details password || COST_CENTRE
|-
| OF_FTP_DEST_DTL_USERNAME || Cargowise Details username || COST_CENTRE
|-
| OF_IF_DTL || Oracle Financial IF DTL || SYSTEM
|-
| OF_IF_FTR || Oracle Financial IF FTR || SYSTEM
|-
| OF_IF_HDR || Oracle Financial IF HDR || SYSTEM
|-
| OF_JRNL_ENTRY_SOURCE_NAME || Oracle Financial Journal Entry Source Name || SYSTEM
|-
| OF_ORIGID || Stores the name of ORIGID || SYSTEM
|-
| OF_SECTION2 || Stores the name of section 2 on the OF filename || SYSTEM
|-
| OF_SETTINGS || Controls if Oracle Financial settings are required for 11i and R12 || SYSTEM
|-
| OF_SOURCE_SYSTEM_CODE || Oracle Financial System Code || SYSTEM
|-
| OMS_ACTUALS_MANDATORY || Governs which ACTUAL_QUANTITY fields require mandatory population in Debrief forms. || SYSTEM
|-
| OMS_ADD_ORDER_TO_LOCS || Should orders added to a Trip be added to existing stops based on Location Id - YES or NO || SYSTEM
|-
| OMS_ADD_ORDER_TO_MILK || Allow orders to be added to Milk round Routes || COST_CENTRE
|-
| OMS_ADD_PACKED_LINE || Allow an order to be valid when it contains an order line with a planned qty of zero? (Y/N) || COST_CENTRE
|-
| OMS_ALLOW_DUPL_CUST_REF || This parameter when set will allow the duplicate customer references || SYSTEM
|-
| OMS_ALLOW_MANUAL_SCHEDULE || Display Manual Schedule Flag in orders screen || COST_CENTRE
|-
| OMS_ALTERNATE_REBOOK || Alternative Rebook Functionality || COST_CENTRE
|-
| OMS_AMEND_SVC_FLAGS || OMS_AMEND_SVC_FLAGS || SYSTEM
|-
| OMS_AVG_WEIGHT || Uses average weight to calculate the weight against an order || COST_CENTRE
|-
| OMS_CHANGE_DEL_TYPE || List of Delivery types allowing change || SYSTEM
|-
| OMS_CHECK_CUTOFF || Controls if cut of times for product and du are considered when creating orders || SYSTEM
|-
| OMS_CONSOLIDATE_DUPLICATE_LINES || Enables the consolidation of duplicate order lines during order entry (Y/N). || COST_CENTRE
|-
| OMS_CONSOL_ITEMS || Controls if items are consolidated in order xml || COST_CENTRE
|-
| OMS_CONTACT_TRACKING || To control the use of the order and location contacts for the contacts when they are sent to EPOD and Portal TTM. || SYSTEM
|-
| OMS_CREATE_DUMMY_SOL || Create dummy SOL records for Dunelm || SYSTEM
|-
| OMS_CREATE_POD || Create CSV POD files for the customer? (Y/N) || CUSTOMER
|-
| OMS_CUTOFF_TIME_DEFAULT || Sets the default cut-off time in format HH24:MI for the order time window calculation should a schedule rule not exist for the locations. || SYSTEM
|-
| OMS_DEFAULT_ORDER_CREATION || Controls dates needed when creating Orders in Orders form. ALL, COLLECTION, DELIVERY or STANDARD || SYSTEM
|-
| OMS_DEFAULT_SERVICE_LEVEL || Default service level for the derivation of the time windows for parcel orders. || COST_CENTRE
|-
| OMS_DEFAULT_TEMPLATE_METHOD || Default method for generating orders from order template screen (M for Multiple, S for Single) || SYSTEM
|-
| OMS_DEF_PROD_TYPE || Default Prod Type for Dunelm || SYSTEM
|-
| OMS_EXCLUDE_AUDIT || Exclude changes to field from audit || SYSTEM
|-
| OMS_FOOTPRINT_FOR_VOLUME || Will the footprint of the order line be include in the VOLUME item for the outbound XML file for the despatch units instead of the cubic volume (Y/N)? || COST_CENTRE
|-
| OMS_INCLUDE_X_ITEM_PREFIX || Allow items with a prefix of X to be included in the Load Management screen and Microlise files (Y/N)? || COST_CENTRE
|-
| OMS_INVALID_SAME_LOCS || Set the order status to INVALID when the from and to locations are the same (Y/N) || SYSTEM
|-
| OMS_ITEMS || Generate Item Identifier using OMS reference and count of items || COST_CENTRE
|-
| OMS_ITEM_AKA_DISPLAY || Controls the label on the AKA Code field || COST_CENTRE
|-
| OMS_LEAVE_AS_NEW || To indicate if orders currently at status NEW are to be left at that status after validation other than the paragon interface? (Y/N) || SYSTEM
|-
| OMS_MIC_DEL_DATE || Are MIC files generated when delivery windows are updated || SYSTEM
|-
| OMS_NO_LIFTS || Controls if lifts are included in order xml || COST_CENTRE
|-
| OMS_NO_TRIP_REF_TRG || Do not obtain trip information in order triggers || SYSTEM
|-
| OMS_OFFERED_EARLY_OFFSET || The number of hours (minus) to offset the early collection or delivery time for the order when its booking status is OFFERED. || COST_CENTRE
|-
| OMS_OFFERED_LATE_OFFSET || The number of hours (plus) to offset the late collection or delivery time for the order when its booking status is OFFERED. || COST_CENTRE
|-
| OMS_ORDER_ARCH_DEL_DAYS || Number of days that archived Order Audit messages will be retained for. || SYSTEM
|-
| OMS_ORDER_AUDIT_ARCH_DAYS || Number of days that Order Audit message should be retained in the main table before being archived. || SYSTEM
|-
| OMS_ORDER_ID || Use the OMS Ref for the Order ID || COST_CENTRE
|-
| OMS_RECALC_OH_RPE || Recalculate the planned and packed RPE when an order is validated (Y/N). || COST_CENTRE
|-
| OMS_RESET_AUTO_PROC || Will the auto-processed flags of the order for the scheduling engine be reset when the early delivery date and time is changed? (Y/N) || COST_CENTRE
|-
| OMS_RE_BOOK_STATUS || Controls the status of re-book orders to DEL_FUTILE || SYSTEM
|-
| OMS_SEQ_CTL_ITEM_FORMAT || Add a prefix for the OMS reference for the order items as well as a sequential number (Y/N) || SYSTEM
|-
| OMS_SESSION_EARLY || Earliest arrival offset before the end of the handling time || SYSTEM
|-
| OMS_SESSION_HANDLING || Handling time associated with session collections || SYSTEM
|-
| OMS_SESSION_LATE || Latest arrival offset after the end of the handling time || SYSTEM
|-
| OMS_SESSION_WINDOW || Percentage value used to calculate the collection date and time window for transport orders generated from sessions || SYSTEM
|-
| OMS_SET_DATES || Change Delivery dates on Invalid Back orders || COST_CENTRE
|-
| OMS_SET_DELIVERY_TYPE || Order on/off/not in Schedule || COST_CENTRE
|-
| OMS_STD_ITEMS || Controls if Standard items are auto generated || COST_CENTRE
|-
| OMS_STD_RULE || Schedule rules applied excluding transport mode and delivery types || SYSTEM
|-
| OMS_TAG_TO_ASSET_TYPE || Order types to be validated in TAG to Asset Scanning || SYSTEM
|-
| OMS_TRACK_ITEMS || Indicates if the tracking references will be stored as order items. (Y/N) || CUSTOMER
|-
| OMS_TRACK_ITEMS || Indicates if the tracking references will be stored as order items. (Y/N) || COST_CENTRE
|-
| OMS_UNIQUE_EXT_REF || Controls if imports can load multiple order lines || CUSTOMER
|-
| OMS_UPDATE_SCHEDULE_TO_TRIP || Update the time windows for the orders that exist on a trip when the schedule of the trip is changed in the Planning screen. || SYSTEM
|-
| OMS_VALIDATE_INACTIVE_CODES || To validate orders with error condition for an invalid code for delivery type and service level || SYSTEM
|-
| OMS_VALIDATE_TEMPLATE || Controls whether the Template Id is populated with the associated Lane Id - LANE or NULL || SYSTEM
|-
| OPEN_FTP_DESTINATION_DIRECTORY || OPEN FTP destination Directory || SYSTEM
|-
| OPEN_FTP_DESTINATION_IP_ADDRESS || OPEN FTP destination IP Address || SYSTEM
|-
| OPEN_FTP_DESTINATION_IP_ADDRESS_COPY || OPEN FTP destination IP Address || SYSTEM
|-
| OPEN_FTP_DESTINATION_PASSWORD || OPEN FTP Password || SYSTEM
|-
| OPEN_FTP_DESTINATION_PORT || OPEN FTP destination Port || SYSTEM
|-
| OPEN_FTP_DESTINATION_USERNAME || OPEN FTP Username || SYSTEM
|-
| OP_SYS || Operating system || SYSTEM
|-
| OP_SYS_VER || Operating system version || SYSTEM
|-
| OR3_INTERFACE || Is the PR3 interface active || SYSTEM
|-
| ORDER_SEARCH_CONSOL || Include orders that have passed through a user's SCHED GROUP || SYSTEM
|-
| ORDER_WELL_HIGHLIGHT || Highlight Orders where matching trip found || COST_CENTRE
|-
| ORD_ALLOW_SHIPMENTS || Consolidate Orders on Shipments || COST_CENTRE
|-
| ORD_BOOKING_METHOD || CSV Import - Booking Method -HOME for home delivery, any other value for standard || COST_CENTRE
|-
| ORD_BOOKING_STATUS || Controls if Booking status is displayed || COST_CENTRE
|-
| ORD_CHANGE_BOOKING || Controls if a change to the booking ref is reflected on the payment || COST_CENTRE
|-
| ORD_CHECK_DUPLICATE_ORDERS || For orders where source system is IMPORTS check to see if order is a duplicate - Y or N || SYSTEM
|-
| ORD_CLEAR_DATES || Are dates cleared in the interface || SYSTEM
|-
| ORD_CONF_REPORT || Ord Conf report || COST_CENTRE
|-
| ORD_COPY_ALL_REFS || Are all references copied when items are split? || SYSTEM
|-
| ORD_CREATE_MANIFEST || Controls if a portal manifest record is created for Manual Orders || COST_CENTRE
|-
| ORD_CREATE_PORTAL_ITEM_IDS || Does C-TMS generate the item identifiers for Portal orders || SYSTEM
|-
| ORD_CREATTE_PORTAL_ITEM_IDS || Does C-TMS generate the item identifiers for Portal orders || SYSTEM
|-
| ORD_DEBRIEF_DAYS || Default number of days used to restrict Orders displayed by Order Debrief form. || SYSTEM
|-
| ORD_DEFAULT_AIR || Default Dimensional Weight Factor for Air Transport || SYSTEM
|-
| ORD_DEFAULT_CC || Order Default Cost Centre || SYSTEM
|-
| ORD_DEFAULT_CUST || Order Default Customer || SYSTEM
|-
| ORD_DEFAULT_DEL_TYPE || Order Default Delivery Type || SYSTEM
|-
| ORD_DEFAULT_ROAD || Default Dimensional Weight Factor for Road Transport || SYSTEM
|-
| ORD_DEFAULT_SEND_TO_MTM || Order Default Send to MTM Flag || SYSTEM
|-
| ORD_DEFAULT_SESSION_DU_TYPE || Standard delivery unit used to transport unprocessed blood from sessions || SYSTEM
|-
| ORD_DEFAULT_SESSION_PROD_TYPE || Standard product type used to transport unprocessed blood from sessions || SYSTEM
|-
| ORD_DEFAULT_TRANSCODE || Order Default Trans. Code || SYSTEM
|-
| ORD_DESP2_RESEND || Allow Desp2 message to be resent from orders screen || COST_CENTRE
|-
| ORD_DISPLAY_LIFTS || Display Lifts in preference to quantity || SYSTEM
|-
| ORD_EARLY_COLLECT_THRESHOLD || Number of Hours Early Collection Time can be before the Current Date/Time when creating an Order || SYSTEM
|-
| ORD_EDIT_RPE || Enable the RPE of an order line to be edited? (Y/N) || COST_CENTRE
|-
| ORD_EFFECTIVE_FUEL || Indicates if Fuel charges are fixed or based on effective dates || COST_CENTRE
|-
| ORD_END_TIME || The default late delivery time when a route is not provided for an API order (HH:MM) || SYSTEM
|-
| ORD_ENHANCED_REBOOK || Controls which rebook screen is displayed in the orders form || COST_CENTRE
|-
| ORD_EQUIPMENT_LOAD || Controls if equipment & equipment times are validated || SYSTEM
|-
| ORD_FIXED_SCHEDULE_CHECK || Check for existing fixed schedule generated orders || CUSTOMER
|-
| ORD_FUTURE_LIMIT_DAYS || Maximum Number of days in the future that an order can be created || SYSTEM
|-
| ORD_FUTURE_OFFSET || How far in the future can order offset be set || COST_CENTRE
|-
| ORD_IGNORE_LINE || Are some order lines ignored in the interface || SYSTEM
|-
| ORD_JUST_IN_TIME || Is the collection window set just in time || CUSTOMER
|-
| ORD_LATE_TIME || Late time windows for generated stack orders || SYSTEM
|-
| ORD_LINE_LENGTH || Store LENGTH i/o FOOTPRINT || COST_CENTRE
|-
| ORD_LINE_METHOD || Line Qty Calc Method || COST_CENTRE
|-
| ORD_LINK_CONTENTS || Link Items and contents in the interface || SYSTEM
|-
| ORD_NO_DEL_FOR_FAILS || Controls if DEL messages are generated for FAILED orders - Y to prevent, C to send as CAN || COST_CENTRE
|-
| ORD_OMIT_PACK_SCHEDULING || Omit the scheduling of the order and only print the label when pack confirming. || COST_CENTRE
|-
| ORD_ON_SCHED_DEL_LOC || Du category to be assessed for exclusion from parcel scheduling || CUSTOMER
|-
| ORD_POSTCODE_SEARCH || Determines whether he user can search for order addresses via a postcode (Y/N). || SYSTEM
|-
| ORD_PROCESSED_MSG || Ord Conf Processed Email Msg || COST_CENTRE
|-
| ORD_PROCESSED_SUBJECT || Ord Conf Processed Subject || COST_CENTRE
|-
| ORD_QUANTITY_DU_FIELDS_FORMAT_MASK || Default quantity and pallet fields format mask || SYSTEM
|-
| ORD_QUANTITY_PALLET_FIELDS_FORMAT_MASK || Default quantity and pallet fields format mask || SYSTEM
|-
| ORD_RBO_PREFIX || Is the rebook prefix stripped for LOTS? || SYSTEM
|-
| ORD_REASON_CODE_FILTER || Order Reason Code Filter || SYSTEM
|-
| ORD_REASON_SUP || Reason codes to be supressed in the web service || COST_CENTRE
|-
| ORD_RECEIVED_MSG || Ord Conf Received Email Msg || COST_CENTRE
|-
| ORD_RECEIVED_SUBJECT || Ord Conf Received Subject || COST_CENTRE
|-
| ORD_REMOVE_CANC || Controls if Orders Cancelled in C-TMS generate REM message to LOTS || COST_CENTRE
|-
| ORD_REPRINT_PACK_VISIBLE || Determines whether the Reprint Labels and Pack Confirm buttons are visible. (Y/N). || SYSTEM
|-
| ORD_RETAIN_PLANNED || Planned weight is retained on lines || COST_CENTRE
|-
| ORD_RPE_LM_FACTOR || The factor for loading meters to calculate the RPE of the orders. || COST_CENTRE
|-
| ORD_SET_BUSINESS_TYPE || Set Business Type on Orders || COST_CENTRE
|-
| ORD_SET_SERVICE || Controls if the service level is set to match the delivery type || SYSTEM
|-
| ORD_SPLIT_ALL_REFS || Are all references copied when items are split? || SYSTEM
|-
| ORD_SPLIT_REBOOK_ITEMS || Controls if items on the original order suffixed with X when the order is re-booked || COST_CENTRE
|-
| ORD_SPLI_ALL_REFS || Are all references copied when items are split? || SYSTEM
|-
| ORD_STACK_DEBRIEF || Order Stack Debrief || COST_CENTRE
|-
| ORD_START_TIME || The default early delivery time when a route is not provided for an API order (HH:MM) || SYSTEM
|-
| ORD_TARGET_SEND_TO_MTM || Order Target Send to MTM - Y or N || SYSTEM
|-
| ORD_TEMPERATURE_COMBO || Use Temperature Combo to determine if the customer reference should be highlighted. || COST_CENTRE
|-
| ORD_TEMPLATE_EDIT_UPDATE || Controls whether the user can edit the order template data during generation (Y/N). || SYSTEM
|-
| ORD_UNSCHEDULE_FAILS || Controls if Orders Cancelled in EPOD generate a CANC message to LOTS || COST_CENTRE
|-
| ORD_UNSCHED_COMP || Controls if Orders with 0 qty delivered be unscheduled from COMPLETED trips? || COST_CENTRE
|-
| ORD_UPDATE_LATE_COLL_DATE_TO_DEL || Controls if the Late Collection Date/Time is updated at Save to Match the Late Delivery Date/Time. || SYSTEM
|-
| ORD_VALIDATE_GROUP_NAME || Validate Group Name during order entry || COST_CENTRE
|-
| ORD_WRITE_NOTES || Write Order Notes. || SYSTEM
|-
| ORD_XDOCK_LOTS_DEL_MSG || Lots DEL msg is only sent on last trip for xdock orders (Y/N) || SYSTEM
|-
| ORS_DELIMITER || Oracle reporting suite data field delimiter || SYSTEM
|-
| ORS_SUMMARY || Allow the summarisation OF ORS reports || SYSTEM
|-
| ORS_TYPE_DEF_GROUP_BY || List of the ORS types to default group by fields || SYSTEM
|-
| ORS_TYPE_EXC_GROUP || Exclude ORS types from grouping fields || SYSTEM
|-
| OST_DEBRIEF_WARNING_DAYS || Number of days prior to current date for which orders not debriefed will included in warning message in Order Tracking form. || SYSTEM
|-
| OUTBOUND_3 || File path for Outbound Trips. || SYSTEM
|-
| P2 || users || SYSTEM
|-
| PALLET_BASED_RATING || Rate based on chargeable/non chargeable pallets || CUSTOMER
|-
| PARAGON_IMPORT_LAYOUT || Paragon Import Layout || COST_CENTRE
|-
| PARAGON_INSTALLED || Paragon Installed ? - YES or NO. Only one of MTM_INSTALLED or PARAGON_INSTALLED should be set to YES. || SYSTEM
|-
| PARAGON_INSTALLED || Paragon Installed ? - YES or NO. Only one of MTM_INSTALLED or PARAGON_INSTALLED should be set to YES. || COST_CENTRE
|-
| PARAGON_RUNNING || Paragon Import is currently running (to stop outbound XML jobs) || SYSTEM
|-
| PARAGON_SCHED_DAYS || Determines how many days back paragon should extract records || COST_CENTRE
|-
| PAR_ALLOW_IMPORT_UNDO || Used to indicate if the UNDO button is allowed to be pressed on the Paragon Trip Import? (Y/N) || COST_CENTRE
|-
| PAR_API || Create Control records for Paragon API || SYSTEM
|-
| PAR_AUDIT || Include auditing of the import process in the STP version of the Paragon API (Y/N) || SYSTEM
|-
| PAR_AUTO_RESET_NEW || Auto reset orders at status New after paragon run || COST_CENTRE
|-
| PAR_CHECKSUM_OFF || To indicate if the checksum validation code is required for paragon imports? (Y/N) || SYSTEM
|-
| PAR_DISPLAY_IMPORT_DETAILS || Used to indicate whether the additional message containing the imported details is displayed or not on the Paragon Trip Import? (Y/N) || COST_CENTRE
|-
| PAR_DUN_COL_END_OFFSET || Offset for Dunelm collection end time || SYSTEM
|-
| PAR_DUN_COL_START_OFFSET || Offset for Dunelm collection start time || SYSTEM
|-
| PAR_DUN_TRUNK_CUTOFF_TIME || Set a cut-off time in format HH24:MI to apply to trunk trips to use the current schedule for the day. || SYSTEM
|-
| PAR_DUN_TRUNK_OFFSET_DAYS || Set a number of days to assess the trunk trips for the DUN radial trips. || SYSTEM
|-
| PAR_ENDPOINT_URL || URL for paragon API || SYSTEM
|-
| PAR_EXPORT_FORECAST || Send forecast values to Paragon || COST_CENTRE
|-
| PAR_FREQUENCY || Frequency for PAR Master keys || SYSTEM
|-
| PAR_FTP_DESTINATION_DIRECTORY || Directory for FTP of Paragon Files || SYSTEM
|-
| PAR_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Paragon Files || SYSTEM
|-
| PAR_FTP_DESTINATION_IP_ADDRESS_OLD || IP for FTP of Paragon Files || SYSTEM
|-
| PAR_FTP_DESTINATION_PASSWORD || Password for FTP of Paragon Files || SYSTEM
|-
| PAR_FTP_DESTINATION_PORT || Port for FTP of Paragon Files || SYSTEM
|-
| PAR_FTP_DESTINATION_USERNAME || Username for FTP of Paragon Files || SYSTEM
|-
| PAR_GROUP_STAGING || Paragon Group Staging Level || SYSTEM
|-
| PAR_INBOUND_ARCH || Path for Paragon XML archiving || SYSTEM
|-
| PAR_INBOUND_FAIL || Path for Paragon XML failures || SYSTEM
|-
| PAR_INBOUND_IDENTIFIER || Pattern for Paragon Trip Inbound XML || SYSTEM
|-
| PAR_INBOUND_LISTING_NAME || Filename for list of files in directory for Paragon XML trip Inbound || SYSTEM
|-
| PAR_INBOUND_PATH || Path for yet to be processed XML files from Paragon || SYSTEM
|-
| PAR_INT_SCREEN_CLASSIC_LAYOUT || Removes/Renames fields in PAR_INT to traditional C-TMS system setup rather than those changed for industrial || SYSTEM
|-
| PAR_KEY_FORMAT || PAR Master key format WKXX, DDMM, DAYX || SYSTEM
|-
| PAR_KEY_PROJECT || PAR Project name || SYSTEM
|-
| PAR_LISTING_SCRIPT_NAME || Script name foe Paragon XML Trip Inbound || SYSTEM
|-
| PAR_OUTBOUND_ARCH || Path for archiving outbound Paragon XML interfaces || SYSTEM
|-
| PAR_OUTBOUND_FAIL || Path for failing outbound Paragon XML interfaces || SYSTEM
|-
| PAR_OUTBOUND_PATH || Path for outbound Paragon XML interfaces || SYSTEM
|-
| PAR_PLAN_DIRECT || Controls if Paragon will plan direct collections (Not to owning depot) || COST_CENTRE
|-
| PAR_PROXY || Paragon Proxy Server || SYSTEM
|-
| PAR_RUN_NUMBER || Is Paragon Planning based on Run Numbers? || SYSTEM
|-
| PAR_SEND_ALL_LOCATIONS || Are locations sent out via API || SYSTEM
|-
| PAR_SET_ALL_FROM_NEW || Should all orders and trips set as NEW be updated after Paragon Run || SYSTEM
|-
| PAR_SHUNT_TRUNK || Check if the shunt and trunk routing has been completed prior to exporting to Paragon (Y/N). || SYSTEM
|-
| PAR_SLOT_CUTOFF_TIME || Number of minutes before slot window start that it closes to new orders || SYSTEM
|-
| PAR_START_DATE || Start Date for Master Keys || SYSTEM
|-
| PAR_TENNANT || Tennant for paragon API || SYSTEM
|-
| PAR_TENNANT_KEY1 || Tennant KEY 1 for paragon API || SYSTEM
|-
| PAR_TENNANT_KEY2 || Tennant KEY 2 for paragon API || SYSTEM
|-
| PAR_TRIP_STATUS || Controls the status of any Trips that are created via the Paragon Interface. || SYSTEM
|-
| PAR_TRUNK_THRESHOLD_UOM || Controls the order qty measure used as a threshold when assigning orders to Trunk trips in the Paragon Import. Values are WEIGHT, RPE or VOLUME. || COST_CENTRE
|-
| PAR_TRUNK_TRIP || Are trunk trips generated from Paragon Plan || SYSTEM
|-
| PAR_USE_LOC || Paragon Use From location of order s depot || SYSTEM
|-
| PAR_USE_RPOXY || Paragon Use Proxy || SYSTEM
|-
| PAR_USE_SLOTS || Use slots when exporting to Paragon (DUN format) || SYSTEM
|-
| PAR_VIRTUAL_OUT_ARCH || Path for webshow of archiving outbound Paragon XML interfaces || SYSTEM
|-
| PAR_VIRTUAL_OUT_FAIL || Path for webshow of failing outbound Paragon XML interfaces || SYSTEM
|-
| PAR_XML_OLD_ORDERS || Number of days in the past to still be included for sending orders to paragon || SYSTEM
|-
| PERCENTAGE_MARGIN || Percentage Margin Value || SYSTEM
|-
| PETAL_STARTS_AT_ANY_DEPOT || Does a Petal start at a Depot ? || SYSTEM
|-
| PLANNING_AUTO_SCHED_INACTIVE_DEPOTS || List the inactive depots by commas and in single quotes to exclude their orders in the Planning screen. || SYSTEM
|-
| PLAN_REG_COUNTRY || Planning Region Country suffix || COST_CENTRE
|-
| POLAR_CUST_REF || Controls the source of cust ref in Polar Speed labels || CUSTOMER
|-
| POM_DATE_END || Number of days after Purchase Order dates || SYSTEM
|-
| POM_DATE_START || Number of days before Purchase Order dates || SYSTEM
|-
| POM_DEF_COST || Default Cost Centre for PO || SYSTEM
|-
| POM_DEF_CUST || Default Customer for PO || SYSTEM
|-
| POM_DEF_PROD_TYPE || Default Product Type for PO || SYSTEM
|-
| POM_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header || SYSTEM
|-
| POM_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header || SYSTEM
|-
| POM_INBOUND_PATH || Path for yet to be processed XML files || SYSTEM
|-
| POM_OUTBOUND_ARCH || Path for processed POM outbound XML files that have successfully completed processing || SYSTEM
|-
| POM_OUTBOUND_PATH || Path for PO outbound files || SYSTEM
|-
| PORSCHE_DOT_CODE || Tyre Age for PORSCHE || SYSTEM
|-
| PORTAL_AUTO_SCHED_RET_DAYS || Day range for auto allocation of return orders || SYSTEM
|-
| PORTAL_DEF_DEL_TYPE || Delivery Type for Return orders || SYSTEM
|-
| PORTAL_ORDERS || Portal Imports available || SYSTEM
|-
| POSTAL_STRINGS_TOWN || Is town compared in postal string zones || SYSTEM
|-
| POSTCODE_SHIPMENTS || Indicates if shipments are postcode based || COST_CENTRE
|-
| PO_OVERRIDE_DU_WITH_SUB || A comma-separated list of transit DU types for which the sub-transit DU type will be used instead to generate order lines for the PO || SYSTEM
|-
| PRD_ITEM_IMPORT_FILE || Name of Product Item Import file || SYSTEM
|-
| PRD_ITEM_IMPORT_PATH || Product Item Import path || SYSTEM
|-
| PREVENT_ORD_COL_AFTER_DEL || Stop any ORD or COL messages after a DEL message || COST_CENTRE
|-
| PRINT_ACCEPTED_LABEL || Controls if customer labels are printed when trip is Accepted || COST_CENTRE
|-
| PRINT_INBOUND_LABELS || Controls if labels are generated for inbound xml orders || SYSTEM
|-
| PRINT_LABEL || Controls if customer labels may be reprinted from Order screen || COST_CENTRE
|-
| PRINT_LABEL_PATH || File path for Parcel Carrier Labels to be printed || SYSTEM
|-
| PROJECT_LOCATIONS || Indicates which prefixes are used for project location ids || COST_CENTRE
|-
| PTV_RO_ARCH_DIR || Folder for archive of PTV RO files || SYSTEM
|-
| PTV_RO_AUTO || PTV Automatic Response from Import || SYSTEM
|-
| PTV_RO_DEL_PRIORITY_DAYS || Number of days before late delivery when prioritized in Route Optimiser || SYSTEM
|-
| PTV_RO_DIR || Folder for PTV RO files || SYSTEM
|-
| PTV_RO_EXTEND || PTV plan covers more than 1 week || SYSTEM
|-
| PTV_RO_FILE_API || Create File or send data via API || SYSTEM
|-
| PTV_RO_FIX_MINUS1 || Reduce fix time by 1 when sending to PTV RO || SYSTEM
|-
| PTV_RO_GROUP_NAME || Select PTV unscheduled orders by group name rather than depot || SYSTEM
|-
| PTV_RO_MASTER_PROFILE || Profile for PTV RO webservice || SYSTEM
|-
| PTV_RO_MASTER_PROFILE_DEPOT || Profile for PTV RO webservice || SYSTEM
|-
| PTV_RO_ORDER_PAIRS || PTV Send load and unload tasks combined || SYSTEM
|-
| PTV_RO_ORD_FUTURE_DAYS || PTV Orders Future Days || SYSTEM
|-
| PTV_RO_ORD_HISTORIC_DAYS || PTV Orders Historic Days || SYSTEM
|-
| PTV_RO_PASSWORD || Password for PTV RO webservice || SYSTEM
|-
| PTV_RO_PASSWORD_BETA || Password for PTV RO webservice || SYSTEM
|-
| PTV_RO_PROFILE || Profile for PTV RO webservice || SYSTEM
|-
| PTV_RO_PROFILE_DEPOT_SCHED || Profile for PTV RO webservice || SYSTEM
|-
| PTV_RO_PROJECT || Project for PTV RO webservice || SYSTEM
|-
| PTV_RO_PROXY || Proxy server name for PTV RO webservice || SYSTEM
|-
| PTV_RO_SEND_RETRO || Send retro orders || SYSTEM
|-
| PTV_RO_SET_ROUTE || Set route code on trips from PTV RO || SYSTEM
|-
| PTV_RO_SPLIT || PTV imported route returns to Start Depot || SYSTEM
|-
| PTV_RO_TIMEOUT || Timeout for PTV RO webservice || SYSTEM
|-
| PTV_RO_TRIPS_HISTORIC_DAYS || PTV Trips Historic Days || SYSTEM
|-
| PTV_RO_TRIP_FUTURE_DAYS || PTV Trips Future Days || SYSTEM
|-
| PTV_RO_URL || URL for PTV RO webservice || SYSTEM
|-
| PTV_RO_URL_BETA || URL for PTV RO webservice || SYSTEM
|-
| PTV_RO_URL_NHS || URL for PTV RO webservice || SYSTEM
|-
| PTV_RO_USERNAME || Username for PTV RO webservice || SYSTEM
|-
| PTV_RO_USERNAME_BETA || Username for PTV RO webservice || SYSTEM
|-
| PTV_RO_USERNAME_NHS || Username for PTV RO webservice || SYSTEM
|-
| PTV_RO_WAIT_TIMEOUT || Timeout for PTV RO webservice Response || SYSTEM
|-
| RADIO_DU || Radio active || COST_CENTRE
|-
| RDT_441_CHECK_DAYS || Set a number of days in which to assess the prior loading messages for WCS. || SYSTEM
|-
| REBOOK_ALT_STATUS || If set to Y when an order is rebooked the original orders status will not be changed || SYSTEM
|-
| REBOOK_COPY_SUB_REF_CONTACTS || Set as Y or N to copy Sub References on Rebook, contact details only i.e. SMS and Email details || COST_CENTRE
|-
| RECORD_LIMIT || Limitation of records to display on Customer Service Screen || SYSTEM
|-
| REFRESH_WHEN_CLOSE_ORDER_DETAILS || Refresh the order summary screen when you close the order details page in the Orders form || SYSTEM
|-
| REPORT_CONNECT_STRING || Report auto production - connect string (user/pass@database). || SYSTEM
|-
| REPORT_DIRECTORY || Report auto production - place report in directory. || SYSTEM
|-
| REPORT_FLOC || Report auto production - name of FLOC directory for reports. || SYSTEM
|-
| REPORT_IP_ADDRESS || Report auto production - IP address server. || SYSTEM
|-
| REPORT_PORT || Report auto production - Port || SYSTEM
|-
| REPORT_SERVER || Report auto production - name of report server. || SYSTEM
|-
| REP_DELIVERY_DOCS || Name of the Delivery report printed from trip tree || COST_CENTRE
|-
| REP_JAVA_PDF || Java Report Controller Script || SYSTEM
|-
| REP_JAVA_PDF_DIR || Java Report Folder || SYSTEM
|-
| REP_JAVA_PDF_SHOW || Java Report Webshow Folder || SYSTEM
|-
| REP_LOADING || Name of the loading report printed from trip tree || COST_CENTRE
|-
| REP_ORARRP_DEST_FILEPATH || Reports Destination Filepath || SYSTEM
|-
| REP_ORD_EXTRACT_DAYS || Number of days that the order extract can be run for || SYSTEM
|-
| REP_PDF_DEST_FILEPATH || Reports PDF File Path || SYSTEM
|-
| REP_PDF_FILE_LOC || Reports PDF file location || SYSTEM
|-
| REP_PDF_WEB_DEST_NAME || Reports PDF destination || SYSTEM
|-
| REP_PDF_WEB_SERVER_NAME || Reports PDF Wed Server Name || SYSTEM
|-
| REP_PDF_WEB_SERVER_URL || Reports PDF Web Server URL || SYSTEM
|-
| REP_SERVER_WEB || Reports Server || SYSTEM
|-
| REP_SHOW_CARRIER || Controls if Carrier id is included in the Unsched Orders report || SYSTEM
|-
| REP_SO_REF_FORMAT || Set as 1 or 0 to reformat Order Reference, extract all characters up to the first '-' or '_' || COST_CENTRE
|-
| REP_WEB_SERVER_NAME || Reports Web Server name || SYSTEM
|-
| REP_WEB_SERVER_URL || Reports Server URL || SYSTEM
|-
| RESEND_EFX_STATUS || Can users resend EFX at status Accepted and En-route || COST_CENTRE
|-
| RESOURCE_DIARY || Resource Diary for display of trip allocation || SYSTEM
|-
| RES_ALTERNATIVE_CARRIER || During MTM sync, if Carrier does not exist should MTS check for alternative carrier ? - Y or N || SYSTEM
|-
| RES_ALT_CARRIER || Controls access to Alternate carriers button on Resource form, these are used in TRIPSUM_JRL. - Y or N || SYSTEM
|-
| RES_AVAILABILITY_ALLOC || Determines how resources are allocated to a trip || COST_CENTRE
|-
| RES_CONTROL_ALLOC_RESOURCE || Controls whether a resource can be assigned to more than one Carrier / Carrier Group || SYSTEM
|-
| RES_DT_FUEL_UNITS || Current fuel unit - Litres or Gallons || SYSTEM
|-
| RES_EXTERNAL_DRIVER || Use External Drivers || SYSTEM
|-
| RES_TRACKING_SYSTEM_DISPLAYED || Null, Tractor, Trailer or Both to indicate if Tracking systems are enabled. || SYSTEM
|-
| RETAIN_INTERFACE_ERRORS || Number of days Interface Errors are retained || COST_CENTRE
|-
| RE_PLAN_ORDERS || Controls if the Planner splits order for planning || SYSTEM
|-
| RE_SEQUENCE_STOPS || Are trip stops validate || COST_CENTRE
|-
| RHA_INDEXES || Use RHA indexes || SYSTEM
|-
| RICO_ACCOUNT || Rico Account login to Star-Gate || SYSTEM
|-
| RICO_OUT_ARCH || Outbound archive folder for Rico XML files || SYSTEM
|-
| RICO_OUT_DIR || Outbound folder for Rico XML files || SYSTEM
|-
| RTE_CHECK_MISSING_STOPS || Determines which stops must be present on a Trip, either HIGHEST_OPTIONAL or ALL. || SYSTEM
|-
| RTE_DEF_CAPACITY_MEASURE || Fixed Routes, default capacity measure (RPE, WEIGHT or VOLUME) || SYSTEM
|-
| RTE_DISBAND_SEMI_HOURS || Sets the number of hours prior to departure when a SEMI_FIXED Trip should be disbanded || SYSTEM
|-
| RTE_LOG_DEL_DAYS || Number of days that Fixed Routes log messages should be kept for || SYSTEM
|-
| RTE_MAINT_RDC_ALL_USAGE || Allow the values for the fixed route locations to include an RDC location when the depot has not been assigned to a customer or a customer group (Y/N) || SYSTEM
|-
| RTE_ORDERS_ASC_OR_DESC || Should orders be orders in Ascending or Descending order (ASC or DESC) || SYSTEM
|-
| RTE_PLAN_BY_REGION || Allow Fixed Routes to plan by Postal Region or Planning Region, values are PL and PO. || SYSTEM
|-
| RTE_PRIORITISE_URG_LATE_ORDS || Controls whether urgent and late orders are to prioritised in the Fixed Route process. || SYSTEM
|-
| RTE_REGION_AND_ZONE || Will fixed routes crossdock by planning region and location zone? (Y/N) || SYSTEM
|-
| RTE_SCHED_OFFSET_HRS || Fixed Routes Schedule Offset in hours || SYSTEM
|-
| RTE_SEMI_FIXED_CAPACITY || Determines whether capacity is checked by FILL or TRAILER capacity. || SYSTEM
|-
| RTE_SEMI_FIXED_FUNCTION || Should trips go to SEMI_FIXED if they are not optimum, Y or N. || SYSTEM
|-
| RTE_STOPOVER_MINS || Default number of minutes for a stopover for the network route. || COST_CENTRE
|-
| RTE_TRIPS_DEL_DAYS || Fixed Route RTE Trips in status DELETED on schedules older than this value will be deleted || SYSTEM
|-
| RTE_TRIPS_FIN_STATUS || Fixed Routes final status || SYSTEM
|-
| RTE_TRIPS_TO_ACCEPTED || Defines if ACCEPTED or PLANNED Trips are deleted in Rev TI, if yes then ACCEPTED, otherwise PLANNED - Y or N || SYSTEM
|-
| RTE_USE_CROSSDOCK || Should Fixed Routes allow crossdocks to be used. || SYSTEM
|-
| SALES_EXPORT || Payments are to be exported || SYSTEM
|-
| SAP_DEFAULT_DU_QTY || Default DU Quantity for bookings received via the SAP Interface. || SYSTEM
|-
| SAP_DEFAULT_DU_TYPE || Default DU Type for bookings received via the SAP Interface. || SYSTEM
|-
| SAP_DEFAULT_PROD_TYPE || Default Product Type for bookings received via the SAP Interface. || SYSTEM
|-
| SAP_POD_MSG_RQD || Is SAP (POD) Messages Required to be Extracted out of MTS - Y or N. || SYSTEM
|-
| SCHEDULE_RULES_SERVICE || Is service level displayed in schedule rules || COST_CENTRE
|-
| SCHED_ENG_DEL_OFFSET || The number of days that the order will remain in the delivery depot before it can be assigned to its delivery trip || COST_CENTRE
|-
| SCHED_ENG_DEL_OFFSET_CUTOFF || The cut off time at the delivery depot before an order can be assigned to its delivery trip || COST_CENTRE
|-
| SCHED_ENG_EXC_DU_CATEGORY || Du category to be EXCLUDED from parcel scheduling || CUSTOMER
|-
| SCHED_ENG_PART_PLAN || Will the network scheduling engine allow orders to be partially planned?(Y/N) || COST_CENTRE
|-
| SCHED_EXC_SI || Exclude order with special instructions from engine || COST_CENTRE
|-
| SCHED_RULE_SHOW_ZONE || Display zones instead of master location on delivery schedules in Sched Rules form || SYSTEM
|-
| SCH_CSCS_EST_IMPORT_FILE || Name of CSCS Estimate Import file || SYSTEM
|-
| SCH_CSCS_FC_IMPORT_FILE || Name of CSCS Forecast Import file || SYSTEM
|-
| SCH_CSCS_IMPORT_PATH || CSCS Import path || SYSTEM
|-
| SCH_DEFAULT_FIXED_TEMPLATE || Default Fixed Template Name for Auto Generation || SYSTEM
|-
| SCH_DELETE_PROD_QUANT_DURATION || Number of days worth or Product Quantity data that gets deleted. || SYSTEM
|-
| SCH_MANUAL_CREATE_SCHED || Ability to manually create schedules - Y or N || SYSTEM
|-
| SCH_NAME_FORMAT || Schedule Name Format || SYSTEM
|-
| SCH_RECORD_ITEM_DU_USE || Determine whether to update avg used flag and DU data on product quantity. This might be switched off to improve performance - Y or N || SYSTEM
|-
| SCH_SCHEDULE_ADV_DAYS || Determines how many days in advance to generate fixed routes Schedule || SYSTEM
|-
| SCH_SCHED_DATE_RANGE || Range in days for displaying schedules || SYSTEM
|-
| SCH_SCHED_DURATION || Schedule Duration (Days) || SYSTEM
|-
| SCH_SCHED_ORD_DERIVE || Controls the Order Schedule Date. Acceptable values ECDT, LCDT, EDDT, LDDT. || SYSTEM
|-
| SCH_SCHED_ORD_IMP_IGGESUND_SCHED_DATE_OVERRIDE || When Importing IGGESUND data, can the sched_date be over-written by the SCH_SCHED_ORD_DERIVE rule? || SYSTEM
|-
| SCH_SCHED_ORD_IMP_TI_ORDER_SCHED_DATE_OVERRIDE || When Importing TI_ORDER data, can the sched_date be over-written by the SCH_SCHED_ORD_DERIVE rule? || SYSTEM
|-
| SCH_SCHED_START || Schedule Start time || SYSTEM
|-
| SCH_TRIP_ID_DEPOT || Controls if Trip ID is derived from Owning Depot || SYSTEM
|-
| SCH_TRIP_ID_FMT || SCH Trip Id FMT || SYSTEM
|-
| SCH_TRIP_ID_PREFIX || Prefix for Depot based Trip ID || SYSTEM
|-
| SCH_VLS_IMPORT_FILE || Name of VLS Import File || SYSTEM
|-
| SCH_VLS_IMPORT_PATH || VLS Import Path || SYSTEM
|-
| SCR_CURRENT_HIGHLIGHT_COLOUR || Controls colour of highlighted rows in tables || SYSTEM
|-
| SCR_HEADER_BKG_COLOUR || Colour for header toolbars on forms || SYSTEM
|-
| SCR_HEADER_BMP_PATH || Location of BMP to control the colour of the toolbar/header in forms. Leave a trailing slash. || SYSTEM
|-
| SCR_HEADER_TEXT_COLOUR || Colour of text in header toolbars on forms || SYSTEM
|-
| SEC_GROUP_OR_BASEDAT || Security - Lock Monitor, display Group or Based at || SYSTEM
|-
| SEND_CAN_WITHOUT_BOOKING || Allow CAN message to be sent without Booking Ref || SYSTEM
|-
| SEND_INTERFACE_FAIL_EMAIL || Send email for interface errors || COST_CENTRE
|-
| SEND_LINE_ITEM_TO_LOTS || Send Line Item To LOTS. Y - send both Order Line (D) and Item (S) records. N - Checks for Items and, if there are any, sends Item (S) records, else Order Line (D) records. || SYSTEM
|-
| SEND_MANF_TO_SUPP || Indicates if the supplier manifest report will be automatically generated when a trip is accepted for the cost centre of the trip being collected. || COST_CENTRE
|-
| SEND_MANF_TO_SUPP || Indicates if the supplier manifest report will be automatically generated when a trip is accepted for the cost centre of the trip being collected. || CUSTOMER
|-
| SEND_MIL_MESSAGES || Send Tracking Milestone Messages || CUSTOMER
|-
| SEND_PALLET_ID_XML || Send Pallet ID tag in xml || COST_CENTRE
|-
| SEND_SCP_MESSAGES || Send Supplier Collection Messages || CUSTOMER
|-
| SEND_SMS_EMAIL || Controls whether a SMS or an e-mail may be sent to the recipient of the order being delivered on the trip (Y/N). || COST_CENTRE
|-
| SEND_SMS_EMAIL_OLD || Controls whether a SMS or an e-mail may be sent to the recipient of the order being delivered on the trip (Y/N). || COST_CENTRE
|-
| SEND_TO_ISOTRAK || Send to ISOTRAK - ALL or NONE. || SYSTEM
|-
| SERVICES || Controls if service payments are generated || COST_CENTRE
|-
| SESSION_DEFAULT_LOAD_RATE || Session Default Load rate || COST_CENTRE
|-
| SESSION_DEFAULT_UNLOAD_RATE || Session Default Unload rate || COST_CENTRE
|-
| SET_FAST_ORD_WINDOWS || Call fast order windows in Import || SYSTEM
|-
| SET_MICROLISE_SLOTS || Determines if the delivery slot times are sent to Microlise instead of the planned delivery times. || SYSTEM
|-
| SET_TRUNKS_ACCEPTED || Are Trunk trips automatically set to ACCEPTED status? || SYSTEM
|-
| SFTP_LOG_LEVEL || SFTP Log level - numeric 0-3 || SYSTEM
|-
| SHA_EXCLUDE_AUDIT || Activity types that will be excluded from writing audit log records when they are activated. || SYSTEM
|-
| SHIFT_ADDITIONAL_HOURS || Threshold for charging additional shift hours || COST_CENTRE
|-
| SHIFT_DISTANCE || Shift Distance || COST_CENTRE
|-
| SHIPMENT_NO_QTY_RATING || Indicates if a shipment can be rated without quantities || COST_CENTRE
|-
| SHIPMENT_VOLUME || Maximum shipment volume || SYSTEM
|-
| SHIPMENT_WEIGHT || Maximum shipment weight || SYSTEM
|-
| SHOW_CAPPED_TONNAGE || Display Capped Tonnage Details || SYSTEM
|-
| SHOW_CARRIER_NAME || Is carrier name shown on Planning screen? || SYSTEM
|-
| SHOW_CONTACT || Show contact name and number on labels. || COST_CENTRE
|-
| SHOW_FULL_ADDRESS || Show full delivery address on labels. || COST_CENTRE
|-
| SHOW_SCANNED_ITEMS_BTN || Display Scanned Items Update Button || SYSTEM
|-
| SLOT_DFLT_TRAILER_TYPE || Default Trailer Type for Slots || SYSTEM
|-
| SLOT_EXP_DIR || Slot Export - FTP to directory || SYSTEM
|-
| SLOT_EXP_IP || Slot Export - FTP to IP address || SYSTEM
|-
| SLOT_EXP_LOGIN || Slot Export - FTP using login || SYSTEM
|-
| SLOT_EXP_PORT || Slot Export - FTP to Port || SYSTEM
|-
| SLOT_INC_ADD_CORE_TYPES || Set to Y if Slot are to be defined as type CORE or ADDITIONAL || SYSTEM
|-
| SMA_ALLOW_CREATE_ORDERS || Allow orders to be created || SYSTEM
|-
| SMA_FTP_DESTINATION_DIRECTORY || Directory for FTP of Smartphone Files || SYSTEM
|-
| SMA_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Smartphone Files || SYSTEM
|-
| SMA_FTP_DESTINATION_PASSWORD || Password for FTP of Smartphone Files || SYSTEM
|-
| SMA_FTP_DESTINATION_PORT || Port for FTP of Smartphone Files || SYSTEM
|-
| SMA_FTP_DESTINATION_USERNAME || Username for FTP of Smartphone Files || SYSTEM
|-
| SMA_INBOUND_ARCH || Path for Smartphone XML archiving || SYSTEM
|-
| SMA_INBOUND_FAIL || Path for Smartphone XML failure || SYSTEM
|-
| SMA_INBOUND_IDENTIFIER || Pattern for SMA Trip inbound XML || SYSTEM
|-
| SMA_INBOUND_LISTING_NAME || Filename for list of files in directory for SMA XML trip inbound || SYSTEM
|-
| SMA_INBOUND_PATH || Path for yet to be processed XML files from Smartphone || SYSTEM
|-
| SMA_LISTING_SCRIPT_NAME || Script name for SMA XML Trip inbound || SYSTEM
|-
| SMA_OUTBOUND_ARCH || Path for archiving outbound Smartphone XML interface || SYSTEM
|-
| SMA_OUTBOUND_FAIL || Path for failing outbound Smartphone XML interface || SYSTEM
|-
| SMA_OUTBOUND_PATH || Path for outbound Smartphone XML interface || SYSTEM
|-
| SMA_OWNING_DEPOT || Indicates if the Smartphone file is sent with Database or owing depot in the name || SYSTEM
|-
| SMA_RESOURCE_UPDATE || Update resources on receipt of Smartphone message || COST_CENTRE
|-
| SMA_SEND_ACCEPTED || Send ACCEPTED message to SMARTPHONE || SYSTEM
|-
| SMA_SET_TO_COMP_CONF || Update Trip Status once Smartphone has provided all quantities and times || SYSTEM
|-
| SMA_TO_DELIVER_IS_DELIVERED || Auto-Default the TO_DELIVER quantity from the DELIVERED quantity || COST_CENTRE
|-
| SMS_AUDITING || Will records be audited in ADM_LOG for the SMS_EMAIL messages (Y/N)? || SYSTEM
|-
| SMS_COL_DEL_BOTH || Send SMS for delivery/collection orders or both? (COL, DEL, BOTH) || COST_CENTRE
|-
| SMS_GATEWAY_PWD || SMS Gateway Password || SYSTEM
|-
| SMS_GATEWAY_URL || SMS Gateway URL || SYSTEM
|-
| SMS_GATEWAY_USER || SMS Gateway Username || SYSTEM
|-
| SMS_LANDLINE_EXCLUSION || Will SMS be excluded for landlines? (Y/N) || SYSTEM
|-
| SMS_LOC_TYPES || Limit SMS and EMAIL Notifications to this list of location types only. If blank messages are sent for all stops || COST_CENTRE
|-
| SMS_MULTI_MSG || Send multiple SMS message for each trip stop (Y/N) || COST_CENTRE
|-
| SMS_SENDER_NUM || SMS Sender number to stop replies || SYSTEM
|-
| SMS_SERVICE_BOX || Stores the e-mail address of the SMS service box. || SYSTEM
|-
| SMS_SERVICE_BOX_OLD || Stores the e-mail address of the SMS service box. || SYSTEM
|-
| SMTP_ORDER_SENDER || Order Email Sender address || SCHED_GROUP
|-
| SMTP_ORD_CONF_SENDER || Ord Conf Email Sender Address || COST_CENTRE
|-
| SMTP_ORD_CONF_SENDERXX || Ord Conf Email Sender Address || COST_CENTRE
|-
| SMTP_PASSWORD || SMTP password || SYSTEM
|-
| SMTP_PORT_NUMBER || SMTP Port Number || SYSTEM
|-
| SMTP_PRIMARY || Primary Mail Server || SYSTEM
|-
| SMTP_SECONDARY || Secondary Mail Server || SYSTEM
|-
| SMTP_SENDER || Email Sender address || SYSTEM
|-
| SMTP_SMS_PRIMARY || Primary mail server for SMS. || SYSTEM
|-
| SMTP_SMS_SECONDARY || Secondary mail server for SMS. || SYSTEM
|-
| SMTP_SMS_SENDER || Sender address for SMS. || SYSTEM
|-
| SMTP_TRIP_SENDER || Trip Email Sender address || CONTROL_TOWER
|-
| SMTP_USER || STMP Username || SYSTEM
|-
| SOUTHERN_MANIFEST || Depot Linked to Southern Manifests || SYSTEM
|-
| STOP_PID || LOTS - is STOP_PID included in the extract || SYSTEM
|-
| SUBMIT_CARGOWISE_HEADER || Enter the number of minutes from FTP support files complete status to send header file? || SYSTEM
|-
| SUGGEST_TRIP || Suggest an appropriate trip for an order || COST_CENTRE
|-
| SUPPLIER_MANF || Indicates the name of the supplier manifest report to be automatically generated when a trip is accepted. || COST_CENTRE
|-
| SVC_USE_SERVICE_TYPES || Controls whether Service types are to be used which includes the use of transaction, manual, late and urgent order charging. || SYSTEM
|-
| T2A_ASSET_ARRIVED_OFFSET_DAYS || A number of offset days from the current date to select orders that have arrived at the depot for T2A Forward Items. || SYSTEM
|-
| T2A_ASSET_DUE_OFFSET_DAYS || A number of offset days from the current date to select orders that are due arrive at the depot for T2A Forward Items. || SYSTEM
|-
| TAG_TO_ASSET_SCANNING || Allow scanning and recording of Tags || SYSTEM
|-
| TA_EMAIL_SUBJECT || Email subject for automatically e-mailing manifest || COST_CENTRE
|-
| TA_EMAIL_SUBJECT || Trip accept. Email subject. || SYSTEM
|-
| TA_EMAIL_TEXT || Trip accept. Email message || SYSTEM
|-
| TA_EMAIL_TEXT || Email text for automatically e-mailing manifest || COST_CENTRE
|-
| TA_FILE_NAME || Trip accept. Name of output file. || SYSTEM
|-
| TA_FTP_DIRECTORY || Trip accept. FTP report to upload directory. || SYSTEM
|-
| TA_FTP_IP_ADDRESS || Trip accept. FTP report to IP address. || SYSTEM
|-
| TA_FTP_PASS || Trip accept. FTP report using password. || SYSTEM
|-
| TA_FTP_PORT || Trip accept. FTP port. || SYSTEM
|-
| TA_FTP_USER || Trip accept. FTP report using username. || SYSTEM
|-
| TA_PDF_TO_TIFF1 || Trip accept. Convert pdf to tiff. || SYSTEM
|-
| TA_PDF_TO_TIFF2 || Trip accept. Convert pdf to tiff. || SYSTEM
|-
| TA_PDF_TO_TIFF3 || Trip accept. Convert pdf to tiff stage 3. || COST_CENTRE
|-
| TA_PDF_TO_TIFF3 || Trip accept. Convert pdf to tiff. Rotation for landscape || SYSTEM
|-
| TA_REPORT_NAME || Trip accept. Name of report to be run. Please include the .rep extension. || COST_CENTRE
|-
| TA_REPORT_NAME || Trip accept. Name of report to be run. Please include the .rep extension. || SYSTEM
|-
| TA_SUB_FROM || Trip accept. Sub file from || COST_CENTRE
|-
| TA_SUB_FROM || Indicates Zetafax value in .sub file in FROM: || COST_CENTRE
|-
| TA_SUB_FROM || Trip accept. Sub file from || SYSTEM
|-
| TA_SUB_ORGANISATION || Trip accept. Sub file organisation || SYSTEM
|-
| TA_SUB_PRIORITY || Trip accept. Sub file priority || SYSTEM
|-
| TA_SUB_USER || Trip accept. Sub file user || COST_CENTRE
|-
| TA_SUB_USER || Trip accept. Sub file user || SYSTEM
|-
| TA_SUB_USER || Indicates Zetafax value in .sub file in USER: || COST_CENTRE
|-
| TDL_GEN_ITEMS || Allow order items to be generated from lines || SYSTEM
|-
| TDL_INBOUND_ARCH || Path for TDL XML archiving || SYSTEM
|-
| TDL_INBOUND_IDENTIFIER || Pattern for TDL Inbound XML || SYSTEM
|-
| TDL_INBOUND_PATH || Path for yet to be processed XML files from TDL || SYSTEM
|-
| TDL_ITEM_IN_PORTAL_FORMAT || Generate item identifier in portal format in order entry || SYSTEM
|-
| TEND_EMAIL || Different format for Tender invitation || SYSTEM
|-
| TEST || Controls whether certain testing functions are enabled - Y or N || SYSTEM
|-
| TIMES_LOADING_TIME || Default Loading Time used in Slots import when recalculating times || SYSTEM
|-
| TIME_ZONE_ACTIVE || Time Zone Active || SYSTEM
|-
| TMS_AUTO_DEFAULT_RESOURCE || Automatically default the Resource - Smartphone || COST_CENTRE
|-
| TMS_OTBOUND_SO_REF || Controls the outbound format for SO_REF in LOTSC || CUSTOMER
|-
| TOK_CNAME || Defines the Tokairo Customer Name. || CUSTOMER
|-
| TOK_CUSTOMERS || A comma-delimited list of customers to interface with Tokairo. || SYSTEM
|-
| TOK_FIELD || Defines the Tokairo field name. || CUSTOMER
|-
| TOK_OUTBOUND_ARCHIVE || Filepath for Tokairo Daily Extract archive || SYSTEM
|-
| TOK_OUTBOUND_PATH || Filepath for Tokairo Daily Extract || SYSTEM
|-
| TOK_POD_AVAIL || Is Tokairo being used to view POD documents - Y or N. || SYSTEM
|-
| TOK_SRCH_PAGE || Defines the Tokairo search page. || SYSTEM
|-
| TOK_URL_PREFIX || Defines the Tokairo URL prefix. || SYSTEM
|-
| TOK_VIRDIR || Defines the Tokairo virtual directory. || CUSTOMER
|-
| TOMTOM_CHECK_DEPOT || Check the depot to control data sent to depot || SYSTEM
|-
| TOMTOM_DRIP_FEED || Are stops sent to Webfleet by drip feed process || SYSTEM
|-
| TOMTOM_ORDER_TYPES || Are WEBFLEET order types derived || SYSTEM
|-
| TOMTOM_TIMES_ONLY || Do actual times on SU and CL set trip status || SYSTEM
|-
| TRANSPORT_MODE || Are Customer Transport Mode Factors Required || COST_CENTRE
|-
| TRIP_ALWAYS_SHOW_EMERGENCY_ORDERS || Emergency Deliveries are always displayed regardless of filter criterion || SYSTEM
|-
| TRIP_BRIEF_MAINTENANCE || Enable the Trailer Type, Rated Cost and Message Configuration to be maintained in Carrier Selection for trip planning (Y/N). || COST_CENTRE
|-
| TRIP_CHARGING_METHOD || Determines whether the calculation for the costs includes the trailer type of the trip: F is Fixed and includes the trailer type. || COST_CENTRE
|-
| TRIP_HAZARD_DISPLAYED || Show the Trip hazardous Totals or not. || SYSTEM
|-
| TRIP_HAZARD_LEVEL1_CODE || The colour code of the hazardous weight level 1. || SYSTEM
|-
| TRIP_HAZARD_LEVEL1_FROM || The lower value in the range of the hazardous weight level 1. || SYSTEM
|-
| TRIP_HAZARD_LEVEL1_TO || The upper value in the range of the hazardous weight level 1. || SYSTEM
|-
| TRIP_HAZARD_LEVEL2_CODE || The colour code of the hazardous weight level 2. || SYSTEM
|-
| TRIP_HAZARD_LEVEL2_FROM || The lower value in the range of the hazardous weight level 2. || SYSTEM
|-
| TRIP_HAZARD_LEVEL2_TO || The upper value in the range of the hazardous weight level 2. || SYSTEM
|-
| TRIP_HAZARD_LEVEL3_CODE || The colour code of the hazardous weight level 3. || SYSTEM
|-
| TRIP_HAZARD_LEVEL3_FROM || The lower value in the range of the hazardous weight level 3. || SYSTEM
|-
| TRIP_HAZARD_LEVEL3_TO || The upper value in the range of the hazardous weight level 3. || SYSTEM
|-
| TRIP_HAZARD_PRODUCTS || List the descriptions of the product types considered to be hazardous using a comma as a delimiter. || SYSTEM
|-
| TRIP_LABELS || Indicates the name of the report to be run from the Print Labels menu option in the trip tree in the Planning screen. || COST_CENTRE
|-
| TRIP_ORDER_XSD_VERS || Version of TRIP XSD being used. || SYSTEM
|-
| TRIP_ORD_LATE_FORMAT_MASK || Display the format of the late available and late delivery columns as time only (TIME) or date and time (DATETIME). || SYSTEM
|-
| TRIP_OVERVIEW_CURRENT_TYRES || Use the current quantity of tyres in the Trip Waterfall screen (Y/N) || SYSTEM
|-
| TRIP_PREVENT_PARCEL_CARRIER_ASSIGNMENT || Controls the manual assignment and cross-docking of transport orders to trips for parcels (Y to disable or N to enable). || COST_CENTRE
|-
| TRIP_SHEET || Trip Sheet Report || COST_CENTRE
|-
| TRIP_TRAMPS_ON_WATERFALL || Allow tramping trips to be shown in waterfall form by date not schedule || SYSTEM
|-
| TRIP_VALIDATE_PARCEL_ORDER_ASSIGNMENT || Controls validation of parcel orders to trips for parcel carriers (Y to disable or N to enable). || COST_CENTRE
|-
| TRLR_TYPE_RATE || Are trailer types included when estimating cost? || COST_CENTRE
|-
| TRM_3PL_SCHEDULE_NO_DROP || Enable orders without a drop number for the run to be pre-planned for Paragon (Y/N) || SYSTEM
|-
| TRM_ACTION_MITIGATION || Order Reason Actions requiring Mitigation || SYSTEM
|-
| TRM_ACTIVITY_QTY || Use Activity Quantity to determine when to create DEP control record || COST_CENTRE
|-
| TRM_ACT_PMTS_DEL_ORD_AT_CONF || Control whether Order_payments should be updated, and Orders set to DELIVERED when Trip is set to confirmed || SYSTEM
|-
| TRM_ADD_EDIT_ITEMS || Trip manipulation - display additional edit items. || SYSTEM
|-
| TRM_ALLOW_REJECTIONS || Allow trips to be rejected when they are not tendered (Y/N)? || SYSTEM
|-
| TRM_APPLY_DRIVER_BREAK_RULES || Switches Driver Breaks on or off - Y or N || SYSTEM
|-
| TRM_APPLY_POD_AFTER_ACTUALS || Apply the POD after the all actuals button is pressed (IIB) || SYSTEM
|-
| TRM_AUTO_DEL_TRIP_UNSCHED || Automatically delete trips when the last order is unscheduled from it || COST_CENTRE
|-
| TRM_AUTO_SET_ACCEPTED || Auto Set trip to accepted once all resources allocated || COST_CENTRE
|-
| TRM_BAXTER_ROUTES || Used to control when the process to populate trunk and radial routes is called || COST_CENTRE
|-
| TRM_BOL_PREFIX || Prefix that will be added to BOL when created in MTS. || COST_CENTRE
|-
| TRM_BOL_SUFFIX || Suffix that will be added to BOL when created in MTS. || COST_CENTRE
|-
| TRM_CANCEL_EMPTY_ORDER || Remove orders from trip going to Accepted if there are no items || COST_CENTRE
|-
| TRM_CARRIER_AUDIT || Controls whether audit records are written for Carrier CHANGES || COST_CENTRE
|-
| TRM_CHECK_CREW || Indicates if the Check_Crew functionality should be run. || COST_CENTRE
|-
| TRM_CHECK_LIMITS || Controls level at which Weight, RPE and Volume limits are checked - BY_STOP or NULL || SYSTEM
|-
| TRM_CHK_DRIVER_CARRIER || Use carrier hubs if driver hubs not set || COST_CENTRE
|-
| TRM_CL_DFLT_fixed_time || Default Close Down time (minutes) || SYSTEM
|-
| TRM_COMPLETED_SETTINGS || Indicates if CC/Customer Completed settings are in use || COST_CENTRE
|-
| TRM_CONSOLIDATE_STOPS || Allow consolidation of order on stops if time windows do not overlap || SYSTEM
|-
| TRM_CONSOL_ORDER_AFTER_XDOCK || Consolidate the available time windows for a collected order against the orders being loaded for delivery (Y/N) || SYSTEM
|-
| TRM_CROSSDOCK_TIME || Time offset for delivery into crossdock location || COST_CENTRE
|-
| TRM_DEBRIEF_SCREEN_TIME_VARIANCE_DISPLAYED || Is the Time Variance field displayed and updateable in the Trip Debrief screen. || SYSTEM
|-
| TRM_DEFAULT_DRIVER || Default Driver ID || COST_CENTRE
|-
| TRM_DEFAULT_TRACTOR || Default Tractor ID || COST_CENTRE
|-
| TRM_DEPOT_SCANS || Are trunk trip scans checked || SYSTEM
|-
| TRM_DESP_FOR_DEL || Maintain the Actual Despatched Quantity for a Delivery Trip in Trip Debrief (Y/N). || COST_CENTRE
|-
| TRM_DFLT_DRV_BREAK_MINS || Default Driver Break (minutes) || SYSTEM
|-
| TRM_DFLT_MAX_DRV_HRS_WO_BREAK || Default maximum drive hours without break || SYSTEM
|-
| TRM_DFLT_MAX_DRV_HRS_WO_STOPOVER || Default maximum drive hours without stopover. || SYSTEM
|-
| TRM_DFLT_MAX_WRK_HRS_WO_BREAK || Default maximum work hours without break || SYSTEM
|-
| TRM_DFLT_MAX_WRK_HRS_WO_STOPOVER || Default maximum work hours without stopover. || SYSTEM
|-
| TRM_DFLT_STOPOVER_BREAK_MINS || Default stopover duration (minutes). || SYSTEM
|-
| TRM_DFLT_WRK_BREAK_MINS || Default work break duration (minutes) || SYSTEM
|-
| TRM_DISPLAY_ERROR_MULTI_TRIP || Display Errors when changing multiple trips status || COST_CENTRE
|-
| TRM_DISP_ISOTRAK_OR_EFX || Controls whether the Isotrak Ref or EFX Ref is displayed in the TRIPSUM form - ISOTRAK or EFX || SYSTEM
|-
| TRM_DISP_OMS_OR_CUST_REF_OR_BOOK_OR_CONT_NO || Display OMS, Customer Ref, Booking Ref or Container No - OMS_REF, CUST_REF, CONT_NO or BOOKING_REF. || SYSTEM
|-
| TRM_DISP_REV_COLDEL || Display Revenue on collection or delivery trip || COST_CENTRE
|-
| TRM_DISP_RPE_DU_OR_WEIGHT || Controls whether RPE Qty, DU Qty or Total Weight is displayed in the TRIPSUM form - RPE, DU or WEIGHT. || SYSTEM
|-
| TRM_DISP_SCHED_ALL || Trip manipulation - display schedule all check box. || SYSTEM
|-
| TRM_DISP_VOL_OR_CASES || Controls whether Volume or Cases is displayed in Unscheduled Orders in TRIPSUM forms - VOLUME or CASES || SYSTEM
|-
| TRM_DISTRIBUTE_MAX_ORD_COST || Indicates if the cost centre will DISTRIBUTE revenue charges || COST_CENTRE
|-
| TRM_DO_NOT_UPDATE_ORD_DEL || Leave the order delivery type when the trip delivery type is different || COST_CENTRE
|-
| TRM_DRIVER_HUB || Drivers are aligned to a Hub Location || SYSTEM
|-
| TRM_DRIVER_RQD_FOR_ENROUTE_OR_ACC || Is a Driver required before a Trip can be set to EN_ROUTE or ACCEPTED || COST_CENTRE
|-
| TRM_EARLIEST_STOP_WINDOW || Toggle (Y/N) to specify whether consolidation uses the earliest stop || SYSTEM
|-
| TRM_ENFORCE_CARRIER_RULES || Enforce Carrier Hub Location Rules || COST_CENTRE
|-
| TRM_ENFORCE_TRIP_RECALC || Enforce Trip Recalculation - YES or NO || SYSTEM
|-
| TRM_EXCL_REG_AUTO || Planning Regions to be excluded from Auto Scheduling || COST_CENTRE
|-
| TRM_EXCL_TIME_VALIDATION || Indicates if the available time of an order is not compared to the cut-off time for TRUNK or LINEHAUL routes in the network scheduling engine (Y/N). || SYSTEM
|-
| TRM_FIXED_TRIP_STATUS || Determines status of trips created via Fixed Schedules. P for PLANNED or A for ACCEPTED. || SYSTEM
|-
| TRM_HIGHLIGHT_OVERDUE_FINISH || Trip Status used in Trip Overview screen to highlight overdue finish time || SYSTEM
|-
| TRM_HIGHLIGHT_OVERDUE_START || Trip Status used in Trip Overview screen to highlight overdue start time || SYSTEM
|-
| TRM_IGNORE_DUP_LOC_CHECK || Dunelm orders from a supplier in Scotland to a store in Scotland need to visit the trailer swap location twice so ignore standard checks in TRM || SYSTEM
|-
| TRM_INCL_TRUNK || Are trunk trips to be validated || SYSTEM
|-
| TRM_INC_BASED_AT_LOC_TRIPS || Allows viewing of other depots transiting || SYSTEM
|-
| TRM_LFS_PRINT_TRIP_POD_POC || Display LFS Trip Sheet POD POC report menu option (Y/N)? || SYSTEM
|-
| TRM_LOAD_DFLT_fixed_time || Default Loading Time (minutes) || SYSTEM
|-
| TRM_LOAD_dflt_mins_per_rpe || Default loading rate per RPE (minutes) || SYSTEM
|-
| TRM_LOAD_dflt_mins_per_weight || Default Loading rate per Weight (minutes) || SYSTEM
|-
| TRM_LOC_RADIAL_ROUTES || Indicates if a radial route that is stored for the location will be used in the scheduling engine instead of the location zones (Y/N). || SYSTEM
|-
| TRM_MANIFEST_DATES || Controls if the manifest is run based on dates || COST_CENTRE
|-
| TRM_MAX_DRIVING_HOURS || Maximum Driving Hours || SYSTEM
|-
| TRM_MAX_ORD_COST || Indicates if the cost centre will base revenue charges on the Maximum at a single stop || COST_CENTRE
|-
| TRM_MAX_SHIFT_HOURS || Maximum Shift Hours || SYSTEM
|-
| TRM_MAX_STOP_COST || Indicates if the cost centre will base cost charges on the Maximum at a single stop || COST_CENTRE
|-
| TRM_MAX_STOP_REVENUE || Indicates if the cost centre will base revenue charges on the Maximum at a single stop. || COST_CENTRE
|-
| TRM_MAX_WAIT_TIME || Maximum waiting time at Location (minutes) || COST_CENTRE
|-
| TRM_MERGE_END_OR_EXISTING_STOPS || Method-assigning orders to resulting trip in merge trips. Values: END or EXISTING. END adds orders to end. EXISTING adds orders to 1st available stop. || SYSTEM
|-
| TRM_MIC_DRIVER || Are driver minutes updated from Microlise debrief || COST_CENTRE
|-
| TRM_MODIFY_SCHED || Allow the stop times of the delivery trip to be updated to match the new delivery times of the scheduled order (Y/N). || COST_CENTRE
|-
| TRM_MOVE_ITEM_TO_DESP_BAY || Move an item from the grid to the despatch bay when added to the order on the trip or its order is assigned to the trip (Y/N) || SYSTEM
|-
| TRM_NETWORK_STOPS || Are trunk trip times set by the network table || COST_CENTRE
|-
| TRM_NEW_TRIP_STATUS_CHECKS || Control new restrictions on trip status change. || SYSTEM
|-
| TRM_NLP_SUMMARY || Request a summary by country in the NLP distance and time calculations(Y/N) || COST_CENTRE
|-
| TRM_NLP_SUMMARY || Request a summary by country in the NLP distance and time calculations(Y/N) || COST_CENTRE
|-
| TRM_NON_STD_INSTRUCTIONS || Calculate Planning Instructions on Carrier Trip Form || COST_CENTRE
|-
| TRM_NO_STOP_DELETE || Do not delete stops || COST_CENTRE
|-
| TRM_NO_TIME_VALIDATION || Trip prefix to prevent validation || COST_CENTRE
|-
| TRM_ODO_DISTANCE_LIMIT || Limit used to validate difference between odo start and end entries in debrief areas of Trip Forms || SYSTEM
|-
| TRM_OFFSET_PUBLIC_HOLIDAY || Indicates if the order time windows and the scheduling engine will be offset for the public holiday at the country, depot or route level (Y/N). || SYSTEM
|-
| TRM_ORD_OVERVIEW || Include Orders in Trip Overview screen || COST_CENTRE
|-
| TRM_ORD_SCHED_FROM || Number of days back for schedule range || COST_CENTRE
|-
| TRM_ORD_SCHED_FROM_PLANNING || Number of days back for schedule range in Planning screen || SYSTEM
|-
| TRM_ORD_SCHED_SEARCH || Maximum number of days for schedule range || COST_CENTRE
|-
| TRM_ORD_SCHED_SEARCH_PLANNING || Maximum number of days for schedule range in Planning screen || SYSTEM
|-
| TRM_ORD_SCHED_TO || Number of days forward for schedule range || COST_CENTRE
|-
| TRM_ORD_SCHED_TO_PLANNING || Number of days forward for schedule range in Planning screen || SYSTEM
|-
| TRM_OVERVIEW_AMBER_TIME || Time allowed before start and finish times are amber in TRIP OVERVIEW || SYSTEM
|-
| TRM_OVERVIEW_RED_TIME || Time allowed before start and finish times are red in TRIP OVERVIEW || SYSTEM
|-
| TRM_PLAN_ALL_RET_ORDERS || Plan all RET orders || COST_CENTRE
|-
| TRM_PLAN_INVALID || Are un-manifested orders set to invalid || SYSTEM
|-
| TRM_PREVENT_ALL_DEBRIEF || Prevent setting of actuals in trip debrief || SYSTEM
|-
| TRM_PREVENT_CONSOL_ACROSS_STOPS || Stop orders being added to shipments when not on same stops || COST_CENTRE
|-
| TRM_PREVENT_ORD_ON_COMP_STOP || Prevent Orders Being Planned on Completed stops || SYSTEM
|-
| TRM_PROSPERO_ADV_DAYS || Advance Scheduling days for Prospero || SYSTEM
|-
| TRM_PROTECT_SHUNTS || Protect the times from the order windows for the trip stops for shunt trips for collections (Y/N) || SYSTEM
|-
| TRM_RECALC_ELAPSED_TIME || Always recalculate elapsed time on trip || COST_CENTRE
|-
| TRM_RETAIN_CARRIER_NEW_SCHED || It is to retain a carrier when the schedule of the trip is updated. Otherwise, the carrier is reset to the carrier for the owning depot. || COST_CENTRE
|-
| TRM_RETAIN_EMPTY_STOPS || Retain empty stops when validating the trip. || COST_CENTRE
|-
| TRM_RETAIN_MTM || Retain MTM cost when set to Planned || SYSTEM
|-
| TRM_RETAIN_ORD_STATUS_TRIP_COMPLETE || Retain the current order status if trip status is set to COMPLETED (Y/N) || COST_CENTRE
|-
| TRM_RETAIN_PACK_DATA || Retain Pack Data either via Paragon or advise user to retain or delete pack data if manually unscheduling order. || COST_CENTRE
|-
| TRM_ROUND_RPE_AT_STOP || Round RPE at unload stop || SYSTEM
|-
| TRM_SCHEDULE_BY_DEL || Controls if orders are manually scheduled onto trips by del time || SYSTEM
|-
| TRM_SEND_PLUTO_ACTUALS || Actuals process for PLUTO || COST_CENTRE
|-
| TRM_SEND_PRE_DELIVERY_MSG || Activates email and SMS functionality || COST_CENTRE
|-
| TRM_SET_ACTUALS_AFTER_ENROUTE || Should Actuals (arrive/depart) be set for Trip stop 1 when trip is set to En-Route - Y or N || COST_CENTRE
|-
| TRM_SET_DESP_AFTER_ENROUTE || Should the actual despatched values for an order be set when the trip status is set to EN-ROUTE (Y to enable or N to disable). || COST_CENTRE
|-
| TRM_SET_NEW_STOP_TIMES || Trip prefix to set stop times based on trip duration || COST_CENTRE
|-
| TRM_SET_OWNING_DEPOT || Priority for assigning owning depot to a trip || COST_CENTRE
|-
| TRM_SET_TO_COMPLETED || Should trip be auto set to Completed. Values are N, ACTUAL (after actuals have been applied), POC/POD (when POC and POD applied to all Orders). || COST_CENTRE
|-
| TRM_SET_TO_COMP_AFTER_TIMES || Are trips set to completed when stop actuals have been set? || SYSTEM
|-
| TRM_SET_TO_CONFIRMED || Should trip be auto set to Confirmed. Values are N, ACTUAL (after actuals have been applied), POC/POD (when POC and POD applied to all Orders). || SYSTEM
|-
| TRM_SET_TO_ENROUTE_AFTER_ACTUALS || Should trip be set to En-Route after first order has been collected - Y or N || COST_CENTRE
|-
| TRM_SHIFT_TIMES_FOR_TRIP || Use Shift Times For Start And End Times Of Trip || SYSTEM
|-
| TRM_SHOW_LATE_BUTTON || Is the Show Late Reasons Button visible. || SYSTEM
|-
| TRM_SHOW_TIME_DEBRIEF_BTNS || Show time debrief buttons in trip debrief || SYSTEM
|-
| TRM_SHOW_TRIP_EXPORT_BTN || Show Export Button in TRIP screens. Specifically for Road Ops Report || SYSTEM
|-
| TRM_SOURCE_SYSTEM || Highlight the trip details when it contains an order without an OPEN status in the WMS source system (Y/N) || SYSTEM
|-
| TRM_STACK_DEBRIEF || Trip Stack Debrief || COST_CENTRE
|-
| TRM_STATUS_FOR_CONSOLIDATION || The trip status that controls the consolidation by customer or customer group, enter BOTH for ACCEPTED and PLANNED || SYSTEM
|-
| TRM_STOP_TIMES_FROM_ORDS || Will the trip stop times be inherited from the delivery time window of the order? (Y/N) || CUSTOMER
|-
| TRM_STORE_TRIP_MOVES || Determines whether audit of old and new trips is stored against orders || COST_CENTRE
|-
| TRM_SU_DFLT_fixed_time || Default Start Up time (minutes) || SYSTEM
|-
| TRM_SVC_TYPE || Is SVC_TYPE Editable on TRIP forms? || SYSTEM
|-
| TRM_TEMP_DEBRIEF || Display temperature on Trip debrief || SYSTEM
|-
| TRM_TRACTOR_RQD_FOR_ENROUTE_OR_ACC || Is a Tractor (Vehicle) required before a Trip can be set to EN_ROUTE or ACCEPTED || COST_CENTRE
|-
| TRM_TRAILER_RQD_FOR_ENROUTE_OR_ACC || Is a Trailer Id required on every stop before a Trip can be set to EN_ROUTE or ACCEPTED || COST_CENTRE
|-
| TRM_TRANSPORT_MODE_REQD || Is the transport mode on the trip screens a required field || COST_CENTRE
|-
| TRM_TREE_FORMAT || Determines trip tree display format || COST_CENTRE
|-
| TRM_TREE_ROUTE || Determines whether Route code is displayed in trip tree || COST_CENTRE
|-
| TRM_TRIP_STATUSES || List of Trip Statuses to control which trips displayed in Tripdtl/Trip Debrief form. || SYSTEM
|-
| TRM_TRUNK_TIME || Time in minutes for assessing Trunk Trips || COST_CENTRE
|-
| TRM_UNLOAD_DFLT_fixed_time || Default unloading time (minutes) || SYSTEM
|-
| TRM_UNLOAD_dflt_mins_per_rpe || Default unloading rate per RPE (minutes) || SYSTEM
|-
| TRM_UNLOAD_dflt_mins_per_weight || Default Unloading rate per RPE (minutes) || SYSTEM
|-
| TRM_UNSCHEDULE_TO_CANCEL || Controls if orders are Unscheduled when a cancellation is received || SYSTEM
|-
| TRM_UPDATE_ALL_ACTUALS || When a line actual is debriefed all actuals are set || COST_CENTRE
|-
| TRM_USE_ACTUALS_FOR_STOP_TIMES || Use Actual Times at stops to calculate times for next stop || SYSTEM
|-
| TRM_USE_MAX_RPE_OF_LARG_TRAILER || Controls whether MTS uses Max RPE of Largest Trailer Type when adding Orders to Trips - Y or N (N will use Current Trailer) || SYSTEM
|-
| TRM_VALIDATE_STOP_TIMES || Show Validation messages on stop times and prevent the user from going to accepted (Y/N) || SYSTEM
|-
| TRM_VALIDIDATE_DU_TEMP || Validate Du temp by product and DU || COST_CENTRE
|-
| TRM_VAL_CAR_VESSEL || Trip manipulation - validate carrier after vessel has been allocated. || SYSTEM
|-
| TRM_WASTE_SITE || Amend TO_LOC to a waste site in order well || COST_CENTRE
|-
| TRM_WEIGHTED_AVE_FILL_ACCEPT_PCENT || Defines the acceptable percentage for trip weighted average fill || SYSTEM
|-
| TRM_WEIGHTED_AVE_FILL_MIN_PCENT || Defines the minimum required percentage for trip weighted average fill || SYSTEM
|-
| TRM_WMS_STATUS || Controls if WMS status is calculated and if WMS status fields displayed in Trip forms. || COST_CENTRE
|-
| TRM_XDOCK_VALIDATION || Different Validation for the Cross dock process || COST_CENTRE
|-
| TRM_XDOCK_VIA_ROUTE || Display additional route information when selecting trip for XDOCK orders (Y/N) || SYSTEM
|-
| TRP_RED_TRUCK_ERRORS || Indicates if the truck icon is red to indicate an error || SYSTEM
|-
| TRP_SEND_ENABLE_MSG || Which enabling message is to be sent by Trip form || SYSTEM
|-
| TRP_SEND_WAREHOUSE_LOAD || Include Warehouse Loading Time in the outbound XML flow. || COST_CENTRE
|-
| TRP_STACK_DEBRIEF || Trip Stack Debrief || COST_CENTRE
|-
| TRUNK_LOAD || Time (minutes) to load an order on a trunk trip || SYSTEM
|-
| TRUNK_UNLOAD || Time (minutes) to unload an order on a trunk trip || SYSTEM
|-
| UKMAIL_ADD_INFO_LABEL || Additional information on UKMail Label || COST_CENTRE
|-
| UKMAIL_USE_CUST_REF_ON_LABEL || Controls if customer ref is displayed on UKMAIL label || CUSTOMER
|-
| UNISON_ORDER_INT_TYPE || EIH Interface Type (UNISON ORDER) || SYSTEM
|-
| UNI_DEFAULT_DU_TYPE || Default DU Type for Orders created via the UNISON interface. || SYSTEM
|-
| UNI_ENABLED || To enable the inbound and outbound file processing on this DB || SYSTEM
|-
| UNI_FTP_DESTINATION_DIRECTORY || Directory for FTP of Unilever Files || SYSTEM
|-
| UNI_FTP_DESTINATION_IP_ADDRESS || IP for FTP of Unilever Files || SYSTEM
|-
| UNI_FTP_DESTINATION_PASSWORD || Password for FTP of Unilever Files || SYSTEM
|-
| UNI_FTP_DESTINATION_PORT || Port for FTP of Unilever Files || SYSTEM
|-
| UNI_FTP_DESTINATION_USERNAME || Username for FTP of Unilever Files || SYSTEM
|-
| UNI_INBOUND_ARCH || Path for processed XML files that have successfully completed processing, see: int_po_inbound_header (Unilever) || SYSTEM
|-
| UNI_INBOUND_FAIL || Path for processed XML files that have failed processing for reasons described against int_po_inbound_header (Unilever) || SYSTEM
|-
| UNI_INBOUND_PATH || Path for yet to be processed XML files (Unilever) || SYSTEM
|-
| UNI_LOCATION || Location for Unilever || SYSTEM
|-
| UNI_OUTBOUND_ARCH || Path for processed XML files for Unilever || SYSTEM
|-
| UNI_OUTBOUND_FAIL || Path for processed XML files for Unilever that have failed processing || SYSTEM
|-
| UNI_OUTBOUND_IDENTIFIER || Unilever outbound file identifier || SYSTEM
|-
| UNI_OUTBOUND_PATH || Path for yet to be processed XML files for Unilever || SYSTEM
|-
| UNSCHED_ORDERS_DEL_DAYS || Unscheduled orders on schedules older than this value will be deleted || SYSTEM
|-
| UPDATE_DIR || client Server Update directory || SYSTEM
|-
| UPDATE_IP_ADDR || Client Server Update IP Address || SYSTEM
|-
| UPDATE_IP_ADDR_CGEY || CGEY Client Server IP Address || SYSTEM
|-
| UPDATE_ORDERS_TO_TRIP || Update Order Windows to match selected trip || COST_CENTRE
|-
| UPDATE_ORDER_TIMES_TO_TRIP || Enable the current orders to have their time windows updated to match the stop time windows in the 'Confirm Update/Add' process (Y/N) || COST_CENTRE
|-
| UPDATE_PASSWORD || Client Server Update Password || SYSTEM
|-
| UPDATE_TO_DELIVER || update the To deliver quantity with the Ordered quantity for New order Items || SYSTEM
|-
| UPDATE_USER || Client Server Update User || SYSTEM
|-
| UPD_CUST_DATES || Default part Number || CUSTOMER
|-
| UPGRADE_PASSWORD || Client Server Upgrade Password || SYSTEM
|-
| UPGRADE_USER || Client Server Upgrade Username || SYSTEM
|-
| UPPERCASE_ASSET_ID || Asset id to be stored in upper case || SYSTEM
|-
| URGENT_ORDER || Controls if Urgent Notification emails are sent to planners || COST_CENTRE
|-
| URGENT_ORD_DELIVERY || Controls which delivery types trigger an urgent notification || COST_CENTRE
|-
| URGENT_ORD_RECIPIENT || Controls who receives an urgent notification || COST_CENTRE
|-
| USE_CHILD_LOCATIONS || Use any child locations in preference to the master locations of an order in the requested reports? (Y/Y) || COST_CENTRE
|-
| USE_ORDER_ADDRESSEE || Will the addressee name be used for the order? (Y/N) || COST_CENTRE
|-
| USE_PACK_QUANTITY || Use the current quantity of tyres in the Trip Waterfall screen (Y/N) || SYSTEM
|-
| USE_PALLET_ID_XML || Use Pallet ID instead of item identifier in XML Outbound files || COST_CENTRE
|-
| USE_SECURITY_PROFILES || Use Security Profiles for users || SYSTEM
|-
| USE_SMS_GATEWAY || Use SMS Gateway for SMS message sending || SYSTEM
|-
| USE_XML_ORDER_SUB_REFS || Print order sub refs on outbound XML || COST_CENTRE
|-
| USE_XML_ORDER_SUB_REFS || Print order sub-references in the outbound XML file? (Y/N) || COST_CENTRE
|-
| UTL_IMPORT_IGNORE_INVALID_OPERATION || The import process of files will suppress the auditing of messages when a file does not exist on the server to overwrite (Y/N) || SYSTEM
|-
| VALIDATE_LOCATION_ON_CLOSE || Validate address details if the close button is pressed within locations screen (Y/N)? || SYSTEM
|-
| VALIDATE_MASTER_LOC || Validate the collection and delivery location of the order against the decoded master locations (Y/N) || COST_CENTRE
|-
| VB_UPLOAD_APP_VERSION || Version number of the PC MTS Upload/Import Application written in Visual Basic || SYSTEM
|-
| WARN_MISSING_PO || Warn if No PO Allocated to a trip when status or carrier changed || CARRIER
|-
| WARN_OUTSTANDING4933 || Warn of unmatched 4933 orders on trip status change || CUSTOMER
|-
| WATERFALL_UPDATES || control updates on the waterfall screen || SYSTEM
|-
| WCS_441_CHECK_DAYS || Set a number of days in which to assess the prior loading messages for WCS. || SYSTEM
|-
| WCS_CALC_ITEM_WGT_VOL || Calculate the weight and volume for the DU in the 804 scan (Y/N). || COST_CENTRE
|-
| WCS_CALC_ITEM_WGT_VOL || Calculate the weight and volume for the DU in the 804 scan (Y/N). || CUSTOMER
|-
| WCS_CLEARDOWN_DAYS || Number of days after which WCS control records will be cancelled. || SYSTEM
|-
| WCS_COLLECTION_PREADVICE || Do we call collection pre-advice || NONE
|-
| WCS_COMBINED_ADD_LOAD || WCS add items and loading into a single scan || SYSTEM
|-
| WCS_DEFAULT_AGENT || Default agent for WCS messages || SYSTEM
|-
| WCS_DUAL_INSTANCE || Dual Instance WCS....***DUNELM ONLY*** || SYSTEM
|-
| WCS_ENABLED || Is the WCS system enabled? || SYSTEM
|-
| WCS_MIN_ITEM_LENGTH || Min length of WCS_ITEM to check for match in CTMS || SYSTEM
|-
| WCS_MULTI_DEPOTS || Pre-advise WCS when depot is different || SYSTEM
|-
| WCS_OLD_404_DAYS || Number of days to allow old 404 messages to be sent to WCS || SYSTEM
|-
| WCS_ORD_BUILD_ENABLED || Y to enable WCS Re-advice resend of Orders Overnight Processing || SYSTEM
|-
| WCS_RETAIN_EMPTY_LINES || Retain any empty order lines that have been created when their items have been deleted during the order confirmation process? (Y/N) || SYSTEM
|-
| WCS_SET_BAY_GRID_ITEMS_ONLY || Only update item locations that are on the grid || SYSTEM
|-
| WCS_SPLIT_LOAD_PLAN || Automatically plan the split load orders to final destination || SYSTEM
|-
| WCS_SPLIT_ORDER_BY_TRIP || Allow an order to be split when its items are loaded on different trips for delivery (Y/N)? || COST_CENTRE
|-
| WEB_SERVICE_STORE_REQ || Determines if the message request sent to the web server enquiry should be stored in the audit record - Y will store the message as a CLOB value. || SYSTEM
|-
| WEB_SERVICE_STORE_RESP || Determines if the message in response to the web server enquiry should be stored in the audit record - Y will store the message as a CLOB value. || SYSTEM
|-
| WEB_SERVICE_USER || User name for web service || SYSTEM
|-
| WMS_INBOUND_ARCH || Path for WMS XML archiving || SYSTEM
|-
| WMS_INBOUND_FAIL || Path for WMS XML failures || SYSTEM
|-
| WMS_INBOUND_LISTING_NAME || Filename for list of files in directory for WMS XML Order Inbound || SYSTEM
|-
| WMS_INBOUND_ORD_IDENTIFIER || Pattern for WMS Order Inbound XML || SYSTEM
|-
| WMS_INBOUND_PATH || Path for yet to be processed XML files from WMS || SYSTEM
|-
| WMS_LISTING_SCRIPT_NAME || Script name for WMS XML Order Inbound || SYSTEM
|-
| WOC_MSG_SEND_COUNT || Number of message per run sent to WCS via WOC || SYSTEM
|-
| WSA_ARCHIVE_DAYS || Determines the number of days that the web service messages will be retained in C-TMS prior to being archived. || SYSTEM
|-
| WS_COLLECT_LOCATION || Collection location to override one provided in web service to override collection depot in partnership || CUSTOMER
|-
| WS_COL_CUTOFF || Cut-off time for web service orders from an RDC to make the next days delivery. || SYSTEM
|-
| WS_DERIVE_COL_WINDOW || Derive Collection windows for Web Service Orders || COST_CENTRE
|-
| WS_DUMMY_DU_TYPE || Dummy DU Type used for Web Service order creation || SYSTEM
|-
| WS_EARLY_AVAIL_TIME || Early available time for Web Service Orders || COST_CENTRE
|-
| WS_MAX_MANF_RPE || Maximum RPE value for Web service || SYSTEM
|-
| WS_NUM_OF_RETRIES_ALLOWED || Max number of times a record will be sent to a web service endpoint || SYSTEM
|-
| WS_REASON_CODE || Default reason code for Web service || SYSTEM
|-
| WS_USE_TRIP_STATUS || Use Trip Status for Web Service || COST_CENTRE
|-
| XML_NO_DELAY_FILES || List of XML filenames that will require no delay in polling time (eg pack confirmation). || SYSTEM
|-
| XML_OUT_SUMM_LVL || Level to summarize XML outbound message || SYSTEM
|-
| ZERO_MANIFEST || Allow orders to be zero manifested and set to ABORTED || COST_CENTRE
|-
| ZERO_PACK_REASON || Zero packed reason code || COST_CENTRE
|-
| ZETES_INSTALLED || Zetes installed || SYSTEM
|-
| ZET_INBOUND_ARCH || Path for Microlise XML archiving || SYSTEM
|-
| ZET_INBOUND_FAIL || Path for Microlise XML failures || SYSTEM
|-
| ZET_INBOUND_IDENTIFIER || Pattern for MIC Trip Inbound XML || SYSTEM
|-
| ZET_INBOUND_LISTING_NAME || Filename for list of files in directory for MIC XML Trip Inbound || SYSTEM
|-
| ZET_INBOUND_PATH || Path for yet to be processed XML files from Microlise || SYSTEM
|-
| ZET_INC_SSCC_PREFIX || Include prefixes for SSCC formats for the Zetes interface (Y/N). || COST_CENTRE
|-
| ZET_LISTING_SCRIPT_NAME || Script name foe MIC XML Trip Inbound || SYSTEM
|-
| ZET_OUTBOUND_ARCH || Path for safe copy of XML files for Zetes || SYSTEM
|-
| ZET_OUTBOUND_PATH || Path for yet to be collected XML files for Zetes || SYSTEM
|-
| ZIP || Zip executable location on application server || SYSTEM
|-
| ZIP_SERVER || Application server folder for zipped Invoice files || SYSTEM
|-
| ZONE_POSTCODE_CHECK || Does Zone import check the postcode || SYSTEM
|-
| zip || Location of the zip executable on the application server || SYSTEM
|-
|API_CARRIER_PLAN ||The carrier for the API process which the customer will use with pre-packed labels ||CUSTOMER
|-
|DO_NOT_UPDATE_LOADING_RATES ||Do not update loading rates via customer onboarding ||SYSTEM
|-
|FLEXIPOD ||Set to Y to indicate the FlexiPod interface is active ||SYSTEM
|-
|FLEXIPOD_ACID ||Flexipod acid ||SYSTEM
|-
|FLEXIPOD_BREAK_DROPS ||Flexipod include breaks for the drops in the Add API call (Y/N) ||SYSTEM
|-
|FLEXIPOD_CARRIERS ||Set to Y indicates the Carrier can control if a trip is sent to FlexiPod ||SYSTEM
|-
|FLEXIPOD_CLIENTNUM ||FleXipod ClientNum sent in interface ||SYSTEM
|-
|FLEXIPOD_DEPOTS ||Set to Y indicates the Depot can control if a trip is sent to FlexiPod ||SYSTEM
|-
|FLEXIPOD_DIRECT ||Set to Y to indicate the FlexiPod interface is direct and not using Route Execution ||SYSTEM
|-
|FLEXIPOD_DROP ||Determines the Drop level STOP-OMS or ITEM ||SYSTEM
|-
|FLEXIPOD_EXPIRY ||Sets the expiry date for the manifest as a number of days after the end of the trip. ||SYSTEM
|-
|FLEXIPOD_EXTERNALSYSTEMUPDATE ||Flexipod process the External System Update messages in the API call (Y/N) ||SYSTEM
|-
|FLEXIPOD_FORCEITEMSCAN ||Force the items to be scanned separately: 0 to use the ScanLevel or 1 to force the scan by item. ||SYSTEM
|-
|FLEXIPOD_LISTPENDINGMANIFESTS ||Flexipod process the List Pending Manifest Update messages in the API call (Y/N) ||SYSTEM
|-
|FLEXIPOD_MERGE_DROPS ||Flexipod merge the orders on the drop in the Add API call (Y/N) ||SYSTEM
|-
|FLEXIPOD_PASSWORD ||FleXipod Webservice password ||SYSTEM
|-
|FLEXIPOD_PROXY ||Flexipod proxy server ||SYSTEM
|-
|FLEXIPOD_READDROP ||Flexipod process the Read Drop messages in the API call (Y/N) ||SYSTEM
|-
|FLEXIPOD_SCAN_LEVEL ||1,2 or 3 to indicate line or item level scanning ||SYSTEM
|-
|FLEXIPOD_SCAN_TYPE ||Contents and items ||SYSTEM
|-
|FLEXIPOD_SIGNATORY ||Set to Y to store the SignedByName as the actual signatory as information for the order at its collection of delivery location ||SYSTEM
|-
|FLEXIPOD_SPLIT ||Are orders to be split? ||SYSTEM
|-
|FLEXIPOD_SYSTEM ||FleXipod SYSTEM ID sent in interface ||SYSTEM
|-
|FLEXIPOD_TPCLIENTNUM ||FleXipod TPClientNum sent in interface ||SYSTEM
|-
|FLEXIPOD_USERCODE ||FleXipod webservice usercode ||SYSTEM
|-
|FLEXIPOD_USERNAME ||FleXipod webservice username ||SYSTEM
|-
|FLEXIPOD_WEBSERVICE ||Flexipod webservice endpoint URL ||SYSTEM
|-
|FLEXIPOD_WEBSERVICE_TASK ||Flexipod webservice endpoint URL for Tasks ||SYSTEM
|-
|FLEXIPOD_WEBSERVICE_UI ||Flexipod webservice endpoint URL ||SYSTEM
|-
|FLEXIPOD_WEBSERVICE_UI_EXEC ||Flexipod webservice endpoint URL for Route Execution ||SYSTEM
|-
|FLEXIPOD_X_API_KEY ||Flexipod x-api-key for External System Update messages ||SYSTEM
|-
|IMP_DERIVE_FROM_LOCATION ||Derive the collection location of an order. ||COST_CENTRE
|-
|IMP_DERIVE_ORDER_WINDOWS ||Derive the order windows. ||COST_CENTRE
|-
|IMP_SET_ORDER_TYPE ||Set the order type to RET, SLS or DIR. ||COST_CENTRE
|-
|IMP_SPLIT_CONTACT_NAME ||Split a contact name into Forename and Surname. ||COST_CENTRE
|-
|LIMIT_ADDRESS_MATCH ||Limit address matching to line1, line2 and postcode ||SYSTEM
|-
|LOOKUP_FOR_ROUTE_CODES ||Display lookup button in PLANNING beside Route Code ||SYSTEM
|-
|PSD_CONTACT_ADDRESS ||Polar Speed Distribution Ltd ||SYSTEM
|-
|PSD_CONTACT_TEL ||Tel: +44 (0) 1525 217666 ||SYSTEM
|-
|REBOOK_REQ_SUBREF ||Add Rebook Sub reference when CBR exception added to item ||SYSTEM
|-
|REBOOK_SERVICE_LEVEL ||Service Level For rebooked orders when set to copy use existing ||SYSTEM
|-
|RESET_MANUAL_SCHEDULE ||Reset manual schedule flag from the planning screen ||SYSTEM
|-
|TMP_ENG_TRIP_PREFIX ||Scheduling Engine Trip Prefix ||COST_CENTRE
|-
|TRM_3PL_REROUTE ||Reroute the order in the fixed-drop scheduling engine to the next available route for the day (Y/N) ||SYSTEM
|}

Interface - CTMS XML EDI Order Flow Guide

2025-09-16T07:48:01Z

Anw: Updated

{{Doc_Title
| System = Calidus TMS
| Title = Interface - CTMS XML EDI Order Flow Guide
| Reference = INTERFACE
| Version = 3.03
| Date = 16th September 2025
| Sysver = 12.48
| Client = Aptean
}}

=Overview=
== Introduction ==
{{:TripOrder Interface XML}}

[[Category:Documents]][[Category:C-TMS Training Guides]]
[[Category:Interface Guides]]

TripOrder Interface XML

2025-09-16T07:47:31Z

Anw: Updated

This document is designed to give a brief overview of integration methods into and out of the Aptean TMS - Calidus Edition (CTMS) for transport orders.

The transport orders can be created in CTMS from external systems using XML files based on a standard XSD file format for CTMS called 'TripOrder'.

The following sections will describe some of the sections that are available in the XSD file to create and amend transport orders.

The same XSD file format is used for files being sent by CTMS to external systems to provided information about the transport orders in CTMS and how they have been, or will be, transported between depots and sites.

= XML Inbound Order File Structure =
== EDI Maintenance ==
The XML files for CTMS will be received into a directory structure and processed as may be specified in the 'EDI Maintenance' screen.

Multiple EDI flows may be active to process XML files from different source systems with different filename formats as required.

There are various EDI parameters that can be set to provide different levels of validation of the data that is extracted from the file.

There are also EDI parameters that can be used to set default values for when the data is not able to be provided in the file.

For example, the order time windows can be recalculated and the hazardous data can be defaulted.

== TripOrder File ==
<OBS_XML>
<EVENT>
<EVENT_HEADER>
<EVENT_DETAIL>

The overall file structure consists of two complex type elements - the file header information and then the details. Each element must only exist once per file.

The different sections within <OBS_XML> can occur differently, the data in bold type is included in the text. {{Note}} Not all of the sections and elements that are available in the XSD file format are listed, just the most common use cases:

<OBS_XML> 1.1 <EVENT>
<EVENT> 1.1 <EVENT_HEADER>
<EVENT_HEADER> 1.1 <ALL ELEMENTS>
<EVENT> 0.00 <EVENT_DETAIL>
<EVENT_DETAIL> 1.1 <TRIP_HEADER>
<TRIP_HEADER> 1.1 <TRIP_IDENTIFIER>
<TRIP_HEADER> 0.1 <TRIP_TRANSACTION_DATE>
<TRIP_HEADER> 0.1 <TRIP_ID>
<EVENT_DETAIL> 0.1 <TRIP_DETAIL>
<EVENT_DETAIL> 0.1 <STOPS>
<STOPS> 1.00 <STOP>
<STOP> 1.1 <STOP_HEADER>
<STOP_HEADER> 1.1 <STOP_IDENTIFIER>
<STOP_HEADER> 0.1 <STOP_ID>
<STOP_HEADER> 0.1 <STOP_SEQ>
<STOP> 0.1 <STOP_DETAIL>
<STOP> 0.1 <ORDERS>
<ORDERS> 1.1 <ORDER>
<ORDER> 1.1 <ORDER_HEADER>
<ORDER_HEADER> 1.1 <ORDER_TRANSACTION_DATE>
<ORDER_HEADER> 0.1 <ORDER_TYPE>
<ORDER_HEADER> 0.1 <WMS_WAREHOUSE>
<ORDER_HEADER> 0.1 <WMS_OWNER>
<ORDER_HEADER> 0.1 <SO_REF>
<ORDER_HEADER> 0.1 <TMS_REF>
<ORDER_HEADER> 0.1 <PO_REF>
<ORDER_HEADER> 0.1 <BOOK_REF>
<ORDER_HEADER> 0.1 <BOOK_DATE>
<ORDER_HEADER> 0.1 <SPECIAL_INSTR>
<ORDER_HEADER> 0.1 <ORDER_COMMENTS>
<ORDER_HEADER> 0.1 <ORDER_HEADER_TMS>
<ORDER_HEADER_TMS> 1.1 <EARLY_AVAIL_DATE>
<ORDER_HEADER_TMS> 1.1 <LATE_AVAIL_DATE>
<ORDER_HEADER_TMS> 1.1 <EARLY_DEL_DATE>
<ORDER_HEADER_TMS> 1.1 <LATE_DEL_DATE>
<ORDER_HEADER_TMS> 0.1 <TMS_GROUP_NAME>
<ORDER_HEADER_TMS> 0.1 <TMS_DELIVERY_TYPE>
<ORDER_HEADER_TMS> 0.1 <TMS_COST_CENTRE>
<ORDER_HEADER_TMS> 0.1 <HAULIER>
<ORDER_HEADER_TMS> 0.1 <TRANSPORT_MODE>
<ORDER_HEADER> 0.1 <ORDER_HEADER_ADDRESSES>
<ORDER_HEADER_ADDRESSES> 1.00 <ORDER_HEADER_ADDRESS>
<ORDER_HEADER_ADDRESS> 1.1 <ADDRESS_TYPE>
<ORDER_HEADER_ADDRESS> 1.1 <ADDRESS_ID>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_NAME>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LINE1>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LINE2>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LINE3>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_TOWN>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_COUNTY>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_COUNTRY_CODE>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_POSTCODE>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LOC_TYPE>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_CUST_GROUP>
<ORDER_HEADER_ADDRESS> 0.1 <OH_ADDRESS_CONTACTS>
<OH_ADDRESS_CONTACTS> 1.00 <OH_ADDRESS_CONTACT>
<OH_ADDRESS_CONTACT> 0.1 <ALL ELEMENTS>
<ORDER_HEADER> 0.1 <CUSTOMER_ID>
<ORDER_HEADER> 0.1 <CUSTOMER_NAME>
<ORDER> 0.1 <ORDER_SUB_REFS>
<ORDER_SUB_REFS> 1.1 <ORDER_SUB_REF>
<ORDER_SUB_REF> 1.1 <SUB_REF_IDENTIFIER>
<ORDER_SUB_REF> 1.1 <SUB_REFERENCE>
<ORDER> 0.1 <ORDER_DETAILS>
<ORDER_DETAILS> 1.1 <ORDER_DETAIL>
<ORDER_DETAIL> 1.1 <DETAIL_TYPE>
<ORDER_DETAIL> 0.1 <DETAIL_ID>
<ORDER_DETAIL> 0.1 <PRODUCT_TYPE>
<ORDER_DETAIL> 0.1 <PRODUCT_TYPE_DESC>
<ORDER_DETAIL> 0.1 <DU_TYPE>
<ORDER_DETAIL> 1.1 <ITEM_IDENTIFIER>
<ORDER_DETAIL> 0.1 <ITEM_DESCRIPTION>
<ORDER_DETAIL> 0.1 <PALLET_ID>
<ORDER_DETAIL> 0.1 <ITEM_AKA_CODE>
<ORDER_DETAIL> 0.1 <ITEM_FACTOR>
<ORDER_DETAIL> 0.1 <LIFTS>
<ORDER_DETAIL> 0.1 <RPE_QTY>
<ORDER_DETAIL> 0.1 <WEIGHT>
<ORDER_DETAIL> 0.1 <VOLUME>
<ORDER_DETAIL> 0.1 <ORDERED>
<ORDER_DETAIL> 0.1 <TO_DELIVER>
<ORDER_DETAIL> 0.1 <DELIVERED>
<ORDER_DETAIL> 0.1 <PLANNED_CASES>
<ORDER_DETAIL> 0.1 <LENGTH>
<ORDER_DETAIL> 0.1 <WIDTH>
<ORDER_DETAIL> 0.1 <HEIGHT>
<ORDER_DETAIL> 0.1 <COMMODITY_ID>
<ORDER_DETAIL> 0.1 <CLASS_ID>
<ORDER> 0.1 <ORDER_HAZARDOUS_DETAILS>
<ORDER_HAZARDOUS_DETAILS> 1.00 <ORDER_HAZARDOUS_DETAIL>
<ORDER_HAZARDOUS_DETAIL> 0.1 <ALL ELEMENTS>

The XML items have the following definitions in the XSD file format:

{| class="wikitable apt-searchable" border="1" id="triporderxml"
|- bgcolor="silver"
!Item !!Type !!Size !!Restriction !!CTMS Mandatory*
|-
|EVENT_PROCESSED ||STRING ||1 ||E,N,Y ||Y
|-
|EVENT_SOURCE_TYPE ||STRING ||4 ||New Value ||Y
|-
|EVENT_SOURCE_NAME ||STRING ||10 || ||Y
|-
|EVENT_DATE ||DATETIME || || ||Y
|-
|EVENT_TYPE ||STRING ||3 || ||Y
|-
|EVENT_ACTION ||STRING ||1 ||A,C,D ||Y
|-
|TRIP_IDENTIFIER ||STRING ||1 ||O,T ||Y
|-
|TRIP_TRANSACTION_DATE ||DATETIME || || ||
|-
|TRIP_ID ||STRING ||12 || ||
|-
|STOP_IDENTIFIER ||STRING ||1 ||O,S ||Y
|-
|STOP_ID ||STRING ||51 || ||
|-
|STOP_SEQ ||INTEGER ||6 || ||
|-
|ORDER_TRANSACTION_DATE ||DATETIME || || ||Y
|-
|ORDER_TYPE ||STRING ||1 || ||
|-
|WMS_WAREHOUSE ||STRING ||3 || ||
|-
|WMS_OWNER ||STRING ||12 || ||Y
|-
|SO_REF ||STRING ||20 || ||Y
|-
|TMS_REF ||STRING ||20 || ||
|-
|PO_REF ||STRING ||20 || ||
|-
|BOOK_REF ||STRING ||20 || ||
|-
|BOOK_DATE ||DATETIME || || ||
|-
|SPECIAL_INSTR ||STRING ||2000 || ||
|-
|ORDER_COMMENTS ||STRING ||2000 || ||
|-
|EARLY_AVAIL_DATE ||DATETIME || || ||Y
|-
|LATE_AVAIL_DATE ||DATETIME || || ||Y
|-
|EARLY_DEL_DATE ||DATETIME || || ||Y
|-
|LATE_DEL_DATE ||DATETIME || || ||Y
|-
|TMS_GROUP_NAME ||STRING ||12 || ||
|-
|TMS_DELIVERY_TYPE ||STRING ||35 || ||
|-
|TMS_COST_CENTRE ||STRING ||12 || ||Y
|-
|HAULIER ||STRING ||12 || ||
|-
|TRANSPORT_MODE ||STRING ||30 || ||
|-
|ADDRESS_TYPE ||STRING ||3 || ||Y
|-
|ADDRESS_ID ||STRING ||25 || ||Y
|-
|ADDRESS_NAME ||STRING ||50 || ||
|-
|ADDRESS_LINE1 ||STRING ||50 || ||
|-
|ADDRESS_LINE2 ||STRING ||50 || ||
|-
|ADDRESS_LINE3 ||STRING ||50 || ||
|-
|ADDRESS_TOWN ||STRING ||50 || ||
|-
|ADDRESS_COUNTY ||STRING ||50 || ||
|-
|ADDRESS_COUNTRY_CODE ||STRING ||3 || ||
|-
|ADDRESS_POSTCODE ||STRING ||9 || ||
|-
|ADDRESS_LOC_TYPE ||STRING ||12 || ||
|-
|ADDRESS_CUST_GROUP ||STRING ||12 || ||
|-
|ADDRESS_CONTACT_TYPE ||STRING ||1 ||L,O ||
|-
|ADDRESS_CONTACT_FORENAME ||STRING ||50 || ||
|-
|ADDRESS_CONTACT_SURNAME ||STRING ||50 || ||
|-
|ADDRESS_CONTACT_NUMBER ||STRING ||50 || ||
|-
|ADDRESS_EMAIL ||STRING ||100 || ||
|-
|ADDRESS_CONTACT_JOB ||STRING ||50 || ||
|-
|CUSTOMER_ID ||STRING ||12 || ||
|-
|CUSTOMER_NAME ||STRING ||50 || ||
|-
|SUB_REF_IDENTIFIER ||STRING ||50 || ||Y
|-
|SUB_REFERENCE ||STRING ||512 || ||Y
|-
|DETAIL_TYPE ||STRING ||1 ||D,S ||Y
|-
|DETAIL_ID ||STRING ||30 || ||
|-
|PRODUCT_TYPE ||STRING ||12 || ||
|-
|PRODUCT_TYPE_DESC ||STRING ||50 || ||Y
|-
|DU_TYPE ||STRING ||12 || ||
|-
|ITEM_IDENTIFIER ||STRING ||20 || ||Y
|-
|ITEM_DESCRIPTION ||STRING ||122 || ||
|-
|PALLET_ID ||STRING ||100 || ||
|-
|ITEM_AKA_CODE ||STRING ||30 || ||
|-
|ITEM_FACTOR ||STRING ||12 || ||
|-
|LIFTS ||DECIMAL ||8,2 || ||
|-
|RPE_QTY ||DECIMAL ||10,2 || ||
|-
|WEIGHT ||DECIMAL ||10,2 || ||
|-
|VOLUME ||DECIMAL ||15,5 || ||
|-
|ORDERED ||DECIMAL ||28,4 || ||
|-
|TO_DELIVER ||DECIMAL ||28,4 || ||
|-
|DELIVERED ||DECIMAL ||28,4 || ||
|-
|PLANNED_CASES ||INTEGER ||8 || ||
|-
|LENGTH ||DECIMAL ||10,2 || ||
|-
|WIDTH ||DECIMAL ||10,2 || ||
|-
|HEIGHT ||DECIMAL ||10,2 || ||
|-
|COMMODITY_ID ||STRING ||256 || ||
|-
|CLASS_ID ||STRING ||256 || ||
|-
|UN_NUMBER ||STRING ||50 || ||Y
|-
|HAZARDOUS_QTY ||DECIMAL ||28,4 || ||Y
|-
|HAZARDOUS ||STRING ||1 ||N,Y ||Y
|-
|HAZARDOUS_DESCRIPTION ||STRING ||40 || ||Y
|}

*The mandatory flag for CTMS is only valid if the optional section has been provided in the file.

Note that an item quantity must be provided as 'ORDERED' or 'TO_DELIVER' depending which item is being used (as set by an EDI parameter).

=== Event Header <EVENT_HEADER> ===
<EVENT_HEADER>
<EVENT_PROCESSED>N</EVENT_PROCESSED>
<EVENT_SOURCE_TYPE>SAGE</EVENT_SOURCE_TYPE>
<EVENT_SOURCE_NAME>SAGE</EVENT_SOURCE_NAME>
<EVENT_DATE>2015-05-31T12:52:13</EVENT_DATE>
<EVENT_TYPE>ORD</EVENT_TYPE>
<EVENT_ACTION>C</EVENT_ACTION>
</EVENT_HEADER>

The header section describes the fact that an event has occurred. Each event must generally create a new file and this complex type element must not repeat within the file.

Each of the simple type elements outlined above is mandatorily required.

The <EVENT_PROCESSED> is expected to have a value of 'N'.

The <EVENT_SOURCE_TYPE> must be setup as a recognised source system within CTMS, within the [[System Configuration]] screen, [[System Configuration#Sources|Sources]] tab.

Although a number of <EVENT_TYPE> values can be received it is the 'ORD' event type which represents a transport order to be created or amended in CTMS, the <EVENT_ACTION> value of 'C' (for 'C'reate) will ensure a new order is generated, an event action value of 'A' (for 'A'mend) will update an order, and an event action value of 'D' (for 'D'elete) will delete an order.

Validation will exist to check that the transport order can be created, amended or deleted as directed.

The <EVENT_DATE> simple element must be in the format 'YYYY-MM-DDTHH:MI:SS'

=== Event Detail <EVENT_DETAIL> ===
<EVENT_DETAIL>
<TRIP_HEADER>
<STOPS>
<STOP>
<STOP_HEADER>
<ORDERS>
<ORDER>
<ORDER_HEADER>
<ORDER_DETAILS>
<ORDER_HAZARDOUS_DETAILS>
</ORDER>

The event detail section consists of complex type elements representing the 'Trip' - a CTMS planned transport movement representing a vehicle with one or more transport orders to one or more location.

The trip can have several 'stops' (a geographical location visited) against which one or more 'orders' can be handled for loading or unloading the vehicle at each stop.

Therefore, the <STOPS> and <ORDERS> may contain multiple stops and transport orders that exist on the trip.

=== Trip Header <TRIP_HEADER> ===
<TRIP_HEADER>
<TRIP_IDENTIFIER>O</TRIP_IDENTIFIER>
</TRIP_HEADER>

The 'ORD' event type does not require trip header information, although this complex type is mandatory in the file, it is exempted by denoting the <TRIP_IDENTIFIER> with 'O' to represent that the file contains order data only.

The order data received is denoted as an 'unplanned' order, that is it has not been built into a vehicle movement and routed through one or more load and unload activities. This planning activity is handled within CTMS.

=== Stops <STOPS> ===
<STOPS>
<STOP>
<STOP_HEADER>
<STOP_IDENTIFIER>O</STOP_IDENTIFIER>
</STOP_HEADER>

The ORD event type does not require any trip stop information and although the complex type is mandatory it is exempted by denoting the <STOP_IDENTIFIER> with 'O' to indicate that the file contains order data only.

=== Orders <ORDERS> ===
<ORDER>
<ORDER_HEADER> ... </ORDER_HEADER> [1]
<ORDER_SUB_REFS> ... </ORDER_SUB_REFS> [0..1]
<ORDER_DETAILS> ... </ORDER_DETAILS> [0..1]
<ORDER_HAZARDOUS_DETAILS> ... </ORDER_HAZARDOUS_DETAILS> [0..1]
</ORDER>
The orders complex type contains the core information that constitutes a transport order request in CTMS, that is, a unique instruction to collect and deliver a number of goods items of a particular type between two points at requested times.

The <ORDER> element can repeat to represent multiple orders within the same file; however it is recommended best practice when using the ORD event type to receive one per individual XML file.

The structure is made up of complex elements representing the higher level order header information which is none repeating and the lower level order details complex type element which may repeat.

The <ORDER_HEADER> complex type is mandatory and must occur once and only once.

The <ORDER_HEADER> complex type is optional.

The <ORDER_DETAILS> complex type is mandatory for transport orders and can repeat but must occur at least once.

The <ORDER_HAZARDOUS_DETAILS> complex type is optional.

=== Order Header <ORDER_HEADER> ===
<ORDER_HEADER>

<ORDER_HEADER>
<ORDER_TRANSACTION_DATE> ... </ORDER_TRANSACTION_DATE> [1]
<ORDER_TYPE> ... </ORDER_TYPE> [0..1]
<WMS_WAREHOUSE> ... </WMS_WAREHOUSE> [0..1]
<WMS_OWNER> ... </WMS_OWNER> [0..1]
<SO_REF> ... </SO_REF> [0..1]
<TMS_REF> ... </TMS_REF> [0..1]
<PO_REF> ... </PO_REF> [0..1]
<BOOK_REF> ... </BOOK_REF> [0..1]
<BOOK_DATE> ... </BOOK_DATE> [0..1]
<SPECIAL_INSTR> ... </SPECIAL_INSTR> [0..1]
<ORDER_COMMENTS> ... </ORDER_COMMENTS> [0..1]
<ORDER_HEADER_TMS> ... </ORDER_HEADER_TMS> [0..1]
<ORDER_HEADER_ADDRESSES> ... </ORDER_HEADER_ADDRESSES> [0..1]
<CUSTOMER_ID> ... </CUSTOMER_ID> [0..1]
<CUSTOMER_NAME> ... </CUSTOMER_NAME> [0..1]
<ORDER_STATUS> ... </ORDER_STATUS> [0..1]
</ORDER_HEADER>

The order header structure represents the high level simple single attributes of the order which exist in isolation, such as references and who the transport order is being conducted on behalf of.

The <ORDER_TRANSACTION_DATE> simple element is mandatory and must be in the format 'YYYY-MM-DDTHH:MI:SS'

The <ORDER_TYPE> simple type element is mandatory and must be received with a value of 'O'.

The <WMS_OWNER> simple type element indicates the customer and must match the customer IDs setup on CTMS, this is a mandatory field.

The <SPECIAL_INSTR> simple type element captures any additional information that is presented to the driver on his hand held delivery device at that may be relevant to the transport planning.

=== Order Header TMS <ORDER_HEADER_TMS> ===
<ORDER_HEADER_TMS>
<EARLY_AVAIL_DATE>2015-05-24T17:00:00</EARLY_AVAIL_DATE>
<TMS_GROUP_NAME>OBS</TMS_GROUP_NAME>
<TMS_DELIVERY_TYPE>Standard</TMS_DELIVERY_TYPE>
<TMS_COST_CENTRE>OBS</TMS_COST_CENTRE>
<TRANSPORT_MODE>ROAD</TRANSPORT_MODE>

The order header TMS section contains additional information relevant to the order and is simply an extension to the main order header complex type.

Most of the simple type elements in the section are optional.

The <TMS_DELIVERY_TYPE> is used to receive the service level: this value must be populated and is validated against CTMS master data

The <EARLY_AVAIL_DATE> simple type element is mandatory and will be used to calculate forward the collection/loading date/time window and also the approximate delivery date/time window. It must be in the format 'YYYY-MM-DDTHH:MI:SS'.

The other 3 dates for the order may be omitted because they can be calculated from the early available date that is provided and the delivery type (i.e. service level) of the order, however, the configuration in CTMS (TBC) will determine the required level of data.

All elements in this section are validated against CTMS master data and therefore must match CTMS configuration.

The accepted values in the <TRANSPORT_MODE> simple type element are:
* AIR
* ROAD

This will be validated and the order file rejected if the value does not match.

The <TOTAL_PRICE> element is optional and defines the TOTAL price of the order. If provided and populated, the value must be a valid decimal value, or an error will be raised. If not provided or null, the value will be set to 0.

=== Order Header Addresses <ORDER_HEADER_ADDRESSES> ===
<ORDER_HEADER_ADDRESSES>
<ORDER_HEADER_ADDRESS>
<ORDER_HEADER_ADDRESS>
<OH_ADDRESS_CONTACTS>

An <ORDER_HEADER_ADDRESSES> complex type element must always exist once per order.

It must include two instances of the <ORDER_HEADER_ADDRESS> complex type element, one for the loading/pickup location (i.e. 'DEP' address type) and one for the unloading/drop-off location (i.e. 'DEL' address type).

=== Order Header Addresses <ORDER_HEADER_ADDRESS> ===
<ORDER_HEADER_ADDRESS>
<ADDRESS_TYPE>DEP</ADDRESS_TYPE>
<ADDRESS_ID>OBS</ADDRESS_ID>
<ADDRESS_NAME>OBS Logistics</ADDRESS_NAME>
<ADDRESS_LINE1>Southern Gateway</ADDRESS_LINE1>
<ADDRESS_LINE2>Speke Boulevard</ADDRESS_LINE2>
<ADDRESS_LINE3></ADDRESS_LINE3>
<ADDRESS_TOWN>Liverpool</ADDRESS_TOWN>
<ADDRESS_COUNTY>Merseyside</ADDRESS_COUNTY>
<ADDRESS_COUNTRY_CODE>GB</ADDRESS_COUNTRY_CODE>
<ADDRESS_POSTCODE>L24 9HZ</ADDRESS_POSTCODE>
<ADDRESS_CUST_GROUP>OBS</ADDRESS_CUST_GROUP>
<OH_ADDRESS_CONTACTS>

The <ORDER_HEADER_ADDRESS> complex type element includes the address attributes for either the initial point of collection/loading or the final point of delivery/unloading.

The <ADDRESS_TYPE> simple type element is mandatory and must be either:
* 'DEP' - Indicates that the address represents the initial 'DEP'arture location of the order.
* 'DEL' - Indicates that the address represents the final 'DEL'ivery location of the order.

The <ADDRESS_TOWN> item and <ADDRESS_POSTCODE> elements will not be validated and will be accepted regardless of data content.

The <ADDRESS_ID> item is mandatory and can be sent as a unique account identifier for the sender/recipient or it can be sent with the word 'UNKNOWN' which will allow CTMS to generate this unique address identifier where necessary.

The system will initially cross check the received Address Name and Address Postcode in the order file to see if any locations exist for that address name and postcode (to narrow down the number of records to validate), if so it will identify against all other address attributes (Address lines, town/suburb, county/state, country code) to see if there is an existing EXACT match.

If an existing EXACT address match is found the existing CTMS location code will be used against the received order - as the address detail matches all attributes. If any difference is found a new location is generated with the data received, generating a new location ID in the following format:

* Characters 1 to 8: Characters 1 to 8 from <ADDRESS_NAME>
* Character 9: '-'
* Characters 10 to 12: Sequence number 001 to 999

The location ID generated will be a maximum of 12 characters, for example:

<ADDRESS_ID>UNKNOWN<ADDRESS_ID>
<ADDRESS_NAME>OBS Logistics</ADDRESS_NAME>
<ADDRESS_POSTCODE>L24 9HZ</ADDRESS_POSTCODE>

Would create location code 'OBS Logi-001'.

Also note that new addresses for existing locations can be provided for each order and new locations can be created for the specific address that may be provided.

Once a location is created it will not be updated via the order upload process, any amendments can be carried out manually or via the import of a 'CSV' file.

New locations will only be created for the address details provided.

=== Order Header Address Contact <OH_ADDRESS_CONTACT> ===
<OH_ADDRESS_CONTACT>
<ADDRESS_CONTACT_TYPE>O</ADDRESS_CONTACT_TYPE>
<ADDRESS_CONTACT_FORENAME>Yard Manager</ADDRESS_CONTACT_FORENAME>
<ADDRESS_CONTACT_SURNAME></ADDRESS_CONTACT_SURNAME>
<ADDRESS_CONTACT_NUMBER>0151 123 5678</ADDRESS_CONTACT_NUMBER>
<ADDRESS_EMAIL>yardmanager@obs.com</ADDRESS_EMAIL>

For each address an optional <OH_ADDRESS_CONTACT> complex type element can be received. This element must only occur once for within a <OH_ADDRESS_CONTACT>.

The <ADDRESS_CONTACT_TYPE> simple type element is mandatory where the <OH_ADDRESS_CONTACT> is used and indicates if the contact information is to be permanently associated to the address master data (value 'L') or whether it is only related to that particular address for the instance of that particular order (value 'O'). For this implementation 'O'rder type contacts should always be received.

If there is no contact information for the loading location then this element is not required for the "DEP" address type.

The other simple type elements are optional.

=== Order Sub-references <ORDER_SUB_REFS> ===
<ORDER_DETAILS>
<ORDER_SUB_REFS>
<ORDER_SUB_REF> <ORDER_SUB_REF>
<SUB_REF_IDENTIFIER> ... </SUB_REF_IDENTIFIER> [1]
<SUB_REF_IDENTIFIER> ... </SUB_REFERENCE> [1]
</ORDER_SUB_REF>
</ORDER_SUB_REFS>
<ORDER_DETAIL>
This <ORDER_SUB_REFS> section is optional, and allows you to store additional references for an order.

The section must include at least one instance of the <ORDER_SUB_REF> complex type element.

The <SUB_REF_IDENTIFIER> simple type must match up to a configured order sub-reference type. These are maintained by your system administrator in the CTMS [[Imports]] screen, on the [[Imports#Decodes|Decodes]] tab, type "XML_REFERENCE". Include the CODE here, not the NAME.

The <SUB_REF_IDENTIFIER> simple type is the value you want to store against that reference. The value can be anything at all, but to 512 characters long. These values are not validated.

You can add as many order sub references as you need for the order.

{{Note|
* If system parameter USE_XML_ORDER_SUB_REFS is set to "Y", sub references will be automatically generated from lane comments that begin with ORDER_REFS:", followed by a comma-delimited list of sub reference names and values. Otherwise this section will contain the order sub references for this order.
* A sub reference of TRIP_TYPE may be automatically generated based on EDI parameter INC_TRIP_TYPE being set. In this case, the value may be set to
** COL - if the from location is the load location of the trip stop and the load location type is not RDC
** TRUNK - if the from location is the load location and the order to location is not the unload location
** XDOCK_DEL - if the order to location is equal to the unload location, and there are onward trips.
** DIRECT_DEL - if the order to location is equal to the unload location, and there are no onward trips.
* If the sub-ref name DELIVERY_METHOD is present, the value will be translated for the carrier.
}}Several static sub-references are supported.

The following will automatically store data as order information, for contact purposes:

* SMS_ADDRESS_1
* SMS_ADDRESS_2
* SMS_ADDRESS_3
* SMS_ADDRESS_4
* EMAIL_ADDRESS

Depending on which values you provide here, the order will be stamped with contact preferences:

* E - Email only.
* S - SMS Only
* B - Both

{{Note}}SMS sending from CTMS is supported at additional transaction cost per message.

The reference ORDER_WMS_STATUS may be used to update a source system status against the trip. Values are:

* OPEN STAGED
* IN PROGRESS STAGED
* CLOSED STAGED
* OPEN
* IN PROGRESS
* CLOSED

=== Order Detail <ORDER_DETAIL> ===
<ORDER_DETAIL>
<DETAIL_TYPE>S</DETAIL_TYPE>
<PRODUCT_TYPE_DESC>CANTEEN</PRODUCT_TYPE_DESC>
<DU_TYPE>20x9</DU_TYPE>
<ITEM_IDENTIFIER>ABC004783</ITEM_IDENTIFIER>
<ITEM_DESCRIPTION>CARTON</ITEM_DESCRIPTION>
<ITEM_AKA_CODE>10*20*30</ITEM_AKA_CODE>
<LIFTS>1</LIFTS>
<WEIGHT>5.37</WEIGHT>
<ORDERED>1</ORDERED>
<TO_DELIVER>1</TO_DELIVER>
<LENGTH>10</LENGTH>
<WIDTH>20</WIDTH>
<HEIGHT>30</HEIGHT>
<COMMODITY_ID>DG</COMMODITY_ID>
<CLASS_ID>2.1</CLASS_ID>
</ORDER_DETAIL>

The <ORDER_DETAIL> complex element is mandatory and can repeat but must occur at least once to form a valid CTMS order.

The order details will be used to generate both the individual dispatch box/carton detail (per unique barcode) and also the higher level summary order detail line level.

The <DETAIL_TYPE> simple element is mandatory and must be received as either:
* 'D' - Represents a CTMS order detail line - summary level of the total of unique package types.
* 'S' - Represents a CTMS order detail item - the lowest level entry for each individual carton/box.

Note that the DU types (i.e. for the order lines) and its items, just the DU types (if items are not being recorded) or just the items may be provided.

If just items are provided then the DU types and thus the order lines may be generated automatically for the order based on the types of items that have been provided.

The <PRODUCT_TYPE_DESC> simple element is mandatory and will be validated against CTMS master data to ensure it is a recognised value. An unrecognised or blank value will cause the order upload to fail with applicable validation message recorded.

The <DU_TYPE> simple element is optional and will be validated against CTMS master data to ensure it is a recognised value. An unrecognised will cause the order upload to fail with applicable validation message recorded.

The <ITEM_IDENTIFIER> simple element is mandatory and will not be validated although it must be a maximum of 15 alphanumeric characters.

The <ITEM_DESCRIPTION> and <ITEM_AKA_CODE simple type elements are an optional freetext tags and can be used as required.

One of the <ORDERED> and <TO_DELIVER> simple type elements will be mandatory and must be received with a numeric integer value. This represents the number of items reflected by the <ORDER_DETAIL> segment received

As this is at individual carton/box level then this is expected to always be 1 for this implementation.

The <WEIGHT>, <HEIGHT>, <WIDTH>, <LENGTH> simple type elements are optional.

{{Note|* The weight provided is a TOTAL weight of the item or line, not a UNIT weight.
* The height, width and length will be used by CTMS to calculate the carton/box level volume for each order item as per existing standard processing logic.}}

The <COMMODITY_ID> simple type element is optional and will be validated against CTMS master data to ensure it is a recognised value. An unrecognised value will cause the order upload to fail with applicable validation message recorded.

The <CLASS_ID> simple type element is optional but must be received when a <COMMODITY_ID> element is provided which has a 'Dangerous' flag setting of 'Y' (in CTMS master data setup). The value will be validated against CTMS master data to ensure it is a recognised value. An unrecognised will cause the order upload to fail with applicable validation message recorded.

The <ITEM_PRICE> element is optional and defines the TOTAL price of the item. This applies only to Item detail type lines. If provided and populated, the value must be a valid decimal value, or an error will be raised. If not provided or null, the value will be set to 0.

=== Order Hazardous Details ===
<ORDER_HAZARDOUS_DETAILS>
<ORDER_HAZARDOUS_DETAIL>

The <ORDER_HAZARDOUS_DETAILS> complex type element is optional and can be provided if required.

If this element is used then one or more <ORDER_HAZARDOUS_DETAIL> complex type elements is mandatorily required.

=== Order Hazardous Detail ===
<ORDER_HAZARDOUS_DETAIL>
<UN_NUMBER>1089</UN_NUMBER>
<HAZARDOUS_QTY>1</HAZARDOUS_QTY>
<HAZARDOUS>Y</HAZARDOUS>
<HAZARDOUS_DESCRIPTION>CARBONYL SULFIDE</HAZARDOUS_DESCRIPTION>
</ORDER_HAZARDOUS_DETAIL>

The <ORDER_HAZARDOUS_DETAIL> complex type element and all its simple type elements are mandatory. The elements are not validated against CTMS master data and will be stored as received.

= XML Outbound Order File Structure =
== EDI Maintenance ==
The XML files from CTMS will be generated and placed into a directory structure and processed as may be specified in the 'EDI Maintenance' screen.

Multiple EDI flows may be active to process XML files at different stages of processing.

There are various EDI parameters that can be set to provide different levels of validation to generate the files.

== TripOrder File ==
<OBS_XML>
<EVENT>
<EVENT_HEADER>
<EVENT_DETAIL>

The same XSD file format is used for files from CTMS as per files into CTMS.

These files may contain more data in each section than are required in the inbound order files.

For example, an outbound file may contain data about the trip, its stops, each order on each stop and the DU types and/or items on each order.

Export depends on the events that are being exported, controlled by EDI Parameters on the API EDI process:
* API_ARR
* API_COL
* API_DEL
* API_DEP
* API_ORD
* API_TRP

Additional EDI parameters are also present (described in detail in the following sections):
*INCLUDE_CDATA_TAG - affects variable text data entry from the execution level - should it be wrapped to prevent interface errors?
* SEND_AND_FORGET - affects the basic interface - should the message be sent with no expectation of explicit acknowledgement back from the destination?
*PRINT_STOP_PID
*PRINT_ROUTE_CODE
*INCLUDE_ORDER_STATUS
*SEND_DEL_TYPE_CODE
*EXPORT_SERVICES
*INC_TRIP_TYPE
*INC_TRIP_ACTION
*INC_PACKED_TO_DEL
*INCLUDE_SAP_LINE_NOS
*INCLUDE_REASON_CODES
*INCLUDE_NON_CON_CODES
* INCLUDE_TRACK_REF
*INCLUDE_ITEM_DELIVER
*INCLUDE_REASON_TYPE

Export may also include debrief-level information, depending on the type of event, and where the order is up to.

The Export will be of Trip Type if related to a trip, and Order type (similar to the above) for Order-type events.

Trip type events:
*TRP - any changes to or creation of a trip.
* ARR - Arrival at any stop.
*DEP - departure at any stop.

Order type events:
*ORD - any changes to or creation of an order.
*CAN - if an order is cancelled.
*COL - if an order is collected.
*DEL - if an order is delivered.

In general, trip-type events include everything that an Order-type event would include, but with the following additions:
*TRIP_DETAIL
*STOP_DETAIL
*STOP_SIGNATURE (if LOTS_INC_STOP_SIGNATURE = "Y")
*ORDER_HEADER_TMS

As an indication of what may change, please see the below sections.

===TRIP_DETAIL===
<pre>
<HAULIER> ... </HAULIER> [0..1]
<HAULIER_NAME> ... </HAULIER_NAME> [0..1]
<HAULIER_TYPE> ... </HAULIER_TYPE> [0..1]
<TRACKING> ... </TRACKING> [1]
<TRIP_SCHEDULE> ... </TRIP_SCHEDULE> [0..1]
<DRIVER> ... </DRIVER> [0..1]
<DRIVER_NAME> ... </DRIVER_NAME> [0..1]
<DRIVER_CONTACT> ... </DRIVER_CONTACT> [0..1]
<TRACTOR> ... </TRACTOR> [0..1]
<TRACTOR_LAT> ... </TRACTOR_LAT> [0..1]
<TRACTOR_LON> ... </TRACTOR_LON> [0..1]
<COST_CENTRE> ... </COST_CENTRE> [0..1]
<TRIP_STATUS> ... </TRIP_STATUS> [0..1]
<TRIP_REF> ... </TRIP_REF> [0..1]
<TRIP_TRAILER_ID> ... </TRIP_TRAILER_ID> [0..1]
<TRIP_TRAILER_TYPE> ... </TRIP_TRAILER_TYPE> [0..1]
<TRIP_DISTANCE> ... </TRIP_DISTANCE> [0..1]
<FUEL_DRAWN> ... </FUEL_DRAWN> [0..1]
<OWNING_DEPOT> ... </OWNING_DEPOT> [0..1]
<CONTAINER_NO> ... </CONTAINER_NO> [0..1]
<SEAL_NO> ... </SEAL_NO> [0..1]
<EFX_NUMBER> ... </EFX_NUMBER> [0..1]
<START_ODOMETER> ... </START_ODOMETER> [0..1]
<END_ODOMETER> ... </END_ODOMETER> [0..1]
<ACTUAL_TRIP_DISTANCE> ... </ACTUAL_TRIP_DISTANCE> [0..1]
<ROUTE_CODE> ... </ROUTE_CODE> [0..1]
<COST_PER_TONNE> ... </COST_PER_TONNE> [0..1]
<COST> ... </COST> [0..1]
<COST_REASON> ... </COST_REASON> [0..1]
<AUDIT_ID> ... </AUDIT_ID> [0..1]
<TRIP_SUB_REFS> ... </TRIP_SUB_REFS> [0..1]
</pre>

{{Note|
* Carrier will be modified if the carrier type is 3PL. This will be exported in the HAULIER tag.
* TRACKING tag will only be populated from trips that are tracked through Microlise.
* The information sent to MICROLISE is extremely limited in this section.
* ROUTE_CODE will only be populated if the EDI parameter PRINT_ROUTE_CODE is populated or the TRIP_ORDER_XSD_VERS system parameter is "2.5". If the system parameter INCL_ROUTE_CODE is set, then this will be instead populated with the Baxter route code.
* AUDIT_ID is a unique ID appended to the message for external tracking purposes.
}}

===TRIP_SUB_REF===
<pre>
<TRIP_SUB_REF>
<SUB_REF_IDENTIFIER> ... </SUB_REF_IDENTIFIER> [1]
<SUB_REFERENCE> ... </SUB_REFERENCE> [1]
</TRIP_SUB_REF>
</pre>

{{Note|
* If system parameter INC_TRIP_ACTION is "Y", a trip sub reference will be generated based on the action of the event.
}}

===STOP_DETAIL===
<pre>
<STOP_REF> ... </STOP_REF> [0..1]
<STOP_TYPE> ... </STOP_TYPE> [0..1]
<STOP_LOCATION_TYPE> ... </STOP_LOCATION_TYPE> [0..1]
<STOP_LOCATION_ID> ... </STOP_LOCATION_ID> [0..1]
<STOP_LOCATION_NAME> ... </STOP_LOCATION_NAME> [0..1]
<STOP_ADDR_LINE1> ... </STOP_ADDR_LINE1> [0..1]
<STOP_ADDR_LINE2> ... </STOP_ADDR_LINE2> [0..1]
<STOP_ADDR_LINE3> ... </STOP_ADDR_LINE3> [0..1]
<STOP_TOWN> ... </STOP_TOWN> [0..1]
<STOP_COUNTY> ... </STOP_COUNTY> [0..1]
<STOP_COUNTRY_CODE> ... </STOP_COUNTRY_CODE> [0..1]
<STOP_POSTCODE> ... </STOP_POSTCODE> [0..1]
<STOP_CONTACT_NAME> ... </STOP_CONTACT_NAME> [0..1]
<STOP_CONTACT_PHONE> ... </STOP_CONTACT_PHONE> [0..1]
<STOP_BREAK_DURATION> ... </STOP_BREAK_DURATION> [0..1]
<STOP_PREV_DIST> ... </STOP_PREV_DIST> [0..1]
<STOP_ACTUAL_PREV_DIST> ... </STOP_ACTUAL_PREV_DIST> [0..1]
<STOP_TRAILER_ID> ... </STOP_TRAILER_ID> [0..1]
<STOP_LAT> ... </STOP_LAT> [0..1]
<STOP_LON> ... </STOP_LON> [0..1]
<STOP_PLANNED_ARRIVAL_DATE> ... </STOP_PLANNED_ARRIVAL_DATE> [0..1]
<STOP_PLANNED_DEPARTURE_DATE> ... </STOP_PLANNED_DEPARTURE_DATE> [0..1]
<STOP_ETA_DATE> ... </STOP_ETA_DATE> [0..1]
<STOP_ETA_AT_DATE> ... </STOP_ETA_AT_DATE> [0..1]
<STOP_EARLIEST_BOOKED_DATE> ... </STOP_EARLIEST_BOOKED_DATE> [0..1]
<STOP_ACTUAL_ARRIVAL_DATE> ... </STOP_ACTUAL_ARRIVAL_DATE> [0..1]
<STOP_ACTUAL_DEPARTURE_DATE> ... </STOP_ACTUAL_DEPARTURE_DATE> [0..1]
<STOP_ODO_READING> ... </STOP_ODO_READING> [0..1]
<STOP_FUEL> ... </STOP_FUEL> [0..1]
<STOP_EMAIL> ... </STOP_EMAIL> [0..1]
<STOP_BARCODE> ... </STOP_BARCODE> [0..1]
<STOP_PID> ... </STOP_PID> [0..1]
<STOP_COUNTRY_NAME> ... </STOP_COUNTRY_NAME> [0..1]
<WAREHOUSE_LOAD> ... </WAREHOUSE_LOAD> [0..1]
</pre>

{{Note|
* Dates are in XML DateTime format.
* ETA and ACTUAL Dates will be populated from execution-based systems.
* STOP_PID will only be populated for LOTS and CIM flows in one format, or if EDI parameter PRINT_STOP_PID is set to "Y" in a different format. This second format should not be enabled for LOTS interfaces.
}}

=== STOP_SIGNATURE===
This section will only be generated if system parameter LOTS_INC_STOP_SIGNATURE is set to "Y".

<pre>
<STOP_SIGNATURE>
<SIGNATURE> ... </SIGNATURE> [0..1]
<SIGNED_BY> ... </SIGNED_BY> [0..1]
</STOP_SIGNATURE>
</pre>

===ORDER_HEADER===
<pre>
<ORDER_TRANSACTION_DATE> ... </ORDER_TRANSACTION_DATE> [1]
<ORDER_TYPE> ... </ORDER_TYPE> [0..1]
<WMS_WAREHOUSE> ... </WMS_WAREHOUSE> [0..1]
<WMS_OWNER> ... </WMS_OWNER> [0..1]
<SO_REF> ... </SO_REF> [0..1]
<ORIG_SO_REF> ... </ORIG_SO_REF> [0..1]
<TMS_REF> ... </TMS_REF> [0..1]
<PO_REF> ... </PO_REF> [0..1]
<BOOK_REF> ... </BOOK_REF> [0..1]
<BOOK_DATE> ... </BOOK_DATE> [0..1]
<SPECIAL_INSTR> ... </SPECIAL_INSTR> [0..1]
<ORDER_COMMENTS> ... </ORDER_COMMENTS> [0..1]
<ORDER_HEADER_TMS> ... </ORDER_HEADER_TMS> [0..1]
<ORDER_HEADER_ADDRESSES> ... </ORDER_HEADER_ADDRESSES> [0..1]
<ORDER_HEADER_CONFIRM> ... </ORDER_HEADER_CONFIRM> [0..1]
<CUSTOMER_ID> ... </CUSTOMER_ID> [0..1]
<CUSTOMER_NAME> ... </CUSTOMER_NAME> [0..1]
<ORDER_STATUS> ... </ORDER_STATUS> [0..1]
<DESTINATION_ORDER> ... </DESTINATION_ORDER> [0..1]
<DESTINATION_DRIVER> ... </DESTINATION_DRIVER> [0..1]
<DESTINATION_VEHICLE> ... </DESTINATION_VEHICLE> [0..1]
<ORDER_SERVICES> ... </ORDER_SERVICES> [0..1]
</pre>

{{Note|
* SO_REF will be populated with the External reference of the order. This may be modified to remove any rebooking suffix if system parameter ORD_RBO_PREFIX is set to "Y"
* ORDER_STATUS will only be included if the EDI parameter INCLUDE_ORDER_STATUS is set to "Y". Further, if system parameter INCLUDE_FAILED_ORDERS is set to "Y" and the order status is FAILED, this will be changed to CANCELLED instead.
* DESTINATION_ORDER, DESTINATION_DRIVER and DESTINATION_VEHICLE will only be present if order sub references exist of those names.
}}

===ORDER_HEADER_TMS ===
<pre>
<ORDER_HEADER_TMS>
<SHIPMENT_ID> ... </SHIPMENT_ID> [0..1]
<TMS_ORDER_SCHEDULE> ... </TMS_ORDER_SCHEDULE> [0..1]
<TMS_HAULAGE_ACTIVITY> ... </TMS_HAULAGE_ACTIVITY> [0..1]
<TMS_HAULAGE_TYPE> ... </TMS_HAULAGE_TYPE> [0..1]
<EARLY_AVAIL_DATE> ... </EARLY_AVAIL_DATE> [1]
<LATE_AVAIL_DATE> ... </LATE_AVAIL_DATE> [1]
<EARLY_DEL_DATE> ... </EARLY_DEL_DATE> [1]
<LATE_DEL_DATE> ... </LATE_DEL_DATE> [1]
<TMS_GROUP_NAME> ... </TMS_GROUP_NAME> [0..1]
<TMS_DELIVERY_TYPE> ... </TMS_DELIVERY_TYPE> [0..1]
<TMS_COST_CENTRE> ... </TMS_COST_CENTRE> [0..1]
<SD_TEMP_COMBO> ... </SD_TEMP_COMBO> [0..1]
<SD_POD_BY> ... </SD_POD_BY> [0..1]
<KEY_CODE> ... </KEY_CODE> [0..1]
<REVENUE> ... </REVENUE> [0..1]
<COST> ... </COST> [0..1]
<COST_PER_TONNE> ... </COST_PER_TONNE> [0..1]
<HAULIER> ... </HAULIER> [0..1]
<TRAILER_TYPE> ... </TRAILER_TYPE> [0..1]
<ROUTE_CODE> ... </ROUTE_CODE> [0..1]
<EFX_NUMBER> ... </EFX_NUMBER> [0..1]
<TRANSPORT_MODE> ... </TRANSPORT_MODE> [0..1]
<TRANSPORT_STATUS> ... </TRANSPORT_STATUS> [0..1]
<RPE_QTY> ... </RPE_QTY> [0..1]
<ACTUAL_RPE_QTY> ... </ACTUAL_RPE_QTY> [0..1]
<WEIGHT> ... </WEIGHT> [0..1]
<ACTUAL_WEIGHT> ... </ACTUAL_WEIGHT> [0..1]
<VOLUME> ... </VOLUME> [0..1]
<ACTUAL_VOLUME> ... </ACTUAL_VOLUME> [0..1]
<FOOTPRINT> ... </FOOTPRINT> [0..1]
<ACTUAL_FOOTPRINT> ... </ACTUAL_FOOTPRINT> [0..1]
<TOTAL_PRICE> ... </TOTAL_PRICE> [0..1]
</ORDER_HEADER_TMS>
</pre>

{{Note|
* TMS_DELIVERY_TYPE is set to the full delivery type if the EDI parameter SEND_DEL_TYPE_CODE is set to "Y". Otherwise the short code associated to the delivery type is sent.
}}

===ORDER_SERVICES===
This section is only populated if the EDI parameter EXPORT_SERVICES is set to "Y", or if this is set to "C" and the event is "CAN" or "DEL".

<pre>
<ORDER_SERVICE>
<SERVICE_ID> ... </SERVICE_ID> [1]
<SERVICE_NAME> ... </SERVICE_NAME> [1]
<SERVICE_QTY> ... </SERVICE_QTY> [1]
<SERVICE_VALUE> ... </SERVICE_VALUE> [1]
</ORDER_SERVICE>
</pre>

=== ORDER_DETAIL===
The details sent in this section are subject to configuration:
* Order Lines are sent if LOTS_SEND_LINE_ITEMS = "Y", or the value is "N" and there are no order items.
* Order Items are sent if LOTS_SEND_LINE_ITEMS = "Y", or the value is "N" and there are order items.

<pre>
<ORDER_DETAIL>
<DETAIL_TYPE> ... </DETAIL_TYPE> [1]
<DETAIL_ID> ... </DETAIL_ID> [0..1]
<PRODUCT_TYPE> ... </PRODUCT_TYPE> [0..1]
<PRODUCT_TYPE_DESC> ... </PRODUCT_TYPE_DESC> [0..1]
<DU_TYPE> ... </DU_TYPE> [0..1]
<ITEM_IDENTIFIER> ... </ITEM_IDENTIFIER> [1]
<ITEM_DESCRIPTION> ... </ITEM_DESCRIPTION> [0..1]
<PALLET_ID> ... </PALLET_ID> [0..1]
<ITEM_AKA_CODE> ... </ITEM_AKA_CODE> [0..1]
<ITEM_FACTOR> ... </ITEM_FACTOR> [0..1]
<LIFTS> ... </LIFTS> [0..1]
<STACK> ... </STACK> [0..1]
<RPE_QTY> ... </RPE_QTY> [0..1]
<ACTUAL_RPE_QTY> ... </ACTUAL_RPE_QTY> [0..1]
<WEIGHT> ... </WEIGHT> [0..1]
<ACTUAL_WEIGHT> ... </ACTUAL_WEIGHT> [0..1]
<VOLUME> ... </VOLUME> [0..1]
<ACTUAL_VOLUME> ... </ACTUAL_VOLUME> [0..1]
<FOOTPRINT> ... </FOOTPRINT> [0..1]
<ACTUAL_FOOTPRINT> ... </ACTUAL_FOOTPRINT> [0..1]
<ORDERED> ... </ORDERED> [0..1]
<PACKED> ... </PACKED> [0..1]
<TO_DELIVER> ... </TO_DELIVER> [0..1]
<DELIVERED> ... </DELIVERED> [0..1]
<SAP_LINE_NO> ... </SAP_LINE_NO> [0..1]
<SHIPMENT_DETAIL> ... </SHIPMENT_DETAIL> [0..1]
<REASON_CODES> ... </REASON_CODES> [0..1]
<DIM_WEIGHT> ... </DIM_WEIGHT> [0..1]
<ACTUAL_DIM_WEIGHT> ... </ACTUAL_DIM_WEIGHT> [0..1]
<TRACKING_REFS> ... </TRACKING_REFS> [0..1]
<DU_DESCRIPTION> ... </DU_DESCRIPTION> [0..1]
<DU_CATEGORY> ... </DU_CATEGORY> [0..1]
<PLANNED_CASES> ... </PLANNED_CASES> [0..1]
<ACTUAL_CASES> ... </ACTUAL_CASES> [0..1]
<SCAN_TYPE> ... </SCAN_TYPE> [0..1]
<LENGTH> ... </LENGTH> [0..1]
<WIDTH> ... </WIDTH> [0..1]
<HEIGHT> ... </HEIGHT> [0..1]
<COMMODITY_ID> ... </COMMODITY_ID> [0..1]
<CLASS_ID> ... </CLASS_ID> [0..1]
<WMS_LOCATION> ... </WMS_LOCATION> [0..1]
<LONG_DESCRIPTION> ... </LONG_DESCRIPTION> [0..1]
<ORDER_DETAIL_TYRE> ... </ORDER_DETAIL_TYRE> [0..1]
<ITEM_PRICE> ... </ITEM_PRICE> [0..1]
</ORDER_DETAIL>
</pre>

{{Note|
* DETAIL_TYPE will be "D" if generated from Order Lines, and "S" if generated from Order Items.
* For D lines
** ITEM_IDENTIFIER will be the DU Type
** ITEM_DESCRIPTION will the DU Type description for "D" lines
** RPE_QTY will include Despatched and Packed REP if the EDI Parameter INC_PACKED_TO_DEL is set to "Y", other wise this will just be the Actual RPE and RPE qty.
** PACKED will be populated if the order has been packed.
** TO_DELIVER will be populated if the order has been collected.
** DELIVERED will be present and populated if the order has been delivered to its final destination.
** SAP_LINE_NO will only be present and populated if the EDI Parameter INCLUDE_SAP_LINE_NOS is "Y" and there is a SAP line number against the order line.
** REASON_CODES will be included if there are non-conformity reason codes against the order line for the API interface.
** REASON_CODES will be included for other flows if EDI Parameters INCLUDE_REASON_CODES and INCLUDE_NON_CON_CODES are set. {{Warning}} These should NOT be set against the API process.
** TRACKING_REFS will be included if the EDI Parameter INCLUDE_TRACK_REF is set to "Y".
* For S lines
** ITEM_IDENTIFIER will be the Item Identifier, unless the customer has specified that an alternative item identifier is used and one is provided against the item. If system parameter USE_PALLET_ID_XML is set to "Y", then the Pallet ID of the item record will be used instead.
** PALLET_ID will only be populated if system parameter SEND_PALLET_ID_XML is set to "Y".
** ORDERED will only be present and populated if the value is not null.
** TO_DELIVER will only be present and populated if the value is null i.e. the order item has been collected.
** DELIVERED will only be present and populated if the value is not null i.e. the order item has been delivered and EDI parameter INCLUDE_ITEM_DELIVER is set to "Y", or this is sent through the API.
** SAP_LINE_NO will only be present and populated if the EDI Parameter INCLUDE_SAP_LINE_NOS is "Y" and there is a SAP line number against the order line.
** REASON_CODES will be included if there are non-conformity reason codes against the order line for the API interface.
** REASON_CODES will be included for other flows if EDI Parameters INCLUDE_REASON_CODES and INCLUDE_NON_CON_CODES are set. {{Warning}} These should NOT be set against the API process.
}}

===TRACKING_REFS===
TRACKING_REFS will be included if the EDI Parameter INCLUDE_TRACK_REF is set to "Y".

<pre>
<TRACKING_REF>
<UNIT_TRACKING_REF> ... </UNIT_TRACKING_REF> [1]
<UNIT_TRACKING_NO> ... </UNIT_TRACKING_NO> [1]
</TRACKING_REF>
</pre>

===ORDER_DETAIL_TYRE===
For TYRE-based systems

<pre>
<ORDER_DETAIL_TYRE>
<WPX_PRODUCT_ID> ... </WPX_PRODUCT_ID> [1]
<POSITION> ... </POSITION> [1]
<LOCATION> ... </LOCATION> [1]
<PRICE> ... </PRICE> [1]
<CUSTOMER_VEHICLE> ... </CUSTOMER_VEHICLE> [1]
<AUTHORITY_CODE> ... </AUTHORITY_CODE> [1]
<WORK_TYPE> ... </WORK_TYPE> [1]
<PRESSURE> ... </PRESSURE> [1]
<TREAD_DEPTH> ... </TREAD_DEPTH> [1]
<CASING> ... </CASING> [1]
<CASING_DESTINATION> ... </CASING_DESTINATION> [1]
<NEW_REMOULD> ... </NEW_REMOULD> [1]
<REGROOVED> ... </REGROOVED> [1]
<TYRE_SERIAL_NO> ... </TYRE_SERIAL_NO> [1]
<REMOVAL_REASON> ... </REMOVAL_REASON> [1]
<WORK_TYPES> ... </WORK_TYPES> [1]
<SERVICES_SUPPLIED> ... </SERVICES_SUPPLIED> [1]
<BARCODE> ... </BARCODE> [1]
<TORQUE> ... </TORQUE> [1]
</ORDER_DETAIL_TYRE>
</pre>

=== ORDER_REASON_CODE ===
<pre>
<ORDER_REASON_CODE>
<RC_TYPE> ... </RC_TYPE> [1]
<RC_CODE> ... </RC_CODE> [1]
<RC_DESCRIPTION> ... </RC_DESCRIPTION> [1]
<RC_COMMENT> ... </RC_COMMENT> [0..1]
</ORDER_REASON_CODE>
</pre>

{{Note|
* For reason codes included for Order Item non-conformities, RC_TYPE will only be included if EDI parameter INCLUDE_REASON_TYPE is set to "Y", and will always then be "NONC"
}}

===ORDER_HEADER_TYRE===
For TYRE-based systems

<pre>
<ORDER_HEADER_TYRE>
<CUSTOMER_VEHICLE> ... </CUSTOMER_VEHICLE> [0..1]
<AUTHORITY_CODE> ... </AUTHORITY_CODE> [0..1]
</ORDER_HEADER_TYRE>
</pre>

=== ORDER_VEHICLE===
For TYRE-based systems

<pre>
<ORDER_VEHICLE> - for TYRE-based systems only
<VEHICLE_ID> ... </VEHICLE_ID> [1]
<MAKE> ... </MAKE> [1]
<MODEL> ... </MODEL> [1]
<ODO> ... </ODO> [1]
<DESCRIPTION> ... </DESCRIPTION> [1]
<LAST_INSPECTION_DATE> ... </LAST_INSPECTION_DATE> [1]
<VEHICLE_CONFIG_ID> ... </VEHICLE_CONFIG_ID> [1]
<VEHICLE_CONFIG> ... </VEHICLE_CONFIG> [1]
<EPOD_SERVICE_ID> ... </EPOD_SERVICE_ID> [0..1]
</ORDER_VEHICLE>
</pre>

==System Parameters affecting XML Production==
System parameters affecting content in TripOrder XML

{| class="wikitable apt-searchable" border="1" id="systemparams"
|- bgcolor="silver"
!Parameter!!Description!!Level
|-
|CUST_UPDATE_ORDER_LINES||Update Orders|| CUSTOMER
|-
|EPOD_SIGNATURE_STORAGE||Store signature received from C-ePOD ||COST_CENTRE
|-
|IMP_OVERRIDE_SOURCE_REF||Set source system and control additional functionality in ORD_LINE_ITM CSV order import||SYSTEM
|-
| INCL_ROUTE_CODE||Include Baxter Route code and delivery method||COST_CENTRE
|-
|INCLUDE_FAILED_ORDERS||Include Failed Orders as CANCELLED for API||COST_CENTRE
|-
|LOTS_ADD_DEBRIEF||LOTS Additional Debrief Details||COST_CENTRE
|-
|LOTS_DEL_CUST_SIGNATORY ||Controls if DEL messages for LOTS require an actual signatory - Y to hold messages.||COST_CENTRE
|-
|LOTS_INC_ORDER_HEADER_CONFIRM ||Includes the ORDER_HEADER_CONFIRM section in the DEL file for LOTS. ||SYSTEM - only LOTS, DEL event
|-
|LOTS_INC_STOP_SIGNATURE|| Indicates if the STOP_SIGNATURE section will be displayed in the DEL outbound files to LOTS.||SYSTEM - only for LOTSC
|-
|LOTS_INC_STOP_TYPE_DESC||Include STOP-TYPE_DESC tag in XML||SYSTEM - ONLY FOR LOTS process
|-
|LOTS_SEND_WHEN_VEHICLE_SCANNED||List of LOTS message types that will be held until a vehicle scan is received for the order.||COST_CENTRE
|-
|MIC_ADD_STOP_BARCODE|| Include new tag STOP_BARCODE on Microlise outbound xml||SYSTEM - only for process MIC
|-
| OMS_FOOTPRINT_FOR_VOLUME ||Will the footprint of the order line be include in the VOLUME item for the outbound XML file for the despatch units instead of the cubic volume (Y/N)?||COST_CENTRE
|-
|ORD_NO_DEL_FOR_FAILS||Controls if DEL messages are generated for FAILED orders - Y to prevent, C to send as CAN|| COST_CENTRE
|-
|ORD_RBO_PREFIX||Is the rebook prefix stripped for LOTS? ||SYSTEM
|-
|ORD_TEMPERATURE_COMBO||Use Temperature Combo to determine if the customer reference should be highlighted.||COST_CENTRE
|-
|SEND_LINE_ITEM_TO_LOTS ||Send Line Item To LOTS. Y - send both Order Line (D) and Item (S) records. N - Checks for Items and, if there are any, sends Item (S) records, else Order Line (D) records.||SYSTEM
|-
|SEND_PALLET_ID_XML|| Send Pallet ID tag in xml||COST_CENTRE
|-
| STOP_PID||LOTS - is STOP_PID included in the extract ||SYSTEM - only for LOTS/CIM
|-
|TIME_ZONE_ACTIVE||Time Zone Active||SYSTEM
|-
| TMS_OTBOUND_SO_REF||Controls the outbound format for SO_REF in LOTSC||CUSTOMER
|-
|TRIP_ORDER_XSD_VERS||Version of TRIP XSD being used.||SYSTEM
|-
|TRM_DESP_FOR_DEL||Maintain the Actual Despatched Quantity for a Delivery Trip in Trip Debrief (Y/N).||COST_CENTRE
|-
|UNI_LOCATION||Location for Unilever||SYSTEM
|-
|USE_ORDER_ADDRESSEE||Will the addressee name be used for the order? (Y/N)||COST_CENTRE
|-
| USE_PALLET_ID_XML||Use Pallet ID instead of item identifier in XML Outbound files||COST_CENTRE
|-
|USE_XML_ORDER_SUB_REFS||Print order sub refs on outbound XML||COST_CENTRE
|}

TripOrder Interface XML

2025-09-16T07:35:45Z

Anw: Updated

This document is designed to give a brief overview of integration methods into and out of the Aptean TMS - Calidus Edition (CTMS) for transport orders.

The transport orders can be created in CTMS from external systems using XML files based on a standard XSD file format for CTMS called 'TripOrder'.

The following sections will describe some of the sections that are available in the XSD file to create and amend transport orders.

The same XSD file format is used for files being sent by CTMS to external systems to provided information about the transport orders in CTMS and how they have been, or will be, transported between depots and sites.

= XML Inbound Order File Structure =
== EDI Maintenance ==
The XML files for CTMS will be received into a directory structure and processed as may be specified in the 'EDI Maintenance' screen.

Multiple EDI flows may be active to process XML files from different source systems with different filename formats as required.

There are various EDI parameters that can be set to provide different levels of validation of the data that is extracted from the file.

There are also EDI parameters that can be used to set default values for when the data is not able to be provided in the file.

For example, the order time windows can be recalculated and the hazardous data can be defaulted.

== TripOrder File ==
<OBS_XML>
<EVENT>
<EVENT_HEADER>
<EVENT_DETAIL>

The overall file structure consists of two complex type elements - the file header information and then the details. Each element must only exist once per file.

The different sections within <OBS_XML> can occur differently, the data in bold type is included in the text (N.B. not all of the sections and elements that are available in the XSD file format are listed):

<OBS_XML> 1.1 <EVENT>
<EVENT> 1.1 <EVENT_HEADER>
<EVENT_HEADER> 1.1 <ALL ELEMENTS>
<EVENT> 0.00 <EVENT_DETAIL>
<EVENT_DETAIL> 1.1 <TRIP_HEADER>
<TRIP_HEADER> 1.1 <TRIP_IDENTIFIER>
<TRIP_HEADER> 0.1 <TRIP_TRANSACTION_DATE>
<TRIP_HEADER> 0.1 <TRIP_ID>
<EVENT_DETAIL> 0.1 <TRIP_DETAIL>
<EVENT_DETAIL> 0.1 <STOPS>
<STOPS> 1.00 <STOP>
<STOP> 1.1 <STOP_HEADER>
<STOP_HEADER> 1.1 <STOP_IDENTIFIER>
<STOP_HEADER> 0.1 <STOP_ID>
<STOP_HEADER> 0.1 <STOP_SEQ>
<STOP> 0.1 <STOP_DETAIL>
<STOP> 0.1 <ORDERS>
<ORDERS> 1.1 <ORDER>
<ORDER> 1.1 <ORDER_HEADER>
<ORDER_HEADER> 1.1 <ORDER_TRANSACTION_DATE>
<ORDER_HEADER> 0.1 <ORDER_TYPE>
<ORDER_HEADER> 0.1 <WMS_WAREHOUSE>
<ORDER_HEADER> 0.1 <WMS_OWNER>
<ORDER_HEADER> 0.1 <SO_REF>
<ORDER_HEADER> 0.1 <TMS_REF>
<ORDER_HEADER> 0.1 <PO_REF>
<ORDER_HEADER> 0.1 <BOOK_REF>
<ORDER_HEADER> 0.1 <BOOK_DATE>
<ORDER_HEADER> 0.1 <SPECIAL_INSTR>
<ORDER_HEADER> 0.1 <ORDER_COMMENTS>
<ORDER_HEADER> 0.1 <ORDER_HEADER_TMS>
<ORDER_HEADER_TMS> 1.1 <EARLY_AVAIL_DATE>
<ORDER_HEADER_TMS> 1.1 <LATE_AVAIL_DATE>
<ORDER_HEADER_TMS> 1.1 <EARLY_DEL_DATE>
<ORDER_HEADER_TMS> 1.1 <LATE_DEL_DATE>
<ORDER_HEADER_TMS> 0.1 <TMS_GROUP_NAME>
<ORDER_HEADER_TMS> 0.1 <TMS_DELIVERY_TYPE>
<ORDER_HEADER_TMS> 0.1 <TMS_COST_CENTRE>
<ORDER_HEADER_TMS> 0.1 <HAULIER>
<ORDER_HEADER_TMS> 0.1 <TRANSPORT_MODE>
<ORDER_HEADER> 0.1 <ORDER_HEADER_ADDRESSES>
<ORDER_HEADER_ADDRESSES> 1.00 <ORDER_HEADER_ADDRESS>
<ORDER_HEADER_ADDRESS> 1.1 <ADDRESS_TYPE>
<ORDER_HEADER_ADDRESS> 1.1 <ADDRESS_ID>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_NAME>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LINE1>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LINE2>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LINE3>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_TOWN>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_COUNTY>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_COUNTRY_CODE>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_POSTCODE>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_LOC_TYPE>
<ORDER_HEADER_ADDRESS> 0.1 <ADDRESS_CUST_GROUP>
<ORDER_HEADER_ADDRESS> 0.1 <OH_ADDRESS_CONTACTS>
<OH_ADDRESS_CONTACTS> 1.00 <OH_ADDRESS_CONTACT>
<OH_ADDRESS_CONTACT> 0.1 <ALL ELEMENTS>
<ORDER_HEADER> 0.1 <CUSTOMER_ID>
<ORDER_HEADER> 0.1 <CUSTOMER_NAME>
<ORDER> 0.1 <ORDER_DETAILS>
<ORDER_DETAILS> 1.1 <ORDER_DETAIL>
<ORDER_DETAIL> 1.1 <DETAIL_TYPE>
<ORDER_DETAIL> 0.1 <DETAIL_ID>
<ORDER_DETAIL> 0.1 <PRODUCT_TYPE>
<ORDER_DETAIL> 0.1 <PRODUCT_TYPE_DESC>
<ORDER_DETAIL> 0.1 <DU_TYPE>
<ORDER_DETAIL> 1.1 <ITEM_IDENTIFIER>
<ORDER_DETAIL> 0.1 <ITEM_DESCRIPTION>
<ORDER_DETAIL> 0.1 <PALLET_ID>
<ORDER_DETAIL> 0.1 <ITEM_AKA_CODE>
<ORDER_DETAIL> 0.1 <ITEM_FACTOR>
<ORDER_DETAIL> 0.1 <LIFTS>
<ORDER_DETAIL> 0.1 <RPE_QTY>
<ORDER_DETAIL> 0.1 <WEIGHT>
<ORDER_DETAIL> 0.1 <VOLUME>
<ORDER_DETAIL> 0.1 <ORDERED>
<ORDER_DETAIL> 0.1 <TO_DELIVER>
<ORDER_DETAIL> 0.1 <DELIVERED>
<ORDER_DETAIL> 0.1 <PLANNED_CASES>
<ORDER_DETAIL> 0.1 <LENGTH>
<ORDER_DETAIL> 0.1 <WIDTH>
<ORDER_DETAIL> 0.1 <HEIGHT>
<ORDER_DETAIL> 0.1 <COMMODITY_ID>
<ORDER_DETAIL> 0.1 <CLASS_ID>
<ORDER> 0.1 <ORDER_HAZARDOUS_DETAILS>
<ORDER_HAZARDOUS_DETAILS> 1.00 <ORDER_HAZARDOUS_DETAIL>
<ORDER_HAZARDOUS_DETAIL> 0.1 <ALL ELEMENTS>

The XML items have the following definitions in the XSD file format:

{| class="wikitable apt-searchable" border="1" id="triporderxml"
|- bgcolor="silver"
!Item !!Type !!Size !!Restriction !!CTMS Mandatory*
|-
|EVENT_PROCESSED ||STRING ||1 ||E,N,Y ||Y
|-
|EVENT_SOURCE_TYPE ||STRING ||4 ||New Value ||Y
|-
|EVENT_SOURCE_NAME ||STRING ||10 || ||Y
|-
|EVENT_DATE ||DATETIME || || ||Y
|-
|EVENT_TYPE ||STRING ||3 || ||Y
|-
|EVENT_ACTION ||STRING ||1 ||A,C,D ||Y
|-
|TRIP_IDENTIFIER ||STRING ||1 ||O,T ||Y
|-
|TRIP_TRANSACTION_DATE ||DATETIME || || ||
|-
|TRIP_ID ||STRING ||12 || ||
|-
|STOP_IDENTIFIER ||STRING ||1 ||O,S ||Y
|-
|STOP_ID ||STRING ||51 || ||
|-
|STOP_SEQ ||INTEGER ||6 || ||
|-
|ORDER_TRANSACTION_DATE ||DATETIME || || ||Y
|-
|ORDER_TYPE ||STRING ||1 || ||
|-
|WMS_WAREHOUSE ||STRING ||3 || ||
|-
|WMS_OWNER ||STRING ||12 || ||Y
|-
|SO_REF ||STRING ||20 || ||Y
|-
|TMS_REF ||STRING ||20 || ||
|-
|PO_REF ||STRING ||20 || ||
|-
|BOOK_REF ||STRING ||20 || ||
|-
|BOOK_DATE ||DATETIME || || ||
|-
|SPECIAL_INSTR ||STRING ||2000 || ||
|-
|ORDER_COMMENTS ||STRING ||2000 || ||
|-
|EARLY_AVAIL_DATE ||DATETIME || || ||Y
|-
|LATE_AVAIL_DATE ||DATETIME || || ||Y
|-
|EARLY_DEL_DATE ||DATETIME || || ||Y
|-
|LATE_DEL_DATE ||DATETIME || || ||Y
|-
|TMS_GROUP_NAME ||STRING ||12 || ||
|-
|TMS_DELIVERY_TYPE ||STRING ||35 || ||
|-
|TMS_COST_CENTRE ||STRING ||12 || ||Y
|-
|HAULIER ||STRING ||12 || ||
|-
|TRANSPORT_MODE ||STRING ||30 || ||
|-
|ADDRESS_TYPE ||STRING ||3 || ||Y
|-
|ADDRESS_ID ||STRING ||25 || ||Y
|-
|ADDRESS_NAME ||STRING ||50 || ||
|-
|ADDRESS_LINE1 ||STRING ||50 || ||
|-
|ADDRESS_LINE2 ||STRING ||50 || ||
|-
|ADDRESS_LINE3 ||STRING ||50 || ||
|-
|ADDRESS_TOWN ||STRING ||50 || ||
|-
|ADDRESS_COUNTY ||STRING ||50 || ||
|-
|ADDRESS_COUNTRY_CODE ||STRING ||3 || ||
|-
|ADDRESS_POSTCODE ||STRING ||9 || ||
|-
|ADDRESS_LOC_TYPE ||STRING ||12 || ||
|-
|ADDRESS_CUST_GROUP ||STRING ||12 || ||
|-
|ADDRESS_CONTACT_TYPE ||STRING ||1 ||L,O ||
|-
|ADDRESS_CONTACT_FORENAME ||STRING ||50 || ||
|-
|ADDRESS_CONTACT_SURNAME ||STRING ||50 || ||
|-
|ADDRESS_CONTACT_NUMBER ||STRING ||50 || ||
|-
|ADDRESS_EMAIL ||STRING ||100 || ||
|-
|ADDRESS_CONTACT_JOB ||STRING ||50 || ||
|-
|CUSTOMER_ID ||STRING ||12 || ||
|-
|CUSTOMER_NAME ||STRING ||50 || ||
|-
|DETAIL_TYPE ||STRING ||1 ||D,S ||Y
|-
|DETAIL_ID ||STRING ||30 || ||
|-
|PRODUCT_TYPE ||STRING ||12 || ||
|-
|PRODUCT_TYPE_DESC ||STRING ||50 || ||Y
|-
|DU_TYPE ||STRING ||12 || ||
|-
|ITEM_IDENTIFIER ||STRING ||20 || ||Y
|-
|ITEM_DESCRIPTION ||STRING ||122 || ||
|-
|PALLET_ID ||STRING ||100 || ||
|-
|ITEM_AKA_CODE ||STRING ||30 || ||
|-
|ITEM_FACTOR ||STRING ||12 || ||
|-
|LIFTS ||DECIMAL ||8,2 || ||
|-
|RPE_QTY ||DECIMAL ||10,2 || ||
|-
|WEIGHT ||DECIMAL ||10,2 || ||
|-
|VOLUME ||DECIMAL ||15,5 || ||
|-
|ORDERED ||DECIMAL ||28,4 || ||
|-
|TO_DELIVER ||DECIMAL ||28,4 || ||
|-
|DELIVERED ||DECIMAL ||28,4 || ||
|-
|PLANNED_CASES ||INTEGER ||8 || ||
|-
|LENGTH ||DECIMAL ||10,2 || ||
|-
|WIDTH ||DECIMAL ||10,2 || ||
|-
|HEIGHT ||DECIMAL ||10,2 || ||
|-
|COMMODITY_ID ||STRING ||256 || ||
|-
|CLASS_ID ||STRING ||256 || ||
|-
|UN_NUMBER ||STRING ||50 || ||Y
|-
|HAZARDOUS_QTY ||DECIMAL ||28,4 || ||Y
|-
|HAZARDOUS ||STRING ||1 ||N,Y ||Y
|-
|HAZARDOUS_DESCRIPTION ||STRING ||40 || ||Y
|}

*The mandatory flag for CTMS is only valid if the optional section has been provided in the file.

Note that an item quantity must be provided as 'ORDERED' or 'TO_DELIVER' depending which item is being used (as set by an EDI parameter).

=== Event Header <EVENT_HEADER> ===
<EVENT_HEADER>
<EVENT_PROCESSED>N</EVENT_PROCESSED>
<EVENT_SOURCE_TYPE>SAGE</EVENT_SOURCE_TYPE>
<EVENT_SOURCE_NAME>SAGE</EVENT_SOURCE_NAME>
<EVENT_DATE>2015-05-31T12:52:13</EVENT_DATE>
<EVENT_TYPE>ORD</EVENT_TYPE>
<EVENT_ACTION>C</EVENT_ACTION>
</EVENT_HEADER>

The header section describes the fact that an event has occurred. Each event must generally create a new file and this complex type element must not repeat within the file.

Each of the simple type elements outlined above is mandatorily required.

The <EVENT_PROCESSED> is expected to have a value of 'N'.

The <EVENT_SOURCE_TYPE> must be setup as a recognised source system within CTMS.

Although a number of <EVENT_TYPE> values can be received it is the 'ORD' event type which represents a transport order to be created or amended in CTMS, the <EVENT_ACTION> value of 'C' (for 'C'reate) will ensure a new order is generated, an event action value of 'A' (for 'A'mend) will update an order, and an event action value of 'D' (for 'D'elete) will delete an order.

Validation will exist to check that the transport order can be created, amended or deleted as directed.

The <EVENT_DATE> simple element must be in the format 'YYYY-MM-DDTHH:MI:SS'

=== Event Detail <EVENT_DETAIL> ===
<EVENT_DETAIL>
<TRIP_HEADER>
<STOPS>
<STOP>
<STOP_HEADER>
<ORDERS>
<ORDER>
<ORDER_HEADER>
<ORDER_DETAILS>
<ORDER_HAZARDOUS_DETAILS>
</ORDER>

The event detail section consists of complex type elements representing the 'Trip' - a CTMS planned transport movement representing a vehicle with one or more transport orders to one or more location.

The trip can have several 'stops' (a geographical location visited) against which one or more 'orders' can be handled for loading or unloading the vehicle at each stop.

Therefore, the <STOPS> and <ORDERS> may contain multiple stops and transport orders that exist on the trip.

=== Trip Header <TRIP_HEADER> ===
<TRIP_HEADER>
<TRIP_IDENTIFIER>O</TRIP_IDENTIFIER>
</TRIP_HEADER>

The 'ORD' event type does not require trip header information, although this complex type is mandatory in the file, it is exempted by denoting the <TRIP_IDENTIFIER> with 'O' to represent that the file contains order data only.

The order data received is denoted as an 'unplanned' order, that is it has not been built into a vehicle movement and routed through one or more load and unload activities. This planning activity is handled within CTMS.

=== Stops <STOPS> ===
<STOPS>
<STOP>
<STOP_HEADER>
<STOP_IDENTIFIER>O</STOP_IDENTIFIER>
</STOP_HEADER>

The ORD event type does not require any trip stop information and although the complex type is mandatory it is exempted by denoting the <STOP_IDENTIFIER> with 'O' to indicate that the file contains order data only.

=== Orders <ORDERS> ===
<ORDER>
<ORDER_HEADER> ... </ORDER_HEADER> [1]
<ORDER_SUB_REFS> ... </ORDER_SUB_REFS> [0..1]
<ORDER_DETAILS> ... </ORDER_DETAILS> [0..1]
<ORDER_HAZARDOUS_DETAILS> ... </ORDER_HAZARDOUS_DETAILS> [0..1]
</ORDER>
The orders complex type contains the core information that constitutes a transport order request in CTMS, that is, a unique instruction to collect and deliver a number of goods items of a particular type between two points at requested times.

The <ORDER> element can repeat to represent multiple orders within the same file; however it is recommended best practice when using the ORD event type to receive one per individual XML file.

The structure is made up of complex elements representing the higher level order header information which is none repeating and the lower level order details complex type element which may repeat.

The <ORDER_HEADER> complex type is mandatory and must occur once and only once.

The <ORDER_HEADER> complex type is optional.

The <ORDER_DETAILS> complex type is mandatory for transport orders and can repeat but must occur at least once.

The <ORDER_HAZARDOUS_DETAILS> complex type is optional.

=== Order Header <ORDER_HEADER> ===
<ORDER_HEADER>

<ORDER_HEADER>
<ORDER_TRANSACTION_DATE> ... </ORDER_TRANSACTION_DATE> [1]
<ORDER_TYPE> ... </ORDER_TYPE> [0..1]
<WMS_WAREHOUSE> ... </WMS_WAREHOUSE> [0..1]
<WMS_OWNER> ... </WMS_OWNER> [0..1]
<SO_REF> ... </SO_REF> [0..1]
<TMS_REF> ... </TMS_REF> [0..1]
<PO_REF> ... </PO_REF> [0..1]
<BOOK_REF> ... </BOOK_REF> [0..1]
<BOOK_DATE> ... </BOOK_DATE> [0..1]
<SPECIAL_INSTR> ... </SPECIAL_INSTR> [0..1]
<ORDER_COMMENTS> ... </ORDER_COMMENTS> [0..1]
<ORDER_HEADER_TMS> ... </ORDER_HEADER_TMS> [0..1]
<ORDER_HEADER_ADDRESSES> ... </ORDER_HEADER_ADDRESSES> [0..1]
<CUSTOMER_ID> ... </CUSTOMER_ID> [0..1]
<CUSTOMER_NAME> ... </CUSTOMER_NAME> [0..1]
<ORDER_STATUS> ... </ORDER_STATUS> [0..1]
</ORDER_HEADER>

The order header structure represents the high level simple single attributes of the order which exist in isolation, such as references and who the transport order is being conducted on behalf of.

The <ORDER_TRANSACTION_DATE> simple element is mandatory and must be in the format 'YYYY-MM-DDTHH:MI:SS'

The <ORDER_TYPE> simple type element is mandatory and must be received with a value of 'O'.

The <WMS_OWNER> simple type element indicates the customer and must match the customer IDs setup on CTMS, this is a mandatory field.

The <SPECIAL_INSTR> simple type element captures any additional information that is presented to the driver on his hand held delivery device at that may be relevant to the transport planning.

=== Order Header TMS <ORDER_HEADER_TMS> ===
<ORDER_HEADER_TMS>
<EARLY_AVAIL_DATE>2015-05-24T17:00:00</EARLY_AVAIL_DATE>
<TMS_GROUP_NAME>OBS</TMS_GROUP_NAME>
<TMS_DELIVERY_TYPE>Standard</TMS_DELIVERY_TYPE>
<TMS_COST_CENTRE>OBS</TMS_COST_CENTRE>
<TRANSPORT_MODE>ROAD</TRANSPORT_MODE>

The order header TMS section contains additional information relevant to the order and is simply an extension to the main order header complex type.

Most of the simple type elements in the section are optional.

The <TMS_DELIVERY_TYPE> is used to receive the service level: this value must be populated and is validated against CTMS master data

The <EARLY_AVAIL_DATE> simple type element is mandatory and will be used to calculate forward the collection/loading date/time window and also the approximate delivery date/time window. It must be in the format 'YYYY-MM-DDTHH:MI:SS'.

The other 3 dates for the order may be omitted because they can be calculated from the early available date that is provided and the delivery type (i.e. service level) of the order, however, the configuration in CTMS (TBC) will determine the required level of data.

All elements in this section are validated against CTMS master data and therefore must match CTMS configuration.

The accepted values in the <TRANSPORT_MODE> simple type element are:

* AIR
* ROAD

This will be validated and the order file rejected if the value does not match.

The <TOTAL_PRICE> element is optional and defines the TOTAL price of the order. If provided and populated, the value must be a valid decimal value, or an error will be raised. If not provided or null, the value will be set to 0.

=== Order Header Addresses <ORDER_HEADER_ADDRESSES> ===
<ORDER_HEADER_ADDRESSES>
<ORDER_HEADER_ADDRESS>
<ORDER_HEADER_ADDRESS>
<OH_ADDRESS_CONTACTS>

An <ORDER_HEADER_ADDRESSES> complex type element must always exist once per order.

It must include two instances of the <ORDER_HEADER_ADDRESS> complex type element, one for the loading/pickup location (i.e. 'DEP' address type) and one for the unloading/drop-off location (i.e. 'DEL' address type).

=== Order Header Addresses <ORDER_HEADER_ADDRESS> ===
<ORDER_HEADER_ADDRESS>
<ADDRESS_TYPE>DEP</ADDRESS_TYPE>
<ADDRESS_ID>OBS</ADDRESS_ID>
<ADDRESS_NAME>OBS Logistics</ADDRESS_NAME>
<ADDRESS_LINE1>Southern Gateway</ADDRESS_LINE1>
<ADDRESS_LINE2>Speke Boulevard</ADDRESS_LINE2>
<ADDRESS_LINE3></ADDRESS_LINE3>
<ADDRESS_TOWN>Liverpool</ADDRESS_TOWN>
<ADDRESS_COUNTY>Merseyside</ADDRESS_COUNTY>
<ADDRESS_COUNTRY_CODE>GB</ADDRESS_COUNTRY_CODE>
<ADDRESS_POSTCODE>L24 9HZ</ADDRESS_POSTCODE>
<ADDRESS_CUST_GROUP>OBS</ADDRESS_CUST_GROUP>
<OH_ADDRESS_CONTACTS>

The <ORDER_HEADER_ADDRESS> complex type element includes the address attributes for either the initial point of collection/loading or the final point of delivery/unloading.

The <ADDRESS_TYPE> simple type element is mandatory and must be either:
* 'DEP' - Indicates that the address represents the initial 'DEP'arture location of the order.
* 'DEL' - Indicates that the address represents the final 'DEL'ivery location of the order.

The <ADDRESS_TOWN> item and <ADDRESS_POSTCODE> elements will not be validated and will be accepted regardless of data content.

The <ADDRESS_ID> item is mandatory and can be sent as a unique account identifier for the sender/recipient or it can be sent with the word 'UNKNOWN' which will allow CTMS to generate this unique address identifier where necessary.

The system will initially cross check the received Address Name and Address Postcode in the order file to see if any locations exist for that address name and postcode (to narrow down the number of records to validate), if so it will identify against all other address attributes (Address lines, town/suburb, county/state, country code) to see if there is an existing EXACT match.

If an existing EXACT address match is found the existing CTMS location code will be used against the received order - as the address detail matches all attributes. If any difference is found a new location is generated with the data received, generating a new location ID in the following format:

* Characters 1 to 8: Characters 1 to 8 from <ADDRESS_NAME>
* Character 9: '-'
* Characters 10 to 12: Sequence number 001 to 999

The location ID generated will be a maximum of 12 characters, for example:

<ADDRESS_ID>UNKNOWN<ADDRESS_ID>
<ADDRESS_NAME>OBS Logistics</ADDRESS_NAME>
<ADDRESS_POSTCODE>L24 9HZ</ADDRESS_POSTCODE>

Would create location code 'OBS Logi-001'.

Also note that new addresses for existing locations can be provided for each order and new locations can be created for the specific address that may be provided.

Once a location is created it will not be updated via the order upload process, any amendments can be carried out manually or via the import of a 'CSV' file.

New locations will only be created for the address details provided.

=== Order Header Address Contact <OH_ADDRESS_CONTACT> ===
<OH_ADDRESS_CONTACT>
<ADDRESS_CONTACT_TYPE>O</ADDRESS_CONTACT_TYPE>
<ADDRESS_CONTACT_FORENAME>Yard Manager</ADDRESS_CONTACT_FORENAME>
<ADDRESS_CONTACT_SURNAME></ADDRESS_CONTACT_SURNAME>
<ADDRESS_CONTACT_NUMBER>0151 123 5678</ADDRESS_CONTACT_NUMBER>
<ADDRESS_EMAIL>yardmanager@obs.com</ADDRESS_EMAIL>

For each address an optional <OH_ADDRESS_CONTACT> complex type element can be received. This element must only occur once for within a <OH_ADDRESS_CONTACT>.

The <ADDRESS_CONTACT_TYPE> simple type element is mandatory where the <OH_ADDRESS_CONTACT> is used and indicates if the contact information is to be permanently associated to the address master data (value 'L') or whether it is only related to that particular address for the instance of that particular order (value 'O'). For this implementation 'O'rder type contacts should always be received.

If there is no contact information for the loading location then this element is not required for the "DEP" address type.

The other simple type elements are optional.

=== Order Sub-references <ORDER_SUB_REFS> ===
<ORDER_DETAILS>
<ORDER_SUB_REFS>
<ORDER_SUB_REF> <ORDER_SUB_REF>
<SUB_REF_IDENTIFIER> ... </SUB_REF_IDENTIFIER> [1]
<SUB_REF_IDENTIFIER> ... </SUB_REFERENCE> [1]
</ORDER_SUB_REF>
</ORDER_SUB_REFS>
<ORDER_DETAIL>
This <ORDER_SUB_REFS> section is optional, and allows you to store additional references for an order.

The section must include at least one instance of the <ORDER_SUB_REF> complex type element.

The <SUB_REF_IDENTIFIER> simple type must match up to a configured order sub-reference type. These are maintained by your system administrator in the CTMS [[Imports]] screen, on the [[Imports#Decodes|Decodes]] tab, type "XML_REFERENCE". Include the CODE here, not the NAME.

The <SUB_REF_IDENTIFIER> simple type is the value you want to store against that reference. The value can be anything at all, but to 512 characters long. These values are not validated.

You can add as many order sub references as you need for the order.

{{Note|
* If system parameter USE_XML_ORDER_SUB_REFS is set to "Y", sub references will be automatically generated from lane comments that begin with ORDER_REFS:", followed by a comma-delimited list of sub reference names and values. Otherwise this section will contain the order sub references for this order.
* A sub reference of TRIP_TYPE may be automatically generated based on EDI parameter INC_TRIP_TYPE being set. In this case, the value may be set to
** COL - if the from location is the load location of the trip stop and the load location type is not RDC
** TRUNK - if the from location is the load location and the order to location is not the unload location
** XDOCK_DEL - if the order to location is equal to the unload location, and there are onward trips.
** DIRECT_DEL - if the order to location is equal to the unload location, and there are no onward trips.
* If the sub-ref name DELIVERY_METHOD is present, the value will be translated for the carrier.
}}Several static sub-references are supported.

The following will automatically store data as order information, for contact purposes:

* SMS_ADDRESS_1
* SMS_ADDRESS_2
* SMS_ADDRESS_3
* SMS_ADDRESS_4
* EMAIL_ADDRESS

Depending on which values you provide here, the order will be stamped with contact preferences:

* E - Email only.
* S - SMS Only
* B - Both

{{Note}}SMS sending from CTMS is supported at additional transaction cost per message.

The reference ORDER_WMS_STATUS may be used to update a source system status against the trip. Values are:

* OPEN STAGED
* IN PROGRESS STAGED
* CLOSED STAGED
* OPEN
* IN PROGRESS
* CLOSED

=== Order Detail <ORDER_DETAIL> ===
<ORDER_DETAIL>
<DETAIL_TYPE>S</DETAIL_TYPE>
<PRODUCT_TYPE_DESC>CANTEEN</PRODUCT_TYPE_DESC>
<DU_TYPE>20x9</DU_TYPE>
<ITEM_IDENTIFIER>ABC004783</ITEM_IDENTIFIER>
<ITEM_DESCRIPTION>CARTON</ITEM_DESCRIPTION>
<ITEM_AKA_CODE>10*20*30</ITEM_AKA_CODE>
<LIFTS>1</LIFTS>
<WEIGHT>5.37</WEIGHT>
<ORDERED>1</ORDERED>
<TO_DELIVER>1</TO_DELIVER>
<LENGTH>10</LENGTH>
<WIDTH>20</WIDTH>
<HEIGHT>30</HEIGHT>
<COMMODITY_ID>DG</COMMODITY_ID>
<CLASS_ID>2.1</CLASS_ID>
</ORDER_DETAIL>

The <ORDER_DETAIL> complex element is mandatory and can repeat but must occur at least once to form a valid CTMS order.

The order details will be used to generate both the individual dispatch box/carton detail (per unique barcode) and also the higher level summary order detail line level.

The <DETAIL_TYPE> simple element is mandatory and must be received as either:
* 'D' - Represents a CTMS order detail line - summary level of the total of unique package types.
* 'S' - Represents a CTMS order detail item - the lowest level entry for each individual carton/box.

Note that the DU types (i.e. for the order lines) and its items, just the DU types (if items are not being recorded) or just the items may be provided.

If just items are provided then the DU types and thus the order lines may be generated automatically for the order based on the types of items that have been provided.

The <PRODUCT_TYPE_DESC> simple element is mandatory and will be validated against CTMS master data to ensure it is a recognised value. An unrecognised or blank value will cause the order upload to fail with applicable validation message recorded.

The <DU_TYPE> simple element is optional and will be validated against CTMS master data to ensure it is a recognised value. An unrecognised will cause the order upload to fail with applicable validation message recorded.

The <ITEM_IDENTIFIER> simple element is mandatory and will not be validated although it must be a maximum of 15 alphanumeric characters.

The <ITEM_DESCRIPTION> and <ITEM_AKA_CODE simple type elements are an optional freetext tags and can be used as required.

One of the <ORDERED> and <TO_DELIVER> simple type elements will be mandatory and must be received with a numeric integer value. This represents the number of items reflected by the <ORDER_DETAIL> segment received

As this is at individual carton/box level then this is expected to always be 1 for this implementation.

The <WEIGHT>, <HEIGHT>, <WIDTH>, <LENGTH> simple type elements are optional.

{{Note|* The weight provided is a TOTAL weight of the item or line, not a UNIT weight.
* The height, width and length will be used by CTMS to calculate the carton/box level volume for each order item as per existing standard processing logic.}}

The <COMMODITY_ID> simple type element is optional and will be validated against CTMS master data to ensure it is a recognised value. An unrecognised value will cause the order upload to fail with applicable validation message recorded.

The <CLASS_ID> simple type element is optional but must be received when a <COMMODITY_ID> element is provided which has a 'Dangerous' flag setting of 'Y' (in CTMS master data setup). The value will be validated against CTMS master data to ensure it is a recognised value. An unrecognised will cause the order upload to fail with applicable validation message recorded.

The <ITEM_PRICE> element is optional and defines the TOTAL price of the item. This applies only to Item detail type lines. If provided and populated, the value must be a valid decimal value, or an error will be raised. If not provided or null, the value will be set to 0.

=== Order Hazardous Details ===
<ORDER_HAZARDOUS_DETAILS>
<ORDER_HAZARDOUS_DETAIL>

The <ORDER_HAZARDOUS_DETAILS> complex type element is optional and can be provided if required.

If this element is used then one or more <ORDER_HAZARDOUS_DETAIL> complex type elements is mandatorily required.

=== Order Hazardous Detail ===
<ORDER_HAZARDOUS_DETAIL>
<UN_NUMBER>1089</UN_NUMBER>
<HAZARDOUS_QTY>1</HAZARDOUS_QTY>
<HAZARDOUS>Y</HAZARDOUS>
<HAZARDOUS_DESCRIPTION>CARBONYL SULFIDE</HAZARDOUS_DESCRIPTION>
</ORDER_HAZARDOUS_DETAIL>

The <ORDER_HAZARDOUS_DETAIL> complex type element and all its simple type elements are mandatory. The elements are not validated against CTMS master data and will be stored as received.

= XML Outbound Order File Structure =
== EDI Maintenance ==
The XML files from CTMS will be generated and placed into a directory structure and processed as may be specified in the 'EDI Maintenance' screen.

Multiple EDI flows may be active to process XML files at different stages of processing.

There are various EDI parameters that can be set to provide different levels of validation to generate the files.

== TripOrder File ==
<OBS_XML>
<EVENT>
<EVENT_HEADER>
<EVENT_DETAIL>

The same XSD file format is used for files from CTMS as per files into CTMS.

These files may contain more data in each section than are required in the inbound order files.

For example, an outbound file may contain data about the trip, its stops, each order on each stop and the DU types and/or items on each order.

Export depends on the events that are being exported, controlled by EDI Parameters on the API EDI process:
* API_ARR
* API_COL
* API_DEL
* API_DEP
* API_ORD
* API_TRP

Additional EDI parameters are also present (described in detail in the following sections):
*INCLUDE_CDATA_TAG - affects variable text data entry from the execution level - should it be wrapped to prevent interface errors?
* SEND_AND_FORGET - affects the basic interface - should the message be sent with no expectation of explicit acknowledgement back from the destination?
*PRINT_STOP_PID
*PRINT_ROUTE_CODE
*INCLUDE_ORDER_STATUS
*SEND_DEL_TYPE_CODE
*EXPORT_SERVICES
*INC_TRIP_TYPE
*INC_TRIP_ACTION
*INC_PACKED_TO_DEL
*INCLUDE_SAP_LINE_NOS
*INCLUDE_REASON_CODES
*INCLUDE_NON_CON_CODES
* INCLUDE_TRACK_REF
*INCLUDE_ITEM_DELIVER
*INCLUDE_REASON_TYPE

Export may also include debrief-level information, depending on the type of event, and where the order is up to.

The Export will be of Trip Type if related to a trip, and Order type (similar to the above) for Order-type events.

Trip type events:
*TRP - any changes to or creation of a trip.
* ARR - Arrival at any stop.
*DEP - departure at any stop.

Order type events:
*ORD - any changes to or creation of an order.
*CAN - if an order is cancelled.
*COL - if an order is collected.
*DEL - if an order is delivered.

In general, trip-type events include everything that an Order-type event would include, but with the following additions:
*TRIP_DETAIL
*STOP_DETAIL
*STOP_SIGNATURE (if LOTS_INC_STOP_SIGNATURE = "Y")
*ORDER_HEADER_TMS

As an indication of what may change, please see the below sections.

===TRIP_DETAIL===
<pre>
<HAULIER> ... </HAULIER> [0..1]
<HAULIER_NAME> ... </HAULIER_NAME> [0..1]
<HAULIER_TYPE> ... </HAULIER_TYPE> [0..1]
<TRACKING> ... </TRACKING> [1]
<TRIP_SCHEDULE> ... </TRIP_SCHEDULE> [0..1]
<DRIVER> ... </DRIVER> [0..1]
<DRIVER_NAME> ... </DRIVER_NAME> [0..1]
<DRIVER_CONTACT> ... </DRIVER_CONTACT> [0..1]
<TRACTOR> ... </TRACTOR> [0..1]
<TRACTOR_LAT> ... </TRACTOR_LAT> [0..1]
<TRACTOR_LON> ... </TRACTOR_LON> [0..1]
<COST_CENTRE> ... </COST_CENTRE> [0..1]
<TRIP_STATUS> ... </TRIP_STATUS> [0..1]
<TRIP_REF> ... </TRIP_REF> [0..1]
<TRIP_TRAILER_ID> ... </TRIP_TRAILER_ID> [0..1]
<TRIP_TRAILER_TYPE> ... </TRIP_TRAILER_TYPE> [0..1]
<TRIP_DISTANCE> ... </TRIP_DISTANCE> [0..1]
<FUEL_DRAWN> ... </FUEL_DRAWN> [0..1]
<OWNING_DEPOT> ... </OWNING_DEPOT> [0..1]
<CONTAINER_NO> ... </CONTAINER_NO> [0..1]
<SEAL_NO> ... </SEAL_NO> [0..1]
<EFX_NUMBER> ... </EFX_NUMBER> [0..1]
<START_ODOMETER> ... </START_ODOMETER> [0..1]
<END_ODOMETER> ... </END_ODOMETER> [0..1]
<ACTUAL_TRIP_DISTANCE> ... </ACTUAL_TRIP_DISTANCE> [0..1]
<ROUTE_CODE> ... </ROUTE_CODE> [0..1]
<COST_PER_TONNE> ... </COST_PER_TONNE> [0..1]
<COST> ... </COST> [0..1]
<COST_REASON> ... </COST_REASON> [0..1]
<AUDIT_ID> ... </AUDIT_ID> [0..1]
<TRIP_SUB_REFS> ... </TRIP_SUB_REFS> [0..1]
</pre>

{{Note|
* Carrier will be modified if the carrier type is 3PL. This will be exported in the HAULIER tag.
* TRACKING tag will only be populated from trips that are tracked through Microlise.
* The information sent to MICROLISE is extremely limited in this section.
* ROUTE_CODE will only be populated if the EDI parameter PRINT_ROUTE_CODE is populated or the TRIP_ORDER_XSD_VERS system parameter is "2.5". If the system parameter INCL_ROUTE_CODE is set, then this will be instead populated with the Baxter route code.
* AUDIT_ID is a unique ID appended to the message for external tracking purposes.
}}

===TRIP_SUB_REF===
<pre>
<TRIP_SUB_REF>
<SUB_REF_IDENTIFIER> ... </SUB_REF_IDENTIFIER> [1]
<SUB_REFERENCE> ... </SUB_REFERENCE> [1]
</TRIP_SUB_REF>
</pre>

{{Note|
* If system parameter INC_TRIP_ACTION is "Y", a trip sub reference will be generated based on the action of the event.
}}

===STOP_DETAIL===
<pre>
<STOP_REF> ... </STOP_REF> [0..1]
<STOP_TYPE> ... </STOP_TYPE> [0..1]
<STOP_LOCATION_TYPE> ... </STOP_LOCATION_TYPE> [0..1]
<STOP_LOCATION_ID> ... </STOP_LOCATION_ID> [0..1]
<STOP_LOCATION_NAME> ... </STOP_LOCATION_NAME> [0..1]
<STOP_ADDR_LINE1> ... </STOP_ADDR_LINE1> [0..1]
<STOP_ADDR_LINE2> ... </STOP_ADDR_LINE2> [0..1]
<STOP_ADDR_LINE3> ... </STOP_ADDR_LINE3> [0..1]
<STOP_TOWN> ... </STOP_TOWN> [0..1]
<STOP_COUNTY> ... </STOP_COUNTY> [0..1]
<STOP_COUNTRY_CODE> ... </STOP_COUNTRY_CODE> [0..1]
<STOP_POSTCODE> ... </STOP_POSTCODE> [0..1]
<STOP_CONTACT_NAME> ... </STOP_CONTACT_NAME> [0..1]
<STOP_CONTACT_PHONE> ... </STOP_CONTACT_PHONE> [0..1]
<STOP_BREAK_DURATION> ... </STOP_BREAK_DURATION> [0..1]
<STOP_PREV_DIST> ... </STOP_PREV_DIST> [0..1]
<STOP_ACTUAL_PREV_DIST> ... </STOP_ACTUAL_PREV_DIST> [0..1]
<STOP_TRAILER_ID> ... </STOP_TRAILER_ID> [0..1]
<STOP_LAT> ... </STOP_LAT> [0..1]
<STOP_LON> ... </STOP_LON> [0..1]
<STOP_PLANNED_ARRIVAL_DATE> ... </STOP_PLANNED_ARRIVAL_DATE> [0..1]
<STOP_PLANNED_DEPARTURE_DATE> ... </STOP_PLANNED_DEPARTURE_DATE> [0..1]
<STOP_ETA_DATE> ... </STOP_ETA_DATE> [0..1]
<STOP_ETA_AT_DATE> ... </STOP_ETA_AT_DATE> [0..1]
<STOP_EARLIEST_BOOKED_DATE> ... </STOP_EARLIEST_BOOKED_DATE> [0..1]
<STOP_ACTUAL_ARRIVAL_DATE> ... </STOP_ACTUAL_ARRIVAL_DATE> [0..1]
<STOP_ACTUAL_DEPARTURE_DATE> ... </STOP_ACTUAL_DEPARTURE_DATE> [0..1]
<STOP_ODO_READING> ... </STOP_ODO_READING> [0..1]
<STOP_FUEL> ... </STOP_FUEL> [0..1]
<STOP_EMAIL> ... </STOP_EMAIL> [0..1]
<STOP_BARCODE> ... </STOP_BARCODE> [0..1]
<STOP_PID> ... </STOP_PID> [0..1]
<STOP_COUNTRY_NAME> ... </STOP_COUNTRY_NAME> [0..1]
<WAREHOUSE_LOAD> ... </WAREHOUSE_LOAD> [0..1]
</pre>

{{Note|
* Dates are in XML DateTime format.
* ETA and ACTUAL Dates will be populated from execution-based systems.
* STOP_PID will only be populated for LOTS and CIM flows in one format, or if EDI parameter PRINT_STOP_PID is set to "Y" in a different format. This second format should not be enabled for LOTS interfaces.
}}

=== STOP_SIGNATURE===
This section will only be generated if system parameter LOTS_INC_STOP_SIGNATURE is set to "Y".

<pre>
<STOP_SIGNATURE>
<SIGNATURE> ... </SIGNATURE> [0..1]
<SIGNED_BY> ... </SIGNED_BY> [0..1]
</STOP_SIGNATURE>
</pre>

===ORDER_HEADER===
<pre>
<ORDER_TRANSACTION_DATE> ... </ORDER_TRANSACTION_DATE> [1]
<ORDER_TYPE> ... </ORDER_TYPE> [0..1]
<WMS_WAREHOUSE> ... </WMS_WAREHOUSE> [0..1]
<WMS_OWNER> ... </WMS_OWNER> [0..1]
<SO_REF> ... </SO_REF> [0..1]
<ORIG_SO_REF> ... </ORIG_SO_REF> [0..1]
<TMS_REF> ... </TMS_REF> [0..1]
<PO_REF> ... </PO_REF> [0..1]
<BOOK_REF> ... </BOOK_REF> [0..1]
<BOOK_DATE> ... </BOOK_DATE> [0..1]
<SPECIAL_INSTR> ... </SPECIAL_INSTR> [0..1]
<ORDER_COMMENTS> ... </ORDER_COMMENTS> [0..1]
<ORDER_HEADER_TMS> ... </ORDER_HEADER_TMS> [0..1]
<ORDER_HEADER_ADDRESSES> ... </ORDER_HEADER_ADDRESSES> [0..1]
<ORDER_HEADER_CONFIRM> ... </ORDER_HEADER_CONFIRM> [0..1]
<CUSTOMER_ID> ... </CUSTOMER_ID> [0..1]
<CUSTOMER_NAME> ... </CUSTOMER_NAME> [0..1]
<ORDER_STATUS> ... </ORDER_STATUS> [0..1]
<DESTINATION_ORDER> ... </DESTINATION_ORDER> [0..1]
<DESTINATION_DRIVER> ... </DESTINATION_DRIVER> [0..1]
<DESTINATION_VEHICLE> ... </DESTINATION_VEHICLE> [0..1]
<ORDER_SERVICES> ... </ORDER_SERVICES> [0..1]
</pre>

{{Note|
* SO_REF will be populated with the External reference of the order. This may be modified to remove any rebooking suffix if system parameter ORD_RBO_PREFIX is set to "Y"
* ORDER_STATUS will only be included if the EDI parameter INCLUDE_ORDER_STATUS is set to "Y". Further, if system parameter INCLUDE_FAILED_ORDERS is set to "Y" and the order status is FAILED, this will be changed to CANCELLED instead.
* DESTINATION_ORDER, DESTINATION_DRIVER and DESTINATION_VEHICLE will only be present if order sub references exist of those names.
}}

===ORDER_HEADER_TMS ===
<pre>
<ORDER_HEADER_TMS>
<SHIPMENT_ID> ... </SHIPMENT_ID> [0..1]
<TMS_ORDER_SCHEDULE> ... </TMS_ORDER_SCHEDULE> [0..1]
<TMS_HAULAGE_ACTIVITY> ... </TMS_HAULAGE_ACTIVITY> [0..1]
<TMS_HAULAGE_TYPE> ... </TMS_HAULAGE_TYPE> [0..1]
<EARLY_AVAIL_DATE> ... </EARLY_AVAIL_DATE> [1]
<LATE_AVAIL_DATE> ... </LATE_AVAIL_DATE> [1]
<EARLY_DEL_DATE> ... </EARLY_DEL_DATE> [1]
<LATE_DEL_DATE> ... </LATE_DEL_DATE> [1]
<TMS_GROUP_NAME> ... </TMS_GROUP_NAME> [0..1]
<TMS_DELIVERY_TYPE> ... </TMS_DELIVERY_TYPE> [0..1]
<TMS_COST_CENTRE> ... </TMS_COST_CENTRE> [0..1]
<SD_TEMP_COMBO> ... </SD_TEMP_COMBO> [0..1]
<SD_POD_BY> ... </SD_POD_BY> [0..1]
<KEY_CODE> ... </KEY_CODE> [0..1]
<REVENUE> ... </REVENUE> [0..1]
<COST> ... </COST> [0..1]
<COST_PER_TONNE> ... </COST_PER_TONNE> [0..1]
<HAULIER> ... </HAULIER> [0..1]
<TRAILER_TYPE> ... </TRAILER_TYPE> [0..1]
<ROUTE_CODE> ... </ROUTE_CODE> [0..1]
<EFX_NUMBER> ... </EFX_NUMBER> [0..1]
<TRANSPORT_MODE> ... </TRANSPORT_MODE> [0..1]
<TRANSPORT_STATUS> ... </TRANSPORT_STATUS> [0..1]
<RPE_QTY> ... </RPE_QTY> [0..1]
<ACTUAL_RPE_QTY> ... </ACTUAL_RPE_QTY> [0..1]
<WEIGHT> ... </WEIGHT> [0..1]
<ACTUAL_WEIGHT> ... </ACTUAL_WEIGHT> [0..1]
<VOLUME> ... </VOLUME> [0..1]
<ACTUAL_VOLUME> ... </ACTUAL_VOLUME> [0..1]
<FOOTPRINT> ... </FOOTPRINT> [0..1]
<ACTUAL_FOOTPRINT> ... </ACTUAL_FOOTPRINT> [0..1]
<TOTAL_PRICE> ... </TOTAL_PRICE> [0..1]
</ORDER_HEADER_TMS>
</pre>

{{Note|
* TMS_DELIVERY_TYPE is set to the full delivery type if the EDI parameter SEND_DEL_TYPE_CODE is set to "Y". Otherwise the short code associated to the delivery type is sent.
}}

===ORDER_SERVICES===
This section is only populated if the EDI parameter EXPORT_SERVICES is set to "Y", or if this is set to "C" and the event is "CAN" or "DEL".

<pre>
<ORDER_SERVICE>
<SERVICE_ID> ... </SERVICE_ID> [1]
<SERVICE_NAME> ... </SERVICE_NAME> [1]
<SERVICE_QTY> ... </SERVICE_QTY> [1]
<SERVICE_VALUE> ... </SERVICE_VALUE> [1]
</ORDER_SERVICE>
</pre>

=== ORDER_DETAIL===
The details sent in this section are subject to configuration:
* Order Lines are sent if LOTS_SEND_LINE_ITEMS = "Y", or the value is "N" and there are no order items.
* Order Items are sent if LOTS_SEND_LINE_ITEMS = "Y", or the value is "N" and there are order items.

<pre>
<ORDER_DETAIL>
<DETAIL_TYPE> ... </DETAIL_TYPE> [1]
<DETAIL_ID> ... </DETAIL_ID> [0..1]
<PRODUCT_TYPE> ... </PRODUCT_TYPE> [0..1]
<PRODUCT_TYPE_DESC> ... </PRODUCT_TYPE_DESC> [0..1]
<DU_TYPE> ... </DU_TYPE> [0..1]
<ITEM_IDENTIFIER> ... </ITEM_IDENTIFIER> [1]
<ITEM_DESCRIPTION> ... </ITEM_DESCRIPTION> [0..1]
<PALLET_ID> ... </PALLET_ID> [0..1]
<ITEM_AKA_CODE> ... </ITEM_AKA_CODE> [0..1]
<ITEM_FACTOR> ... </ITEM_FACTOR> [0..1]
<LIFTS> ... </LIFTS> [0..1]
<STACK> ... </STACK> [0..1]
<RPE_QTY> ... </RPE_QTY> [0..1]
<ACTUAL_RPE_QTY> ... </ACTUAL_RPE_QTY> [0..1]
<WEIGHT> ... </WEIGHT> [0..1]
<ACTUAL_WEIGHT> ... </ACTUAL_WEIGHT> [0..1]
<VOLUME> ... </VOLUME> [0..1]
<ACTUAL_VOLUME> ... </ACTUAL_VOLUME> [0..1]
<FOOTPRINT> ... </FOOTPRINT> [0..1]
<ACTUAL_FOOTPRINT> ... </ACTUAL_FOOTPRINT> [0..1]
<ORDERED> ... </ORDERED> [0..1]
<PACKED> ... </PACKED> [0..1]
<TO_DELIVER> ... </TO_DELIVER> [0..1]
<DELIVERED> ... </DELIVERED> [0..1]
<SAP_LINE_NO> ... </SAP_LINE_NO> [0..1]
<SHIPMENT_DETAIL> ... </SHIPMENT_DETAIL> [0..1]
<REASON_CODES> ... </REASON_CODES> [0..1]
<DIM_WEIGHT> ... </DIM_WEIGHT> [0..1]
<ACTUAL_DIM_WEIGHT> ... </ACTUAL_DIM_WEIGHT> [0..1]
<TRACKING_REFS> ... </TRACKING_REFS> [0..1]
<DU_DESCRIPTION> ... </DU_DESCRIPTION> [0..1]
<DU_CATEGORY> ... </DU_CATEGORY> [0..1]
<PLANNED_CASES> ... </PLANNED_CASES> [0..1]
<ACTUAL_CASES> ... </ACTUAL_CASES> [0..1]
<SCAN_TYPE> ... </SCAN_TYPE> [0..1]
<LENGTH> ... </LENGTH> [0..1]
<WIDTH> ... </WIDTH> [0..1]
<HEIGHT> ... </HEIGHT> [0..1]
<COMMODITY_ID> ... </COMMODITY_ID> [0..1]
<CLASS_ID> ... </CLASS_ID> [0..1]
<WMS_LOCATION> ... </WMS_LOCATION> [0..1]
<LONG_DESCRIPTION> ... </LONG_DESCRIPTION> [0..1]
<ORDER_DETAIL_TYRE> ... </ORDER_DETAIL_TYRE> [0..1]
<ITEM_PRICE> ... </ITEM_PRICE> [0..1]
</ORDER_DETAIL>
</pre>

{{Note|
* DETAIL_TYPE will be "D" if generated from Order Lines, and "S" if generated from Order Items.
* For D lines
** ITEM_IDENTIFIER will be the DU Type
** ITEM_DESCRIPTION will the DU Type description for "D" lines
** RPE_QTY will include Despatched and Packed REP if the EDI Parameter INC_PACKED_TO_DEL is set to "Y", other wise this will just be the Actual RPE and RPE qty.
** PACKED will be populated if the order has been packed.
** TO_DELIVER will be populated if the order has been collected.
** DELIVERED will be present and populated if the order has been delivered to its final destination.
** SAP_LINE_NO will only be present and populated if the EDI Parameter INCLUDE_SAP_LINE_NOS is "Y" and there is a SAP line number against the order line.
** REASON_CODES will be included if there are non-conformity reason codes against the order line for the API interface.
** REASON_CODES will be included for other flows if EDI Parameters INCLUDE_REASON_CODES and INCLUDE_NON_CON_CODES are set. {{Warning}} These should NOT be set against the API process.
** TRACKING_REFS will be included if the EDI Parameter INCLUDE_TRACK_REF is set to "Y".
* For S lines
** ITEM_IDENTIFIER will be the Item Identifier, unless the customer has specified that an alternative item identifier is used and one is provided against the item. If system parameter USE_PALLET_ID_XML is set to "Y", then the Pallet ID of the item record will be used instead.
** PALLET_ID will only be populated if system parameter SEND_PALLET_ID_XML is set to "Y".
** ORDERED will only be present and populated if the value is not null.
** TO_DELIVER will only be present and populated if the value is null i.e. the order item has been collected.
** DELIVERED will only be present and populated if the value is not null i.e. the order item has been delivered and EDI parameter INCLUDE_ITEM_DELIVER is set to "Y", or this is sent through the API.
** SAP_LINE_NO will only be present and populated if the EDI Parameter INCLUDE_SAP_LINE_NOS is "Y" and there is a SAP line number against the order line.
** REASON_CODES will be included if there are non-conformity reason codes against the order line for the API interface.
** REASON_CODES will be included for other flows if EDI Parameters INCLUDE_REASON_CODES and INCLUDE_NON_CON_CODES are set. {{Warning}} These should NOT be set against the API process.
}}

===TRACKING_REFS===
TRACKING_REFS will be included if the EDI Parameter INCLUDE_TRACK_REF is set to "Y".

<pre>
<TRACKING_REF>
<UNIT_TRACKING_REF> ... </UNIT_TRACKING_REF> [1]
<UNIT_TRACKING_NO> ... </UNIT_TRACKING_NO> [1]
</TRACKING_REF>
</pre>

===ORDER_DETAIL_TYRE===
For TYRE-based systems

<pre>
<ORDER_DETAIL_TYRE>
<WPX_PRODUCT_ID> ... </WPX_PRODUCT_ID> [1]
<POSITION> ... </POSITION> [1]
<LOCATION> ... </LOCATION> [1]
<PRICE> ... </PRICE> [1]
<CUSTOMER_VEHICLE> ... </CUSTOMER_VEHICLE> [1]
<AUTHORITY_CODE> ... </AUTHORITY_CODE> [1]
<WORK_TYPE> ... </WORK_TYPE> [1]
<PRESSURE> ... </PRESSURE> [1]
<TREAD_DEPTH> ... </TREAD_DEPTH> [1]
<CASING> ... </CASING> [1]
<CASING_DESTINATION> ... </CASING_DESTINATION> [1]
<NEW_REMOULD> ... </NEW_REMOULD> [1]
<REGROOVED> ... </REGROOVED> [1]
<TYRE_SERIAL_NO> ... </TYRE_SERIAL_NO> [1]
<REMOVAL_REASON> ... </REMOVAL_REASON> [1]
<WORK_TYPES> ... </WORK_TYPES> [1]
<SERVICES_SUPPLIED> ... </SERVICES_SUPPLIED> [1]
<BARCODE> ... </BARCODE> [1]
<TORQUE> ... </TORQUE> [1]
</ORDER_DETAIL_TYRE>
</pre>

=== ORDER_REASON_CODE ===
<pre>
<ORDER_REASON_CODE>
<RC_TYPE> ... </RC_TYPE> [1]
<RC_CODE> ... </RC_CODE> [1]
<RC_DESCRIPTION> ... </RC_DESCRIPTION> [1]
<RC_COMMENT> ... </RC_COMMENT> [0..1]
</ORDER_REASON_CODE>
</pre>

{{Note|
* For reason codes included for Order Item non-conformities, RC_TYPE will only be included if EDI parameter INCLUDE_REASON_TYPE is set to "Y", and will always then be "NONC"
}}

===ORDER_HEADER_TYRE===
For TYRE-based systems

<pre>
<ORDER_HEADER_TYRE>
<CUSTOMER_VEHICLE> ... </CUSTOMER_VEHICLE> [0..1]
<AUTHORITY_CODE> ... </AUTHORITY_CODE> [0..1]
</ORDER_HEADER_TYRE>
</pre>

=== ORDER_VEHICLE===
For TYRE-based systems

<pre>
<ORDER_VEHICLE> - for TYRE-based systems only
<VEHICLE_ID> ... </VEHICLE_ID> [1]
<MAKE> ... </MAKE> [1]
<MODEL> ... </MODEL> [1]
<ODO> ... </ODO> [1]
<DESCRIPTION> ... </DESCRIPTION> [1]
<LAST_INSPECTION_DATE> ... </LAST_INSPECTION_DATE> [1]
<VEHICLE_CONFIG_ID> ... </VEHICLE_CONFIG_ID> [1]
<VEHICLE_CONFIG> ... </VEHICLE_CONFIG> [1]
<EPOD_SERVICE_ID> ... </EPOD_SERVICE_ID> [0..1]
</ORDER_VEHICLE>
</pre>

==System Parameters affecting XML Production==
System parameters affecting content in TripOrder XML

{| class="wikitable apt-searchable" border="1" id="systemparams"
|- bgcolor="silver"
!Parameter!!Description!!Level
|-
|CUST_UPDATE_ORDER_LINES||Update Orders|| CUSTOMER
|-
|EPOD_SIGNATURE_STORAGE||Store signature received from C-ePOD ||COST_CENTRE
|-
|IMP_OVERRIDE_SOURCE_REF||Set source system and control additional functionality in ORD_LINE_ITM CSV order import||SYSTEM
|-
| INCL_ROUTE_CODE||Include Baxter Route code and delivery method||COST_CENTRE
|-
|INCLUDE_FAILED_ORDERS||Include Failed Orders as CANCELLED for API||COST_CENTRE
|-
|LOTS_ADD_DEBRIEF||LOTS Additional Debrief Details||COST_CENTRE
|-
|LOTS_DEL_CUST_SIGNATORY ||Controls if DEL messages for LOTS require an actual signatory - Y to hold messages.||COST_CENTRE
|-
|LOTS_INC_ORDER_HEADER_CONFIRM ||Includes the ORDER_HEADER_CONFIRM section in the DEL file for LOTS. ||SYSTEM - only LOTS, DEL event
|-
|LOTS_INC_STOP_SIGNATURE|| Indicates if the STOP_SIGNATURE section will be displayed in the DEL outbound files to LOTS.||SYSTEM - only for LOTSC
|-
|LOTS_INC_STOP_TYPE_DESC||Include STOP-TYPE_DESC tag in XML||SYSTEM - ONLY FOR LOTS process
|-
|LOTS_SEND_WHEN_VEHICLE_SCANNED||List of LOTS message types that will be held until a vehicle scan is received for the order.||COST_CENTRE
|-
|MIC_ADD_STOP_BARCODE|| Include new tag STOP_BARCODE on Microlise outbound xml||SYSTEM - only for process MIC
|-
| OMS_FOOTPRINT_FOR_VOLUME ||Will the footprint of the order line be include in the VOLUME item for the outbound XML file for the despatch units instead of the cubic volume (Y/N)?||COST_CENTRE
|-
|ORD_NO_DEL_FOR_FAILS||Controls if DEL messages are generated for FAILED orders - Y to prevent, C to send as CAN|| COST_CENTRE
|-
|ORD_RBO_PREFIX||Is the rebook prefix stripped for LOTS? ||SYSTEM
|-
|ORD_TEMPERATURE_COMBO||Use Temperature Combo to determine if the customer reference should be highlighted.||COST_CENTRE
|-
|SEND_LINE_ITEM_TO_LOTS ||Send Line Item To LOTS. Y - send both Order Line (D) and Item (S) records. N - Checks for Items and, if there are any, sends Item (S) records, else Order Line (D) records.||SYSTEM
|-
|SEND_PALLET_ID_XML|| Send Pallet ID tag in xml||COST_CENTRE
|-
| STOP_PID||LOTS - is STOP_PID included in the extract ||SYSTEM - only for LOTS/CIM
|-
|TIME_ZONE_ACTIVE||Time Zone Active||SYSTEM
|-
| TMS_OTBOUND_SO_REF||Controls the outbound format for SO_REF in LOTSC||CUSTOMER
|-
|TRIP_ORDER_XSD_VERS||Version of TRIP XSD being used.||SYSTEM
|-
|TRM_DESP_FOR_DEL||Maintain the Actual Despatched Quantity for a Delivery Trip in Trip Debrief (Y/N).||COST_CENTRE
|-
|UNI_LOCATION||Location for Unilever||SYSTEM
|-
|USE_ORDER_ADDRESSEE||Will the addressee name be used for the order? (Y/N)||COST_CENTRE
|-
| USE_PALLET_ID_XML||Use Pallet ID instead of item identifier in XML Outbound files||COST_CENTRE
|-
|USE_XML_ORDER_SUB_REFS||Print order sub refs on outbound XML||COST_CENTRE
|}

UG CALIDUS Transport Systems Cross-Functional Flows

2025-09-12T14:40:39Z

Anw: Categorisation

{{:obs:UG CALIDUS Transport Systems Cross-Functional Flows}}
[[Category:Documents]]
[[Category:Training Guides]]

UG CALIDUS Transport Systems Cross-Functional Flows

2025-09-12T14:39:26Z

Anw: Initial Creation