General Info Table settings that are used by CRM Right

General Info Table settings that are used by CRM Right

General Info Table settings that are used by CRM Right

These General Info Table settings are used by CRM Right, and are saved within the TMWSuite database.

ACS-IncludeCompanyAssetsStats
Applies to	TMWSuite: 2011.10_08.0208 and later and CRM Right
Description	This setting determines whether the system will include revenue and pay information for trips completed by company resources (drivers, tractors, and trailers) when compiling lane analysis data in CRM Right and the Advanced Carrier Selection module.
String1	• N (default) Lane analysis data is based only on trips completed by your company carriers. Note: Using this option requires that you leave the String2 field blank. • Y Lane analysis data is based on trips completed by both your company carriers and your company's resources. Note: Using this option requires that you specify the ID of a carrier profile that represents your company's assets in the String2 field.
String2	• Leave blank (default) Required if you have a value of N in the String1 field. • Enter the carrier ID If String1 has a value of Y, you must enter the ID of the carrier profile you created to represent your company's resources. Revenue and pay data for trips completed by your company's resources will display under the specified ID in CRM Right and Advanced Carrier Selection.
Additional Notes	1. This setting is applicable to CRM Right and Advanced Carrier Selection. It has no effect on TMWSuite's External Equipment or Status Based Loads Grid enhanced brokerage features. 2. CRM Right is a licensed add-on module that is sold separately from TMWSuite and the Advanced Carrier Selection, External Equipment, or Status Based Loads Grid enhanced brokerage offerings. For more information, contact TMW Sales. 3. The Advanced Carrier Selection module is a licensed TMWSuite add-on. To use it, you must have the Enhanced Brokerage license applied to your database. For more information on this module, contact TMW Sales.

CRMAuditTasks
Applies to	TMWSuite: 2010.09_08.0324 and later, CRM Right
Description	This setting activates the audit logging feature in CRM Right. The feature tracks changes made to company profiles in CRM Right and the File Maintenance application.
String1	• N (default) Changes made to company profiles are not audited. • Y Changes to certain fields in company profiles produce an audit record. Audited fields include: • Credit Limit • RevType1 - RevType4 • Bill To (flag) • Active (flag) • Alt ID • CRM Type Note: This field is available in company profiles only in CRM Right.
Additional Notes	CRM Right is TMW's Customer Relations Management application. It is sold separately from TMWSuite. For more information, contact TMW Sales.

CRMBillToOnly
Applies to	CRM Right
Description	This setting determines whether the CRM Right Org Tree tab displays only Bill To companies.
String1	• N (default) All companies associated with a terminal or customer service representative are shown in the Org Tree tab. All companies not yet linked with a terminal or representative appear in the Unassociated Companies list. • Y Only Bill To companies associated with a terminal or customer service representative are shown in the Org Tree tab. Only Bill To companies not yet linked with a terminal or representative appear in the Unassociated Companies list. Note: This option affects the display of parent companies and their children. If a parent company's child is not a Bill To, it will not be shown.

NumberOfDaysForNoteExp
Applies to	TMWSuite: 2005.04_10.0281 and later, CRM Right, Fuel Dispatch
Description	By default, when new notes are created, the value in the note's Note Expires field is the apocalypse date of 12/31/2049. You can enter a specific expiration date for a note, or you can use this setting to specify the number of days until a note expires. In versions prior to V. 2010.09_08.0990, this setting used only the Int1 field. To specify the number of days until a note's expiration, you entered a number from 1 to 9999. The same method of calculating the expiration date was used for all note types (i.e., notes attached to orders, companies, resources, Pay To’s, movements, invoices, settlements, and commodities). Also, the adjusted expiration date did not display until you closed and reopened the Notes window.
Int1	Starting with V.2010.09_08.0990, TMW added options for the String1 fields. These options allow you to set a different numbers of days for order type notes than you set for other note types. Entries are allowed in the String1 and Int1 fields. When String1 is: • Blank (no entry) The expiration date is based on your entry in the Int1 field. When Int1is set to: • 0 (or blank) The expiration date will be the system's apocalypse date of 12/31/2049. • 1 to 9999 The note expires the specified number of days after the date it was first saved. • C The note's expiration date is based on the date/time it was first saved. In the Int1 field enter the number of days that you want the system to add to the date/time the note was first saved. Values from 0 to 9999 are acceptable. • E The note's expiration date is based on the whether the note is order-based. • Order type notes The note's expiration date is based on the date/time recorded in the order's Latest date/time field for the last drop. In the Int1 field enter the number of days that you want the system to add to the date/time recorded in the order's Latest date/time field for the last drop. Values from 0 to 9999 are acceptable. • All other note types The note's expiration date is based on the date/time it was first saved. In the Int1 field enter the number of days that you want the system to add to the date/time the note was first saved. Values from 0 to 9999 are acceptable.
Additional Notes	1. Do not enter a decimal point in the Int1 field. 2. This setting affects notes for companies, resources (drivers, tractors, trailers, carriers) Pay To’s, commodities, orders, movements, invoices, and settlements. 3. Regardless of the options set in this key, you can manually set a different expiration date for a note in the Note Expires field. 4. By default, the Int1 field is blank. Once an entry is made in the field, you cannot delete the value to return the field to its blank state. You must save a value between 0-9999. The value 0 (zero) has the same meaning as blank.

