General Info Table settings that are found in Interface Settings

These General Info Table settings are saved within the TMWSuite database. They are listed in alphabetical order, but appear in the various locations in Interface Settings.

A - EDI210F

AddGeoLocationToEDI214

Applies to

TMWSuite, EDI, TMW Operations

Description

Use this setting to include the current tractor location in the 439 record in this format: 2 miles west of Toledo, OH.

String1

N (default)
Add a 439 record that displays the tractor’s current location.
Y
Do not create a 439 record with the tractor’s current location.

Auto214Flag

Applies to

TMWSuite, EDI, TMW Operations

Description

Determines whether TMWSuite or TMW Operations will automatically produce 214s when the status of each stop on an order meets the profiled criteria for the trading partner.

String1

no (default)
The system does not produce 214s automatically.
yes
The system produce 214s automatically when the status of the stop matches the criteria recorded in the trading partner’s company profile.
- TMWSuite: The Auto 214 tab located in the File Maintenance application’s EDI Codes Maintenance window
- TMW Operations: The Auto 214s tab located in the Interface Settings application’s Customer EDI Codes window

Additional Notes

It is recommended that you set enter the value for this setting in the File Maintenance application’s EDI Codes Maintenance or Interface Settings application’s Customer EDI Codes window. When you enter a value in the Auto214 Enabled field on the All Partner Settings tab, it is transferred to this key.
You must have the EDI 214 Shipment Status SmartLink license to view the Auto214 Enabled field and use auto-214s.

E210NoZero3

Applies to

TMWSuite, EDI, TMW Operations

Description

Determines whether invoice detail lines with a zero dollar ($0) amount appear as 3 records in an EDI 210.

Note: It is recommended that you set this option in the File Maintenance application’s EDI Codes Maintenance or Interface Settings application’s Customer EDI Codes window. When you enter a value in the Eliminate zero charge lines field on the All Partner Settings tab, it is transferred to this key.

String1

no (default)
Include invoice detail lines with a zero dollar ($0) amount as 3 records in a 210 flat file.
yes
Do not include invoice detail lines with a zero dollar ($0) amount as 3 records in a 210 file.

EDI_AddRevtype

Applies to

TMWSuite, EDI, TMW Operations

Description

Determines if an order’s revenue type abbreviations are exported to 214s and 210s. By specifying a revenue type, you activate the feature.

String1

Blank, that is, no entry (default)
No rev type abbreviation appears on 214s or 210s.
User-specified revenue type
Make your entry as RevType1, RevType2, etc. The abbreviation for the specified revenue type listed on the order are exported.
- On 214s, it appears in position 127 on the 139 record.
- On 210s, it appears in position 167 on the 139 record.

EDI_AddrLine2

Applies to

TMWSuite, EDI, TMW Operations

Description

Specifies whether the 239 record shows the Bill To’s Address 2 information.

This setting applies to 210 and 214 flat files.

String1

no (default)
Do not include the Bill To’s address line 2 information in the flat file.
yes
Include the Bill To’s address line 2 in the 239 record of the flat file.

EDI_auto214_preprocess

Applies to

TMWSuite, EDI, TMW Operations

Description

Specifies the name of a client-specific stored procedure to run before processing Auto 214 records

String1

UNKNOWN (default)
No client-specific stored procedure is run before processing Auto 214 records
User-specified name
Enter the name of a client-specific stored procedure to run before processing Auto 214 records.

EDI_EnableLTLOutput

Applies to

TMWSuite, EDI, TMW Operations

Description

Enables processing and output required by LTL Dispatch application requires for order-based 214 activities.

String1

N (default)
Does not enable processing needed for LTL order-based 214 activities
Y
Enable processing and output required by LTL order-based 214 activities

EDI_ExtractbyTP

Applies to

TMWSuite, EDI, TMW Operations

Description

Part of the EDI setup includes setting default folder locations for 210 and 214 flat files. You specify these locations using the [EDIfilesave]210data and [EDIfilesave]214data settings in your TTS50 file.

This setting allows you to modify the default path of the EDI 210 and 214 flat file folders for each trading partner.

String1

N (default)
Only the specified directories are used. The 210 and 214 flat file data for all trading partners are written to the specified folders.
Y
Allow the location of 210 and 214 flat file folders to be set on a trading partner-by- trading partner basis.

When you use this option:

The 214 Save Path and 210 Save Path fields are added to the Partner Info tab in the File Maintenance application’s EDI Codes Maintenance or Interface Settings application’s Customer EDI Codes window.

EDI_GenerateETAOnCreation

Applies to

TMWSuite, EDI, TMW Operations

Description

Controls whether the system generates ETA Auto-214s automatically when you create an order.

String1

N (default)
Do not generate ETA Auto-214s automatically when an order is created.
Y
Generate ETA Auto-214s automatically when an order is created.

EDI_Notification_Process_Type

Applies to

TMWSuite 2003.03_03.0469 and later, EDI, TMW Operations

Description

Determines whether auto-214s will be Bill To- or company-based.

String1

