214 Transportation Carrier Shipment Status Message
Grupo Logico · X12 006010
Grupo Logico’s published 214 specification, rendered as an interactive guide. Expand any segment to see its elements, data types, lengths and accepted codes — then validate your own document against it below.
Specification
20 of 20 segments
HEADING
ST
Transaction Set Header ST
pos 0100
Optional
max —
B10
Beginning Segment For Transportation Carrier Shipment Status Message B10
pos 0200
Required
max —
MS3
Interline Information MS3
pos 0300
Optional
max 12
DETAIL
1000 Looprequired
LX
Transaction Set Line Number LX
pos 0100
Required
max —
L11
Business Instructions And Reference Number L11
To specify instructions or reference numbers pertaining to the specified stop (shipment) on a load.
pos 0200
Required
max 999
Q7
Lading Exception Status Q7
There can only be one Q7 segment per LX Loop.
The Q7 segment is only required if the carrier is reporting a lading exception (overage, shortage, or damage).
pos 0400
Optional
max 10
K1
Remarks K1
pos 0500
Optional
max 10
AT8
Shipment Weight Packaging And Quantity Data AT8
There can only be one AT8 segment per LX Loop.
The AT8 segment must be included starting with AF (Departed Pickup Location with shipment) status messages.
pos 0700
Optional
max 10
1100 Looprequired
AT7
Shipment Status Details AT7
There can only be one AT7 segment per LX loop.
At a minimum, X3, AF, X1 and D1 statuses must be provided for every shipment (bill of lading) as referenced in the 204 S5 Loop, L11 Segment, SI qualified value.
Carriers must also report in-transit updates (X6) every 30 minutes.
Any shipment that will be delivered after the scheduled delivery date/time, as specified on the EDI 204, MUST be reported ASAP with an SD status indicator (AT7 001).
pos 0800
Required
max —
MS1
Equipment Shipment Or Real Property Location MS1
There can only be one MS1 segment per LX loop.
pos 0900
Required
max —
MS2
Equipment Or Container Owner And Type MS2
There can only be one MS2 segment per LX loop.
pos 1000
Optional
max 2
1200 LoopShip Fromvariant 1 of 2required
N1
Party Identification N1
This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency, the "ID Code" (N1 004) must provide a key to the table maintained by the transaction processing party.
This segment is used to transmit the Logico location identifiers (location id) for the ship-from and shipto locations that the status message applies to.
pos 1300
Required
max —
N3
Party Location N3
pos 1500
Required
max 2
N4
Geographic Location N4
pos 1600
Required
max —
G62
Date Time G62
pos 1700
Required
max —
1200 LoopShip Tovariant 2 of 2required
N1
Party Identification N1
This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency, the "ID Code" (N1 004) must provide a key to the table maintained by the transaction processing party.
This segment is used to transmit the Logico location identifiers (location id) for the ship-from and shipto locations that the status message applies to.
pos 1300
Required
max —
N3
Party Location N3
pos 1500
Required
max 2
N4
Geographic Location N4
pos 1600
Required
max —
G62
Date Time G62
pos 1700
Required
max —
SE
Transaction Set Trailer SE
pos 2100
Optional
max —
Validate a 214
Paste or upload a document and check it against Grupo Logico’s published rules — segment order and repetition, required elements, field lengths, data types and accepted codes. Nothing is stored.
Go live on Grupo Logico’s 214 in days, not months
Weredi maps this guide to your ERP, runs the test cycle with Grupo Logico, and keeps the spec current as it changes.