To start and identify an interchange of zero or more functional groups and interchange-related control segments
Rivian Automotive, Inc X12 120 Vehicle Shipping Order
Plan X12 120 Vehicle Shipping Order for Rivian Automotive, Inc. Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 12
- Loops
- 2
- X12 120
- Partner references ↗
Implementation guide
Rivian Automotive, Inc: 120 mapping and validation
X12 120 Vehicle Shipping Order is used when a vehicle is ready to be assigned for transport or service. Preserve vehicle identification number, movement order and destination so the vehicle movement order in your business system stays connected to the original document.
This document is listed for Rivian Automotive, Inc. Confirm the version, required fields and responses that apply to your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | vehicle movement order vehicle identification number, movement order and destination |
|
| Update the receiving system | Processing the vehicle movement order ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the vehicle movement order Original document reference and matching response |
|
The document reference includes 12 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 928 Automotive Inspection Detail
vehicle inspection result: vehicle condition is inspected.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a vehicle is ready to be assigned for transport or service. Name the operational owner of the vehicle movement order and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map vehicle identification number, movement order and destination. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Rivian Automotive, Inc guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic vehicle movement order data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful vehicle movement order processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 120 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic vehicle movement order data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out vehicle movement order without processing it twice.
Transaction context
Where 120 Vehicle Shipping Order fits on Rivian Automotive, Inc
- Rivian Automotive, Inc channels
- 1 of 1
1 of Rivian Automotive, Inc's 1 channel list 120
- Trading partners
- 1
partner references list 120
- Channels
- 1
channel entries list 120
Document structure
X12 120 Vehicle Shipping Order at the element level
The X12 120 reference contains 14 segment entries and 62 data elements; 34 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 14
- Data elements
- 62
- Mandatory elements
- 34
| Segment | Elements | Mandatory |
|---|---|---|
| BVP | 8 | 3 |
| VC | 4 | 1 |
| N1 | 4 | 1 |
| N2 | 1 | 1 |
| N3 | 2 | 1 |
Key identifiers in 120
- Vehicle Production Status
- Identification Code Qualifier
- Identification Code
- Vehicle Identification Number
- Entity Identifier Code
- Name
- Address Information
Segment reference — 12 segments 2 loops · X12 120 Vehicle Shipping Order
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of the Vehicle Shipping Order Transaction Set
G62 Loop Repeat: 99
To specify pertinent dates and times
VC Loop Repeat: 999
To define motor vehicle identification and logistics
To define motor vehicle characteristics
To identify a party by type of organization, name, and code
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To specify additional names or those longer than 35 characters in length
To specify the location of the named party
To specify the geographic place of the named party
Related references
Other transactions in Rivian Automotive, Inc
Other EDI documents listed on this channel.
Transportation Carrier Shipment Status Message X12 214 Automotive Inspection Detail X12 928 Purchase Order Change Request Buyer Initiated X12 860 Purchase Order X12 850 Invoice X12 810 Purchase Order Acknowledgment X12 855 Ship Notice Manifest X12 856 Motor Carrier Load Tender X12 204 Motor Carrier Freight Details And Invoice X12 210 Response To A Load Tender X12 990
No references match your search.
Showing 10 of 10 references
Browse the full directoryRivian Automotive, Inc EDI 120 questions
Common questions about 120 Vehicle Shipping Order on the Rivian Automotive, Inc channel.
What is X12 120 Vehicle Shipping Order used for?
120 is used when a vehicle is ready to be assigned for transport or service. It carries information for the vehicle movement order. Match it to your business system using vehicle identification number, movement order and destination.
Is 120 required for Rivian Automotive, Inc?
120 is listed for Rivian Automotive, Inc. Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 120?
Start with vehicle identification number, movement order and destination and the target vehicle movement order. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 120 error handling?
Change a vehicle destination after allocation and route the change for dispatch review. Submit the same vehicle movement twice and prevent duplicate transport work. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 120 relate to other EDI messages?
X12 928 Automotive Inspection Detail is a related document also listed on Rivian Automotive, Inc. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 120 and 928?
120 is used when a vehicle is ready to be assigned for transport or service. 928 is used when vehicle condition is inspected. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
Connect Rivian Automotive, Inc EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
