Business Data Maintenance

Within the C-TMS 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

Key Functionality

Group Names

Displays valid Order Groups that exist in C-TMS 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 C-TMS 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 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.

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.

Fuel Surcharging

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. 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).

• 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).

Paragon Staging Posts

Displays specified routes from/to with (via) Staging Post locations as supplied via a CSV data file from Paragon Data. The imported data from Paragon, may be supplimented, edited, or deleted via the use of the named buttons within the tab.