INI and General Info Table settings referenced in this site

Settings are listed in alphabetical order in each section. If you know the name of a setting, use your browser’s Find feature to jump to that setting.

INI settings

The TTS50.ini file contains the global settings that control how TMWSuite operates. You must set up this file for your company’s way of doing business.

[Brackets] enclose all the section headings in your TTS50. Each setting must remain in its section. The TTS50 itself is not alphabetical; you must use your text editor’s Find feature to locate a setting or section.

For more information about the TTS50, see Using INI files to configure the system in the System Administration online help.

[Dispatch]

[Dispatch]PromptOnMasterSave

Applies to

TMWSuite 2010 and later

Description

Use this setting to turn on or turn off a notification prompt when saving a Master Order in Dispatch.

Options

  • Y (default)
    A pop-up notification message will display when you edit or try to save a Master Order. The message reads “Are you sure you want to save this Master Order?”

  • N
    The pop-up notification message will not display.

[Invoice]

[Invoice]DedicatedBillValidateIncomplete

Applies to

TMWSuite: 2011.10_08.0208 and later

Description

This setting determines whether a Printed status can be assigned to a dedicated bill that contains charges that have not been set up in the print group.

Options

  • Y (default)
    Prevent the Printed status from being assigned to a dedicated bill that contains charges that have not been set up in the print group.

    When the dedicated bill is printed a warning message is displayed, and a watermark is printed on the invoice stating that the invoice is Incomplete.

  • N
    The Printed status can be assigned. The warning message does not display, and the watermark is not printed.

Additional Notes

Regardless of the option selected, any charges not assigned to a print group category will be listed on the dedicated bill in the category specified by the DedicatedBillOtherChargeGroup INI setting.

[Invoice]InvoiceSuffixPrefix

Applies to

TMWSuite

Description

This setting determines whether invoice numbers will have a letter suffix or letter prefix, e.g., 982A or A982.

Note: The letter code is used to distinguish between multiple invoices for the same order.

Options

  • SUFFIX (default)
    The system will add a letter suffix to the invoice number.

  • NONE
    No suffix or prefix will be added to the invoice number.

  • PREFIX
    The system will add a letter prefix to the invoice number.

  • NP
    The first invoice for an order will have neither a prefix nor a suffix; subsequent invoices, i.e., supplemental invoices, credit memos, and rebills, will have a prefix.

  • NS
    The first invoice for an order will have neither a prefix nor a suffix; subsequent invoices, i.e., supplemental invoices, credit memos, and rebills, will have a suffix.

[Invoice]SetToPrintedButton

Applies to

TMWSuite 2023.1 and later

Description

This setting determines whether the Set to Printed button is available in the Edit Invoice Folder and the Dedicated Billing window.

Options

  • N (default)
    The Set to Printed button is not available.

  • Y
    The Set to Printed button is available.

    TMWSuite enables the button only when the invoice status is Ready to Print. Clicking Set to Printed does the following:

    • In the Edit Invoice Folder: It changes the status to Printed without physically printing the invoice.

    • In the Dedicated Billing Window:

      • It changes the status to Printed for the dedicated bill and any associated invoices. No physical printing takes place.

      • It creates a master bill.

      • It assigns the dedicated bill and associated invoices to the master bill.

[MileageInterface]

[MileageInterface]ExOptions[x]

Applies to

TMWSuite, TMW Operations

Description

This setting determines whether the mileage lookups performed by an interface will include extended routing options. The bracketed number in the setting indicates a specific mileage interface. Each mileage interface can have its own ExOptions[x]= setting, and each interface’s ExOptions[x]= setting has no impact on any other interface.

Notes:

  1. This setting works in conjunction with the Xface[x]=, Type[x]=, and Path[x]= INI settings.

  2. This setting is followed by a number in brackets that serves as the unique identifier for each mileage interface, e.g., the ExOptions[1]= setting affects only the first mileage interface, ExOptions[2]= affects only the second interface, etc.

  3. Each available option in this setting can only be used with one mileage application. ExOptions[x]= options used for ALK will not work for IntelliRoute, and vice versa.

  4. No ExOptions[x]= options will work for Rand MileMaker interfaces.

  5. Changing an interface’s ExOptions[x]= option does not cause the system to overwrite existing mileage data for that interface in the TMWSuite mileage database. You must delete existing mileage data for an interface from the TMWSuite mileage database if you change the option for this setting.

Options for ALK

The following extended options will work only with ALK’s PC*MILER or PC*MILER|Streets:

  • Blank, that is, no entry (default)
    Routing provided by ALK’s Practical or Shortest lookup is determined by settings in the ALK application. The ExOption[x] setting does not affect this routing.

  • T
    Use Toll Discouraged routing.

  • N
    Use National Network routing.

  • F
    Use 53-foot Trailer routing.

  • TN
    Use combination of Toll Discouraged and National Network routing.

  • TF
    Use combination of Toll Discouraged and 53-foot Trailer routing.

  • I
    Specifies that an open borders route may be used, i.e., one that crosses international borders. The I option can be used alone, or added after T, N, F, TN, or TF (without comma separator); for example:

    ExOptions[25]=FI

  • X
    Specifies that a closed borders route must be used, i.e., one that does not cross international borders. The X option can be used alone, or added after T, N, F, TN, or TF (without comma separator); for example:

    ExOptions[10]=TFX

Notes:

  1. To use ExOptions[x]= options with an ALK interface, the Type[x]= value of the interface must be either P (Practical) or S (Shortest).

  2. National Network (N) and 53-foot Trailer (F) routings cannot be combined.

  3. If neither I nor X is specified, the borders are set as specified in the Borders= `setting in the `[Defaults] section of the pcmserve.ini file. By default, this file is located in your C:\Windows folder.

Options for Rand McNally IntelliRoute Deluxe

The following extended options work only with Rand McNally’s IntelliRoute Deluxe, V.10-1-2005 or higher:

  • Blank, that is, no entry (default)
    Routing provided by Rand McNally IntelliRoute Deluxe is determined by settings in the Rand McNally application. The ExOption[x] setting does not affect this routing.

  • CanadianBorder=
    Options are ON (prohibit travel through Canada) and OFF (permit travel through Canada).

  • TollRoadBias=
    Enter a number between 0 (always prefer toll roads) and 100 (always avoid toll roads).

  • TollRoadAvoid=
    Options are 0 (override the TollRoadBias= setting when calculating a Lowest Cost route) and 1 (do not override the setting).

  • TruckLength=
    Options are 0 (only use roads limited to trailers up to 48 feet long) and 1 (also use roads that permit trailers up to 53 feet long).

  • TruckWidth=
    Options are 0 (only use roads limited to tractors up to 96 inches wide) and 1 (also use roads that permit tractors up to 102 inches wide).

  • GreenBand=
    Options are ON (exclude roads with physical restrictions) and OFF (include roads with physical restrictions).

If the Type[x]= option for an IntelliRoute interface is either LB - Lowest Cost With SMB, or LR - Lowest Cost Only, these extended options can also be used for that interface:

  • CostOfTime
    Enter the average cost in dollars per hour.

    Note: To look up toll costs for a mileage interface using the LB or LR option, you must also enter a CostOfTime= value in the ExOptions[x]= setting for that interface.

  • FuelCost
    Enter the average fuel cost in dollars per gallon.

  • MaintenanceCost
    Enter the average maintenance cost in dollars per mile.

  • AvgFuelEfficiency
    Enter the average fuel efficiency in miles per gallon.

Note: All ExOptions[x]= options for IntelliRoute are entered in key=value pairs separated by a comma. For example:

ExOptions[6]=CanadianBorder=ON,TollRoadBias=55,TruckLength=1,TruckWidth=1, CostOfTime=64.40,AvgFuelEfficiency=6.20,FuelCost=2.35, MaintenanceCost=0.17

[Misc]

[Misc]ALTEXTRAINFO

Applies to

TMWSuite: 2002 and later

