MercuryGate
/
Transportation Carrier Shipment Status Message
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from MercuryGate. Contact MercuryGate for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
MercuryGate logo

X12 214 Transportation Carrier Shipment Status Message

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Transportation Carrier Shipment Status Message Transaction Set (214) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a transportation carrier to provide shippers, consignees, and their agents with the status of shipments in terms of dates, times, locations, route, identifying numbers, and conveyance.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
—
  • Sample from Mercury Gate 1
  • Sample from Mercury Gate 2
  • Sample from Mercury Gate 3
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/mercurygate/transportation-carrier-shipment-status-message/01H9K4JXQ5WVSF5ZEDC5BAZB38
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
B10
020
Beginning Segment for Transportation Carrier Shipment Status Message
Max use 1
Required
L11
030
Business Instructions and Reference Number
Max use 300
Optional
0100 Loop
N1
050
Name
Max use 1
Required
N3
070
Address Information
Max use 2
Optional
N4
080
Geographic Location
Max use 1
Optional
0200 Loop
LX
130
Assigned Number
Max use 1
Required
0205 Loop
AT7
140
Shipment Status Details
Max use 1
Required
MS1
143
Equipment, Shipment, or Real Property Location
Max use 1
Optional
MS2
146
Equipment or Container Owner and Type
Max use 1
Optional
0210 Loop
NM1
240
Individual or Organizational Name
Max use 1
Required
0250 Loop
SPO
410
Shipment Purchase Order Detail
Max use 1
Required
SE
610
Transaction Set Trailer
Max use 1
Required
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

>
Component Element Separator
GS

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

QM
Transportation Carrier Shipment Status Message (214)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

GS-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code used in conjunction with Data Element 480 to identify the issuer of the standard

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
214
Transportation Carrier Shipment Status Message
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

B10
020
Heading > B10

Beginning Segment for Transportation Carrier Shipment Status Message

RequiredMax use 1

To transmit identifying numbers and other basic data relating to the transaction set

Example
B10-01
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

  • B1001 is the carrier assigned reference number.
  • B1001 is the carrier's PRO (invoice number) that identifies the shipment.
B10-02
145
Shipment Identification Number
Optional
String (AN)
Min 1Max 30

Identification number assigned to the shipment by the shipper that uniquely identifies the shipment from origin to ultimate destination and is not subject to modification; (Does not contain blanks or special characters)

B10-03
140
Standard Carrier Alpha Code
Required
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

  • B1003 is required when used in Transaction Set 214.
L11
030
Heading > L11

Business Instructions and Reference Number

OptionalMax use 300

To specify instructions in this business relationship or a reference number

Example
L11-01
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

L11-02
128
Reference Identification Qualifier
Required
Identifier (ID)
Min 2Max 3

Code qualifying the Reference Identification

0100 Loop
OptionalMax 10
N1
050
Heading > 0100 Loop > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

BT
Bill-to-Party
CN
Consignee
OB
Ordered By
SF
Ship From
SH
Shipper
SP
Party filling Shipper's Order
ST
Ship To
N1-02
93
Name
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

Used when the AT701 = AG = Estimated Delivery

N3
070
Heading > 0100 Loop > N3

Address Information

OptionalMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

N4
080
Heading > 0100 Loop > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Required
Identifier (ID)
Min 2Max 2

Code (Standard State/Province) as defined by appropriate government agency

  • N402 is required only if city name (N401) is in the U.S. or Canada.
N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N4-04
26
Country Code
Optional
Identifier (ID)
Min 2Max 3

Code identifying the country

0100 Loop end
0200 Loop
RequiredMax 999999
LX
130
Heading > 0200 Loop > LX

Assigned Number

RequiredMax use 1

To reference a line number in a transaction set

Example
LX-01
554
Assigned Number
Required
Numeric (N0)
Min 1Max 6

Number assigned for differentiation within a transaction set

0205 Loop
RequiredMax 10
AT7
140
Heading > 0200 Loop > 0205 Loop > AT7

Shipment Status Details

RequiredMax use 1

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.

Example
If either Shipment Status Code (AT7-01) or Shipment Status or Appointment Reason Code (AT7-02) is present, then the other is required
Only one of Shipment Status Code (AT7-01) or Shipment Appointment Status Code (AT7-03) may be present
If either Shipment Appointment Status Code (AT7-03) or Shipment Status or Appointment Reason Code (AT7-04) is present, then the other is required
AT7-01
1650
Shipment Status Code
Optional
Identifier (ID)
Min 2Max 2

Code indicating the status of a shipment

  • If AT701 is present, AT705 is the date the status occurred. If AT703 is present, AT705 is a date related to an appointment.
  • If AT701 is present, AT706 is the time of the status. If AT703 is present, AT706 is the time of the appointment.
