59
4. Working with EDI 214 Status Updates A 214 is an outbound document that informs the shipper or consignee of the order's status. The 214 documents are created in the Dispatch application. You can use two methods to create 214 data and store it in the TMWSuite database: EDI 214 Shipment Status SmartLink If you have purchased this licensed add-on, you can set up your system to create 214s manually from the Dispatch application. You can use the EDI 214 window to add a status code to an event and store the 214 data in the TMWSuite database. Auto 214 Scheduler If you have purchased this licensed add-on, you can set up the system to create 214s automatically and to transfer the data from the TMWSuite database into a flat file. The trip status must match the status specified for the trading partner in the Auto 214 tab in the EDI Codes Maintenance window, accessed in File Maintenance. Information about using both methods to create 214 data is included in the following sections. Manually creating 214 data for an updated order............................4.3 Reviewing pending or previous 214 transactions sent for an order........4.6 Preventing manual 214s from having future dates/times...................4.7 [EDIFileSave] RestrictFuture214Dates........................................................................................... 4.7 Automatically creating 214 data............................................4.8 Verifying that the required licenses have been applied to the TMWSuite database................................................................4.9 Performing 214-specific setup in EDI Codes Maintenance.................4.11 Setting up activities to trigger an Auto-214...........................4.12 Sending 214 status updates at a specified interval.....................4.22 EDI214ReportLocationWhenParked............................................................................................ 4.22 Using the current date/time for 214 status updates sent at specified intervals..............................................................4.23 EDI214UseCurrentTimeWhenParked.......................................................................................... 4.23 Using the local date/time for EDI 214 Status Updates...................4.24 Localtimezone............................................................................................................................... 4.24 Using Appointment Set activities for Auto-214s.........................4.26 ED1214ApptTrigger...................................................................................................................... 4.26 Handling unknown drivers in Location Reports...........................4.28 EDI214RequireDriverMatchOn06................................................................................................ 4.28 Including the Proof of Delivery name recorded for a stop...............4.29 EDI Interface 1 Revised: 12/2015 TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates - TMW Systemstmws.tmwsystems.com/learningcenter/tmws/docs/EDI/General... · Web viewWorking with EDI 214 Status Updates A 214 is an outbound document

  • Upload
    buihanh

  • View
    348

  • Download
    2

Embed Size (px)

Citation preview

4. Working with EDI 214 Status UpdatesA 214 is an outbound document that informs the shipper or consignee of the order's status. The 214 documents are created in the Dispatch application. You can use two methods to create 214 data and store it in the TMWSuite database:

EDI 214 Shipment Status SmartLinkIf you have purchased this licensed add-on, you can set up your system to create 214s manually from the Dispatch application. You can use the EDI 214 window to add a status code to an event and store the 214 data in the TMWSuite database. Auto 214 SchedulerIf you have purchased this licensed add-on, you can set up the system to create 214s automatically and to transfer the data from the TMWSuite database into a flat file. The trip status must match the status specified for the trading partner in the Auto 214 tab in the EDI Codes Maintenance window, accessed in File Maintenance.

Information about using both methods to create 214 data is included in the following sections.

Manually creating 214 data for an updated order................................................................4.3Reviewing pending or previous 214 transactions sent for an order................................4.6Preventing manual 214s from having future dates/times...............................................4.7

[EDIFileSave] RestrictFuture214Dates.................................................................4.7Automatically creating 214 data..........................................................................................4.8

Verifying that the required licenses have been applied to the TMWSuite database........4.9Performing 214-specific setup in EDI Codes Maintenance............................................4.11Setting up activities to trigger an Auto-214..................................................................4.12Sending 214 status updates at a specified interval......................................................4.22

EDI214ReportLocationWhenParked...................................................................4.22Using the current date/time for 214 status updates sent at specified intervals...........4.23

EDI214UseCurrentTimeWhenParked.................................................................4.23Using the local date/time for EDI 214 Status Updates..................................................4.24

Localtimezone...................................................................................................4.24Using Appointment Set activities for Auto-214s............................................................4.26

ED1214ApptTrigger...........................................................................................4.26Handling unknown drivers in Location Reports.............................................................4.28

EDI214RequireDriverMatchOn06.......................................................................4.28Including the Proof of Delivery name recorded for a stop.............................................4.29

Transferring 214 data into a flat file...................................................................................4.30Manually transferring 214 data.....................................................................................4.30Using the EDI Scheduler to automatically transfer 214 data.........................................4.31

Reviewing Auto-214s that are On Hold...................................................................4.32Specifying the default Reason Late setting for On Hold 214s..................................4.35

[EDIfilesave] HoldQueueSetReason...................................................................4.35Setting up labels for 214s...................................................................................................4.36Including additional information in the EDI 214..................................................................4.38

Creating a separate 214 for each bill of lading number recorded for an order header. 4.39EDI214_MultiBOL...............................................................................................4.39

Displaying the Bill To's address line 2...........................................................................4.39

EDI Interface 1 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

EDI_AddrLine2...................................................................................................4.39Including TotalMail check call information....................................................................4.40

EDI214GPSLocationforESTA...............................................................................4.40Including the trailer 2 ID code.......................................................................................4.40

EDI214_AddTrlTwo............................................................................................4.40Creating a Location Report or ESTA message based on a stop's updated arrival date/time..................................................................................................................................... 4.41

EDI214_ETALocationReport...............................................................................4.41Recording the city/state for the next event..................................................................4.42

EDI214UseDestCityForAG..................................................................................4.42Including the current tractor location...........................................................................4.43

AddGeoLocationToEDI214.................................................................................4.43Including the order delivery date/time..........................................................................4.43

EDI214_DeliveryDateTime.................................................................................4.43Including the scheduled Earliest and Latest date/time.................................................4.44

EDI214_EarliestLatest........................................................................................4.44Including STCC codes...................................................................................................4.44

EDI214ExportSTCC............................................................................................4.44Specifying the reference number types included in record 6 (lading exception)..........4.45

EDI214_AddOSDRef...........................................................................................4.45Including overage, shortage, and damaged information...............................................4.45

EDI214_OSD......................................................................................................4.45Adding the 7 cargo record for each freight detail on a stop..........................................4.46

EDI214CargoRecs..............................................................................................4.46Specifying whether a 214 will be sent for a late arrival................................................4.46

EDI214lateAR....................................................................................................4.46Working with archived EDI 214 status updates..................................................................4.47

