ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 121 — Vehicle Service

The vehicle carrier reports service events: loaded, in transit, delivered, damage observed, delay.

Purpose

The 121 is the status counterpart to the 120: operational events encountered per VIN during transport. Codes: LO (Loaded), AR (Arrived), DL (Delivered), DA (Damaged), DE (Delayed). Pushed to the manufacturer near real-time — auto supply-chain visibility pivot.

Envelope structure

The 121 travels inside the three X12 envelope levels (ISA/IEA, GS/GE with functional group VV, and ST/SE). Didactic example in 004010:

x12 example-121.x12 
ISA*00*          *00*          *ZZ*CARHAULER     *ZZ*ACMEAUTOMFR   *260518*1530*U*00401*000000121*0*P*>~
GS*VV*CARHAULER*ACMEAUTOMFR*20260518*1530*1*X*004010~
ST*121*0001~
B2A*VV*20260518*SVC-VV-001~
N9*VIN*1HGBH41JXMN109186~
N9*46*DL~
DTM*009*20260518152500~
N1*EV*DEALER ANYTOWN*92*DEAL01~
SE*7*0001~
GE*1*1~
IEA*1*000000121~

Common segments

  • Header — ST, B2A.
  • Vehicle event — N9 VIN + N9*46 service event.
  • Date/Time — DTM.
  • Location — N1*EV Event Location + N4.
  • Damage — N9*DA + free text if damage.
  • Summary — SE.

Common pitfalls

  • No DTM: timestamped event missing = uninterpretable.
  • Damage without description: DA alone does not say what is damaged. Include N9*DA + free text + photo URL if possible.
  • VIN unknown manufacturer-side: ensure the 121 references a VIN from the original 120.

Documentation

The 121 code and the Vehicle Service name are public and listed at x12.org/products/transaction-sets. The full loops/qualifiers/code-lists structure is distributed by DISA via proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.