Description

This setting determines the method used to enter data in the Extra Information feature. In addition, it determines if the feature allows you to use master file masks to limit user input.

Options

  • 2 (default)
    When this option is set:

    • Master file masks can be used.

    • Data can be entered directly into Extra Information fields. Separate editing windows are not used.

  • 1
    When this option is set:

    • Master file masks cannot be used.

    • An editing window is used to enter data.

    Note: Data cannot be entered directly into Extra Information fields. Data is entered in an editing window that displays when the user clicks a Change button that displays next to the Extra Information field. After entering data into the editing window, the user clicks the Enter button to close the editing window.

Additional Notes

Master File masks can be used to create drop-down fields containing File Maintenance master file options. For more information, see "Using masks to limit user input" in the Extra Information Feature chapter of the System Administration Guide.

[Misc]CopyCompanyNotestoOrder

Applies to

TMWSuite

Description

This setting specifies whether Order By, shipper, consignee, and Bill To company notes can be edited on an order or stop without affecting the original notes in File Maintenance.

Options

  • No (default)
    The company notes feature follows standard functionality. If you add, change, or delete notes for a company in an application other than File Maintenance, the changes are recorded in the corresponding company notes in File Maintenance as well.

  • Yes
    When you save an order in Order Entry or Dispatch, any notes for the Order By, shipper, consignee, and Bill To companies are copied to the new order, and identified as Order in the Attached to field of the Notes window. You can edit these notes in the Notes window without affecting the original notes in Company File Maintenance. Changes you make to a company’s notes in File Maintenance will appear only on new orders where the company is an Order By, shipper, consignee, or Bill To company.

Additional Notes

  1. When CopyCompanyNotestoOrder=Yes, company notes copied to the order can be identified by Order appearing in the Attached to column in the Notes window.

  2. If you insert or add a note in the Notes window of an application other than File Maintenance that permits viewing/editing company notes, and you specify the Note Type as Company, the note will be recorded in the application and in Company File Maintenance for the selected company ID.

  3. The ExpireCopiedNotesOnDelete and CopyCompanyNotestoOrder settings are interdependent. Normally, both settings should be set to Yes, or both should be set to No. Mixed settings are not recommended.

  4. The ExpireCopiedNotesOnDelete setting is relevant only when CopyCompanyNotestoOrder=Yes. If both settings are set to No, adding, changing, or deleting a note updates the company’s notes in File Maintenance. The Delete button deletes the note from the company profile.

[Misc]CompanyScrollStartField

Applies to

TMWSuite

Description

This setting specifies the default field in which the cursor will be placed when the Find Company scroll window is opened.

Options

  • PrimaryID (default)
    The ID recorded for the company in the Company File Maintenance window’s ID field.

    Note: For information on assigning a specific ID to a company or allowing the system to assign it, refer to "Company File Maintenance" in the File Maintenance User Guide.

  • Address
    The street address recorded for the company location in the Company File Maintenance window’s Address field.

  • City
    The city recorded for the company location in the Company File Maintenance window’s City, State field.

  • State
    The state or province recorded for the company location in the Company File Maintenance window’s City, State field.

  • Geo Loc
    The geographic location recorded for the company in the Company File Maintenance window’s GeoLoc (format) field.

  • Zip
    The zip or postal code recorded for the company in the Company File Maintenance window’s Zip field.

  • Phone
    The primary phone number recorded for the company in the Main field, located in the Phones section of the Company File Maintenance window.

  • Name
    The name recorded for the company in the Company File Maintenance window’s Name field.

[Misc]DatetimeEditMode

Applies to

TMWSuite, CRM Right, TMW Operations, TMW eManifest

Description

This setting determines where the cursor will be positioned within a date/time field when the TAB key is used to enter the field.

Options

  • 0 (default)
    Highlight the month and day (MMDD).

  • 1
    Place the cursor in the time section of the field.
    Note: Fields with genesis and apocalypse dates are exceptions.

    • In TMWSuite:
      For fields with 12/31/49 and 01/01/50, the system highlights the month and day (MMDD).

    • In TMW Operations, CRM Right, and TMW eManifest
      For fields with 12/31/49 and 01/01/50, the system highlights the entire field (MMDDYY HH:MM).

Additional Notes

  1. In TMW Operations, CRM Right, and TMW eManifest, this setting works in tandem with the [Misc]DateTimeTabInteraction setting to determine tabbing behavior.

  2. Fuel TMS does not support this setting.

[Misc]dddwrows

Applies to

TMWSuite

Description

In a data entry field where you must specify the name or ID of a city, company, driver, tractor, trailer, or carrier, you can use TMWSuite’s instant best match feature to reduce typing time and errors.

As you begin to type an ID or name, the system tries to match your entry with IDs or names on file. It automatically displays an ID or name that begins with the same characters you type.

You can click the down arrow on the right to display a drop-down list. It shows the names/IDs alphabetically following the one in the field.

This setting allows you to specify the maximum number of rows, i.e., selections, to display in a drop-down list.

Options

  • 8 (default)

  • 1
    Note: This option is useful in preventing users from accidentally selecting the wrong entry while scrolling through a drop-down list.

  • 16

  • 24

  • 25 or greater
    First available in TMWSuite: 2014.13_07.0242

    There is no maximum.

    Note: This option applies only to data entry fields where you specify the name or ID of a company. It does not apply to fields where you specify a city, driver, tractor, trailer, or carrier. When dddwrows=25 or greater, the drop-down lists for those fields display a maximum of 8 rows.

Additional Notes

  1. If instant best match is disabled, this setting will not work in Dispatch.

  2. TMW Back Office, TMW Operations, CRM, and Fuel Dispatch do not support this setting.

[Misc]DefaultTrlType1-4

Applies to

TMWSuite

Description

These four INI settings set the default value of the TrlType1, TrlType2, TrlType3, and TrlType4 fields in the Add New Trailer window. The options for TrlType1-4 are set in the label file.

DefaultTrlType1=UNK (default)
DefaultTrlType2=UNK (default)
DefaultTrlType3=UNK (default)
DefaultTrlType4=UNK (default)

[Misc]EnableCarrierPayInOrderScroll

Applies to

TMWSuite: 2011.10_08.0208 and later

Description

This setting allows you to add both of the following to the Find Orders scroll window:

  • Carrier pay from/to restriction fields, in which you can enter a range of dollar values for carrier pay. This allows you to retrieve any order having carrier payment that falls in that range.

  • Carrier Pay column in the retrieval area. It displays the total carrier payment issued for individual orders.

Options

  • N (default)
    Do not display the Carrier Pay column and the Carrier pay from/to restriction fields.

  • Y
    Display the Carrier Pay column and the Carrier pay from/to restriction fields.

    Notes:

    1. The Carrier Pay column shows data only when entries are made in the Carrier pay from/to restriction fields.

    2. When restrictions are set in the Carrier pay from/to fields, the system will limit the orders retrieved to ones for which both the following are true:

      • One or more carriers are assigned to deliver the order.

      • The total of all carrier pay associated with the order is within the range specified in the Carrier pay from/to restriction fields.

[Misc]EnableRadiusInOrderScroll

Applies to

TMWSuite: 2011.10_08.0208 and later

Description

This setting determines whether the Find Orders scroll window will show the following:

  • Shipper Radius restriction field, as well as a Ship. Radius column in the retrieval area.

  • Consignee Radius restriction field, as well as a Con. Radius column in the retrieval area.

Options

  • N (default)
    The Radius fields are not displayed.

  • Y
    The Radius fields are displayed.

    These fields allow you to specify a radius (in miles) around the location specified in the shipper’s City field and/or the consignee’s City field.

    When an entry is made in the:

    • Shipper’s Radius field
      The system will limit the orders retrieved to ones that have a shipper within the specified radius around the specified location.

      In addition, for each retrieved order, the Ship. Radius column will display the distance between the specified location and the shipper.

    • Consignee’s Radius field
      The system will limit the orders retrieved to ones that have a consignee within the specified radius around the specified location.

      In addition, for each retrieved order, the Con. Radius column will display the distance between the specified location and the consignee.