Re-extracting 214 files..................................................................................................4.47Displaying an order's delivery appointment date/time in the Planning Worksheet.............4.49

ShowDeliveryAndAppointment..........................................................................4.49

EDI Interface 2 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Manually creating 214 data for an updated orderWhen you modify an order linked to a Bill To that is set up for the EDI 214 service, you can manually create 214 data for the updated order and store it in the TMWSuite database from the Dispatch application. 1. Select the order in the Dispatch Planning Worksheet or Trip Folder.2. Select Dispatch > Create EDI 214. The stops on the trip are displayed at the

top of the EDI 214 window.

Note: If necessary, enter the Order Number at the top of the window and press TAB.

3. Click on the stop for which you are creating the 214.4. Click Add to add information about that stop to the 214.

The system adds the 214 fields for the stop at the bottom of the window.

EDI Interface 3 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

5. Make entries in the following fields at the bottom of the window:EDI Company Defaults to Billto.

If the EDI Notification Method field in the EDI Codes Maintenance window is set to BillTo based, Billto is the only option.If the EDI Notification Method is set to Company based, select another company type, if necessary:

Billto Shipper Consignee OrderBy Selected Stop

Status Code Select the EDI status that the trading partner requires for the stop.If the EDI Notification Method field is set to BillTo based, status codes are from the EDI214Status label in TMWSuite System Administration.If the EDI Notification Method field is set to Company based, status codes are from the Auto 214 tab of the EDI Codes Maintenance window.Notes:1. If you use the Company based EDI notification method

and create manual 214s, you must create Auto-214 activities for each trading partner.

2. For details about the EDI notification method, see Specifying the EDI notification method for Auto-214s.

3. For details about creating Auto-214 activities, see the entry for the EDI Status field in the Setting up activities to trigger an Auto-214 section.

Status Date* Defaults to the current date/time. If necessary, enter another date/time for the event.

Status City* Defaults to the city/state for the selected stop. If necessary, enter the city/state for the event.

Status Reason Select the appropriate status.Note: Reason codes are recorded in the EDI214Reason label in System Administration.

Tractor* Defaults to the ID of the assigned tractor. If necessary, select another tractor.

EDI Interface 4 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Mobile Comm # Applicable only if you are using TotalMail. Enter the ID number of tractor's MobileComm unit.

Trailer* Defaults to the ID of the assigned trailer. If necessary, select another trailer.

Trailer Owner Applicable only if you are using TotalMail. Enter the ID code for the Bill To or trailer owner.

Stop#* Defaults to the stop number of the selected stop. Do not change the stop number.

Wgt* Displays the total weight from the order header. If necessary, enter a different weight for the stop.

Qty Displays the total count from the order header. If necessary, enter a different quantity for the stop.

Reference # Displays the reference number from the stop detail.

*Any changes that you make in these fields will not update the order.6. Repeat Steps 4 and 5 for each stop. 7. Click Save.

Notes: For information about manually transferring 214 data into a flat file, see Manually transferring 214 data.

EDI Interface 5 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Reviewing pending or previous 214 transactions sent for an orderA feature in the EDI 214 window allows you to review all pending manual 214s or prior manual and Auto-214s that have been transferred for an order.1. Select the order in the Dispatch Planning Worksheet or Trip Folder.2. Select Dispatch > Create EDI 214.3. In the EDI 214 window, click the View 214 statuses sent for order button.

4. The View status codes for order window displays the details for all previous 214s that have been sent, both manually and automatically, for the order.

Note: Blue text indicates 214s that have been transferred. Red text indicates manual 214s that are pending.Trading Partner Company ID of the trading partner for the selected stop

Status Code EDI status that the trading partner requires for the stopNote: The EDI status is specified in the Edi Status field of the EDI Codes Maintenance window's Auto 214 tab.

Status Date Date/time the status was recorded

Stop Stop number for the status city/state

City/State City/state for the stop location

EDI Interface 6 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Date Transferred

If the 214 has been transferred, displays the date/time of the transfer.

Status Reason If the 214 has been transferred, displays the reason code for the status.Note: Status reason codes are recorded in the EDI214Reason label in System Administration.

997 Status If the 214 has been transferred, indicates whether a 997 Functional Acknowledgement for the 214 has been accepted (A) or rejected (R). A 997 Functional Acknowledgement is required for all transmissions that include financial data.Note: This feature is available when you have the license for the 997 processor, which is sold separately from the base system. For more information, contact your TMW EDI Support representative.

5. To close the window, click View 214 statuses sent for order again.

Preventing manual 214s from having future dates/timesYou can prevent manually created 214s from having a status date/time in the future.

[EDIFileSave]RestrictFuture214Dates

First available in

TMWSuite: 2010.09_08.0595

Description When you manually create a 214 status update in the Dispatch application, the system defaults the current date/time as the date/time of the update. However, you can change the date/time. This setting determines whether a manually created 214s can have a status date/time in the future.

Options N (default)The manually created 214s cannot have a future status date/time.

YThe manually created 214s can have a future status date/time.Note: A warning message appears if the date/time for a manually created 214 is greater than the current date/time.

EDI Interface 7 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Automatically creating 214 dataIf you are licensed for the EDI 214 Shipment Status SmartLink and EDI Scheduler, you can set up the system to automatically create 214 data when a specified activity occurs on a trip. For each trading partner, you define the activity triggers on the EDI Codes Maintenance window's Auto 214 tab. The window is accessed in the File Maintenance application. For the system to create Auto-214s, you must have the following:

EDI 214 Shipment Status SmartLink license EDI Scheduler The Auto214 Enabled field set as Yes in the All Partner Settings tab in the EDI Codes Maintenance window.

The system creates Auto-214s based on the following criteria: Hard-coded, standard EDI activitiesAuto-214 activities are based on specified events being completed on a trip. After an activity has taken place, the Auto-214 is sent if the activity meets the criteria set up in the Auto 214 tab. Order requirementsYou can set requirements for each Auto-214 activity. An Auto-214 is not sent if the requirements that are set for the activity on the Auto 214 tab are not met on the order.

Notes: 1. The system creates Auto-214s only when the Auto214 Enabled field has a

value of Yes. The field is found on the All Partner Settings tab in the EDI Codes Maintenance window.

2. For more information about setting up Auto-214 activities, see Setting up activities to trigger an Auto-214.