AT7-02
1651
Shipment Status or Appointment Reason Code
Optional
Identifier (ID)
Min 2Max 2

Code indicating the reason a shipment status or appointment reason was transmitted

Usage notes

This is used only when AT701 = X6
Only send status updates when the shipment/load has been delayed"
"allowable value = AF, AI, AG, AJ, AO, AH.

AT7-03
1652
Shipment Appointment Status Code
Optional
Identifier (ID)
Min 2Max 2

Code indicating the status of an appointment to pick-up or deliver a shipment

AT7-04
1651
Shipment Status or Appointment Reason Code
Optional
Identifier (ID)
Min 2Max 2

Code indicating the reason a shipment status or appointment reason was transmitted

AT7-05
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

AT7-06
337
Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

MS1
143
Heading > 0200 Loop > 0205 Loop > MS1

Equipment, Shipment, or Real Property Location

OptionalMax use 1

To specify the location of a piece of equipment, a shipment, or real property in terms of city and state or longitude and latitude

Example
If City Name (MS1-01) is present, then at least one of State or Province Code (MS1-02) or Country Code (MS1-03) is required
MS1-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

MS1-02
156
State or Province Code
Required
Identifier (ID)
Min 2Max 2

Code (Standard State/Province) as defined by appropriate government agency

MS1-03
26
Country Code
Optional
Identifier (ID)
Min 2Max 3

Code identifying the country

MS2
146
Heading > 0200 Loop > 0205 Loop > MS2

Equipment or Container Owner and Type

OptionalMax use 1

To specify the owner, the identification number assigned by that owner, and the type of equipment

Example
MS2-01
140
Standard Carrier Alpha Code
Required
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

MS2-02
207
Equipment Number
Required
String (AN)
Min 1Max 10

Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)

0205 Loop end
0210 Loop
OptionalMax 999999
NM1
240
Heading > 0200 Loop > 0210 Loop > NM1

Individual or Organizational Name

RequiredMax use 1

To supply the full name of an individual or organizational entity

Example
NM1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

N5
Party Who Signed the Delivery Receipt
NM1-02
1065
Entity Type Qualifier
Required
Identifier (ID)

Code qualifying the type of entity

  • NM102 qualifies NM103.
1
Person
NM1-03
1035
Name Last or Organization Name
Required
String (AN)
Min 1Max 35

Individual last name or organizational name

NM1-04
1036
Name First
Optional
String (AN)
Min 1Max 25

Individual first name

0210 Loop end
0250 Loop
OptionalMax 999999
SPO
410
Heading > 0200 Loop > 0250 Loop > SPO

Shipment Purchase Order Detail

RequiredMax use 1

To specify the purchase order details for a shipment

Example
SPO-01
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

0250 Loop end
0200 Loop end
SE
610
Heading > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Heading end
GE

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

IEA

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

Sample from Mercury Gate 1

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231101*0136*U*00401*000000001*0*T*>~
GS*QM*SENDERGS*RECEIVERGS*20231101*013603*000000001*X*004010~
ST*214*003300001~
B10*5556*MBL100*JAXL~
LX*1~
AT7*D1*NS***20141004*1500~
MS1*Tallahassee*FL*USA~
SE*6*003300001~
GE*1*000000001~
IEA*1*000000001~

Sample from Mercury Gate 2

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231101*0136*U*00401*000000001*0*T*>~
GS*QM*SENDERGS*RECEIVERGS*20231101*013618*000000001*X*004010~
ST*214*003300001~
B10*10202*MQ777*JAXL~
L11*TN5000*2I~
N1*CN*Harvard Square~
N3*5 Train Boston Rd*SUITE 48~
N4*Nashville*TN*37201*USA~
LX*1~
AT7***AB*NA*20141004*1500~
MS1*Nashville*TN*USA~
MS2*JAXL*10~
SPO*100920041~
SE*12*003300001~
GE*1*000000001~
IEA*1*000000001~

Sample from Mercury Gate 3

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231101*0136*U*00401*000000001*0*T*>~
GS*QM*SENDERGS*RECEIVERGS*20231101*013630*000000001*X*004010~
ST*214*003300001~
B10*10202*MQ777*JAXL~
L11*TN5000*2I~
N1*CN*Harvard Square~
N3*5 Train Boston Rd*SUITE 48~
N4*Nashville*TN*37201*USA~
LX*1~
AT7*D1*NS***20141004*1500~
MS1*Nashville*TN*USA~
MS2*JAXL*10~
NM1*N5*1*All in Home Supplier*John Jackson~
SPO*100920041~
SE*13*003300001~
GE*1*000000001~
IEA*1*000000001~

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.