1 (default)
Auto-214s are Bill To-based. The auto-214 is sent only if the order’s Bill To company is set up as a trading partner with activities on the Auto 214 tab.

Note: This is the default for most EDI trading partners.
2
Specifies a company-based notification. The trading partner may appear as a Bill To, shipper, consignee, or Order By on the order. The auto-214 is sent based on which company type is specified for the trading partner.

Additional Notes

This setting applies only to auto-214s.
Based on your system, we recommended setting this option in the applicable location:
- TMWSuite: The File Maintenance application’s EDI Codes Maintenance window
- TMW Operations: The Interface Settings application’s Customer EDI Codes window
When you enter a value in the EDI Notification Method field on the All Partner Settings tab, it is transferred to this setting.

EDI_RestrictByTerms

Applies to

TMWSuite, TMW Operations

Description

Use this setting to determine whether the EDI 214: Restrict Creation by Credit Terms and EDI 210: Restrict Creation by Credit Terms fields appear in the Partner Info tab in the EDI Codes Maintenance window. These fields allow you to specify whether the credit terms recorded on each order or invoice must match the credit terms recorded for the trading partner.

String1

N (default)
The fields do not appear in the EDI Codes Maintenance window. You cannot restrict the creation of 214 and 210 files based on the credit terms recorded for the trading partner.
Y
The fields appear in the EDI Codes Maintenance window. You can use the field options to restrict the creation of 214 and 210 files based on the credit terms recorded for the trading partner.

Notes:
1. The following options are available for each field:
  - Allow All
    All 214 and 210 messages will be created, regardless of the credit terms recorded for the order/invoice.
  - Prepaid Only
    The 214/210 files will be created only for orders/invoices with Prepaid (PPD) credit terms.
  - Collect Only
    The 214/210 files will be created only for orders/invoices with Collect (COL) credit terms.
2. This setting affects both the manual and automatic creation of 214/210 messages.

EDI204AllowFuelCity

Applies to

TMWSuite, EDI, TMW Operations

Description

This setting allows Data Exchange to match cities listed on inbound 204 files with those created using the Fuel Import application.

String1

N (default)
Do not match cities on inbound 204 files with unverified cities created in the Fuel Import application.
Y
Match cities listed on inbound 204 files with those created using the Fuel Import program.

Additional Notes

This setting applies to any batch import programs that flag new cities as unverified.

EDI210_DeliveryDateTime

Applies to

TMWSuite, EDI, TMW Operations

Description

Determines if the system adds a miscellaneous record at the header level. This record includes the delivery date and time.

String1

N (default)
Do not add a miscellaneous record.
Y
Add a miscellaneous record.

EDI210_EquipmentRef

Applies to

TMWSuite, EDI, TMW Operations

Description

Specifies the asset types that can be included as a 539 record in the 210 flat file.

Note: A 539 record consists of the following information:

Miscellaneous record type identifier: _EQ.
Qualifier specified by this setting: TRL, TRC, or DRV.
Matching asset ID that has been pulled from the order.
For example: 539_EQTRCTRC01.

String1

Blank, that is, no entry (default)
The system will not include 539 asset type information.
User-specified asset type(s)
Enter the asset type(s) that will be included as a 539 record in the 210 flat file. If including more than one type, separate entries with commas. Do not add spaces between entries (for example, TRL,TRC,DRV).

Valid asset types are:
- TRL
  The trailer ID recorded on the order will appear in the 539 record.
- TRC
  The tractor ID recorded on the order will appear in the 539 record.
- DRV
  The driver ID recorded on the order will appear in the 539 record.

EDI210_StopsBeforeCharges

Applies to

TMWSuite, EDI, TMW Operations

Description

Determines the order in which these records appear in the Flat210 file.

Type 439 stopoff
Type 339 charge detail

String1

N (default)
Present the type3 charge detail records before type4 stopoff records.
Y
Present the type4 stopoff records before type3 charge detail records.

EDI210_TotalMiles

Applies to

TMWSuite, EDI, TMW Operations

Description

Determines whether the total number of miles recorded on the invoice appears as a 539 record in the 210 flat file’s header.

String1

No (default)
Do not include the invoice total miles.
Yes
Include the total miles for the invoice as a miscellaneous 539 record.

Note: The qualifier, _MS TMI, precedes the number of miles in the record.

EDI210AdvOutputSelection

Applies to

TMWSuite

Description

This setting determines the options available in Company File Maintenance for handling a Bill To company’s invoices. You can:

Apply the same output method to all of the Bill To’s invoices.
Apply output methods based on invoice type, definition, and credit terms.

Note: Starting in TMWSuite V.2019.1, this setting and following locations are no longer used to set up invoice outputs:

The EDI 210 field in the company profile
The Advanced EDI Output Settings window in the company profile

Instead, you set up invoice outputs in the Billing Output Configuration Folder in File Maintenance. To access the window, go to Edit > Company Billing Output.

String1

N (default)
Display the EDI 210 field in Company File Maintenance. The field options allow you to specify how all of the Bill To’s invoices will be handled.
- Print Only (default)
  Invoices will be printed.
