Business Data Maintenance: Difference between revisions

From CTMS
No edit summary
No edit summary
Line 12: Line 12:


=== CrossDock Paths ===
=== CrossDock Paths ===
[[Crossdocks]] are used within MTS Host 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.
[[Crossdock]]s are used within MTS Host 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.


=== Adjustment Reason Codes ===
=== Adjustment Reason Codes ===

Revision as of 15:48, 30 December 2008

Within the MTS Host 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 Form

Bdm 1.jpg


Key Functionality

Group Names

Displays valid Order Groups that exist in MTS Host. Order groups are used to group orders together, for example all orders from a location could be grouped together.

CrossDock Paths

Crossdocks are used within MTS Host 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.

Adjustment Reason Codes

Provides a list of valid adjustment reason codes, an adjustment reason code can be selected when performing a Manual Advance.

Reason Codes

Displays a list of valid Reason Codes and their usage. 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.

Min Ti RPE Quantity

Defines the minimum number of RPE’s that should be placed on an order during Create TI’s processing.

Trip Statuses

Displays a read only list of Trip status that are used within MTS, 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.

Order Statuses

Displays a read only list of Order status that are used within MTS, it also shows which options are set against a particular status, for example Orders in that status can be Re-booked.