General Info Table settings referenced in this site

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

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

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

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:

For versions 2024.2 and earlier, this setting affects only Social Security numbers.
You can use the Data Conversion Administration Utility to encrypt groups of numbers. Contact your Professional Services representative to obtain the utility.
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, Fuel Dispatch, TMW Operations

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

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.
You cannot use the 2004 option with any other mileage application.
If a company’s Distance SearchLvl field is blank, mileage lookups will be based on the company’s city in ALK.
The 2004 option overrides the [MileageInterface]DefaultLookupBy setting.
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

You can use the 2004 option with ALK’s PC*MILER|Streets version 17 or higher.
You can use the 2004 option with RAND MileMaker SP32 and RAND IntelliRoute version 18 or greater.
If a company’s Distance SearchLvl field is blank, mileage lookups will be based on the company’s city.
The 2004 option overrides the [MileageInterface]DefaultLookupBy setting.
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

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

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

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:

This setting affects profiles created in the Driver File Maintenance window, the Recruit File Maintenance window, or the Add New Driver window.
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).

EFIncludeOpenStopsOnly

Applies to

TMWSuite, TMW Operations

Description

This setting determines whether only non-completed stops are included in ExpertFuel request records created by the system.

String1

N (default)
Include all stops.
Y
Include only non-completed stops.

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, LTL Operations Module

Description

This setting applies to Trimble Transportation clients who have RateWare XL accounts with SMC³ 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, TMW.Suite

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

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:

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

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

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.
Fuel Dispatch does not support this setting.

TimeCalcDelayApplyAll

Applies to

TMWSuite

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.

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

String2

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

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