972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Master data

EDI 217 Motor Carrier Loading and Route Guide

The X12 document a motor carrier uses to publish its loading instructions, terminals, points served and advertised service times.

Sent by
Motor carrier
Received by
Shippers and other interested parties
Standard
ANSI ASC X12

What is an EDI 217?

The EDI 217 Motor Carrier Loading and Route Guide is the ANSI X12 transaction set a motor carrier uses to provide its loading instructions or routing guide. A transmission can include the carrier's terminals, all the points it serves, a matrix of points served with advertised service times, and the breakbulk terminals used for each point.

Shippers load the 217 into routing and transportation systems to know which carrier serves a destination, how long delivery should take and where freight will be handled. It is reference data, updated when the carrier's network changes.

How the EDI 217 worksDiagram of the EDI 217 Motor Carrier Loading and Route Guide. Motor carrier sends it to shippers and other interested parties. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BLR (Transportation Carrier Identification). 3 optional loops are listed by their first segment.How the EDI 217 worksMotor Carrier Loading and Route Guide: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 217SENDERMotor carrierRECEIVERShippers and otherinterested parties997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code FGGS … GETransaction set 217ST … SEHEADINGBLRTransportation Carrier Identification+ 1 optional loop, starting with:N1DETAIL+ 2 optional loops, starting with:N1LXBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 217. Your trading partner's implementation guide adds its own requirements.
How the EDI 217 worksDiagram of the EDI 217 Motor Carrier Loading and Route Guide. Motor carrier sends it to shippers and other interested parties. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BLR (Transportation Carrier Identification). 3 optional loops are listed by their first segment.How the EDI 217 worksMotor Carrier Loading and Route Guide: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 217SENDERMotor carrierRECEIVERShippers andother interestedparties997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code FG (GS … GE)Transaction set 217 (ST … SE)HEADINGBLRTransportation CarrierIdentification+ 1 optional loop, starting with:N1DETAIL+ 2 optional loops, starting with:N1LXBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 217. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 217, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 217 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Publishing a carrier's service points and transit times
  • Updating terminal lists after network changes
  • Giving shippers loading instructions by destination

Where it fits in the document flow

This document 217 Motor Carrier Loading and Route Guide
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 217 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BLR
  • N1
  • LX
  • SV
  • SE

Practical example

The 217 in practice

An LTL carrier opens two terminals and adjusts its transit times in the Southeast. It sends its major shippers a 217 listing each served ZIP code range, the servicing terminal, the breakbulk terminal and the advertised transit days from each origin. A shipper's transportation system uses the updated times to choose carriers and promise delivery dates.

Implementation

Implementation considerations for the 217

  • Load the guide as reference data with an effective date.
  • Compare advertised transit times with actual performance from status messages.
  • Map carrier terminal and point codes to your own location data.
  • Request regular updates, since carrier networks change.

How ECOM helps

Automate the 217 with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related master data documents

All 25 master data documents

Need help with the EDI 217?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us