[Misc]ForceOrderStatusWhenCreditCheckFails

Applies to

TMWSuite, CRM Right, TMW Operations

Description

This setting applies when the credit checking feature is active. Depending on your system setup, when a Bill To company fails a credit check, the system will:

  • Not allow the order to be saved

  • Allow the order to be saved

  • Warn that the Bill To failed the credit check but allow the order to be saved

  • Require a password before saving the order.

This setting provides an additional way to handle saving an order when the Bill To fails a credit check. You can have the order saved with a non-dispatchable status. Once the Bill To company no longer fails the credit check, the order can be saved with a dispatchable status.

Options

  • Blank, that is, no entry (default)
    The system will apply credit checking functionality, according to your entries for these settings in the [Misc] section:

    • CreditCheckOn

    • WhenNoCreditHistory

    • AllowBkgIfCreditFails

    Orders will not be saved with a non-dispatchable status.

  • User-defined status

    Enter the Abbr field value for the non-dispatchable status.

    Notes:

    1. You must set up the non-dispatchable option in the DispStatus label before making your entry. When you set up the status option, you must:

      • Enter a numeric value of 200 or less in the Code field.

      • Select the Exclude from CreditCheck Total check box.

    2. Your system may be set up to allow an order to be saved even when the Bill To company fails the credit check. This functionality is controlled by the [Misc]AllowBkgIfCreditFails and [Misc]WhenNoCreditHistory settings. When orders over a Bill To’s credit limit can be saved, the system will assign the non-dispatchable status to the order.

Additional Notes

  1. In TMWSuite, credit checking is supported in Order Entry, the Dispatch Trip Folder, and in the Project Dispatch and Agent Order Entry add-on modules.

  2. To activate credit checking, you must have [Misc]CreditCheckOn=Y in your TTS50.

  3. Before TMWSuite V.2012.11_07.1008, the system performed an additional credit check each time you saved an existing order. Starting with V.2012.11_07.1008, the system performs an additional credit check only when you make changes to the line haul or accessorial charges on an order.

  4. In TMW Operations, credit checking is supported only in Order Maintenance.

[Misc]GlobalLogon

Applies to

TMWSuite, CRM Right, Fuel Dispatch, TMW Operations, TMW Back Office

Description

This setting activates the global logon feature.

Options

  • Yes (default)
    Store the current user ID and password and apply it for each TMW application accessed by the user today or until he/she selects the Exit and Sign Off command from the File menu to close an application.

    Notes:

    1. This option requires entry of an ID and password only once a day. Entry is needed the first time the user accesses a TMW application. When subsequent access to an application is needed, the system bypasses the logon screen and immediately opens the application. The user may re-access the same application, or access different applications, during the same day without having to log on each time.

    2. CRM Right does not have an Exit and Sign Off command.

      • If users have accessed the application from within TMW Operations, they must use the File > Exit and Sign Off command in TMW Operations.

      • When used as a standalone product, CRM Right does not allow users to exit and sign off. Once a user accesses CRM Right, the system will bypass the logon screen until the stored user ID and password expire at the end of the day.

  • No
    Require the user to log on every time an application is started.

Additional Notes

TMW eManifest does not support this setting.

[Misc]MaxOrderScrollDays

Applies to

TMWSuite: 2012.11_07.0783, TMW Operations: 3.177.20.0

Description

When you use the Find Orders window in TMWSuite, or the Order Scroll window in TMW Operations, you search for orders within a date range. This setting allows you to limit the number of days in the date range.

  • In TMWSuite, the date range is identified by your entries in the Start From/To and/or Delivery From/To fields on the Company and Asset tabs.

    Notes:

    1. This setting does not apply to the Bk’d Between fields on the Find Orders window’s Reference tab. However, using those fields does not cause the system to ignore the date range on the Company or Asset tabs. If that date range exceeds the limit, the system will behave as defined by the [Misc]MaxOrderScrollExceededAction setting.

    2. The [Misc]OrderScrollDaysBack setting affects the Start From and Delivery From dates on the Scroll Orders window. If that setting’s value makes the date range exceed the specified limit, the system will behave as defined by the [Misc]MaxOrderScrollExceededAction setting.

  • In TMW Operations, the date range is identified by your entries in the Start From/To and/or Delivery From/To fields on the Company, Assets, or Schedule tab. This setting also applies to the Bk’d Between fields on the Reference tab.

    Note: When you modify the dates on the Company, Assets, or Schedule tab, the system changes the dates on all three tabs. It does not change the dates on the Reference tab. Likewise, when you change the dates on the Reference tab, it does not change the dates on any other tab.

Options

  • 30 (default)
    The date range cannot exceed 30 days.

  • User-defined number
    Enter the number of days allowed in a single search. The date range cannot exceed that number of days.

Additional Notes

  1. The [Misc]MaxOrderScrollExceededAction setting specifies how the system will respond when the date range exceeds the specified limit.

  2. The CRM Right, Fuel Dispatch, Inventory Services, and TMW eManifest applications do not support this setting.

[Misc]MaxOrderScrollExceededAction

Applies to

TMWSuite: 2012.11_07.0783, TMW Operations: 3.177.20.0

Description

This setting determines the system’s response when a date range in the Find Orders window in TMWSuite or Order Scroll window in TMW Operations exceeds the limit specified by the [Misc]MaxOrderScrollDays setting.

  • In TMWSuite:

    • This setting does not apply to the Bk’d Between fields on the window’s Reference tab. However, using them does not cause the system to ignore the date range on the Company or Asset tabs. If it exceeds the limit, the system will behave as defined here.

    • The [Misc]OrderScrollDaysBack setting affects the Start From and Delivery From dates on the Scroll Orders window. If the value from that setting makes the date range exceed the limit specified by the [Misc]MaxOrderScrollDays setting, the system will behave as defined here.

  • In TMW Operations:

    • This setting does not apply to the Bk’d Between fields on the window’s Reference tab. When you use those fields to retrieve orders, the system ignores the date ranges on the Company, Asset, and Schedule tabs.

    • The [Misc]OrderScrollDaysBack setting affects the Start From and Delivery From dates on the Scroll Orders window. If the value from that setting makes the date range exceed the limit specified by the [Misc]MaxOrderScrollDays setting, the system will behave as defined here.

Options

  • Ignore (default)
    Complete the search without warning the user that the date range exceeded the limit.

  • Prevent
    Notify the user that the date range exceeded the limit. The user cannot complete the search.

  • Warn
    Notify the user that the date range exceeded the limit. Allow the user to complete or cancel the search.

Additional Notes

The CRM Right, Fuel Dispatch, Inventory Services, and TMW eManifest applications do not support this setting.

[Misc]OrderScrollDaysBack

Applies to

TMWSuite: 2000, CRM Right, Fuel Dispatch, Inventory Services, TMW eManifest, TMW Operations

Description

This setting affects the Start From and Delivery From dates on the Scroll Orders window. Enter the number of days prior to today that you want the From dates set back, such 60 or 90.

Options

  • 30 (default)
    Set the From dates to 30 days prior to today’s date.

  • User-defined number of days
    Enter the number of days prior to today that you want the From dates set back.

  • BeginningOfTime
    Set the From dates to 01/01/50.

Additional Notes

In TMWSuite, the [Misc]MaxOrderScrollDays setting specifies the max number of days for which the system will search for orders. If the date range resulting from this setting exceeds the specified limit, the system will behave as defined by the [Misc]MaxOrderScrollExceededActions setting.

[Misc]ScrollOrdersMasterCriteriaOnly

Applies to

TMWSuite: 2009.08_08.0312 and later

Description

This setting determines whether all Scroll Orders filters are consolidated on the All Criteria tab, or whether they appear on the Company, Asset, Reference, and Regions tabs.

