Changes to the System Administration application (Preliminary: Features are subject to change)
2.Changes to the System Administration application
The V.2003 changes to the System Administration application include:
ShopLink interface setup window
Setting up the General Info Table setting
Setting up expiration label options
Using the Shoplink/Transman interface settings window
Matching Transman unit types to TMWSuite resources
Specifying TMWSuite priorities for Transman preventive maintenance codes
How Shoplink records preventive maintenance expirations in TMWSuite
Rebuilding the menu security list
Migrating rates from one database to another
Granting a user the authority to delete pay details
Configuring latitude/longitude as the mileage lookup
Activating the latitude/longitude feature
Selecting the default mileage look up option
Setting the default latitude and longitude
Specifying your date and time formats
Making the General Info Table settings
Specifying date/time formats in the user profile
Using Regional Options date/time formats
Using four-digit years
Local INI settings
Making the entry in your local.ini that allows you to increase note length
Using the closest available unit feature
New General Info Table settings
Specifying the external accounting system your company uses
Specifying the pay type used by the Accounts Payable Reconciliation feature
Specifying that cargo records be added to EDI 210’s and 214’s
Specifying the equipment type source for EDI 210s
Using the Fax number recorded in a company’s profile for Auto214s
Setting a password to enable trailer beaming
Setting a grace period for expired notes
Specifying how pickup and drop information is shown on the Planning Worksheet
Specifying the location of your invoice imaging list of required supporting documents
Preventing driver or trailer restrictions from affecting the Tractor/Trip Segment grid
Making the General Info Table setting required for the Fuel Pin code function
Assigning a resource to a cancelled trip
Making the Pay Detail Maintenance window accessible in Invoicing for a miscellaneous invoice
Selecting the update priority for the Dispatch Regions feature
Adding characters to system-assigned company IDs
Updating the last recorded commodity for a trailer
Activating the Expiration Audit report feature
Setting up Customized Dispatch reports
Setting up your system to increase note length
Setting the deduction threshold for AP invoices
Using General Info Table entries to set up the Accounts Payable Reconciliation feature
Specifying the calculation method and default free time for automatic detention billing
Restricting the reference number types that display in the Planning Worksheet
Resetting the Comment 1 and Comment 2 fields on the Trailer tab in the Planning Worksheet
New General Info Table setting increases TotalMail message processing speed
Auto-tuning of a company’s latitude and longitude, as displayed in Company File Maintenance
Displaying warnings for all late stops and events
Using an override password with the credit check feature
Automatic change of pickup/delivery event code to match a company's default
Specifying how a driver's seven-day miles are calculated
Excluding trips from the Settlement queue based on a RevType4 value
Specifying your date and time formats
Viewing the Driver as Available in the Tractor/Trip Segment grid
Viewing In the Shop status for tractors in the Tractor/Trip Segment grid
Viewing In the Shop status for trailers in the Trailer grid
Increasing the speed of check call transfers from TotalMail
New INI settings
[Accounting]
Using Great Plains default account numbers
Ensuring GLReset rules are applied when posting data to Great Plains
[Asset Assignment]
Pre-assigning a tractor without assigning a trailer to a trip that has a Begin Empty event
Requiring a trailer ID be assigned before a trip event can be completed
Starting trips with an empty move by default
[DateTimeChecks]
Requiring the user to resolve conflicts on planned trips
Configuring the system to allow trips with date/time conflicts to be saved
[Dispatch]
Setting a default dispatch status for empty moves
Ignoring a tractor’s hub mile reading
Showing the trailer wash count on the Edit Invoice Folder
Setting up the Driver Log Estimate feature
Requiring a deadhead when resources are not at the start of a trip
Requiring entry of reason codes for early/late pickups and drops
Requiring entry of activity dates/times for stops
Sequencing stops in the Stop Detail grid
Using the New Customer indicator
Finding trucks near a specified location
Requiring a company location for event types
New INI settings enforce Arrival and Departure status requirements
New Dispatch functionality added to an existing cross dock INI setting
Updating commodities from the Trip Folder
Bypassing the Invalid Trip Status message when sending load assignments
Using the invoice status to prevent changes to notes in Dispatch
Display warning on bobtail events
Preventing dispatchers from editing expirations that have codes of 900 or greater
Determining how the system handles future resource expirations that conflict with planned trips
Preventing trailer expirations from affecting P1/P2 indicators on the Tractor/Trip Segment tab
Enable/disable warning that a driver/tractor/trailer and a non-board carrier have been assigned
to a movement
Using the Current Hub entry as the hub miles for the first event on the tractor’s next trip
Requiring stops be actualized logically
Making the Add Secondary Trailer Process command available
Displaying a message when schedules are adjusted for holidays
Refreshing the Available Trips grid after a save
Requiring a trailer ID be assigned before a trip event can be completed
Related functionality
Assigning resources through drag-and-drop functionality and the Match command
Configuring the system to automatically create an invoice detail for a post unload or return empty event
Using the closest available unit feature
Combining trailers on consolidated orders
Specifying the OK button text in the Asset Assignment window
Automatically changing the time or status of multiple events that occur at the same location
Preventing the updating of Earliest/Latest pickups when using the Mass Assign function
Automating calculation/recalculation of arrival and departure dates/times
[Expertfuel]
Preventing Expert Fuel® from automatically requesting a confirmation before generating a fuel solution
[FileMaintenance]
Controlling when a company’s Mail To address will be used
[FuelServ]
Specifying which version of Comdata’s Express Cash Batch application you use
Having the system track and charge back miscellaneous fuel card charges
[Invoice]
Controlling whether invoice numbers have a suffix or a prefix
Requiring entry of Revenue Types for an invoice
Specifying how the system should determine the Bill To for an order, based on its terms
Specifying how multiple credit memos and rebills are applied
Configuring the system to require credit memo reasons
Specifying your imaging vendor
Specifying that you are using invoice imaging
Specifying the system should number miscellaneous invoices sequentially
Configuring your system to display the Invoice List to Print window
Configuring lag time
Specifying the date printed on invoices
Associating a Bill To with an invoice format
Additional options that specify when an order can be billed
Creating invoice numbers based on the move number
Restricting users from changing an invoice’s status to Printed
Using the Last Updated By field to restrict which users may retrieve/print invoices
Bypassing imaging for EDI Only clients
Setting the default status of newly-created credit memos
Activating the currency surcharge feature
Setting the invoice currency date
[MileageInterface]
New options for calculating intracity miles
[Misc]
Requiring a warning for load requirement preferences
Setting default trailer types
Controlling trailer beaming
Requiring an entry in the Order Cancel Log window
Choosing a default tab for the Trailer Accessory window
Configuring the system to use Fuel Pin codes
Editing all reference numbers
Having the system auto-copy reference numbers
Specifying the default field for the Find Companies scroll window
Retrieving data for terminated resources
Setting effective dates for P1 and P2 warning indicators
Creating an In-Service move only when a tractor expiration has a code of 200 or greater
Setting up Customized Dispatch reports
Assigning a default internal classification to notes
Making entries in the TTS50.ini file to control the automatic billing for detention
Hiding invoice information
Using the pop-up notes feature
Restricting access to pay information from the Assignment History window
Safeguarding restricted information with field-level security
Hiding the Add PayTo and Edit PayTo buttons
Using an override password with the credit check feature
Changing the status of pay details in the Pay Detail Maintenance window
[MobileComm]
Settings for the ETA Warning Agent
Skipping un-actualized Begin Empty or Begin Bobtail events
Default values for ETA Warning Agent
Having the system send load assignments when multiplanning resources on an order
Selecting arrival or departure time as the basis for late calculations
Determining how the ETA Warning Agent reports tractor locations in relation to cities
[Operations]
Preventing a carrier’s dispatch status change from Available or Planned to Completed
Preventing the system from maintaining the same Earliest/Latest time difference for pickups and drops
New travel time calculation feature added for Order Entry
[Order]
Settings that establish default values in the order header
Requiring RevTypes and Bill Tos on master orders
Suppressing messages for invoiced orders in the Scroll Orders queue
Using Order Summary format 2
Configuring the system to fix settlement quantities
Receiving a warning when you change the Bill To from the default
Using Quick Copy in Order Entry
Specifying reference number types for commodities
Using the invoice status to prevent changes to notes in Order Entry
Setting the default charge type for Rate by Detail orders
New settings used for the Ticket Order Entry feature
Enabling the paperwork check in option
Having the system generate ticket and order numbers automatically
Enabling changes to the Delivery Date field
Using the units specified on the master order
Automatically saving an order when calculating charges
Verifying the quantity of a commodity picked up equals the quantity delivered
[Settlement]
Setting up the system to display notes
Using billed miles for mileage-based pay
Setting up hub mile pay for driver groups
Paying non-mileage based pay for consolidated trips
Attaching carrier advances to an unassigned trip
Setting up your system to pass an accessorial quantity from Invoicing to Settlements
Configuring the system to correctly calculate stop pay for duplicate events
Making the Settlement Rate Tables command available
Displaying hub miles in the Trip Settlements Folder
Paying loaded and empty hub miles separately
Specifying whether the system will display the default AP Invoice Maintenance window
Using total miles or loaded miles for mileage allocation on split trips
Suppressing the duplicate deduction message for standing deductions that are closed
Specifying in Dispatch if an event is payable/non-payable
Allowing advances on a non-existent order
Excluding empty miles from Round Trip (Adjusted) mileage calculations
Adjusting pay quantities based on maximum legal weight
Displaying the Stl # field in the Advances/Misc Labor window
[Split]
Estimating the dates and times of split trip events
[Tariff]
Setting up your system to handle duplicate secondary charges
Adjusting distance-based billing rates on an order
Activating the autosplit billing feature
Resetting the Bill To and RevType1 values on an order from a primary rate
Obsolete settings
ShopLink interface setup window
In TMWSuite V.2003, the Shoplink/Transman interface settings window is accessible in System Administration. The window allows you to match unit descriptions between TMWSuite and Transman, and to assign TMWSuite expiration codes to preventive maintenance scheduled by Transman. Once you have completed the setup, the Shoplink interface can use these codes to create TMWSuite expirations for Transman maintenance schedules and apply them to the appropriate resources.
Before you can use the Shoplink/Transman interface settings window, you must complete two preliminary tasks in System Administration:
- Make an entry in the General Info Table to tell the system where it is to access the Shoplink interface.
- Set up appropriate label options for the Preventive Maintenance expirations Transman will send to TMWSuite through the interface.
Setting up the General Info Table setting
You must tell the Shoplink interface where to find the Transman database.
1.In System Administration, open the General Info Table.
2.Scroll to the Shoplink setting.
Note: General Info Table settings are listed alphabetically.
3.Make the following entries:
String1 / Enter the name of the server on which the Transman database resides.String2 / Enter the name of the Transman database with which TMWSuite is to interface.
Int1 / Enter the Shoplink interface version number you are using. Currently, the version number is 1.
4.Save you entries and exit the General Info Table.
Setting up expiration label options
To allow Transman to create dispatch level expirations for your company’s equipment when it is due for preventive maintenance, you must set up the necessary label options. When you add entries to the label file for creating expirations to be used by Shoplink, remember that the system requires matching entries for the expirations and status labels. For example, when you add a Preventive Maintenance option to the tractor expirations (TrcExp) label, you must also add an identical option to the tractor status (TrcStatus) label. The same holds true for preventive maintenance options added to the trailer expirations (TrlExp) label – a matching option must be added to the trailer status (TrlStatus) label.
Note:Dispatch type expirations are those that can be added, viewed, and updated in the Dispatch application’s Driver/Equipment Status window. Such expirations are assigned codes of 200 or greater. For more information on setting up dispatch level expirations, refer the Expirations guide.
1.In System Administration, open the label file.
2.Access the TrcExp label.
3.Add a label option for Preventive Maintenance. Be sure to:
- Use PRE as the abbreviation.
- Assign a number greater than 200 in the Code field.
4.Repeat Steps 2 and 3 to add options to the TrcStatus, TrlExp, and TrlStatus labels.
Using the Shoplink/Transman interface settings window
The Shoplink/Transman interface settings window is accessed by the Shoplink command in the Utilities menu. The window has two tabs:
- Unit definition
This tab allows you to select the Transman unit types that will correspond to your TMWSuite tractors and trailers.
- PM/Expiration
This tab allows you to specify a TMWSuite priority for Transman preventive maintenance codes.
Matching Transman unit types to TMWSuite resources
In Transman, you can define many types of units for which maintenance must be scheduled. TMWSuite deals with two types of units, i.e., tractors and trailers. To allow the Shoplink interface to create expirations for your TMWSuite units, use the Unit definition tab to categorize Transman unit types as either tractor units or trailer units. The tab has two sections:
- Tractor unit types in Transman
- Trailer unit types in Transman
All unit types defined in Transman are displayed in the Transman column in each of these sections. To have TMWSuite recognize a Transman unit type as a tractor or trailer, highlight it in the Transman column and click the button to add it to the TMWSuite column.
If you mistakenly add a Transman unit to the TMWSuite column, highlight it in the list and click the button to remove it.
Click the Save button to retain your entries.
Specifying TMWSuite priorities for Transman preventive maintenance codes
To allow the Shoplink interface to create out of service expirations for your tractors and trailers when they are due for preventive maintenance, you must assign a TMWSuite priority level to each of the Transman preventive maintenance codes.
When an expiration record is created, it must be given a priority. There are two levels of priorities:
- Priority 1
Critical expirations are assigned a priority of 1. Their completion is required. A resource with an incomplete Priority 1 expiration cannot be dispatched on a trip on, or after, the expiration's effective date.
- Priority 2
Expirations that are not critical are assigned a priority of 2 or greater; such expirations are categorized as Priority 2 expirations.