SearchDuplicateAddress
Applies to	TMWSuite: 2006.05_10.0997 and later, CRM Right
Description	This setting determines whether the system will check for duplicate entries when a new company is being added. If a duplicate entry exists, the system displays a dialog box listing the duplicate(s). The system will not stop you from entering the record. This setting affects the File Maintenance application and the New Company quick add window, and the .NET version of the Company Profile window.
String1	• N (default) Do not check for duplicate entries. • Y Check for duplicate entries.
Additional Notes	1. To use this feature, you must have a value of OLD for the DistanceLookupVersion General Info Table setting. 2. This feature is designed to work in tandem with the CompanyIDFormat=Original setting in the [Misc] section of the TTS50.ini file.

ShowExpiredNotes
Applies to	TMWSuite: 2003 and later, CRM Right, Fuel Dispatch, TMW Operations
Description	Determines whether the system will show expired notes in the Notes window.
String1	• Y (default) The system will show all notes, including those that have expired. • N The system will not show expired notes.

ShowExpiredNotesGrace
Applies to	TMWSuite: 2003 and later, CRM Right, Fuel Dispatch
Description	This setting instructs the system to allow notes to display in the Notes window for a set number of days past their expiration date. After the grace period ends, the system hides the expired note.
Int1	• 0 (default) The system will show all notes, including those that have expired. • Value Enter the number of days you want expired notes to display.
Additional Notes	To use this setting, you must have ShowExpiredNotes=N in the General Info Table.

SmtpEmailer
Applies to	TMWSuite, CRM Right, TMW.Suite Operations, TMW.Suite 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.Suite Operations You can send load confirmations from the Brokerage add-on module. In TMW.Suite 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) 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 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.
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.

TrackBranch
Applies to	TMWSuite: 2005.04_10.0741 and later

Typically, a profile defines a single type of entity, such as a driver or company. TMWSuite users cannot change the definition of what such profiles represent, or how they are used in the system. However, branch profiles are profoundly different from other profiles because they are the only ones that are optional. If you choose to use them, your setup determines what they represent, as well as how they influence your use of the system.

This setting allows you to configure branch-related functionality. Values can be entered in its String1, String2, String3, and Int4 fields. Your entries in these fields allow you to use branch profiles to:

• Identify cost centers and tie them to user profiles.

• Identify booking terminals and executing terminals and tie them to user profiles. Additionally, you can identify the customer service and carrier service representatives who work for these terminals, and associate your companies and carriers with the terminals that service them.

• Identify booking terminals and executing terminals, and the representatives working at those terminals, without tying them to user profiles.

What you enter for a TrackBranch setting field varies, depending on the functionality you want to use. The descriptions in this document help you determine the entries that best suit your business.

Using branches to identify cost centers

By default, revenue types are used to group orders. Your company defines its groups using the RevType1 - 4 labels. When you create an order, you select one of your RevType1 values as its booking revenue type. The booking revenue type is identified in the Bk: RevType1 field. Once an order is saved, the booking revenue type cannot be changed.

Using RevType1 values is a simple way to track orders booked by specific terminals. However, because a terminal is represented by a label entry, there is no way to track other details about it. When you enable the branch tracking feature, you can use branch profiles to capture much more detail.

Typically, asset-based companies use branch profiles to represent cost centers. With this setup, the branch (cost center) is recorded on the order instead of the booking revenue type. If an order must be shifted to a different cost center, you can update the branch on the order to the correct cost center.

The entries described below set up the system to:

• Allow you to associate a user with a cost center in the user's profile.

• Automatically default users' cost center on the orders orders they create.

• Automatically use the user's cost center as a restriction in order lookup windows.

Required TrackBranch settings when using branches to identify cost centers
Applies to	TMWSuite: 2005.04_10.0741 and later
String1	Activates branch configuration functionality in TMWSuite. • Y The system requires orders to have a branch (cost center) specified before they can be saved. To facilitate meeting this requirement, the system allows users to be associated with branches (cost centers) in their profiles. When you do this, the system will: • Automatically stamp a user's cost center on the orders the user creates. • Allow the cost center to be changed after the order has been saved. • Allow a user to retrieve only orders for his/her own cost center in lookup windows. • Automatically stamp the user's cost center on any company, driver, tractor, trailer, or carrier profile the user creates. • Allow a user to retrieve only company and resource records associated with his/her own cost center in lookup windows.
String2	Identifies the source of the branch field name used throughout the system. • Branch The system uses the value recorded in the Branch label's Name field to identify branch fields throughout the system. Note: These windows will not display the name from the Branch label: • Find Invoices scroll window • Restrict Invoices on Hold • Restrict Invoices on Hold for Audit • Additional Header Information • Pay To File Maintenance • Restrict Settlement Data • Trips Ready to Settle retrieval queue
String3	This field is not applicable for using branches to identify cost centers.
Int4	This field is not applicable for using branches to identify cost centers.
Additional notes	For details on setting up branches as cost centers, see the File Maintenance guide's Branch File Maintenance chapter.