Options

  • NO (default)
    Display all Scroll Orders criteria in four tabs.

  • YES
    Display all Scroll Orders criteria in a single tab.

[Misc]ScrollRefIncludeInvoice

Applies to

TMWSuite: 2012.11_07.0190 and later

Description

In the Invoicing application, the Scroll Reference Numbers quick find window allows you to retrieve records that have a specific reference number. By default, only records for invoiced orders are retrieved. This setting determines if the Show orders not invoiced check box will be selected by default.

Options

  • NO (default)
    The Show orders not invoiced check box is cleared by default.

  • YES
    The Show orders not invoiced check box will be selected by default

[Misc]ScrollWinSizeandLocationToRegistry

Applies to

TMWSuite: 2009.08_08.0312 and later

Description

This setting saves the location and size of the Scroll Orders window in the Windows Registry if the user manually moves the window or adjusts its size. When the window is reopened, it will conform to the saved size and location.

Options

  • NO (default)
    Do not save the location and size of the Scroll Orders window when it is moved and/or resized.

  • YES
    Automatically save the location and size of the Scroll Orders window when it is moved and/or resized.

Additional Notes

This functionality applies with any method used to close the Scroll Orders window (for example, by clicking the Close button, or by right-clicking in the window header and selecting Close in the pop-up menu).

[Misc]ShowRevInfo

Applies to

TMWSuite

Description

This setting affects the display of invoicing information for orders in two ways:

  • It determines whether invoice data displays on the Profile Order window’s Invoicing Information tab.

    and

  • It determines whether the Assignment History window’s Revenue button will be available and allow the user to access the Invoice Summary window.

Options

  • Y (default)
    The system will display invoicing data on the Profile Order window’s Invoicing Information tab and the Assignment History window’s Revenue button will be available, allowing the user to access the Invoice Summary window.

  • N
    The system will not display invoicing data on the Profile Order window’s Invoicing Information tab and the Assignment History window’s Revenue button will be disabled, preventing the user from accessing the Invoice Summary window.

[Misc]UserSysAdminAutoLogin

Applies to

TMWSuite: 2009.08_08.0380 and later

Description

This setting determines whether a user must complete a second login when opening the User Maintenance window in the System Administration application.

Options

  • N (default)
    The system will always require a second login when a user attempts to open the User Maintenance window.

  • Y
    If the user logged in to TMWSuite with a SQL Server database administrator login and password, the system will automatically log that user in to the User Maintenance window. If the user ID and password do not belong to a SQL Server database administrator, the user must complete a second login.
    Note: Starting in V.2022.1, if the user does not have SQL Server credentials, the system will check for and allow domain administrative users access by Windows authentication.

[Order]

[Order]OEDefaultItemCode

Applies to

TMWSuite

Description

This setting establishes the default value in the Charge Item field in the freight detail section of the Order Entry Folder.

Options

  • UNK (default)
    Set Unknown as the default value in the Charge Item field.

  • Item Code of any valid charge type
    Populate the Charge Item field from the charge type associated with this Item Code.

    Note: The charge type must be set up for use with Rate by Detail orders.

Additional Notes

  1. This setting only affects Rate by Detail orders created in Order Entry. Orders created in Dispatch are not affected.

  2. This setting does not affect Rate by Total orders.

  3. This setting specifies the default value in the Charge Item field. However, the value can be edited.

[Order]OrderIDFormat

Applies to

TMWSuite 2016.15_07.0311, TMW Operations 2018.4

Description

This setting determines whether the system adds a prefix to a system-generated order number. The prefix is determined by the RevType1 option recorded on the order when it is saved for the first time.

Notes:

  1. Revenue types are user-defined in the label file. A revenue type’s abbreviation is recorded in the Abbr field.

  2. This setting is applicable in both Order Entry and Dispatch.

Options

  • Default
    The system does not add a prefix to the order ID. It uses the default order numbering system, which assigns a sequential numeric value to each new order saved.

  • TERMINALPREFIX
    The system appends a three-character prefix to the order ID the first time a new order is saved. The prefix is determined by the RevType1 option recorded in the order header. The system uses the first three characters from the option’s Abbr column entry in the RevType1 label as the prefix. The numeric part of the order ID consists of a five-digit, zero-filled sequential number. The system starts numbering orders as XXX00001.

    Note: After 99,999, the first digit starts counting with letters, up to 1,000,000:

    • 100,000 to 339,999 convert to A0000 to Z9999

    • 340,000 to 915,999 convert to AA000 to ZZ999

    • 916,000 to 1,000,000 converts to AAA00 to BMA00

  • TERMINALPREFIX6
    The system appends a three-character prefix to the order ID the first time a new order is saved. The prefix is determined by the RevType1 option recorded in the order header. The system uses the first three characters from the option’s Abbr column entry in the RevType1 label as the prefix. The numeric part of the order ID consists of a six-digit, zero-filled sequential number. The system starts numbering orders as XXX000001.

    Note: After 999,999, the first digit starts counting with letters, up to 10,000,000:

    • 1000000 to 3399999 converts to A00000 to Z99999

    • 3400000 to 9159999 converts to AA0000 to ZZ9999

    • 9160000 to 10000000 converts to AAA0000 to BMA0000

  • TERMINALPREFIX7
    The system appends a single-character prefix to the order ID the first time a new order is saved. The prefix is determined by the RevType1 option recorded in the order header. The system uses the first character from the option’s Abbr column entry in the RevType1 label as the prefix. The numeric part of the order ID consists of a seven-digit, zero-filled sequential number. The system starts numbering orders as X0000001.

    Notes:

    1. When using this option, it is suggested that the abbreviations for your RevType1 label options begin with different characters so they can be differentiated when looking up order IDs.

    2. After 9,999,999, the first digit starts counting with letters, up to 100,000,000:

      • 10000000 to 339999 converts to A000000 to Z999999

      • 34000000 to 91599999 converts to AA00000 to ZZ99999

      • 91600000 to 100000000 converts to AAA0000 to BMA0000

  • TERMINALPREFIX9
    The system appends a three-character prefix to the order ID the first time a new order is saved. The prefix is determined by the RevType1 option recorded in the order header. The system uses the first three characters from the option’s Abbr column entry in the RevType1 label as the prefix. The numeric part of the order ID consists of an eight-digit, zero-filled sequential number. The system starts numbering orders as XXX00000001.

    Note: Number repeats after 999,999,999

Additional Notes

The following notes apply to the TERMINALPREFIX, TERMINALPREFIX6, TERMINALPREFIX7, and TERMINALPREFIX9 options only:

  1. When you use these options, you must also have the [Order]UseAlphaOrdID=No setting in your TTS50.

  2. If UNKNOWN is displayed in the RevType1 field when the order is first saved, the system will add the prefix UNK or U to the order number.

  3. When you use these options, the Reserve Order Numbers command is displayed in the Order Entry File menu. Only users that are assigned to booking terminals can use this command. For more information, see the Including your booking terminal as part of your order number section in "Performing Order Entry setup procedures" chapter of the TMWSuite Order Entry guide.

[Order]PromptOnMasterSave

Applies to

TMWSuite V.2023.1 and later

Description

Use this setting to turn on or turn off a notification prompt when saving a Master Order in Order Entry.

Options

  • Y (default)
    A pop-up notification message will display when you edit or try to save a Master Order. The message reads “Are you sure you want to save this Master Order?”

  • N
    The pop-up notification message will not display.

[Settlement]

[Settlement]DoActivityPayDetails

Applies to

TMWSuite: V.2003

Description

This setting applies to the Pay Detail Maintenance window. It determines whether the Calc button can be used to automatically apply pay rates that have been set up in the Rate Schedules application.

Options

  • No (default)
    The Calc button is not functional.

  • Yes
    The Calc button can be used to automatically calculate pay based on pay rates set up in the Rate Schedules application.

Additional Notes

