To start and identify an interchange of zero or more functional groups and interchange-related control segments
Target X12 214 Transportation Carrier Shipment Status Message
Plan X12 214 Transportation Carrier Shipment Status Message for Target Direct Vendor Ship. Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 13
- Loops
- 3
- X12 214
- Partner references ↗
Implementation guide
Target Direct Vendor Ship: 214 mapping and validation
X12 214 Transportation Carrier Shipment Status Message is used when the carrier reports a transport milestone or exception. Preserve shipment reference, event code, event time and location so the shipment status event in your business system stays connected to the original document.
This document is listed for Target Direct Vendor Ship. 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 | shipment status event shipment reference, event code, event time and location |
|
| Update the receiving system | Processing the shipment status event ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the shipment status event Original document reference and matching response |
|
The document reference includes 13 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when the carrier reports a transport milestone or exception. Name the operational owner of the shipment status event and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map shipment reference, event code, event time and location. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Target guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic shipment status event 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 shipment status event processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 214 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic shipment status event 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 shipment status event without processing it twice.
Transaction context
Where 214 Transportation Carrier Shipment Status Message fits on Target Direct Vendor Ship
- Target channels
- 2 of 4
2 of Target's 4 channels list 214
- Trading partners
- 170
partner references list 214
- Channels
- 242
channel entries list 214
Frequently listed alongside 214
Document structure
X12 214 Transportation Carrier Shipment Status Message at the element level
The X12 214 reference contains 68 segment entries and 316 data elements; 63 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 68
- Data elements
- 316
- Mandatory elements
- 63
| Segment | Elements | Mandatory |
|---|---|---|
| B10 | 7 | 1 |
| MAN | 6 | 2 |
| K1 | 2 | 1 |
| N1 | 6 | 1 |
| N2 | 2 | 1 |
| N3 | 2 | 1 |
| G61 | 5 | 2 |
| MS3 | 5 | 2 |
| LX | 1 | 1 |
| Q7 | 3 | 1 |
Key identifiers in 214
- Standard Carrier Alpha Code
- Marks and Numbers Qualifier
- Marks and Numbers
- Free-Form Message
- Entity Identifier Code
- Name
- Address Information
- Contact Function Code
Segment reference — 13 segments 3 loops · X12 214 Transportation Carrier Shipment Status Message
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 transmit identifying numbers and other basic data relating to the transaction set
LX Loop Repeat: 999,999
To reference a line number in a transaction set
To specify instructions in this business relationship or a reference number
To indicate identifying marks and numbers for shipping containers
To transmit information in a free-form format for comment or special instruction
AT7 Loop Repeat: 10
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 the status of a shipment, the reason for that status, the date and time of the status and the date and time of any appointments scheduled.
N1 Loop Repeat: 5
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
Related references
214 Transportation Carrier Shipment Status Message on other Target channels
Compare the listed channel references and confirm their current implementation guides.
Related references
Other transactions in Target Direct Vendor Ship
Other EDI documents listed on this channel.
Purchase Order Change Request Buyer Initiated X12 860 Purchase Order X12 850 Text Message X12 864 Ship Notice Manifest X12 856 Purchase Order Acknowledgment X12 855 Inventory Inquiry Advice X12 846 Purchase Order Change Acknowledgment Request Seller Initiated X12 865
No references match your search.
Showing 7 of 7 references
Browse the full directoryTarget Direct Vendor Ship EDI 214 questions
Common questions about 214 Transportation Carrier Shipment Status Message on the Target Direct Vendor Ship channel.
What is X12 214 Transportation Carrier Shipment Status Message used for?
214 is used when the carrier reports a transport milestone or exception. It carries information for the shipment status event. Match it to your business system using shipment reference, event code, event time and location.
Is 214 required for Target Direct Vendor Ship?
214 is listed for Target Direct Vendor Ship. Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 214?
Start with shipment reference, event code, event time and location and the target shipment status event. 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 214 error handling?
Deliver an older status after a newer one and retain event history without moving the current status backward. Send one milestone twice and avoid duplicate customer notifications. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 214 relate to other EDI messages?
Keep 214 business processing separate from transport receipt and technical validation. Agree which preceding record, response or reconciliation completes the shipment status event workflow; confirm any required companion messages with your partner.
Connect Target 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.
