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 475 Rail Route File Maintenance

The X12 document used to distribute updates of the rail industry route file.

Sent by
Rail industry route file administrator
Received by
Railroads and other users
Standard
ANSI ASC X12

What is an EDI 475?

The EDI 475 Rail Route File Maintenance is the ANSI X12 transaction set used to distribute route file updates of the rail industry route file.

The route file defines the valid routes between railroads, identified by codes used on waybills and in rating. When routes are added, changed or withdrawn, every railroad and shipper using route codes needs the update to avoid rejected waybills and misrouted cars. Route codes appear on bills of lading and waybills, so an unknown or withdrawn code can cause rejected waybills, misrouted cars or billing errors.

How the EDI 475 worksDiagram of the EDI 475 Rail Route File Maintenance. Rail industry route file administrator sends it to railroads and other users. 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: BGN (Beginning Segment) and the required R9 loop with R9 (Route Code Identification) and DTM (Date/Time Reference). 0 optional loops are listed by their first segment.How the EDI 475 worksRail Route File Maintenance: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 475SENDERRail industry route fileadministratorRECEIVERRailroads and otherusers997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code SNGS … GETransaction set 475ST … SEHEADINGBGNBeginning SegmentRequired loop R9 · repeats up to 50R9Route Code IdentificationDTMDate/Time ReferenceBlue 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 475. Your trading partner's implementation guide adds its own requirements.
How the EDI 475 worksDiagram of the EDI 475 Rail Route File Maintenance. Rail industry route file administrator sends it to railroads and other users. 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: BGN (Beginning Segment) and the required R9 loop with R9 (Route Code Identification) and DTM (Date/Time Reference). 0 optional loops are listed by their first segment.How the EDI 475 worksRail Route File Maintenance: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 475SENDERRail industryroute fileadministratorRECEIVERRailroads andother users997 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 SN (GS … GE)Transaction set 475 (ST … SE)HEADINGBGNBeginning SegmentRequired loop R9 · repeats up to50R9Route Code IdentificationDTMDate/Time ReferenceBlue 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 475. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 475, 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 475 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

  • Distributing new or changed routes
  • Withdrawing obsolete routes
  • Keeping routing tables synchronized

Where it fits in the document flow

This document 475 Rail Route File Maintenance
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 475 (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
  • BGN
  • R9
  • DTM
  • SE

Practical example

The 475 in practice

A new interline route is established via a recently opened junction. The route file update is distributed with a 475, and shippers' systems load the new route code so it can be used on bills of lading.

Implementation

Implementation considerations for the 475

  • Load route updates before they are used.
  • Align routes with the junction and interchange data (437).
  • Remove withdrawn routes from shipper systems.
  • Follow industry reference file procedures.

How ECOM helps

Automate the 475 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

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

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 475?

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

Request a Demo Contact us