If you have Yes set in the String1 field of the AgentCommiss General Info Table setting, you must have DoActivityPayDetails=No set. The AgentCommiss setting enables the Agent Pay feature, which uses pay calculation functionality that does not involve the use of rate tables in the Rate Schedules application.

[Settlement]FinalStlmntDetailGrid

Applies to

TMWSuite: 2011.10_08.0208

Description

This setting determines whether the Pay Detail section in the Final Settlements Folder will be presented in a grid form, which allows you to use the right-click grid configuration feature.

Options

  • N (default)
    The Pay Detail section is not displayed as a grid.

  • Y
    The Pay Detail section is displayed as a grid.

    Notes:

    1. This setting affects only the Pay Detail section.

    2. In the Final Settlements Folder, you cannot change the sort order of the records listed regardless of how you set the FinalStlmntDetailGrid= INI.

    3. For more information on grids, see the "Saving and loading grid configurations" chapter in the TMWSuite Basics guide.

[Settlement]IgnoreZeroChargesForBillingRateQty

Applies to

TMWSuite

Description

When the system calculates revenue reductions for percent of revenue pay, this setting determines whether the system will ignore invoice line items having $0.00 in the Charge field.

Options

  • N (default)
    The system will not ignore invoice line items having $0.00 in the Charge field.

  • Y
    The system will ignore invoice line items having $0.00 in the Charge field.

    Note: The Y option is recommended for clients using the Use Billing Rate Type option for revenue reduction.

    This is because the Use Billing Rate Type option calculates its revenue reduction based on the amount recorded in the Quantity field of the invoice line item not the amount recorded in the Charge field. Therefore, line items having a zero dollar charge can still affect the revenue reduction.

Additional Notes

  1. A zero dollar line item charge is created when a minimum charge or minimum quantity specified on a billing rate is applied to an invoice. When such a minimum is applied, the system creates two line items for the charge. One line item shows the actual amount in the Quantity field and $0.00 in the Charge field. The other line item shows the amount and charge applicable for the billing rate’s minimum.

  2. Revenue reductions are set up in the Reduction field and the Reduction RateUnit field on a percent of revenue pay type.

[Settlement]PayExistBeforeQueue

Applies to

TMWSuite

Description

This setting determines how the Trips Ready to Settle queue handles the following for a trip:

  • The processing of pay for a specific resource when line haul pay for that resource/trip combination already exists

  • The update of the paid status for the resource’s asset assignment record

Options

  • Ignore (default)

    • Retains the existing pay details

    • Suppresses application of any pay rates

    • Leaves the paid status of the asset assignment record as Not Prepared

    • Shows an error message in the Batch/Error Log indicating that no change made to trip pay

  • Add

    • Retains the existing pay details

    • Uses applicable rates to re-calculate pay that requires correction, adding new pay details for the corrected pay

    • Sets the asset assignment paid status to Prepared

    Note: This option is required to use the reverse pay functionality.

  • Override

    First available in version 2021.4

    • Removes primary and secondary pay and re-calculates them

    • Retains line item pay details with their quantity, but it sets the rate to zero, then it re-calculates the pay

    • Retains all imported or manually added pay details

    • Sets the status of the resource’s asset assignment record to Prepared

  • Keep

    • Retains the existing pay details

    • Suppresses application of any pay rates

    • Sets the asset assignment record’s paid status to Prepared

    Note: This option does not affect the way the Trips Ready to Settle queue processes trips that do not have line haul pay. Automatic rating of such trips will occur as usual.

Additional Note

When a resource is assigned to a trip, the system automatically creates an asset assignment record. This record is what binds the trip and the resource together.

For pay purposes, at the time of dispatch, the asset assignment record (i.e., the trip/resource combination) is stamped with the paid status of Not Prepared. The Trips Ready to Settle queue can be used to retrieve trips that are marked Not Prepared.

When pay for the trip subsequently is saved in the Trip Settlements Folder or the Trips Ready to Settle queue, the paid status is updated to Prepared. The Trips On Hold queue can be used to retrieve trips that are marked Prepared.

In the database, the asset assignment’s paid status is written to the pyd_status column of the assetassignment table. The database code for Not Prepared is NPD. The code for Prepared is PPD.

[Settlement]SettleUsingBranchRevenueCurrency

Applies to

TMWSuite version 2024.x and later

Description

This setting determines how TMWSuite behaves when calculating pay as a percentage of line haul revenue for a trip that involves a branch that uses a different currency from that used on the Bill To invoice.

Options

  • Y (default)
    TMWSuite calculates pay from the accounts receivable charge generated in the branch’s currency.

  • N
    TMWSuite calculates pay from the total charge generated in the Bill To’s currency.

    Note: Currency conversion may still take place if the asset’s currency (as defined in their profile) differs from the invoice currency.

[Settlement]ShowTeam

Applies to

TMWSuite: 2014.13_07.0847

Description

This setting determines whether you can calculate pay for both team drivers on a trip simultaneously in the Trip Settlements Folder.

Options

  • N (default)
    Do not pay both team drivers on a trip simultaneously.

    Note: The ShowTeam check box will not appear in the Trip Settlements Folder window.

  • Y
    Pay both team drivers on a trip simultaneously.

    Notes:

    1. The ShowTeam check box appears in the Trip Settlements Folder window, and is selected by default.

    2. To add pay details manually, you must select the asset type (Driver or Co-Driver) in the tab area of the Trip Settlements Folder.

Additional Notes

This enhancement affects only the Trip Settlements Folder.

[Settlement]SuppressMsgRemoveTripFromComputeQueue

Applies to

TMWSuite: V.2012 and later

Description

When pay details are manually removed from a settlement in Trip Settlements, a "Remove from Queue" message box provides the option to remove the trip from the Trips Ready to Settle queue and mark it as paid.

This setting provides the option to suppress the message box.

Options

  • N (default)
    Display the message box to allow removal of the trip from the Trips Ready to Settle queue.

  • Y

    • TMWSuite versions 2022.2 and older: When pay details are manually removed, the message will not be displayed. The trip will remain in the Trips Ready to Settle queue and be marked as unpaid.

    • TMWSuite versions 2022.3 and newer: The trip will remain in the Trips Ready to Settle queue only when all pay details are deleted.

[Settlement]UseResourceTypeOnTrip

Applies to

TMWSuite

Description

This setting determines where the rating engine will pull information from when it compares the DrvType1 - 4 and the TrcType1 - 4 classifications on a pay rate to those recorded on a trip.

Options

  • N (default)
    Use the DrvType1 - 4 and the TrcType1 - 4 classifications that are currently recorded in the resource’s profile when the trip is being rated.

  • Y
    Use the DrvType1 - 4 and the TrcType1 - 4 classifications that were recorded in the resource’s profile the last time the trip was saved in Order Entry or Dispatch.

    Note: Each time the order is saved, the DrvType1 - 4 and the TrcType1 - 4 classification information is updated (behind the scenes) in the legheader table of the TMWSuite database.

[Split]

[Split]AllowChangeTrailer

Applies to

TMWSuite: Prior to 2003, TMW Operations

Description

This setting determines whether the HCT-Hook Change Trailer and IHCT-Billable Hook Change Trailer events will be offered as options when you split a trip using the Split Trip: Park and Hook command in the Dispatch or Edit menus. The default for the Hook Event field is HLT-Hook Loaded Trailer.

Options

  • No (default)
    Only the HLT-Hook Loaded Trailer or IHLT-Billable Hook Loaded Trailer events will be offered in the Park and Hook window.

  • Yes
    In the Park and Hook window, allow the user to select one of the following:

    • HLT - Hook Loaded Trailer

    • IHLT - Billable Hook Loaded Trailer

    • HCT - Hook Change Trailer

    • IHCT - Billable Hook Change Trailer

Additional Notes

This setting does not work in Fuel Dispatch.

[Tariff]

[Tariff]SetBillToPartyOnSecondaryFromTariff

Applies to

TMWSuite

Description