EDI Interface 8 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Verifying that the required licenses have been applied to the TMWSuite databaseSpecial licensing is required to run the EDI 214 Shipment Status SmartLink add-on. The licensing is contained in a SQL script that is applied to your TMWSuite database using SQL Server Enterprise Manager/ SQL Query Analyzer. Without proper licensing, the options described in this guide will not appear in your TMWSuite applications.

Note: For instructions on applying the SQL script to your database, refer to your SQL Query Analyzer help system.

To verify that the licensing has been properly applied to your database, follow these steps:1. From any TMWSuite application, select Help >About.2. Click More at the bottom of the window.

3. A second About window provides a table containing three columns: Option Name

Lists the applications and features available in TMWSuite. Option Value

Signifies whether the application/feature is active. Option Expiration

Lists the date that the subscription to each feature will expire.

EDI Interface 9 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

4. Scroll through the list to find the EDI214 and PS Scheduler licenses and verify that the Option Value field contains a value of Y.

5. If you will be running the EDI 210 Invoice SmartLink application to transfer 210 data, scroll through the list to find the EDI210 license and verify that the Option Value field contains a value of Y.Notes: The list is alphabetical. If the required license is not listed, contact your Support Team.

E-mail Phone

Support Team 1 [email protected]

Call 216-831-6606 and choose Option 6. Follow the prompt to select your team's extension. If all support personnel are busy, you can leave a voice mail message.

Support Team 2 [email protected]

Support Team 3 [email protected]

6. Click OK twice to close both About windows.

EDI Interface 10 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Performing 214-specific setup in EDI Codes MaintenanceIn the EDI Codes Maintenance window, the fields directly below the All Partners Setting tab allow you to enter information that is specific to 214 files. 1. In the File Maintenance application, select Edit > EDI Codes. The EDI Codes

Maintenance window displays the All Partner Settings tab.When setting EDI parameters that affect all trading partners, leave the Company field set to UNKNOWN.

2. In the 214 Version field, select the 3.9 option as the EDI 214 flat file version you will be using.

Note: The 3.4 and 1.0 flat file versions are obsolete.3. If you are using an EDI e-mail format or fax format to send Auto-214s, select the

Use Company Fax # for EDI Email/Fax check box to use the company's fax number from the TMWSuite company profile.Notes:

EDI Interface 11 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

1. If you encounter a problem with undeliverable e-mail when sending Auto-214s, it may be a result of an invalid number recorded in the Fax field in the Bill To, shipper, and/or consignee company's profile.

2. When sending an Auto-214, the system will send the e-mail to the number recorded in the Fax field of a company's profile, and to all e-mail and fax numbers recorded for that company in the Company Contacts window.Note: You can access this window in File Maintenance by selecting Contact Info or Tools > Edit Company Contacts.

4. Click Save to keep your changes.

Setting up activities to trigger an Auto-214Auto-214 activities are based on specified scenarios being completed on a trip. After an activity has taken place, the Auto-214 will be sent if the activity meets the criteria set up on the tab.For example, the Arrive at Stop or Depart from Stop activities are based on the Arrival and/or Departure fields being updated and the actualization of the Est and/or Dep. Stat. fields in the Dispatch Trip Folder. After the pickup or drop (specified in the Auto-214 tab's Stop Type field) has been actualized, the Auto-214 is generated.

Arrival and Departure fields in the Stop Detail grid in the Dispatch Trip FolderUse this procedure to set up the activities that will trigger an Auto-214.1. In the File Maintenance application, select Edit > EDI Codes to display the EDI

Codes Maintenance window.2. In the Company field, select a trading partner.3. Select the Auto 214 tab.

EDI Interface 12 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

4. Click Add to add an activity.5. Make entries in the following fields to set up the activity criteria for sending an

Auto-214. Activity Select the activity that will trigger an automatic 214. These

activi-ties are hard-coded EDI Auto-214 standards. The options are:

Arrive at stopThe value in the Stop Type field must be a pickup or drop.Note: The TMWSuite event on the stop must be an actualized pickup or drop, as indicated by the P and D codes in the Trip Folder's Stop Detail grid. Depart from stopThe value in the Stop Type field must be a pickup or drop.Note: The TMWSuite event on the stop must be an actualized pickup or drop, as indicated by the P and/or D codes in the Trip Folder's Stop Detail grid. Appointment setThe value in the Stop Type field must be a pickup or drop.Note: This activity may be triggered by the change of date/time in the Earliest or Latest fields, or when an SAP event is added. Location ReportA Location Report is a check call from a truck. This option requires that you either enter check calls manually in Dispatch or set up your system to transfer TotalMail position reports to the TMWSuite check calls table automatically. Location report 214s are created at specific intervals, from the time the first pickup is complete until the last drop is complete. Consult the TotalMail System Administrator guide for information on setting the interval of TotalMail position report transfers to the TMWSuite check calls table.Note: This activity is triggered by a check call's updates to the Arrival and/or Departure fields. The check call event0020 does not need to be actualized. Order AvailableTriggered when the order status changes to Available. Trip DispatchedTriggered when the order status changes to Dispatched. Trip PlannedTriggered when the order status changes to Planned.

EDI Interface 13 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Activity (Cont.) Arrive – order cancelTriggered by the status of an open order that has been started being changed to Cancelled Billable. Est Arrival revisedTriggered by the scheduled arrival time of the order listed in the Arrival field being updated. Order CancelledTriggered by the status of an order with no actualized stops being changed to Cancelled.

The following activates are custom options: Trip Created Available Date Change Order Available Date Est Arrival Location Trip Completed Change Consignee

Stop Type Select the type of stop that will trigger an automatic 214. The options are:

Drop LocationsOnly a stop at a consignee location will trigger the creation of the 214. Pickup LocationsOnly a stop at a shipper location will trigger the creation of the 214. Not ApplicableThe stop type will not be considered as a criterion for triggering the creation of the 214. Billable Begin EmptyThis billable event at the beginning of a movement will trigger the creation of the 214. Billable End EmptyThis billable event at the end of a movement will trigger the creation of the 214. Billable Customs StopThis billable stop at a customs location will trigger the creation of the 214.

EDI Interface 14 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Stop Position Select the stop on the order that will trigger the automatic 214. For example, if you have an order with multiple drops, you may want an automatic 214 sent when the last drop is made, rather than when the first drop is made. The options are:

AnyAny stop on the order that matches the selected activity and stop type will trigger the 214 creation. FirstOnly the first stop on the order that matches the selected activity and stop type will trigger the 214 creation. LastOnly the last stop on the order that matches the selected activity and stop type will trigger the 214 creation. All but firstAny stop but the first one on the order that matches the selected activity and stop type will trigger the 214 creation. All but lastAny stop but the last one on the order that matches the selected activity and stop type will trigger the 214 creation.

SEQ If you are going to generate more than one transaction set per activity, you must indicate the order in which they should be written to the flat file. Enter the sequence number.Note: A transaction set is the set of flat file records that can be mapped through an EDI translator.

EDI Interface 15 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

EDI Status (comma separated list)

The status specified here is used for the Auto-214. Enter the EDI status code that corresponds to the stop type and activity you selected. Notes: 1. When you use the Company based EDI notification

method, a trading partner’s Auto-214 activities determine the EDI status codes used for manual 214s. For details, see Specifying the EDI notification method for Auto-214s.

2. The Auto 214 tab allows you to specify the criteria for multiple 214 transaction sets. Each row you add represents instructions for writing flat file records for a single transaction set. If you include a comma-delimited list of status codes, that transaction set would have multiple status records. In the flat file, a transaction set with multiple status records would be represented by a #3 record for each status code.

3. Do not use X9 or XA unless recommended by a TMW EDI Support representative. Use AA for pick up appointment date and time and AB for delivery appointment date and time.

4. Normally, when the Activity field displays Trip Dispatched, the 214 includes the pickup location. If you prefer to include a check call location, enter the X6 (En Route to Location) EDI status. This triggers a Location Report 214 for the tractor's current GPS location and nearest city.1. The 214 includes the pickup location (not the current

GPS location) if any of the following is true: The last check call occurred more than one week