- EDI Only
  Invoices will be sent as an EDI 210 (electronic invoice).
  
  Note: Rebill information will also be sent as a 210.
- Print & EDI
  Invoices will be both printed and sent as an EDI 210 document.
- EDIOrig/PrintRebill
  Original invoices will be sent only as an EDI 210. Rebilled invoices will be printed. The 210 will not be resent with the rebill.
Y
Display the Invoice Output Method button in Company File Maintenance. Clicking the button displays the Advanced EDI Output Settings window. Window features allow you control invoice handling for each Bill To company based on invoice type, definition, and credit terms.

Notes:
1. If no options are specified in the Advanced EDI Output Settings window, all invoices will be printed.
2. If an option was previously specified for a company in the EDI 210 field, that option is used for all invoices for the Bill To.

EDI210CargoRecs

Applies to

TMWSuite, EDI, TMW Operations

Description

Determines whether the system will add a 739 cargo record in the 210 flat file for each freight detail recorded on the stop.

String1

No (default)
Do not include cargo records in the 210.
Yes
Include a 739 cargo record in the 210 for each freight detail on the stop.

EDI210EqptTypeSource

Applies to

TMWSuite, EDI, TMW Operations

Description

This setting determines the source of the trailer value used in the 139 record in the 210 flat file’s header.

String1

Type1 (default)
The trailer value comes from the TrlType1 field in the profile of the trailer assigned on the order.

You may enter Type2, Type3, or Type4 to have the trailer value come from the TrlType2, TrlType3, or TrlType1 field.

Note: If no trailer is assigned on the order, the value comes from the corresponding field in the profile of the tractor assigned on the order.
OrdType1-4
The value comes from the corresponding trailer type field on the order header.

Note: If there is no trailer type recorded in the order header, the system will not add a value in the 139 record at column 161.
OptType4
This option is custom.

EDI210ExistWarning

Applies to

TMWSuite, EDI, TMW Operations

Description

Indicates whether to display a warning message if users try to transfer EDI data that already exists.

String1

N (default)
Do not display a warning message if users try to transfer existing EDI data.
Y
Display a warning message if users try to transfer existing EDI data.

EDI210ExportSTCC

Applies to

TMWSuite, EDI, TMW Operations

Description

Determines if a commodity’s Standard Transportation Commodity Code is included in 210 flat files. When enabled, the value comes from the Commodity Profile window’s STCC field. It is used as a 539 freight reference and appears after the 439 record.

String1

No (default)
Do not include STCC codes.
Yes
Include the STCC field value from the commodity profile.

Notes:
1. The reference qualifier appears as 539REFSTC<STCC code>.
2. If there are multiple commodities on a stop, all codes on the record are included.

EDI210FgtSupplierLocationCode

Applies to

TMWSuite, EDI, TMW Operations

Description

Displays the supplier EDI location code in the output.

String1

Y (default)
Display the supplier EDI location code in the output.
N
Do not display the supplier EDI location code.

Version number
EDI 210 flat file version number

Additional Notes

The recommended entry is 3.9.
It is recommended that you set this option in the File Maintenance application’s EDI Codes Maintenance or Interface Settings application’s Customer EDI Codes window. When you enter a value in the 210 Version field of the All Partner Settings tab, it is transferred to this key.

EDI210WriteInvDate

Applies to

TMWSuite, EDI, TMW Operations

Description

Determines whether the invoice bill date appears as a 539 record in the 210 flat file.

String1

no (default)
Do not include the invoice bill date in the 210.
yes
Include the invoice bill date as a 539 record in the 210 flat file.

Note: The qualifier, DTIDT, precedes the date.

EDI214_AddOSDRef

Applies to

TMWSuite, EDI, TMW Operations

Description

A 214 file’s 639 record is a lading exception record. It provides information about overages, shortages, and damages (OSD). Use this setting to specify the reference number types that will be included in the 639 record.

String1

Blank, that is, no entry (default)
Do not include reference numbers.
User-defined list
Enter a comma-separated list of reference number types that will be added to the OSD record; for example, BL#,REF,SID,ST#.

Notes:
1. Your entries must match the values recorded in the ReferenceNumber label’s Abbr field. The label is accessed in System Administration.
2. Reference numbers of the types specified here are appended to the end of each 639 record. The first 15 characters are used.

EDI214_AddTrlTwo

Applies to

TMWSuite, EDI, TMW Operations

Description

If a secondary trailer is used on an order, use this setting to include the Trailer 2 ID in the 339 record of the 214 file.

String1

N (default)
Do not include the Trailer 2 ID in the 339 record.
Y
Include the Trailer 2 ID in the 339 record.

EDI214_DeliveryDateTime

Applies to

TMWSuite, EDI, TMW Operations

Description

Use this setting to include the estimated or actual order complete date/time in every 214 file. The information appears in a 439 record. The record is found in the order header section of each 214.

String1

N (default)
Do not include the "439_DTRDT" delivery date/time in the 214.
Y
Include the "439_DTRDT" delivery date/time in the 214.

EDI214_EarliestLatest