This setting activates the autosplit billing feature. When it is enabled, the Set Bill To Cmp ID field appears on the Index Settings tab in the Edit Billing Rate Schedule folder. You use this field to identify the Bill To responsible for an order’s accessorial charges.

Note: The field is available only on accessorial rates.

String1

  • No (default)
    The feature is disabled. Do not show the Set Bill To Cmp ID field.

  • Yes
    The feature is enabled. Show the Set Bill To Cmp ID field.

[Tariff]ShowDotNetTab

Applies to

TMWSuite 2014 and later, TMW Back Office 17.10 and later

Description

This setting determines whether to activate the .Net rating features in the Edit Billing Rate Schedule Folder and Edit Settlement Rate Schedule Folder of TMWSuite’s Rate Schedules application.

Options

  • N (default)
    Do not activate the .Net rating features.
    Note: The .Net tab is not available in the rate header.

  • Y
    Activate the .Net rating features.
    Note: The .Net tab is available in the rate header.

[TmwsuiteAddIns]

[TmwSuiteAddins]EnableInterface

Applies to

TMWSuite: 2009.08_08.0569 and later

Description

Activates TMW’s Add-Ins interface, which enables the system to call Microsoft .NET Framework components.

Note: As of TMW Operations 17.25, the Add-Ins interface is no longer required for the Load Tender SmartLink (LTSL) 2.0 module. However, if you are using TMWSuite Dispatch, the Add-Ins are still required. Both LTSL 2.0 and the Add-Ins interface must have the same version number.

Options

  • N (default)
    The interface is not activated.

  • Y
    The interface is activated.

    Notes:

    1. You have the option to install the Add-Ins interface when you install TMWSuite.

    2. If you are using the Advances/Fuel Import application, you must use this option.

[TmwSuiteAddins]EnableScrolls

Applies to

TMWSuite: 2009.08_08.0569 and later

Description

If TMW’s Add-Ins interface has been installed, this setting determines whether a newer version of scroll and profile windows will be enabled by default. The old version of the scroll windows was coded in PowerBuilder; the new version was coded using the Microsoft .NET Framework.

Options

  • Y (default)
    If the Add-Ins interface has been installed, automatically make the .NET version of the scroll and profile windows active.

    Note: To use this options, you must also have the EnableInterface=Y setting in the [TmwSuiteAddins] section of the TTS50.ini file.

  • N
    Keep the older PowerBuilder version of the scroll windows in place.

    Note: This option is useful if you want to use other features coded in .NET, but you are not yet ready to retrain your staff on usage of the new scrolls.

General Info Table settings

The General Info Table is a global configuration file with many settings. These settings appear in a grid that you can access only in System Administration. The grid allows you to see many system parameters at once. These parameters affect how various TMWSuite applications work, similar to the customization of features allowed by TTS50.ini settings.

For more information, see Using the General Info Table in the System Administration online help.

BackOfficeViews

Applies to

TMWSuite: 2012.11_07.0291

Description

This setting enables you to set up views for invoicing queues. This allows you to set pre-defined restrictions for users who access the Orders Ready to Invoice, Invoices on Hold, and Invoices on Hold for Audit queues. This allows you to control the records that they can process.

String1

  • N (default)
    There is no way to set up views. Users can process all trips that appear in the Orders Ready to Invoice, Invoices on Hold, and Invoices on Hold for Audit queues.

  • Y
    Enable the Define Views and Assign Views commands under the Edit menu in the Invoicing application. Users can only process invoices based on views to which they have been assigned.

String2

First available in TMWSuite: 2013.12_08.0891

  • N (default)
    Allow users to retrieve records only with the restriction sets established by their assigned views.

  • Y
    Allow users to retrieve records by temporarily modifying a restriction set to which they have been assigned.

DataEncryption

Applies to

TMWSuite 2020.2, TMW.Suite 2020.2

Description

This setting determines whether sensitive data you enter in the driver profile are encrypted automatically in the TMWSuite database.

Notes:

  1. For versions 2024.2 and earlier, this setting affects only Social Security numbers.

  2. You can use the Data Conversion Administration Utility to encrypt groups of numbers. Contact your Professional Services representative to obtain the utility.

  3. You must use the Data Conversion Administration Utility to decrypt data.

String1

As of version 2024.3:

  • Y (default)
    Encrypt data defined in String2-4.

  • N
    Do not encrypt data.

Prior to version 2024.3:

  • Y (default)
    Encrypt Social Security numbers.

  • N
    Do not encrypt Social Security numbers.

String2

First available in TMWSuite 2024.3 and TMW.Suite 2024.3

  • Blank; that is, no entry (default)

  • SQL table field(s)
    Encrypt the data represented by the field(s). If you want, you can include two or more values separated by commas.

    Valid values include:

    Value Definition Database table Database column

    DRVSSN

    Driver Social Security number

    manpowerprofile

    mpp_ssn

    PAYTOSSN

    Pay To Social Security number

    manpowerprofile

    pto_ssn

    DRVLIC

    Driver license number

    manpowerprofile

    mpp_licensenumber

    CDCODEWORD

    Fuel security card password

    Note: Currently, EFS is the only vendor supported.

    cdsecuritycard

    csc_codeword

String3

Same as String2.

String4

Same as String2.

DistanceLookupVersion

Applies to

TMWSuite: 2005.04_10.0211, Fuel Dispatch, TMW Operations: 15.30.074

Description

When stop locations are entered or modified on an order, this setting determines how the system chooses the location information used for mileage lookups, i.e., whether lookups are based on street addresses, latitude and longitude data, ZIP Codes/postal codes in TMWSuite company profiles, or each city’s primary ZIP Code/postal code in the mileage application.

String1

  • OLD (default)
    The system will use [MileageInterface]DefaultLookupBy option to determine the location information for all mileage lookups.

  • 2004
    The system determines the location information for mileage lookups on a company-by-company basis.

    The Distance SearchLvl field displays in the General section of the Company File Maintenance window. The option in this field determines the location information used for mileage lookups involving that company.

    The available options in the Distance SearchLvl field are:

    • A (address)
      Mileage lookups will be based on the company’s street address.

    • L (latitude and longitude)
      Mileage lookups will be based on the company’s latitude and longitude data.

    • Z (ZIP Code)
      Mileage lookups will be based on the company’s ZIP Code/postal code.

    • C (city)
      Mileage lookups will be based on the primary ZIP Code/postal code for the company’s city in ALK.

Notes for TMWSuite users

  1. To use the 2004 option TMWSuite must be set up to use either:

    • ALK’s PC*MILER|Streets version 17 or higher, or

    • RAND MileMaker with Intelliroute 18 or higher.
      This option is first available in 2014.13_07.0644.

  2. You cannot use the 2004 option with any other mileage application.

  3. If a company’s Distance SearchLvl field is blank, mileage lookups will be based on the company’s city in ALK.

  4. The 2004 option overrides the [MileageInterface]DefaultLookupBy setting.

  5. The 2004 option is required to enable any of the following optional features:

    • Storing separate entries in the mileage database for each direction of the same route
      For more information on this feature, see the description of the DistanceCacheOneWay setting.

    • Saving travel directions for routes in the mileage database
      For more information on this feature, see the description of the DistanceCacheRouting setting.

    • Recording the states traveled through on a route in the mileage database
      For more information on this feature, see the description of the DistanceCacheByState setting.

      Note: To use the Permitting feature in TMWSuite, you must enable the state cached mileage feature. The Permitting feature is a licensed add-on that must be purchased separately.

    • Specifying a company ID as the origin point for calculations performed by the Calc Distance button in Company File Maintenance
      For more information on this feature, see the description of the DistanceValidateCmpID setting.