before or more than one hour after the estimated arrival time.

A carrier (not a driver, tractor, and/or trailer) is assigned to the trip.

A code other than X6 appears in the EDI Status field.

2. You must have the TotalMail messaging system to use the X6 status.

3. By default, the driver and tractor recorded in a check call must be linked in File Maintenance or TotalMail. Otherwise, the Location Report will not be recorded in the EDI 214. As of TMWSuite 2014.13_07.0644, you can use the EDI214RequireDriverMatchOn06 General Info Table setting to record Location Reports in an EDI 214 when the driver and tractor in the check call are not linked, or when the driver is recorded as UNKNOWN.

EDI Interface 16 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Set Per Stop This is a custom setting. Do not select this check box.

Send As Specify the transmission method the system uses when sending a fax or e-mail. When the BillTo based option is selected in the EDI Notification Method field on the All Partner Settings tab, the following options appear.

EDI 214The transaction set will be sent as a 214, using your EDI communication provider (Value, Visual, ProEDI, or Kleinschmidt). Note: The 214 will be sent only if the trading partner appears as the Bill To on the order. Email/FaxThe transaction set will be sent as e-mail or as a computer-generated fax; it will not be sent via your EDI communication provider.Notes: 1. EDI Scheduler must be running to produce e-mail, fax,

or Auto-214 output.2. Fax documents are sent to the e-mail software. If your

e-mail software requires a flag indicating fax instead of

e-mail, please contact the TMW EDI Support representative to review your requirements.

3. You can record a company's e-mail address or fax number in the Company Contacts window. You can access this window in File Maintenance by selecting  Contact Info or Tools > Edit Company Contacts.

EDI Interface 17 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Send As (cont.)When the Company based option is selected in the EDI Notification Method field on the All Partner Settings tab, check boxes appear that allow you to select how the transaction set will be sent.

M (Email)The transaction set will be sent as e-mail; it will not be sent using your EDI communication provider. E (EDI)For an Auto-214 to be sent, the trading partner must be the selected option (Bill To, shipper, consignee, or Order By) on the order. F (Fax)The transaction set will be sent as a computer-generated fax; it will not be sent using your EDI communication provider.

Notes:1. The options in this field default from the option selected

in the EDI Notification Method field in the EDI Codes Maintenance window's All Partner Settings tab.

2. This setting does not apply to EDI format output.

EDI Interface 18 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Recipient Select the check box of the entity type that is to receive the Auto-214 fax or e-mail. This also determines the type of profile that must appear on the order when sending an Auto-214.The options in this field default from the option selected in the EDI Notification Method field in the EDI Codes Maintenance window's All Partner Settings tab.

When the Bill To based method is selected, the Recipient field is displayed. The options available depend on what is selected in the Send As field: When EDI 214 is selected, the Bill To is the default

recipient.

When Email/Fax is selected, check boxes appear. Use them to identify the entities that will receive the email or fax.

B (BillTo)The trading partner paying for the order.

S (Shipper)The company where the pickup takes place.

C (Consignee)The company where the drop takes place.

EDI Interface 19 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Recipient (Cont.) When the Company based option is selected in the EDI Notification Method field in the All Partner Settings tab, the Apply When field displays check boxes for selecting the role the trading partner plays on the order.

B (BillTo)The trading partner must appear as the Bill To on the order for an Auto-214 to be sent.

S (Shipper)The trading partner must appear as the shipper on the order for an Auto-214 to be sent.

C (Consignee)The trading partner must appear as the consignee on the order for an Auto-214 to be sent.

O (Order By)The trading partner must appear as the Order By on the order for an Auto-214 to be sent.

Don't send if late/ no reason

You can prevent the sending of an Auto-214 when no reason codes are recorded for a late arrival at, or departure from, a stop. Select the appropriate check boxes. Your selection applies to all Auto-214 activities.

Arrival Depart

Note: Use this feature to place the 214s in the Auto 214 Hold queue. To view Auto-214 activities in the Dispatch application, select Dispatch > View Auto 214 Hold Records.

Require Trailer

Select this check box to prevent an Auto-214 from being sent for the specified activity when a trailer is not on the order.

Maintain Sequence

Select this check box to have later messages that meet all requirements held until any earlier messages that are on hold are cleared.Note: The check box appears only if EDI 214 is selected in the Send As field.

EDI Interface 20 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Freight Detail From Delivery

Select this check box to include the freight detail information from each order in the Auto-214.Note: The check box appears only if EDI 214 is selected in the Send As field, and Pickup Locations is selected in the Stop Type field.

WeightVolumeCount