Applies to

TMWSuite, EDI, TMW Operations

Description

Use this setting to include the scheduled Earliest and Latest date/time for each stop in the 214 file. The information appears in a 439 record. It follows the record for each stop.

String1

N (default)
Do not include the scheduled earliest and latest date/time for each stop in the 214.
Y
Include the scheduled earliest and latest date/time for each stop in the 214.

EDI214_ETALocationReport

Applies to

TMWSuite, EDI, TMW Operations

Description

This setting allows you to specify what is sent when the arrival date/time for a stop is updated. You can send:

A location report or an estimated arrival (ESTA) message.
Both a location report and ESTA message.

The message will include the updated arrival date/time and the current GPS data for the tractor assigned to the order.

Notes:

You must set up the system for the location report and ESTA message in the Auto 214 tab in the EDI Codes Maintenance window.
- For the location report, use the Est. Arrival Location option in the Activity field.
- For the ESTA message report, use the Est Arrival Revised option in the Activity field.
This setting applies to auto-214 files only.

String1

N (default)
Send both the location report and ESTA message.
Y
Send only the ESTA message.
O
Send only the location report.

Additional Notes

For more information, see the Setting up activities to trigger an auto-214 section in the Working with EDI 214 Status Updates chapter of the TMWSuite EDI Interface guide.

EDI214_MultiBOL

Applies to

TMWSuite, EDI, TMW Operations

Description

Use this setting to create a separate 214 for each bill of lading reference number recorded for an order header. A unique document ID will be assigned to each 214. A unique bill of lading reference number will appear in the 139 record of the 214.

String1

N (default)
Do not create a separate 214 for each bill of lading reference number.
Y
Create a separate 214 for each bill of lading reference number.

Notes:
1. Setting up a trading partner’s EDI profile to create a separate 214 for each stop reference number overrides this option for that trading partner. The system will not create multiple header-level BOL reference numbers. It will create a 214 for each stop reference number of the specified type.
2. For information about creating 214s for stop reference numbers, see the Recording the trading partner’s 214 requirements section in the Setting up TMWSuite for EDI chapter of the General EDI guide and in Interface Settings online help.

Additional Notes

This setting is applicable only when you are licensed for EDI 214 Shipment Status SmartLink.

Applies to

TMWSuite, EDI, TMW Operations

Description

Determines whether the 639 lading exception record in a 214 flat file contains overage, shortage, and damage information. This information is recorded for a freight detail in the Dispatch Trip Folder. Values come from these fields:

OSD Reason
OSD Qty
OSD Unit
OSD Comment

String1

No (default)
Do not include the OSD field data in the 214 flat file.
Yes
Include the entries from the OSD fields in the Freight Detail grid as a 639 record in the 214 flat file.

For example, a lading exception containing data for an overage of 65 cases displays in a 639 record as OCAS6500comment.

Applies to

TMWSuite: 2015.14_07.0590, EDI, TMW Operations: 15.40.107

Description

Use this setting to include the source application and user ID in 214 files. The information will appear in an additional miscellaneous/439 record in the order header section of each 214.

String1

N (default)
Do not include the source application and user in 214 files.
Y
Include the source application and user ID in 214 files.

Notes:
1. In the miscellaneous/439 record, the source application appears as 439REFAPPxxxxxxxxxx.
2. In the miscellaneous/439 record, the user ID appears as 439REFUIDxxxxxxxxxx.

EDI214ApptTrigger

Applies to

TMWSuite, EDI, TMW Operations

Description

Identifies which event will trigger Set Appointment Auto 214s.

String1

T (default)
Change the earliest and latest times to one new time.
S
Actualize an SAP event arrival.
B
Change both the earliest and latest times to a new time and actualize an SAP event arrival.
L
Change the latest time.

EDI214CancelRefAfterOrderRefs

Applies to

TMWSuite, EDI, TMW Operations

Description

Specifies whether the cancel status code is placed before or after reference numbers in a cancellation 214 flat file.

String1

N (default)
Include the cancel status before reference numbers in the cancellation 214 flat file.
Y
Include the cancel status after order header reference numbers in the cancellation 214 flat file

For example, PO# is listed before the cancel status.

EDI214CargoRecs

Applies to

TMWSuite, EDI, TMW Operations

Description

Determines whether the system will add a 739 cargo record in the 214 flat file for each freight detail recorded on the stop.

String1

N (default)
Do not include cargo records in the 214.
Y
Include a 739 cargo record in the 214 for each freight detail on the stop.

EDI214ExportSTCC

Applies to

TMWSuite, EDI, TMW Operations

Description

Determines whether the entry recorded in the STCC (Standard Transportation Commodity Code) field in a commodity’s profile will be included as a freight reference after the 439 record of 214 flat files.

String1

No (default)
Do not include STCC codes after the 439 record.
Yes
Include the STCC field value from the commodity profile as a freight reference after the 439 record.

Notes:
1. The reference qualifier appears as 539REFSTC<STCC code>.
2. If there are multiple commodities on a stop, all codes on the record are included.

EDI214GPSLocationforESTA