Notes for Fuel Dispatch users

  1. You can use the 2004 option with ALK’s PC*MILER|Streets version 17 or higher.

  2. You can use the 2004 option with RAND MileMaker SP32 and RAND IntelliRoute version 18 or greater.

  3. If a company’s Distance SearchLvl field is blank, mileage lookups will be based on the company’s city.

  4. The 2004 option overrides the [MileageInterface]DefaultLookupBy setting.

  5. The following optional features are available when you have a value of 2004 or OLD in the String1 field.

    • Storing separate entries in the mileage database for each direction of the same route
      For more information on this feature, see the description of the DistanceCacheOneWay setting.

    • Saving travel directions for routes in the mileage database (available only for ALK)
      For more information on this feature, see the description of the DistanceCacheRouting setting.

    • Recording the states traveled through on a route in the mileage database (available only for ALK)
      For more information on this feature, see the description of the DistanceCacheByState setting.

      Note: To use the Permitting feature in TMWSuite, you must enable the state cached mileage feature. The Permitting feature is a licensed add-on that must be purchased separately.

    • Specifying a company ID as the origin point for calculations performed by the Calc Distance button in Company File Maintenance
      For more information on this feature, see the description of the DistanceValidateCmpID setting.

String2

First available in V. 2006.05_10.1071

String 2 is applicable only when the String1 field has a value of 2004.

  • TMWSuite

    It is possible for the mileage on some trips to be incorrect because of the lookup used for the companies on the trip segments. For example, if a company has its Distance SearchLvl field set to A (Address), but the address is not valid according to ALK, the system will perform the lookup as city-to-ZIP Code. However, the company’s SearchLvl field remains set to A. You can use the String2 field to specify the search method that will be used when the one specified in a company’s profile fails. The options are:

  • Fuel Dispatch

    String2 options are used only when the system validates the company’s address in the company profile.

    • Blank, that is, no entry (default)
      Base the lookup on the company’s address. If the address is not a valid ALK address, no other lookup will be made.

    • A
      Base the lookup on the company’s address. If the address is not a valid ALK address, base the lookup on the company’s city location.

    • C
      Base the lookup on the company’s city location. If the city is not a valid ALK city, base the lookup on the company’s ZIP Code.

    • L
      Base the lookup on the company’s location, as defined by the lat/long entries in its profile. If no lat/long data is recorded in the company’s profile, base the lookup on the company’s ZIP Code.

    • Z
      Base the lookup on the company’s ZIP Code.

String3

First available in V. 2011.10_08.1029

String3 options are valid only for TMWSuite.

String3 is applicable only when the String1 field has a value of 2004.

When you are using a manual mileage interface and a company on an order has the Distance SearchLvl field set to Z (ZIP Code) in its profile, the system does not return saved Zip-to-Zip lookup miles. Instead, it returns miles equal to the option recorded in the [MileageInterface]DefaultIntraCityMileage setting in your TTS50.

You can force the system to perform a new lookup, and base it on the company’s ZIP Code, or its ZIP Code and its city/state location. The options are:

  • N (default)
    When the company’s Distance SearchLvl field is set to Z, return miles equal to the value record in the [MileageInterface]DefaultIntraCityMileage INI setting.

  • Y
    When the company’s Distance SearchLvl field is set to Z, the company’s city and state will be added after the ZIP Code to provide more information to the mileage system for the mileage lookup.

DrvIDAutoGen

Applies to

TMWSuite: 2010.09_08.1208 and later

Description

Prior to this release of TMWSuite, when adding a driver record, the system automatically generated a driver ID that consisted of the first three characters of the driver’s last name and the first two characters of his/her first name.

With this release, you can use this setting to determine the format the system uses when it generates a driver ID.

Notes:

  1. This setting affects profiles created in the Driver File Maintenance window, the Recruit File Maintenance window, or the Add New Driver window.

  2. Regardless of the options specified in this setting, you can manually enter a user-defined driver ID.

String1

  • LastNameFirstName (Default)
    The automatically generated Driver ID will be composed of:

    • The first [value in Int1] characters of the last name,

    • Followed by the first [value in Int2] characters of the first name.

  • FirstNameLastName
    The automatically generated Driver ID will be composed of:

    • The first [value in Int1] characters of the first name,

    • Followed by the first [value in Int2] characters of the last name.

  • GetSystemNumber
    The automatically generated Driver ID will be a number based on the last numeric value stored by the system. The maximum value is 99,999,999. When this value is reached, the system will no longer auto-generate an ID.

String2

  • ZeroPadding=Blank (Default)
    If, in String1, you selected GetSystemNumber, enter the total number of digits you want to use for the system-generated ID.

    The system will fill, or pad, the preceding digits with zeroes. For example, when the field size is six (6), then a numeric value of 25 displays as 000025.

    A maximum of eight (8) digits is allowed.

Int1

  • 3 (Default)
    If, in String1, you selected:

    • LastNameFirstName,
      enter the number of first characters to use from the driver’s last name.

    • FirstNameLastName,
      enter the number of first characters to use from the driver’s first name.

    Notes:

    1. The entry must be greater than zero (0).

    2. The total value of the entries in Int1 and Int2 fields cannot exceed six (6).

Int2

  • 2 (Default)
    If, in String1, you selected:

    • LastNameFirstName,
      enter the number of first characters to use from the driver’s first name.

    • FirstNameLastName,
      enter the number of first characters to use from the driver’s last name.

    Notes:

    1. The entry must be greater than zero (0).

    2. The total value of the entries in Int1 and Int2 fields cannot exceed six (6).

GP_AccountNumberDelimiter

Applies to

TMWSuite version 2024.6 and later

Description

This setting lets you match the account separator character to the one defined in Microsoft Dynamics GP’s account format setup.

String1

  • - (default)
    Account numbers use the hyphen as a separator.

  • Character used in Microsoft Dynamics GP
    Account numbers use the specified character as a separator.

Additonal Notes

If the value in this setting does not match the value in Microsoft Dynamics GP, an error occurs when transferring invoices or settlements from TMWSuite.

PaperWorkCheckLevel

Applies to

TMWSuite

Description

This setting is operational only if [Invoice]RequirePaperwork=Yes and/or [Settlement]RequirePaperworktosettle=Yes in your TTS50. It determines whether required paperwork needs to be checked in for an order, or for every trip segment associated with the order.

Options

  • Order (default)

    • When [Invoice]RequirePaperwork=Yes, the system will not allow the saving of an invoice with a Ready to Print status unless all required paperwork has been checked in for the order.

      Note: If the order is associated with multiple trip segments, the invoice status change is allowed only if paperwork has been checked in for all trip segments.

    • When [Settlement]RequirePaperworktosettle=Yes, the system will not allow calculation of pay for a trip unless all required paperwork has been checked in for the entire order.

      Note: If the order is associated with multiple trip segments, pay calculation will not occur for any trip segment unless paperwork has been checked in for the order.

  • Leg

    • When [Invoice]RequirePaperwork=Yes, the system will not allow the saving of an invoice with a Ready to Print status unless all required paperwork has been checked in for all trip segments associated with the order.

    • When [Settlement]RequirePaperworktosettle=Yes, the system will not allow calculation of pay for a trip segment unless all required paperwork has been checked in for that trip segment. Lack of paperwork for one trip segment will not affect calculation of pay for a different trip segment on the same trip.

      Note: When the Leg option is used, the Required Supporting Paperwork window accessed from a Bill To company’s profile, displays the fields needed to link the paperwork requirement to the pickup, the drop, or both.

RateWareXL

Applies to

TMWSuite: 2009.08_08.0312 and later, LTL Operations Module: 2018.1 and later

Description

This setting applies to Trimble Transportation clients who have RateWare XL accounts with SMC3 and who have purchased Trimble Transportation’s RateWare XL interface. It activates the interface and is used to record the RateWare XL user name, password, and license key. Entries are required in the String1 - String4 fields.

String1

An entry in this string determines if the interface is active.

  • N (default)
    The RateWare XL interface is not active.

  • Y
    The RateWare XL interface is active.

String2

If String1 is set to Y, enter your Rateware XL user name.

String3

If String1 is set to Y, enter the RateWare XL password (case sensitive).

String4