Set the quantity to restrict when an Auto-214 can be sent for the specified activity. The quantity is based on the total of all freight details on the stop of the activity.

The options are: NoneThere are no freight details restrictions for the order. The Auto-214 will be sent. Greater Than >The quantity on the order must be more than the quantity entered in the required quantity field for the system to send an Auto-214. Less Than <The quantity on the order must be less than the quantity entered in the required quantity field for the system to send an Auto-214.

EDI Interface 21 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Sending 214 status updates at a specified intervalWhen you set up an Auto-214 to send Location Reports (check calls) for a trading partner, the system automatically creates and sends a 214 at a specified interval. The reports continue to be sent as long as a new Location Report is received from the tractor after the last 214 was sent.You can set up the system to continue sending 214 status updates at the specified interval during a period when a new Location Report has not been received. For example, the system would continue sending Location Reports at the specified interval while a tractor is parked.

EDI214ReportLocationWhenParked

Applies to TMWSuite, EDIDescription 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.

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

Note: For details about the EDI214UseCurrentTimeWhenParked General Info Table setting, see Using the current date/time for 214 status updates sent at specified intervals.

Using the current date/time for 214 status updates sent at specified intervalsThe EDI214ReportLocationWhenParked General Info Table setting allows the system to continue sending 214 status updates when a new Location Report has not been received. By default, each Location Report sent during this time includes the date/time of the last status update sent from the check call location.If you prefer, you can have Location Reports use the current date/time.

EDI Interface 22 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

EDI214UseCurrentTimeWhenParked

Applies to TMWSuite 2013.12_08.0891Description 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 settingUse 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.

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

Note: For details about the EDI214ReportLocationWhenParked General Info Table setting, see Sending 214 status updates at a specified interval.

EDI Interface 23 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Using the local date/time for EDI 214 Status UpdatesFirst available in TMWSuite: 2014.13_07.0242The EDI 214 Status Update informs the shipper or consignee of an order's status. The date/time recorded for each event allows you to verify a trip's progress and determine on-time performance. By default, the dates/times recorded in an EDI 214 reflect the dispatcher system's date/time, not the date/time where the event occurs.In the City File Maintenance window, the Time Zone field specifies the location's Greenwich Mean Time (GMT) offset. The system uses this information to calculate the local time.When you specify the GMT offset this way, you can use the Localtimezone General Info Table setting to adjust the date/time for each event in a 214 to the date/time where the event occurred.

Localtimezone

Applies to TMWSuite: 2014.13_07.0242Description 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.

EDI Interface 24 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Localtimezone

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.

CIThe 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 Setting is blank by defaultThe system records the dispatcher system date/time for each event.

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

EDI Interface 25 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Using Appointment Set activities for Auto-214sBy default, Appointment Set activities are based on changes made in the Trip Folder's Earliest and Latest fields. Actualizing an event on a stop does not trigger the creation of an Auto-214 for an appointment.

Notes:1. The exception to using the Appointment Set activity rule can be the SAP

(Scheduled Appointment) event. If the EDI214ApptTrigger key in your General Info Table has a value of S or B, Auto-214s are triggered by the actualization of the event, not by the change in the Trip Folder's Earliest and Latest fields.

2. Actualizing activities in the Dispatch Quick Trip window or the Agent Order entry module does not trigger Auto-214s to be sent. For more information on the Quick Trip window, see:

Guide: TMWSuite EDI Interface | Chapter: Using the Quick Trip window The Agent Order Entry add-on module requires special licensing. For more

information, see the Agent Order Entry guide.

You can specify which updates must occur in the Dispatch Trip Folder to send an Auto-214 based on an Appointment Set activity.

ED1214ApptTrigger

Applies to TMWSuite V.2003Description This setting specifies the updates in the Dispatch Trip Folder that must

occur to send an auto-214 based on an Appointment Set activity. Make your entry in the String1 field.

EDI Interface 26 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

ED1214ApptTrigger

String1 TThe dates/times in the Earliest and Latest fields must be updated to identical date/times to trigger the Appointment Set activity and send an auto-214. The updated dates/times indicate that the timeframe for the appointment has been closed.

SAn SAP arrival event must be actualized to trigger the Appointment Set activity and send an auto-214.Note: The SAP event actualization is dependent on the existence of an order number in the Order Number column in the Trip Folder’s Stop Detail grid. The system will verify the order number appears in this column before actualizing the event.

BBoth the T and S options must occur to trigger the Appointment Set activity and send an auto-214.

LOnly the date/time in the Latest field must be updated to trigger the Appointment Set activity and send an auto-214.This option allows retentions of an arrival and departure time window in the Earliest and Latest fields, and when triggering the appointment.

EDI Interface 27 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Handling unknown drivers in Location ReportsFirst available in TMWSuite: 2014.13_07.0644The X6 (En Route to Location) status triggers a Location Report 214 for the tractor's current GPS location and nearest city. By default, the driver and tractor recorded in a check call must be linked in File Maintenance or TotalMail. If they are not linked, the Location Report is not recorded in the EDI 214.The EDI214RequireDriverMatchOn06 General Info Table setting allows you to record Location Reports in an EDI 214 when the driver and tractor in the check call are not linked, or when the driver is recorded as UNKNOWN.

EDI214RequireDriverMatchOn06

Applies to TMWSuite: 2014.13_07.0644Description Set up your system to record Location Reports in an EDI 214 when the

driver and tractor in a check call are not linked, or when 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.

YRecord Location Reports in the 214 when the driver and tractor are not linked, or when the driver is recorded as UNKNOWN.

Additional Notes

1. To use this feature, you must have String1 set to Y in the ManualCheckCall General Info Table setting.

2. Prior to 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

EDI Interface 28 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Including the Proof of Delivery name recorded for a stopIn the Trip Folder's Stop Detail grid, the POD Name field allows you to enter the name of the person who signed the Proof of Delivery for each stop. This information is exported to the 214 file, where it appears with the company information for the stop for which the POD was signed.

EDI Interface 29 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Transferring 214 data into a flat fileEDI 214 Shipment Status SmartLink creates the TMWSuite 214 flat file, which contains electronic update data that is sent to your internal or external mapping service. Your mapping service then forwards the 214 to your trading partner.Before your mapping service can send 214s, you must extract the data from your TMWSuite database and create the flat files. There are two methods for transferring 214 data from the TMWSuite database and exporting it into a flat file with EDI 214 Shipment Status SmartLink:

Manually transfer 214 data from the Dispatch application. If licensed for EDI Scheduler, you can set up the system to transfer the data to a 214 flat file at a required interval.

Manually transferring 214 dataYou can manually transfer 214 data that is stored in the TMWSuite database into a 214 flat file from the Dispatch application. 1. In TMWSuite Dispatch, select Dispatch > Transfer EDI 214.

Note: A message is displayed if there is no data to be sent. Click OK to close the message.

2. When there is 214 data to be transferred, the Save EDI214 File as window is

displayed.

If necessary, navigate to the correct folder and enter the File name.Notes:1. Verify that a file with the same name does not already exist in the same

directory. If it does, alter the file name to make it unique.2. To set up your system to default to the EDI folder, contact your company's

network administrator.

EDI Interface 30 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

3. Click Save.

Using the EDI Scheduler to automatically transfer 214 dataIf you are licensed for EDI Scheduler, you can set up a recurring export to automatically transfer the created 214 data from the TMWSuite database to a 214 flat file. This application also provides an interface to the mail system for e-mailing or faxing EDI 214 status updates.Using EDI Scheduler eliminates the need to extract EDI transaction data manually from your TMWSuite database for mapping. You must set up the trading partner's 214 information before you can use the EDI Scheduler. This table defines the steps that must be completed before the system can automatically extract 214 data to a flat file.Setup Description For more information, see

Specify the location of the 214 data folder

Use the 214data INI setting to specify the path and name of the folder where 214 flat files will be stored.

Identifying the 214 data folder section of the "Setting up TMWSuite for EDI" chapter.

Activate the system to create Auto-214s

Select Yes in the Auto214 Enabled field of the EDI Codes Maintenance window's All Partner Settings tab.

Making entries that update the General Info Table section of the "Setting up TMWSuite for EDI" chapter.

Verify a trading partner's 214 information

Use the features in the EDI Codes Maintenance window to configure trading partner requirements for EDI 214 status updates.

Recording the trading partner's 214 requirements section of the "Setting up TMWSuite for EDI" chapter.

Define Auto-214 activities Use the features in the Auto 214 tab in the EDI Codes Maintenance window to define which activities will trigger an Auto-214 for each trading partner.

Setting up activities to trigger an Auto-214

Note: Refer to the "Using EDI Scheduler to transfer 210 and 214 data" chapter for additional information about setting up EDI Scheduler to transfer 214 flat files automatically.

EDI Interface 31 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Reviewing Auto-214s that are On HoldFor each trading partner, you can set requirements for Auto-214 activities. For example, you can require that the trailer ID be identified, or that a reason be provided for a late arrival. Any Auto-214 that does not meet all the requirements is not sent, and is placed in the Auto 214 Hold queue.If you are set up to maintain sequencing, subsequent Auto-214s for a trading partner will also be placed on hold until the Auto-214 that failed to meet a requirement is corrected.Follow these steps to review and correct your On Hold 214s.1. In the Dispatch application, go to Dispatch > View Auto 214 Hold Records.2. Use the filter options at the top of the EDI Auto 214s on Hold window to display

On Hold 214s for a specific Bill To and/or date range.

Note: If you leave the Billto Company field set to UNKNOWN, the window will display the On Hold 214s for all Bill To's for the specified date range.

3. Click Apply Filter to retrieve the On Hold 214s.

Note: If you are set up to maintain sequencing for Auto-214s, the retrieval list may contain records that show Prior 214's for order held in the Hold Reason field. You do not edit these records. They will be handled when you correct the record that caused them to be placed On Hold.

4. In the retrieval list, select a record with a Hold Reason other than Prior 214's for order held.

5. The fields that appear at the bottom of the window are controlled by the requirements that you identified in the EDI Codes Maintenance window's Auto 214 tab. You use these fields to make the needed corrections.

EDI Interface 32 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Notice that the system highlights the field(s) associated with the unfulfilled requirement. In our example, the Reason Late - Arrival field is highlighted in yellow.

6. Make all needed entries and click Update.

EDI Interface 33 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

The system sends the corrected record and any records for that order with Prior 214's for order held in the Hold Reason field.

Note: The information for the trip is updated with the entries that you make at the bottom of the window.

EDI Interface 34 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Specifying the default Reason Late setting for On Hold 214sFirst available in TMWSuite: 2014.13_07.0242When you update the arrival and/or departure times for an event in the Edit Auto 214s on Hold window, the Reason Late - Arrival and Reason Late - Departure fields default to Normal Status. The system will process the record even though the new time indicates that the event was late.Use the HoldQueueSetReason setting in your TTS50 to display UNKNOWN in the Reason Late - Arrival and Reason Late - Departure fields when you update the arrival and/or departure times. The system cannot process these records until you specify why the event was late.

[EDIfilesave]HoldQueueSetReason

Applies to TMWSuite: 2014.13_07.0242Description Use this setting to specify the default status for the Reason Late -

Arrival and Reason Late - Departure fields in the Edit Auto 214s on Hold window. The fields display the specified status when you update the arrival and/or departure times for an event.Note: The window is accessed from File Maintenance's EDI Codes Maintenance window. It is used to review/correct auto 214s that have been placed on hold.

Options Y (default)The fields display Normal Status when you update event times. Note: The system will process a record even when a new time indicates that the event was late.

NThe fields display UNKNOWN when you update event times. Note: The system cannot process the record until you select a reason that indicates why the event was late.

EDI Interface 35 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Setting up labels for 214sYou use the TMWSuite label files to customize the system for your company's way of doing business. Two labels are used when manually creating 214s.

EDI214ReasonLists standard EDI status reason codes used for manual 214s. EDI214StatusLists standard EDI status codes used for manual 214s.

Add entries to the labels that pertain to EDI.1. Open the System Administration application.

2. Click Labels in the frame toolbar, or select Edit > Label File. The Edit User Definable Fields window is displayed. Use the Field Name drop-down list to display the label for which you want to add or change an entry.

Example of the EDI214Reason label

3. To add an entry, click Insert in the sheet toolbar. The system adds an empty row to the bottom of the list.

4. Make entries in these fields: Name Enter the name you want to display as the field name on the

corresponding screen. Note: When a field name is hard-coded into the system, the Name field is blank. Any text that you enter here will not display on the corresponding screen.

Description Type the name of the label option, as you want it to display in drop-down lists.