Applies to

TMWSuite, EDI, TMW Operations

Description

Specifies whether the most recent TotalMail check call information is used for the pickup or delivery in the 239 record of ESTA Estimated Arrival activity auto-214s.

String1

No
Use the stop company location information (city, state, and ZIP Code) in the 239 record.
Yes
Include city, state, and ZIP Code data from the most recent TotalMail check call on the 239 record, instead of the stop company location.

Note: The arrival or departure activity must be actualized to trigger the Estimated Arrival EDI 214 status, which in turn sends the auto-214.

EDI214lateAR

Applies to

TMWSuite, EDI, TMW Operations

Description

Determines whether a 214 will be sent upon a late arrival.

String1

No (default)
The system will not send a 214 upon a late arrival.
Yes
The system will send a 214 upon a late arrival.

Note: Do not use this option if you selected the Don’t send if late/no reason check box on the Auto 214 tab when setting up your trading partners. You can access the tab from:
- The File Maintenance application’s EDI Codes Maintenance window
- The Interface Settings application’s Customer EDI Codes

EDI214PENDINGDELAY

Applies to

TMWSuite, EDI, TMW Operations

Description

Specifies how many seconds the system will wait to send a pending auto-214 flat file after a 214 has been processed.

String1

0 (default)
Do not include a delay when waiting to send a pending auto-214 flat file.
User-defined time delay
Enter the number of seconds (recommended length: 1 through 59).

Note: Be careful with this setting, especially when setting it higher than 59 seconds. It can cause delays of 214s.

EDI214PlannedConsolidation

Applies to

TMWSuite, EDI, TMW Operations

Description

Determines if the Consolidated Changed option appears in the Activity field located on the Auto 214s tab.

String1

N (default)
Do not display the option.
Y
Display the option.

EDI214R - SCAC

EDI214ReportLocationWhenParked

Applies to

TMWSuite, EDI, TMW Operations

Description

Continue sending 214 status updates at a specified interval when no new Location Report/check call has been received. For example, when a tractor is parked, its location does not change. You can have the system continue sending Location Reports while a tractor is parked.

String1

N (default)
Do not continue sending 214 status updates.
Y
Continue sending 214 status updates at the specified interval.

Notes:
1. By default, each Location Report includes the date/time of the last status update sent from the check call location. You can use the EDI214UseCurrentTimeWhenParked General Info Table setting to include the current date/time instead.
2. For information about setting the interval of TotalMail position report transfers to the TMWSuite check calls table, see the TotalMail System Administrator guide.

Additional Notes

This feature requires the EDI Scheduler and EDI 214 Shipment Status SmartLink licensed add-ons, which must be purchased from TMW.

EDI214RequireDriverMatchOnX6

Applies to

TMWSuite: 2014.13_07.0644, EDI, TMW Operations

Description

Use this setting to set up your system to record Location Reports in an EDI 214 for either of these situations:

* The driver and tractor in a check call are not linked * The driver is recorded as UNKNOWN in the check call

String1

N (default)
Do not record Location Reports in the 214 when the driver and tractor are not linked, or when the driver is recorded as UNKNOWN.
Y
Record Location Reports in the 214 when the driver and tractor are not linked, or when the driver is recorded as UNKNOWN.

Additional Notes

To use this feature, you must have String1 set to Y in the ManualCheckCall General Info Table setting.
Before TMWSuite 2014.13_07.0644, the driver and tractor recorded in the check call must be linked in File Maintenance or TotalMail. Otherwise, the Location Report will not be recorded in the EDI 214

EDI214UseCurrentTimeWhenParked

Applies to

TMWSuite 2013.12_08.0891, EDI, TMW Operations

Description

When you set up the system to continue sending 214 status updates while the truck is parked, each Location Report sent includes the date/time of the last status update sent from the check call location.

Note: Sending 214 status updates when the truck is parked requires a String1 value of Y for the EDI214ReportLocationWhenParked General Info Table setting

Use this setting to substitute the current date/time in location reports for the date/time of the last status update.

String1

N (default)
Include the date/time of the last status update sent from the check call location in each Location Report.
Y
Include the current date/time in each Location Report.

Additional Notes

This feature requires the EDI Scheduler and EDI 214 Shipment Status SmartLink, which are licensed add-ons that you must purchase from TMW.

EDI214UseDestCityForAG

Applies to

TMWSuite, EDI, TMW Operations

Description

By default, when the next arrival time has the AG (estimated arrival) status, the date/time for the next stop is recorded in the 214 file’s 339 Status record. The location recorded in the 214 is the city/state for the stop that generated the 214.

This setting also allows you to specify whether the 339 Status record displays the city/state for the stop that generated the 214, or the city/state for the next drop or pickup stop.

String1

N (default)
When the next arrival time has the AG status, display the city/state for the stop that generated the 214 in the 339 record.
Y
When the next arrival time has the AG status, display the city/state for the next drop or pickup stop in the 339 record.

String2

If String1 is set to Y, specify whether the 339 Status record will display the city/state for the next drop or pickup stop. Options include:

DRP (default)
Display the date/time and city for the next drop stop.
PUP
Display the date/time and city for the next pickup stop.
ANY
Display the date/time and city for the next pickup or drop, whichever occurs first.

Note: When no subsequent pickup stop exists, the date/time and city for the final drop stop are displayed.

EDI214Ver

Applies to

TMWSuite, EDI, TMW Operations

Description

Use this setting to specify the version of the EDI 214 flat file that you are using.

String1

The recommended entry is 3.9.

Note: When you enter a value in the 214 Version field on the All Partner Settings tab, it is transferred to this key.

EDI856_Processing

Applies to

TMWSuite, EDI, TMW Operations

Description

Use this setting to indicate whether to export freight information when sending outbound 214s. This information is also mapped to the 856 freight record.

String1

N (default)
Do not export freight information when sending outbound 214s or map the information to the 856 freight record.
Y
Export freight information when sending outbound 214s or map the information to the 856 freight record.

EDI856_StatusCodes

Applies to

TMWSuite, EDI, TMW Operations

Description

A 214 is an outbound document that informs the shipper or consignee of the order’s status.

This setting controls:

Retrieval of 856 status codes information
Display of OSD information in the 214.

Before using this setting, make sure you have:

Created 856 X12 documents for affected trading partners that send information to the shipper and import information to the 856 table. Be sure to instruct trading partners that they must include the order number on the 856.
Set up the DX custom 856 import script. Contact EDI support to do this.
Set the String1 value for the EDI856_Processing General Info table setting to Y. This allows you to send information gathered from the 856 to the 214s.

String1

Your entry determines whether OSD information is included in the 214’s 639 records.

Blank, that is, no entry (default)
Do not send shipment OSD information with any 214.
User-specified statuses

Include shipment OSD information for 214s having the specified statuses.

Enter the 214 statuses you want to use. Your entry must exist in the EDI Status(es) field for an activity for a trading partner.

The field is found on the Auto 214s tab. You access the tab in the Interface Settings or the File Maintenance application. Separate your entries with commas. Do not add spaces between them.

String2

Your entry determines whether warehouse OSD information is included in 639 records for shipments.

Blank, that is, no entry (default)
Do not send the warehouse OSD information.
User-specified statuses

Include warehouse OSD information for 214s having the specified statuses.

Enter the 214 statuses you want to use. Your entry must exist in the EDI Status(es) field for an activity for a trading partner.

The field is found on the Auto 214s tab. You access the tab in the Interface Settings or the File Maintenance application. Separate your entries with commas. Do not add spaces between them.

String3

Blank, that is, no entry (default)
Do not send the delivery OSD information.
User-specified statuses

Include the delivery OSD information on 214s having the specified statuses.

Enter the 214 statuses you want to use. Your entry must exist in the EDI Status(es) field for an activity for a trading partner.

The field is found on the Auto 214s tab. You access the tab in the Interface Settings or the File Maintenance application. Separate your entries with commas. Do not add spaces between them.

String4

Blank, that is, no entry (default)
Do not send the load OSD information.
User-specified statuses

Send the load OSD information on 214s having the specified statuses.

Enter the 214 statuses you want to use. Your entry must exist in the EDI Status(es) field for an activity for a trading partner.

The field is found on the Auto 214s tab. You access the tab in the Interface Settings or the File Maintenance application. Separate your entries with commas. Do not add spaces between them.

EDIBookedByAccept

Applies to

EDI, TMW Operations: 3.125.52.43 and later

Description

By default, when the Data Exchange application imports a 204 load tender, the letters DX are recorded as the Booked By ID for the order.

Use this setting to update the Booked By for an order to the user ID of the person who accepted the order.

String1

N (default)
Retain DX as an order’s Booked By ID, even after a specific user accepted the order.
Y
Change the Booked By to the user ID of the person who accepted the order.

EDIRefCustomSort

Applies to

TMWSuite, TMW Operations

Description

Specifies the sequence in which reference number types will display in 214s and 210s.

String1

Blank, that is, no entry
The system will not display reference number types in 214s and 210s
User-assigned reference type(s)
Enter a comma separated list of reference types, e.g., BOL,PO#,SID in the String1 field from first to last.

EDISecondsWait

Applies to

TMWSuite, EDI, TMW Operations

Description

Specifies how many seconds the system will wait to send a 210 invoice after printing an invoice. This allows you to free valuable database server space for other applications.

String1

0 (default)
Send a 210 invoice immediately after printing an invoice.
User-specified number of seconds (1-59)
Specify the number of seconds to wait until sending a 210 invoice after printing.

EDIUseCompanyFaxForAuto214

Applies to

TMWSuite, TMW Operations

Description

Specifies whether the Use Company Fax # For EDI Email/Fax check box is selected by default in the EDI Code Maintenance window’s All Partner Settings tab.

String1

YES (default)
The Use Company Fax # For EDI Email/Fax check box is selected. The fax number on the Bill To company profile will be used for auto-214s.
NO
The Use Company Fax # For EDI Email/Fax check box is not selected.

Additional Notes