If String1 is set to Y, enter the RateWare XL license key.

RebillRefNumCheck

Applies to

TMWSuite 2024.7 and later

Description

This setting determines whether TMWSuite validates reference numbers on rebill invoices.

String1

  • N (default)
    Do not validate reference numbers on rebill invoices.

  • Y
    Validate reference numbers on rebill invoices.

RowSecurity

Applies to

TMWSuite: 2008.07_08.0637 and later; TMW.Suite 14.20 and later

Description

This setting activates the Row Level Security (RLS) feature. RLS lets you secure records on a user level. For example, you can apply security to records belonging to specific companies, divisions, or terminals. It limits access so that only users or groups assigned to them retrieve their records.

Starting with V.2022.1, if you use RLS, you can also restrict access to field options defined in the Edit User Definable Fields window. You specify which options a user can select in fields that have security applied to them.

String1

* N (default)
User-level security is not applied. Field option filtering is not available.

* Y
User-level security is applied. If field option filtering is set up, it is applied. + You define the security in the Row Level Security Setup window. You assign security to users in the Row Level Security Assignment window. If you want, you can turn on field option filtering in the setup window.

String2

First available in TMW.Suite and CRMRight, V.14.20.

If the String1 field has a value of Y, the system automatically applies a table’s security to its instant best match fields. Instant best match fields include:

  • Carrier

  • Company

  • CRM Work Company

  • Driver

  • PayTo

  • Third Party

  • Tractor

  • Trailer

If you want, you can have security applied to instant best match fields on a case-by-case basis.

  • Y (default)
    Security is applied to all instant best match fields.

  • N
    Security is not applied to all instant best match fields.

    Note: When you use this option, you can apply security to individual fields. You use QuickDesigner to set it up. In each application window, you set the field preferences for the instant best match fields. If you want security applied, you set the TMW Properties section’s UseRowLevelSecurity option to True. See Applying security to fields in the application’s online help for instructions.

Note: As of V.2022.1, RLS functionality lets you filter the field options users can see in drop-down lists. It is based on the Labelkey field you select in the Row Level Security Setup window. Label filtering does not affect security set up for instant best match fields.

+

Additional Notes

Row Level Security is a licensed add-on module. For more information, contact Trimble Sales.

SmtpEmailer

Applies to

TMWSuite, CRM Right, TMW Operations, TMW Back Office

Description

Use this setting to provide information the system needs to send reports and free form messages using SMTP e-mail. SMTP allows you to send reports/messages to recipients outside your company’s network securely.

  • In TMWSuite
    You can send integrated reports.

  • In TMW Operations
    You can send load confirmations from the Brokerage add-on module.

  • In TMW Back Office
    You can send invoices and settlement sheets.

  • In CRM Right
    You can send e-mails to contacts.

String1

Identifies the SMTP server.

  • Blank, that is, no entry (default)
    No e-mails will be sent using an SMTP e-mail server.

  • SMTP e-mail server address
    E-mails will be sent using the identified SMTP e-mail server.

String2

Provides the reply address for e-mails sent from within TMW applications.

  • Blank, that is, no entry (default)
    No reply address will be available for e-mails sent using a SMTP e-mail server.

  • Enter the e-mail reply to address
    Reply e-mails will be sent to this address.

    If you want all replies to go to a single address, enter that e-mail address. If you do not provide an optional reply address, the system will use the e-mail address of the logged-in user.

Notes:

  1. TMW Operations does not use this string. Each user using SMTP e-mail must have an e-mail address defined in his/her user profile.

  2. CRM Right requires an entry in this field.

String3

The String3 and String4 options work together to provide a user name and password to the SMTP server.

Note: If your SMTP server is set up to use Windows authentication, no entry is required in String3 and String4.

  • Blank, that is, no entry (default)
    No SMTP server user ID is provided.

    Unless your SMTP server is set up to use Windows authentication, e-mails will not be sent by the SMTP server.

  • User ID for the SMTP server
    When you click in this field, the SMTP Authentication Credentials window opens. Enter the SMTP user ID and password in this window.

    Notes:

    1. An entry in this field causes the [Misc]SMTPServer INI setting to be ignored.

    2. Once a value is set, you cannot clear entries in this field. If you no longer need to use this field, contact your TMW customer service representative.

String4

The String3 and String4 options work together to provide a user name and password to the SMTP server.

Note: If your SMTP server is set up to use Windows authentication, no entry is required in String3 and String4.

  • Blank, that is, no entry (default)
    No SMTP server password is provided.

    Unless your SMTP server is set up to use Windows authentication, e-mails will not be sent by the SMTP server.

  • Password (encrypted) for the SMTP server
    When you click in this field, the SMTP Authentication Credentials window opens. Enter the SMTP user ID and password in this window.

    Notes:

    1. The system encrypts your password when you save your changes.

    2. Once a value is set, you cannot clear entries in this field. If you no longer need to use this field, contact your TMW customer service representative.

Int1

Determines whether Secure Sockets Layer (SSL) authentication is active.

  • 1 (default)
    The system enables SSL authentication when sending e-mails in CRM Right or TMW Back Office.

    Note: The SMTP server must support SSL authentication for this setting to function correctly.

  • 0
    The system disables SSL authentication when sending e-mails in CRM Right or TMW Back Office. Instead, it uses the entries in String3 and String4.

Note: TMWSuite and TMW Operations do not support this field.

Int2

Determines whether the SMTP server uses Windows authentication when sending e-mails in CRM Right.

  • 0 (default)
    Windows authentication is not used by CRM Right.

    Instead of using Windows authentication, CRM Right uses the entries in String3 and String4.

  • 1
    Windows authentication is used by CRM Right.

    Note: You can use this field to enable/disable Windows authentication for CRM Right, or you can use it for the SMTP server port number. However, TMW recommends using Int3 for all port numbers instead of Int2.

Int3

Specifies the port used by the SMTP server.

  • Blank, that is, no entry (default)
    Uses the default SMTP port 25.

  • User-defined number
    User-defined numbers indicate the SMTP server’s port number.

Int4

First available in TMWSuite: 2019.4

In TMWSuite, determines whether Secure Sockets Layer (SSL) authentication is active.

  • 0 (default)
    The system disables SSL authentication when sending e-mails in TMWSuite.

  • 1
    The system enables SSL authentication when sending e-mails in TMWSuite.

    Note: The SMTP server must support SSL authentication for this setting to function correctly.

Note: This setting affects only TMWSuite.

Additional Notes

  1. When Integrated Reporting was first introduced, the [Misc]SMTPServer INI setting was used to send integrated reports and free form messages from within any TMWSuite application.

  2. Fuel Dispatch does not support this setting.

TimeCalcDelayApplyAll

Applies to

TMWSuite: 2010.09_08.0324 and later

Description

This setting allows you to set up rates that will automatically create:

  • Detention charges for any billable event type.

    and/or

  • Detention pay for any payable event type.

The actual event types used are specified on a rate-by-rate basis.

String1

  • N (default)
    Do not activate the feature.

  • Y
    Activate the feature.

    Notes:

    To use this option, you must have Y set in the String1 field of the HourlyOTPay General Info Table setting.

    If you are using V.2012 or earlier, this setting overrides the custom TimeCalcDelayApply setting. Be sure that custom setting has a String1 field value of N.

String2

First available in version 2015.14_07.0207

Allow line item rates with this feature that calculates detention charges automatically:

  • N (default)
    Do not allow line item rates.

  • Y
    Allow line item rates.

String3

First available in version 2015.14_07.0207

Skip detention calculation when the driver arrives late. Late is defined as arriving after the scheduled latest time.

  • N (default)
    Do not skip detention calculation when the driver is late.

  • Y
    Skip calculation of detention when the driver is late.

    Note: In versions prior to 2020.3, this option was limited to very specific scenarios. The rate must have both the following options set:

    • DelayPerStop set in the Calculation Method field

    • Greatest of Arrival vs Scheduled Latest set in the Option field