EDI Interface 36 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Abbr Enter a unique abbreviation to represent this row. This value will be stored in the database.Note: This should be the same value as the EDI qualifier and can be no more than three characters long.

Code Enter a unique sequential number. This number specifies the order in which the entry is displayed in the drop-down list for this field. For convenience in making your selection, make sure the ones you will use most often have the lowest 'code' numbers.

EDI Code Enter the same code in the EDI and Abbr fields.Note: The EDI Code comes from the trading partner's specifications. It can be no more than three characters long. Any changes made here update the code in the EDI Code Maintenance window. Any changes there update the value here. If left blank, the system uses the first three characters of the Item code as the default EDI code.

System Code A check mark in this field indicates that this item is essential to the integrity of system performance.Warning: You cannot modify or delete label entries that are system codes. You can, however, retire one that is no longer needed. To retire a system code, select its Retired check box.

5. When your addition is complete, click Save in the sheet toolbar. put in new format.Note: If you need to modify a description, you can place the cursor in that text field and type the change. Do not modify any other fields, as this will interfere with the label's history throughout the system. Be sure to save the change as you would a new entry.

6. Click Close on the sheet toolbar, or select File > Close.

EDI Interface 37 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Including additional information in the EDI 214The following table lists the General Info Table settings that allow you to include additional information that is trading partner-specific in your 214 flat files. The following sections provide a detailed description of each setting.General Info Table Setting Adds this information to the flat file In this recordEDI214_MultiBOL Create separate 214 for each BOL

reference number recorded for an order header

1

EDI_AddrLine2 Bill To company profile's address line 2 2EDI214GPSLocationforESTA City, state, and zip code data from the

most recent TotalMail check call2

EDI214_AddTrlTwo Trailer 2 ID code 3EDI214_ETALocationReport Send Location Report and/or ESTA

message when the arrival date/time for a stop is updated

3

EDI214UseDestCityForAG City/state for the next stop location when the next arrival time has the AG status

3

ddGeoLocationToEDI214 City/state data of the current GPS location

4

EDI214_DeliveryDateTime Date/time the final drop was actualized and changes to Completed status.

4

EDI214_EarliestLatest Scheduled Earliest and Latest dates/times

4

EDI214ExportSTCC STCC commodity data 4EDI214_AddOSDRef Reference number types that will be

added to the OSD record6

EDI214_OSD Overage, shortage, and damaged freight information

6

EDI214CargoRecs Freight detail recorded on each stop 7EDI214lateAR Send a 214 upon a late arrival Not

applicable

EDI Interface 38 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Creating a separate 214 for each bill of lading number recorded for an order headerYou can have the system create a separate 214 file for each bill of lading reference number recorded for an order header.

EDI214_MultiBOL

Applies to TMWSuiteDescription 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 1 record of the 214.

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

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

Additional Notes

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

Displaying the Bill To's address line 2You can have the system display address line 2 from the Bill To company profile in the 2 record of 210 and 214 files.

EDI_AddrLine2

Applies to TMWSuiteDescription Specifies whether the address line 2 in the Bill To company profile will

display in the 2 record of 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 2 record of the flat file.

EDI Interface 39 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Including TotalMail check call informationYou can specify whether the most recent TotalMail check call information for the pickup or delivery should be included in record 2 of the 214 file.

EDI214GPSLocationforESTA

Applies to TMWSuiteDescription Specifies whether the most recent TotalMail check call information is

used for the pickup or delivery in the 2 record of auto-214s.String1 No

Use the stop company location information (city, state, and ZIP Code) in the 2 record.

YesInclude city, state, and ZIP Code data from the most recent TotalMail check call on the 2 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.

Including the trailer 2 ID codeYou can set up the system to include the Trailer 2 ID code in the 214 file.

EDI214_AddTrlTwo

Applies to TMWSuiteDescription If a secondary trailer is used on an order, use this setting to include the

Trailer 2 ID in the 3 record of the 214 file.String1 N (default)

Do not include the Trailer 2 ID in the 3 record. Y

Include the Trailer 2 ID in the 3 record.

EDI Interface 40 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Creating a Location Report or ESTA message based on a stop's updated arrival date/timeWhen the arrival date/time for a stop is updated, the system can send either:

An EDI Location Report, which indicates a shipment's current location. An ESTA message, which indicates the shipment's estimated arrival date/time at the next stop.

You can have the system send one or the other, or both, when the arrival date/time for a stop is updated.

EDI214_ETALocationReport

Applies to TMWSuiteDescription 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:1. 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.

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

Recording the city/state for the next eventYou can set up the system to record the date/time and city/state for the next pickup or drop in the 214 file's 3 Status record.

EDI Interface 41 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

EDI214UseDestCityForAG

Applies to TMWSuiteDescription 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 3 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 3 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 3 record.

YWhen the next arrival time has the AG status, display the city/state for the next drop or pickup stop in the 3 record.

String2 If String1 is set to Y, specify whether the 3 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.

EDI Interface 42 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Including the current tractor locationYou can set up the system to add a 4 record to the 214 file that displays the tractor's location in City, State format.

AddGeoLocationToEDI214

Applies to TMWSuiteDescription Use this setting to include the current tractor location in the 4 record in

this format: 2 miles west of Toledo, OH.String1 N (default)

Add a 4 record that displays the tractor's current location. Y

Do not create a 4 record with the tractor's current location.

Including the order delivery date/timeYou can set up the system to include the date/time the final drop was actualized and changed to Completed status in the 4 record of the 214 file.

EDI Interface 43 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Including the scheduled Earliest and Latest date/timeYou can set up the system to include the scheduled Earliest and Latest dates/times in a miscellaneous/4 record that follows the record for each stop.

EDI214_EarliestLatest

Applies to TMWSuiteDescription Use this setting to include the scheduled Earliest and Latest date/time

for each stop in the 214 file. The information will appear in a miscellaneous/4 record following the record for each stop.

String1 N (default)Do not include the scheduled earliest and latest date/time for each stop in the 4 record.

YInclude the scheduled earliest and latest date/time for each stop in the 4 record.

Including STCC codesStandard Transportation Commodity Codes (STCC) are commodity identifier codes recognized throughout the transportation industry. You can specify whether the STCC code from the commodity profile will be included as a freight reference in the 4 record of 210 and 214 flat files.

EDI214ExportSTCC

Applies to TMWSuiteDescription 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 in the 4 record of 214 flat files.