Using branches to track booking and executing entities' commissions

Brokerage operations may classify a branch as a booking terminal or an executing terminal in order to track revenue, costs, and the commissions due customer and carrier service representatives.

In TMWSuite, you can use branches as:

• Booking terminals, where customer service representatives perform order entry work.

• Executing terminals, where carrier representatives monitor the dispatch of third party carriers.

You use the Booking Terminal and Executing Terminal flags on branch profiles to identify their type. You can also use branches to represent customer service and carrier service representatives, and associate them with the terminals in which they work.

This branch profile setup is used by the Status Based Loads Grid add-on module. It is part of the Enhanced Brokerage license bundle. To use the module, you must associate:

• Customers with a booking terminal or a customer service representative.

• Carriers with an executing terminal or carrier service representative.

You can make the associations in branch profiles, or in the company and carrier profiles.

To set up the system for the Status Based Loads Grid module, you must make these entries:

Required TrackBranch settings when using branches to track booking and executing entities' commissions
Applies to	TMWSuite: 2005.04_10.0741 and later
String1	Activates branch configuration functionality in TMWSuite. • Y The system allows branches to be identified as: • Booking terminals, or the customer service representatives who work for them. • Executing terminals, or the carrier service representatives who work for them. It requires orders to have a booking entity specified before they can be saved. To facility meeting this requirement, the system allows users to be associated with both booking and executing entities in their profiles. It automatically stamps a user's booking entity on any orders he/she creates. By default, when a user uses a lookup window, he/she can retrieve: • Only orders stamped with his/her own booking entity. • Only resources associated with his/her own executing entity. Notes: 1. By default, branches can be only one type. If you need to have branches that are both booking and executing entities, you must have the BranchTerminalTypeRestricted=No setting in the [Dispatch] section of your TTS50.ini file. This INI setting is applicable only in TMWSuite. 2. When you are using this option to identify booking and executing terminals, you must also make entries in the String2 and String3 fields.
String2	Identifies the source of the booking terminal field name used throughout the system. • BookingTerminal The system will use the value recorded in the BookingTerminal label's Name field to identify booking terminal fields throughout the system.
String3	Identifies the source of the executing terminal field name used throughout the system. • ExecutingTerminal The system will use the value recorded in the ExecutingTerminal label's Name field to identify booking terminal fields throughout the system.
Additional notes	For details on using branches as booking and executing entities with the Enhanced Brokerage module, see the Status Based Loads Grid guide.

Using branches with CRM Right

CRM (Customer/Carrier Relations Management) Right CRM is a TMWSuite a calendar-based add-on application that enables customer service representatives and carrier service representatives to schedule and log customer and carrier-related calls, events, and tasks. It requires you to establish branch profiles for all of your booking and executing terminals, as well as the individual representatives assigned to them. This structure appears in the CRM Org Tree pane.

If you are using CRM Right without any of the Enhanced Brokerage modules, you can set up the system to:

• Allow you to create the branch profiles in CRM Right.

• Associate companies and carriers with their appropriate representatives.

If you are using CRM Right with the Enhanced Brokerage module, you must use the setup described in the Using branches to track booking and executing entities' commissions section.

Required TrackBranch settings when using branches with CRM Right
Applies to	CRM Right
String1	Branch configuration functionality is not turned on in TMWSuite. The system does not require orders to have a branch specified or apply the user's branch as a look up restriction. • N (default)
String2	An entry in this field is not required to identify the source of the booking terminal field name used in CRM Right. The system automatically uses the name recorded in the BookingTerminal label's Name field.
String3	An entry in this field is not required to identify the source of the booking terminal field name used in CRM Right. The system automatically uses the name recorded in the ExecutingTerminal label's Name field.
Int4	Activates branch configuration functionality in the CRM Right add-on module. • 1 The system allows you to create branch profiles for: • Booking terminals, or the customer service representatives who work for them. • Executing terminals, or the carrier service representatives who work for them. You must associate your customers with the customer service reps assigned to their accounts and your carriers with the carrier reps assigned to them from within CRM Right. Note: If you determine that you no longer want to use the functionality provided by this option, you must enter a 0 (zero) to disable it.
Additional Notes	1. For details on using CRM Right, see the CRM Right help, or the CRM Right guide, which is the PDF version of the help. 2. By default, this set up does not add the Booking Terminal and Executing Terminal check boxes to the CRM Right Branch Maintenance window. You must add them. For more information on using QuickDesigner to add the check boxes, see the Adding fields to a window topic in the CRM Right documentation.