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 121 Vehicle Service

The X12 document a carrier uses to tell a vehicle manufacturer that a requested movement or service has been performed, or that a vehicle's status changed.

Sent by
Rail or truck carrier
Received by
Vehicle manufacturer
Standard
ANSI ASC X12

What is an EDI 121?

The EDI 121 Vehicle Service is the ANSI X12 transaction set a carrier uses to notify a vehicle manufacturer that a requested movement or service has been performed on motor vehicles, or that a change in status has occurred.

Manufacturers track every finished vehicle from the plant to the dealer. Carriers report events such as receipt at the ramp, departure, arrival and delivery, and services performed. The events update the vehicle's status in the manufacturer's systems and support payment of the carrier.

How the EDI 121 worksDiagram of the EDI 121 Vehicle Service. Rail or truck carrier sends it to vehicle manufacturer. It usually follows 120. It is usually followed by 126 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BVS (Beginning Segment for Vehicle Service) and the required VC loop with VC (Motor Vehicle Control). 0 optional loops are listed by their first segment.How the EDI 121 worksVehicle Service: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS120Vehicle Shipping OrderEDI 121SENDERRail or truck carrierRECEIVERVehicle manufacturer997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY126Vehicle Application Advice997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code VSGS … GETransaction set 121ST … SEHEADINGBVSBeginning Segment for Vehicle ServiceRequired loop VC · repeats up to 9,999VCMotor Vehicle ControlBlue 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 121. Your trading partner's implementation guide adds its own requirements.
How the EDI 121 worksDiagram of the EDI 121 Vehicle Service. Rail or truck carrier sends it to vehicle manufacturer. It usually follows 120. It is usually followed by 126 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BVS (Beginning Segment for Vehicle Service) and the required VC loop with VC (Motor Vehicle Control). 0 optional loops are listed by their first segment.How the EDI 121 worksVehicle Service: who sends it, where it fits andwhat the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS120Vehicle Shipping OrderEDI 121SENDERRail or truckcarrierRECEIVERVehiclemanufacturer997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY126Vehicle Application Advice997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code VS (GS … GE)Transaction set 121 (ST … SE)HEADINGBVSBeginning Segment forVehicle ServiceRequired loop VC · repeats up to9,999VCMotor Vehicle ControlBlue 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 121. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 121, 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 121 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 vehicle departures and arrivals
  • Reporting delivery to dealers
  • Reporting services performed on vehicles

Where it fits in the document flow

Usually follows 120 Vehicle Shipping Order
This document 121 Vehicle Service
Usually followed by 126 Vehicle Application Advice997 Functional Acknowledgment

Structure

Mandatory segments in the 121 (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
  • BVS
  • VC
  • SE

Practical example

The 121 in practice

A truck carrier delivers eight vehicles to a dealer. Its system sends the manufacturer a 121 for each vehicle with the delivery time and any exceptions noted at handover. The manufacturer updates the vehicles to delivered and includes them in the carrier's next payment cycle.

Implementation

Implementation considerations for the 121

  • Report events promptly; they drive dealer and customer information.
  • Use the event codes the manufacturer defines.
  • Identify vehicles by their vehicle identification numbers.
  • Reconcile reported services with carrier invoices.

How ECOM helps

Automate the 121 with ECOM

Industry

Automotive

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

Solution

Supply Chain Visibility

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

Industry

Trucking and Transportation

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

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

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

Request a Demo Contact us