String1 No (default)Do not include STCC codes in the 4 record.

YesInclude the STCC field value from the commodity profile as a freight reference in the 4 record.Notes: 1. The freight reference qualifier, REFSTC, will precede the STCC

code.2. If there are multiple commodities on a stop, all codes on the

record are included.

EDI Interface 44 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Specifying the reference number types included in record 6 (lading exception)Record 6 of the 214 file provides information about overages, shortages, and damages (OSD). You can specify the reference number types that will be included in the 6 record (the lading exception record).

EDI214_AddOSDRef

Applies to TMWSuiteDescription Record 6 of the 214 file provides information about overages,

shortages, and damages (OSD). Use this setting to specify the reference number types that will be included in the 6 record (lading exception record).

String1 User-define listEnter a comma-separated list of reference number types that will be added to the OSD record; for example, BL#,REF,SID,ST#.Note: Your entries must match the values recorded in the ReferenceNumber label's Abbr field. The label is accessed in System Administration.

Additional Notes

Reference numbers of the types specified here are appended to the end of each 6 record. The first 15 characters are used.

Including overage, shortage, and damaged informationYou can specify whether the overage, shortage, and damages (OSD) information recorded in the Trip Folder's Freight Detail grid will appear as a lading exception 6 record in the 214 file.

Adding the 7 cargo record for each freight detail on a stop You can specify whether a 7 record (cargo/commodity) will be added to the 214 file for each freight detail recorded on a stop.

Specifying whether a 214 will be sent for a late arrivalYou can specify whether a 214 will be sent for a late arrival.

EDI Interface 45 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Working with archived EDI 214 status updatesThe EDI Archive window, accessed in the Invoicing and Dispatch applications, allows you to view a list of archived 214 trip status documents. When a 214 flat file does not transfer properly, you re-extract the original document using the EDI Archive window.

Re-extracting 214 filesSometimes a 214 flat file does not transfer properly through the communication process, such as an FTP site. When this happens, you can re-extract the document without making any changes and make it available to send again.To re-extract 214 files, follow these steps.1. To open the EDI Archive window, do one of the following:

In the TMWSuite Dispatch application, go to Dispatch > View EDI Archives. In the TMWSuite Invoicing application, go to Process > View EDI Archive.At the top of the EDI Archive window, Search Mode defaults to Archive.

2. Make entries in the fields at the top of the window about the file you want to reprocess.Field definitionsOrder# Enter the system-assigned order number.

Batch # Enter the universal EDI control number.Note: This number is not commonly used.

EDI Interface 46 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

Partner Select the trading partner whose documents you want to re-extract.

Type Select 214 Trip Status.

From / To Enter the start and end dates of the date range for which you want to re-extract archived documents.

ISA # Enter the ISA control number.

997 Select one of the following options: ReceivedView all 214s for which a 997 has been received. Not ReceivedView all 214s for which a 997 has not been received. AnyView all 214s, regardless of whether a 997 has been received.

Note: This feature is available when you have the license for the 997 processor, which is sold separately from the base system. For more information, contact your TMW EDI Support representative.

824 Select one of the following options: ReceivedView all 214s for which a 824 has been received. Not ReceivedView all 214s for which a 824 has not been received. AnyView all 214s, regardless of whether a 824 has been received.

Note: This feature is available when you have the license for the 824 processor, which is sold separately from the base system. For more information, contact your TMW EDI Support representative.

3. Click Retrieve.

EDI Interface 47 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

4. In the list, select each file that you want to re-extract.

Note: If no rows are selected, all documents in the list will be reprocessed.5. Click Re Extract.6. The EDI Extract message asks if you want to extract the file using the original

control number. Click Yes.Note: To assign a new control number to the re-extracted file, click No.

7. In the Save EDI File As window, navigate to the correct folder.Note: The file name defaults to that specified in the [EDIFileSave]214Data setting in your TTS50. If necessary, enter a different File name.

8. Click Save.A message indicates that the extraction to a flat file is complete.

9. Click OK to close the message.10.Click Close to exit the EDI Archive window.

Displaying an order's delivery appointment date/time in the Planning WorksheetUse this setting to display the delivery appointment date/time recorded for each order in the Planning Worksheet's Available Trips grid.

ShowDeliveryAndAppointment

Applies to TMWSuite, EDIDescription Use this setting to populate the Appt Date and Delivery Date fields in

the Dispatch Planning Worksheet.

EDI Interface 48 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

ShowDeliveryAndAppointment

String1 N (default)Do not populate the Appt Date and Delivery Date fields.

YPopulate the Appt Date and Delivery Date fields.1. The Appt Date field appears in the Available Trips grid. It

displays the delivery appointment date/time recorded for each order in the EDI 214 status document with the Accepted status.

2. The Delivery Date field appears in the Available Trips grid and Available Resources grid.

o In the Available Trips grid, it displays the requested delivery date/time for the final drop entered in the Req Delivery field in Order Entry.o In the Available Resources grid, it displays the date/time the driver's departure from the drop location was actualized.

EDI214lateAR

Applies to TMWSuiteDescription Specifies 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 EDI Codes Maintenance window's Auto 214 tab when setting up your trading partners.

EDI214CargoRecs

Applies to TMWSuiteDescription Determines whether the system will add a 7 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 7 cargo record in the 214 for each freight detail on the stop.

EDI Interface 49 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company

Working with EDI 214 Status Updates

EDI214_OSD

Applies to TMWSuiteDescription Determines whether the overage, shortage, and damaged information

recorded in the OSD Reason, OSD Qty, OSD Unit, and OSD Comment fields in the Freight Detail grid in the Dispatch Trip Folder will appear as a lading exception 6 record in the 214 flat file.

String1 No (default)Do not include the OSD field data in the 214 flat file.

YesInclude the entries from the OSD fields in the Freight Detail grid as a 6 record in the 214 flat file. For example, a lading exception containing data for an overage of 65 cases displays in a 6 record as OCAS6500comment.

EDI214_DeliveryDateTime

Applies to TMWSuiteDescription Use this setting to include the date/time the order was completed in

the 214 file. The information will appear in a miscellaneous/4 record in the order header section of each 214.

String1 N (default)Do not include the delivery date/time in the 4 record.

YInclude the delivery date/time in the 4 record.

EDI Interface 50 Revised: 12/2015TMWSuite Copyright TMW Systems, Inc. | A Trimble Company