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 125 Multilevel Railcar Load Details

The X12 document used to report the departure of a multilevel railcar and the vehicles loaded on it to the vehicle manufacturer.

Sent by
Origin rail carrier or loading contractor
Received by
Vehicle manufacturer and destination parties
Standard
ANSI ASC X12

What is an EDI 125?

The EDI 125 Multilevel Railcar Load Details is the ANSI X12 transaction set the origin rail carrier or loading contractor uses to report the departure of a multilevel railcar and its contents to the vehicle manufacturer. It is used by the manufacturer, the origin and destination carriers and the unloading facility.

Multilevel railcars, or auto-racks, carry finished vehicles on two or three decks. Knowing which vehicles are on each car lets the destination ramp plan unloading and the manufacturer track every vehicle in transit.

How the EDI 125 worksDiagram of the EDI 125 Multilevel Railcar Load Details. Origin rail carrier or loading contractor sends it to vehicle manufacturer and destination parties. It usually follows 120. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BMM (Beginning Segment for Multilevel Railcar Load Details Transaction), G62 (Date/Time) and N7 (Equipment Details). 0 optional loops are listed by their first segment.How the EDI 125 worksMultilevel Railcar Load Details: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS120Vehicle Shipping OrderEDI 125SENDEROrigin rail carrier orloading contractorRECEIVERVehicle manufacturerand destination parties997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code MRGS … GETransaction set 125ST … SEHEADINGBMMBeginning Segment for Multilevel Railcar Load Details TransactionG62Date/TimeN7Equipment DetailsBlue 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 125. Your trading partner's implementation guide adds its own requirements.
How the EDI 125 worksDiagram of the EDI 125 Multilevel Railcar Load Details. Origin rail carrier or loading contractor sends it to vehicle manufacturer and destination parties. It usually follows 120. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BMM (Beginning Segment for Multilevel Railcar Load Details Transaction), G62 (Date/Time) and N7 (Equipment Details). 0 optional loops are listed by their first segment.How the EDI 125 worksMultilevel Railcar Load Details: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWS120Vehicle Shipping OrderEDI 125SENDEROrigin railcarrier orloadingcontractorRECEIVERVehiclemanufacturerand destinationparties997 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 MR (GS … GE)Transaction set 125 (ST … SE)HEADINGBMMBeginning Segment forMultilevel Railcar LoadDetails TransactionG62Date/TimeN7Equipment DetailsBlue 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 125. Your trading partner'simplementation guide adds its own requirements.

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

  • Reporting the vehicles loaded on each auto-rack
  • Reporting departures from the loading ramp
  • Informing destination unloading facilities

Where it fits in the document flow

Usually follows 120 Vehicle Shipping Order
This document 125 Multilevel Railcar Load Details
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 125 (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
  • BMM
  • G62
  • N7
  • SE

Practical example

The 125 in practice

A loading contractor at a plant ramp fills a tri-level auto-rack with 15 vehicles. When the car departs, it sends the manufacturer and the destination ramp a 125 with the railcar's identification and each vehicle's identification number and deck position. The destination ramp plans unloading and truck deliveries before the car arrives.

Implementation

Implementation considerations for the 125

  • Record each vehicle's position on the railcar.
  • Report departures promptly to all parties.
  • Match vehicles to their shipping orders.
  • Identify railcars by reporting marks and numbers.

How ECOM helps

Automate the 125 with ECOM

Industry

Automotive

Schedules, ship notices, labels, self-billing and multi-plant routing for automotive suppliers.

Industry

Trucking and Transportation

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

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 transportation documents

All 80 transportation documents

Need help with the EDI 125?

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

Request a Demo Contact us