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 437 Railroad Junctions and Interchanges Activity

The X12 document the rail industry reference file uses to tell subscribers about junction and interchange updates.

Sent by
Rail industry reference file central site
Received by
Subscribers such as railroads
Standard
ANSI ASC X12

What is an EDI 437?

The EDI 437 Railroad Junctions and Interchanges Activity is the ANSI X12 transaction set that lets the Railroad Industry Reference File central site communicate junction and interchange update activity to subscribers, including the creation and expiration of interchange agreements.

Junctions are the points where railroads connect and exchange cars. Routing, rating and car hire all depend on knowing which interchanges exist and are active. Interchange agreements have effective and expiration dates, and routing and car hire systems must load each update before it applies.

How the EDI 437 worksDiagram of the EDI 437 Railroad Junctions and Interchanges Activity. Rail industry reference file central site sends it to subscribers such as railroads. 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: BJF (Beginning Segment Railroad Junctions and Interchanges Update Activity). 1 optional loops are listed by their first segment.How the EDI 437 worksRailroad Junctions and Interchanges Activity: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 437SENDERRail industry referencefile central siteRECEIVERSubscribers such asrailroads997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code RVGS … GETransaction set 437ST … SEHEADINGBJFBeginning Segment Railroad Junctions and Interchanges Update Activity+ 1 optional loop, starting with:JSBlue 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 437. Your trading partner's implementation guide adds its own requirements.
How the EDI 437 worksDiagram of the EDI 437 Railroad Junctions and Interchanges Activity. Rail industry reference file central site sends it to subscribers such as railroads. 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: BJF (Beginning Segment Railroad Junctions and Interchanges Update Activity). 1 optional loops are listed by their first segment.How the EDI 437 worksRailroad Junctions and Interchanges Activity:who sends it, where it fits and what thestandard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 437SENDERRail industryreference filecentral siteRECEIVERSubscriberssuch asrailroads997 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 RV (GS … GE)Transaction set 437 (ST … SE)HEADINGBJFBeginning Segment RailroadJunctions and InterchangesUpdate Activity+ 1 optional loop, starting with:JSBlue 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 437. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 437, 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 437 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 new interchange points
  • Notifying expired interchange agreements
  • Keeping routing data current

Where it fits in the document flow

This document 437 Railroad Junctions and Interchanges Activity
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 437 (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
  • BJF
  • JS
  • SE

Practical example

The 437 in practice

Two railroads agree to open a new interchange at a junction. The central site distributes the update with a 437, and railroads load it so the junction can be used in routes and rate calculations.

Implementation

Implementation considerations for the 437

  • Load updates before routes use the junction.
  • Remove expired interchanges from routing tables.
  • Align junction data with the route file.
  • Follow industry reference file procedures.

How ECOM helps

Automate the 437 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 437?

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

Request a Demo Contact us