When the Use Company Fax # For EDI Email/Fax field of the All Partner Settings tab is selected, this setting’s String1 field will display as YES. If the field is unselected, this setting will display as NO.

EDIWrap

Applies to

TMWSuite, EDI, TMW Operations

Description

Defines the type of wrapper records you are using for flat files. Wrapper records are required to group together all documents for the same customer. The wrapper records act as a separator.

String1

FULL (default)
A #TMW record and \\P record appear at the front of all documents for the same trading partner. A #EOT record appears at the end. If you specify this entry, one wrapper will group together all invoices for a single trading partner.

Note: If you use Kleinschmidt or ValueEDI, make this your entry.
PART
A \\P record appears at the front of each document for the same trading partner. If you specify this entry, an individual wrapper is put around each invoice.

Note: If you use Visual or ProEDI, make this your entry.

Additional Notes

When #TMW,\\P,<data>,#EOT is entered in the Wrap flat file recs for partner with field of the All Partner Settings tab, FULL displays for this key. If \\P,<data> is entered in the field, PART displays for this key.

Localtimezone

Applies to

TMWSuite: 2014.13_07.0242, EDI, TMW Operations

Description

In City File Maintenance, the Time Zone field allows you to specify the Greenwich Mean Time (GMT) offset for each location. For example, cities in the Eastern Time Zone of the United States have a GMT offset of -5 hours.

This setting allows the system to use the GMT offset to record the local date/time for each event in an EDI 214 instead of the date/time of the dispatch system.

String1

LT (default)
The system records the dispatch system date/time for each event.

Note: When you use this option, the value recorded for String2 does not change how date/time is calculated.
CI
The system records the date/time of the city in which the event takes place.

Note: When you use this option, you can use String2 to include the GMT offset.

String2

Blank, that is, no entry (default)
The system records the dispatcher system date/time for each event.
Y
The system adjusts the date/time for each event based on the GMT offset in each location’s city profile.

Notes:
1. This option is valid only when String1 is set to CI.
2. If no GMT offset is specified in a location’s city profile, the date/time for each event at that location will reflect the dispatcher’s system date/time.

LTSLForceRevTypes

Applies to

TMWSuite, EDI, TMW Operations

Description

Use this setting to require that accepted EDI orders include revenue types. You can specify that any or all RevType1-4 fields must have values other than UNKNOWN.

String1

An entry in this field relates to the RevType1 field.

N (default)
No RevType1 value is required to accept an EDI order.
Y
Accepted orders must have a RevType1 field value other than UNKNOWN.

String2

An entry in this field relates to the RevType2 field.

N (default)
No RevType2 value is required to accept an EDI order.
Y
Accepted orders must have a RevType2 field value other than UNKNOWN.

String3

An entry in this field relates to the RevType3 field.

N (default)
No RevType3 value is required to accept an EDI order.
Y
Accepted orders must have a RevType3 field value other than UNKNOWN.

String4

An entry in this field relates to the RevType3 field.

N (default)
No RevType4 value is required to accept an EDI order.
Y
Accepted orders must have a RevType4 field value other than UNKNOWN.

LTSLMatchCompaniesLatLong

Applies to

TMWSuite, EDI, TMW Operations

Description

Use this setting to have the system apply the latitude and longitude for new companies created using the Company Matching feature.

String1

N (default)
Do not include latitude and longitude for new companies.
Y
Include latitude and longitude for new companies.

LTSLResponseOverrides

Applies to

TMWSuite, EDI, TMW Operations

Description

You may have EDI trading partners for which you want to hold 990 responses and keep them queued until assets are assigned. Use this setting to identify those companies.

String2

Blank, that is, no entry
Automatically send a 990 response for each 204 file you receive. Responses will be sent to all trading partners.
User-specified trading partner name(s)
Do not automatically send 990 responses to all trading partners. Instead, queue them for specified trading partners. When assets are assigned to the order, send the 990.

LTSLUsingVisualEDI

Applies to

TMWSuite, EDI, TMW Operations

Description

This field affects the size of the EDI trading partner ID in the #TMW line of the outbound 990.

String1

N (default)
The full value of the trading partner ID is included.
Y
The system limits the trading partner ID to 10 characters.

LTSLWrkshtOverrides

Applies to

TMWSuite: 2008.07_08.0580 and later, TMW Operations

Description

This setting specifies the types of load tender orders that display in the Planning Worksheet’s EDI grid.

String1

Your entry in the String1 field determines whether only load tenders that require a decision are displayed.

N (default)
The system displays all load tender orders.
Y
The system displays only orders requiring a decision. Once the accept/ decline decision for an order is processed, the system removes those orders.

String2

Your entry in the String2 field determines whether pending 990s are displayed.

N (default)
The system does not display 990s.
Y
The system displays pending 990s.

String3

List additional customized LTSL 2 states that will display in the EDI grid.

ManualEDIUseReasonLate

Applies to

EDI, TMW Operations: 3.125.52.325

Description

In TMW Operations, you use the Create EDI 214 window to generate EDI 214s manually. In the window, the Status Reason field identifies the reason for an event status.

