Transport Setup

General

By defining the settings, it is possible to influence the basic operation of the TMS module.

Functionality

The transport setup page consists of a number of tab sheets.

Tab: General

The basic setting for the transport setup.

Fields

• Default Activity Calculation: Specifies how activities are calculated. Options: Default(activities are calculated), Milk Run(activities are ordered based on trip templates), or Manual Activities(required when using Visual Planning).
• Rate Calculation With Manual Lines: Specifies how the system must act when manual revenue lines have been entered on an Order. Options: Keep Manual - Add All, Keep Manual - Add Surcharge and Discount, Keep Manual - Add None, Delete Manual - Add All
• Contract Customer Not Found: Specifies how the sytem must act when performing Calculate Revenue or Execute Contract Strategy on an Order and no Contract can be found . Options: Notification, Message, Error, Nothing.
• Contract Vender Not Found: Specifies how the sytem must act when performing Calculate Revenue/Costs or Execute Contract Strategy on a Trip and no Contract can be found . Options: Notification, Message, Error, Nothing.
• Line Amount Editable: Specifies if users are allowed to edit the amount on an automatically generated revenue/cost-line. : Error, Warning, Allowed.
• Base Calender Code: The default calender to be used.
• Revenue Posting Date: Specifies what date to be used on Posting Revenues. Options: Document Date, Order Date, Posting Date, Loading Date, Unloading Date, Actual Loading Date, Actual Unloading Date, Actual or Requested Loading Date, Actual or Requested Unloading Date, Loading Date(Local Date), Unloading Date(Local Date), Actual Loading Date(Local Date) or Actual Unloading Date(Local Date)
• Invoice Info Description Code: Functionality to add additional information to Sales Invoice Lines.
• Contract Price Search: What date is to be used when determinating which Contracts Detail Lines is applicable on an Order when caculating revenues. Options: Document Date, Order Date, Posting Date, Loading Date, Unloading Date, Actual Loading Date, Actual Unloading Date, Actual or Requested Loading Date, Actual or Requested Unloading Date, Loading Date(Local Date), Unloading Date(Local Date), Actual Loading Date(Local Date) or Actual Unloading Date(Local Date)
• Skip Default Sell-To-Contact No.: -
• Delete Sub Document Line: Specifies what to do with the Order when the last Sub Document Line is deleted. Options: Keep Order and Delete Order.
• Default From Address Confirm Answer: Specifies if the: From Address on a Trip has to be overwritten with the value: Default Site as set on the Truck, when assigning a Truck to a Trip. Options: Yes, No and Empty(users will have to select an answer on each assignement).
• Default To Address Confirm Answer: Specifies if the: To Address on a Trip has to be overwritten with the value: Default Site as set on the Truck, when assigning a Truck to a Trip. Options: Yes, No and Empty(users will have to select an answer on each assignement).
• Track Trip To Address No. Changes: Specifies whether manual changes to the To Adress No. have to be tracked for trips based on the previous valueOptions: Previous not Empty and Always.
• Default Overwrite Resource with Assignement Answer: Default answer to the confirm question whether already filled resources should be overwritten by assigned resources. If left empty, the question has to be confirmed manually.
• Advances Fuel Clause Surcharge: Advanced fuel clause feature that provides the option to define a base price and additional information to calculate the fuel surcharge percentage for the next period.';
• Get From or To Address from Order Type: -
• Multiple Time Zones in System: When enabled, all regular dates and times are considered to be in UTC. Local Dates are in the Time zone of the corresponding Address.
• Weight Validation: Specifies the validation priority when entering net, gross and tarra weight. Options: Default(Adjust tarra weight if both gross and net weight are filled) and Tarra(Retain tarra weight if possible).
• Volume Validation: Specifies the way Volume is determined. Default(Volume is just the total volume of the goods) and Incl. Handling Unit(Volume is total volume of goods and handling unit).
• Route Text Provider: Specifies how the route text will be generated. This setting can be overridden on Plan Department.
• Route Currenct Location identifier: Specifies the identifier used to show where the route is in the text as show in the Trip. If left blank, no location identifier will be shown.
• Route Text Only Based on: When true, the route text is based on the activities which are marked as "Use in RouteText" in the Activity List.

Tab: Integrations

The setting for integrating with PTV Xserver for geocoding addresses and calculating distances and driving times on sections and trips.

Tab: Status Templates

The settings on which status template is applicable on what TMS-document.

Tab: Numbering

The numbers to be used automatically or manualy on an entity. By clicking through on the values it is possible to set up your own number series for different periods(years).

Tab: Order

The settings on an order.

Field	Description
Leadtime Warning	-
Unloading Date Calc Method	The option to determine the automatic calculation of Unloading date when manualy entering an order
Default Unloading Date	For next day: 1D.
Default Start time	When no openingtimes or timeslot are registered on an address this value will be used in the order.
Default End Time	When no openingtimes or timeslot are registered on an address this value will be used in the order.
Reuse Customer Reference	The option to determine if a Customer Reference on an order can be used more than once.
Reuse Customer Reference (Posted)	The option to determine if a Customer Reference on a posted order can be used more than once.
Reuse External Document No.	The option to determine if an External Document No. on an order can be used more than once.
Reuse External Document No.(Posted)	The option to determine if a External Document No. on a posted order can be used more than once.
Default trip order type	This trip order type will be applied automaticaly to new trips.

Tab: Unit of Measure

Settings on which codes apply to the various Unit of Measure on the goods lines of an order

The standard units can be set for use in the ordering- and planning process. On the 1st line, select the code applicable to the description. On the 2nd line a weight conversion can be entered so that a payweight can be calculated on orders. If there are multiple units that apply to the same description, for example PALLET and BLOKP then a conversion has to be added to the Unit of Measure.

Tab: Extra Unit of Measure

The Values set on this tab will be calculated/shown in the Visual Planning, Window: Planned Sections. These values can be shown as Balance-totals and Percentage-Utilisation.

Tab: Planning Units

The standard planning units for capacity-settings on resources and load factor calculation on trips. set in this tab will be shown as extra Settings on which Unit of Measure on Orders, Sections and Trips have to be aggregated for planning and contract purposes.

Tab: Capacity

More info will follow.

Tab: Planning

Settings on the planning functionality.

Field	Description
Sequence Calculation Method	Options: - Container/FTL - Groupge - Distibution For more information see Design Details Sequence Determination.

Tab: Calculation

Settings related to both estimated and revised calculating revenue and cost on Orders and Trips

Tab: Contract Strategy

Setting to on contract strategy.

Note

Contact your Boltrics Consultant to activate Contract Strategy.

Field	Description
Contract Strategy Nos.	The numbers to be used when registering a Contract Strategy. By clicking through on the values it is possible to set up your own number series for different periods.
Contrac Strategy Logging	When set to Enabled logging will be recorded when calculating revenue on orders

Tab: CMR

Setting to add special instructions on the CMR in box 16. Depending on the function set selected, the comment lines related to the transport order are printed. e.g. loadingreference-comments, unloadingreference-comments or the Goods comments.