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 · Transportation

EDI 419 Advance Car Disposition

The X12 document that gives a receiving rail carrier advance notice of cars offered for interchange, so it can decide their disposition in advance.

Sent by
Delivering rail carrier or switching carrier
Received by
Receiving rail carrier
Standard
ANSI ASC X12

What is an EDI 419?

The EDI 419 Advance Car Disposition is the ANSI X12 transaction set that gives the receiving rail carrier advance notice of cars being offered for interchange, either directly or through a switching carrier, so it can decide their disposition before the actual interchange.

Disposition means deciding what will happen to each car on arrival, such as which train or yard track it goes to, or whether an empty car should be redirected. Knowing in advance helps the receiving railroad avoid delays and unnecessary handling.

How the EDI 419 worksDiagram of the EDI 419 Advance Car Disposition. Delivering rail carrier or switching carrier sends it to receiving rail carrier. It usually starts the exchange. It is usually followed by 420 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required E6 loop with E6 (Advance Car Disposition). 0 optional loops are listed by their first segment.How the EDI 419 worksAdvance Car Disposition: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 419SENDERDelivering rail carrieror switching carrierRECEIVERReceiving rail carrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY420Car Handling Information997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code SRGS … GETransaction set 419ST … SEHEADINGRequired loop E6 · repeats up to 150E6Advance Car DispositionBlue 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 419. Your trading partner's implementation guide adds its own requirements.
How the EDI 419 worksDiagram of the EDI 419 Advance Car Disposition. Delivering rail carrier or switching carrier sends it to receiving rail carrier. It usually starts the exchange. It is usually followed by 420 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required E6 loop with E6 (Advance Car Disposition). 0 optional loops are listed by their first segment.How the EDI 419 worksAdvance Car Disposition: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 419SENDERDelivering railcarrier orswitchingcarrierRECEIVERReceiving railcarrier997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY420Car Handling Information997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code SR (GS … GE)Transaction set 419 (ST … SE)HEADINGRequired loop E6 · repeats up to150E6Advance Car DispositionBlue 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 419. Your trading partner'simplementation guide adds its own requirements.

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

  • Offering cars for interchange in advance
  • Letting the receiving carrier plan car disposition
  • Coordinating interchange through a switching carrier

Where it fits in the document flow

This document 419 Advance Car Disposition
Usually followed by 420 Car Handling Information997 Functional Acknowledgment

Structure

Mandatory segments in the 419 (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
  • E6
  • SE

Practical example

The 419 in practice

A short line railroad will deliver 20 empty grain cars to a Class I railroad tomorrow. It sends a 419 listing the cars offered for interchange. The Class I railroad decides that 12 cars will go to a loading point on its own network and eight will return to their owner, and sends handling instructions with a 420.

Implementation

Implementation considerations for the 419

  • Send offers early enough for disposition decisions.
  • Identify cars and their status precisely.
  • Coordinate with switching carriers where involved.
  • Track the responses that redirect or block the cars.

How ECOM helps

Automate the 419 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 transportation documents

All 80 transportation documents

Need help with the EDI 419?

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

Request a Demo Contact us