This setting determines two things:

Whether the available reason codes come from the EDI214Reason label or ReasonLate label in System Administration.
The source of the EDI code recorded in the 214.

String1

N (default)
The available options come from the EDI214Reason label.

The value in the label’s Abbr field is used in the 214.
Y
The available options come from the ReasonLate label.

The EDI code recorded in the 214 will come from either the ReasonLate label or the Reason Codes tab in the EDI Codes Maintenance window.
- If the Status Reason matches a reason code recorded for the trading partner, the EDI code recorded for that reason code is used in the 214.
  
  This allows you to use customized status codes for each EDI trading partner.
  
  Note: You record reason codes for trading partners in the File Maintenance application’s EDI Codes Maintenance or Interface Settings application’s Customer EDI Codes window.
- If the Status Reason does not match a reason code recorded for the trading partner, the value in the Abbr field of the ReasonLate label is used in the 214.

ReqSchChangeReason

Applies to

TMWSuite 2002.02_05.0054 and later, EDI, TMW Operations

Description

This setting determines whether users must specify a reason code for an appointment change when the Bill To on the order is set up for the EDI 214 service. This setting applies to stops with previously scheduled appointments.

Notes:

You enter reason codes in the Schedule Dates Change Log.
The Schedule Dates Change Log appears only for Bill To’s that have schedule change reasons configured for them on the Sch Reasons tab.
You access the Sch Reasons and Default Sch Reason tabs in:
- TMWSuite - The File Maintenance application’s EDI Codes Maintenance window
- TMW Operations - The Interface Settings application’s Customer EDI Codes window.
- String2 applies only to TMW Operations.

String1

TMWSuite
- NONE (default)
  No reason is required when a trip’s Earliest or Latest date/time is changed.
- SPECIFIC
  When the Earliest or Latest date/time is changed in the Trip Folder, the user must select a schedule change reason specific to the Bill To in the Schedule Dates Change Log.
  
  Notes:
  1. The Schedule Dates Change Log appears only for Bill To’s that have schedule change reasons recorded in the EDI Codes Maintenance window.
  2. Schedule change reasons for each Bill To are created on the EDI Codes Maintenance window’s Sch Reasons tab.
TMW Operations
- NONE (default)
  No reason is required when a stop with a previously scheduled appointment’s Earliest or Latest date/time is changed.
- SPECIFIC
  For every 214 trading partner, you must set up a trading partner-specific change reasons list. When a stop’s Earliest or Latest date/time is changed in the Trip Folder’s Appointment Scheduler tab for a stop with a previously scheduled appointment, this list, which is specific to the Bill To, appears in the Schedule Dates Change Log. You are required to select a reason from this list.
  
  Note: If you use this option, you must make an entry in String2.
ALL
A reason is required when a stop with a previously scheduled appointment’s Earliest or Latest date/time is changed. The system uses a generic reason code list configured on the Def Sch Reasons tab.

String2

If you entered Specific in String1, you must make an entry in this field. Your entry determines where the Schedule Change Reason tab appears when the earliest and/or latest date for a previously scheduled stop are changed.

N (default)
The Schedule Change Reason tab appears within the Trip Folder’s Schedule Dates Change Log tab or in the Appointment Scheduler window. The user must select a reason from those listed on the Sch Reasons tab.

The system will write the code associated with the selected reason to the 214 flat file.

Note: If you have [.NetMisc]ScheduleReschedule=Y, in your TTS50, the system assumes you are using this option.
Y
The Trip Folder’s Schedule Dates Change Log tab appears. The Schedule tab does not.

The system writes the trading partner specific code associated with the selected reason to the 214 flat file.

RowSecurityForLTSL2

Applies to

TMWSuite 2016.20.105, EDI, TMW Operations

Description

This 204-based security feature allows you to secure the records pertaining to specific 204s so that only companies assigned to a certain group can be matched to the 204. This setting enables record security for LTSL2 inbound 204 batch processing. It also applies to the manual 204 acceptance process.

String1

N (default)
Security is not enabled.
Y
Security is enabled.

SCAC

Applies to

TMWSuite, EDI, eManifest, TMW Operations

Description

Specifies your company’s SCAC code. This code is used on all EDI documents.

String1

Blank, that is, no entry (default)
No output generated.
User-specified SCAC code
Enter your company’s assigned code. Your entry can be from four to six characters.

Note: When you enter a value or select an option in the SCAC field of the All Partner Settings tab, the entry is transferred to this key.
User-specified RevType value
Enter FromRevType1, FromRevType2, FromRevType3, or FromRevType4, depending on which revenue type you use for your SCAC code. You can use the label option’s Abbr field value or its EDI Code field value.

String2

The entry in this string applies only to eManifest dispatched empty moves, which do not have revenue types. If you entered a SCAC code in String1, you do not make an entry here.

If you use a revenue type as your SCAC code, enter the leg header type (LGHType1, LGHType2, LGHType3, or LGHType4) value you use for your SCAC code. You can use the label option’s Abbr field value or its EDI Code field value.