Ryder
/
Shipment Status Update
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Ryder. Contact Ryder for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Ryder logo

X12 214 Shipment Status Update

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
  • LT Example
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/ryder/shipment-status-update/01GMR40DKZ31GJG83E2Y8V4YXK
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
Required
0100 Loop Consignee
0200 Loop
LX
130
Assigned Number
Max use 1
Required
AT8
200
Shipment Weight, Packaging and Quantity Data
Max use 10
Required
0260 Loop
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

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).

Ryder: For Truck Load carriers, the status update is required within 4 hours of the event.
For Less Than Truck Load carriers the status update is required by 5:00 am CST the morning following the event.

214
Transportation Carrier Shipment Status Message
ST-02
329
Transaction Set Control Number
Required
String (AN)
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
Required
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's PRO (invoice number) that identifies the shipment.
Usage notes

Ryder: Carrier Pro/Invoice Number as sent in the N9 02 on the EDI 990. Sent in the L11 01 with a CN Qualifier In the L11 02 on the EDI 204.

B10-02
145
Shipment Identification Number
Required
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)

Ryder: Shipper's Bill Of Lading Number. May be sent in the Header Level L11 01 with a MB qualifier in the L11 02, the Header Level L11 01 with an OQ qualifier in the L11 02, or in the Detail Level L11 01 with a P8 qualifier in the L11 02 on the EDI 204.

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.
B10-04
71
Inquiry Request Number
Optional
Numeric (N0)
Min 1Max 3

Identifying number assigned by inquirer

L11
030
Heading > L11

Business Instructions and Reference Number

RequiredMax use 300

To specify instructions in this business relationship or a reference number

  • At least one of L1101 or L1103 is required.
  • If either L1101 or L1102 is present, then the other is required.
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)

Code qualifying the Reference Identification

Ryder:
AO - Consignee Confirmation Number
BM - Should be sent in the B10 02.
LO - Ryder Load Number. Sent in the B2 04 in the EDI 204
PO - Customer PO. Sent in the L11 01 with a DJ qualifier in the L11 02 on the EDI 204
QN - Stop Number, 1 is the Pick Up, Increment Each Additional Stop By 1. 99 may be used for the final delivery location.

AO
Appointment Number
BM
Bill of Lading Number
LO
Load Planning Number
PO
Purchase Order Number
QN
Stop Sequence Number
L11-03
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

0100 Loop Consignee
RequiredMax 10
Variants (all may be used)
0100 Loop Shipper
N1
050
Heading > 0100 Loop Consignee > N1

Name

RequiredMax use 1

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

  • At least one of N102 or N103 is required.
  • If either N103 or N104 is present, then the other is required.
Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

CN
Consignee
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

94
Code assigned by the organization that is the ultimate destination of the transaction set
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party

Note- Ryder does not currently support this functionality. This will be supported in the upcoming release of the v005010 EDI 214.

If you are going to use a single Ryder EDI Receiver Id for all Ryder EDI 214 responses then you MUST put the correct Ryder client code in this element. The correct Ryder client code is mandatory either by using Ryder's unique client EDI Receiver Id or through the use of the N1 04.

Ryder Client Id For N1 04:
ABC – ABC Bottling Group
BACARDI - Bacardi
BOEING - Boeing
ADAMS – Cadbury Adams
DAP – Philips DAP
DRPEPPER – Dr. Pepper/Seven Up
DUKE – Duke Energy
FPLG – Florida Power and Light
HAR – Harman
HONEYWELL - Honeywell
HPFTL – Hewlett Packard FTL
HPNACC –Hewlett Packard NACC
HUHTAMAKI – Huhtamaki Americas
IGPS – Intelligent Global Pooling Systems
ITC – Imperial Tobacco Canada
ITO – Imperial Tobacco Mexico
LEX - Lexmark
MFRIDGE - Microfridge
MHA – Master Halco
MOLSON – Molson
MOTTS – Motts/Snapple
PBC – Pitney Bowes
PCE – Philips Consumer
PELLA – Pella Window and Door
PRC – Pratt & Whitney Canada
PRU – Pratt & Whitney US
RECKITT – Reckitt Benckiser
SYNGENTA – Syngenta Seed
USPS – United States Postal Service
XEROXGT - Xerox

N3
070
Heading > 0100 Loop Consignee > N3

Address Information

RequiredMax 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 Consignee > N4

Geographic Location

RequiredMax 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 Consignee end
0100 Loop Shipper
RequiredMax 10
Variants (all may be used)
0100 Loop Consignee
N1
050
Heading > 0100 Loop Shipper > N1

Name

RequiredMax use 1

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

  • At least one of N102 or N103 is required.
  • If either N103 or N104 is present, then the other is required.
Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

SH
Shipper
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

94
Code assigned by the organization that is the ultimate destination of the transaction set
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party

Note- Ryder does not currently support this functionality. This will be supported in the upcoming release of the v005010 EDI 214.

If you are going to use a single Ryder EDI Receiver Id for all Ryder EDI 214 responses then you MUST put the correct Ryder client code in this element. The correct Ryder client code is mandatory either by using Ryder's unique client EDI Receiver Id or through the use of the N1 04.

Ryder Client Id For N1 04:
ABC – ABC Bottling Group
BACARDI - Bacardi
BOEING - Boeing
ADAMS – Cadbury Adams
DAP – Philips DAP
DRPEPPER – Dr. Pepper/Seven Up
DUKE – Duke Energy
FPLG – Florida Power and Light
HAR – Harman
HONEYWELL - Honeywell
HPFTL – Hewlett Packard FTL
HPNACC –Hewlett Packard NACC
HUHTAMAKI – Huhtamaki Americas
IGPS – Intelligent Global Pooling Systems
ITC – Imperial Tobacco Canada
ITO – Imperial Tobacco Mexico
LEX - Lexmark
MFRIDGE - Microfridge
MHA – Master Halco
MOLSON – Molson
MOTTS – Motts/Snapple
PBC – Pitney Bowes
PCE – Philips Consumer
PELLA – Pella Window and Door
PRC – Pratt & Whitney Canada
PRU – Pratt & Whitney US
RECKITT – Reckitt Benckiser
SYNGENTA – Syngenta Seed
USPS – United States Postal Service
XEROXGT - Xerox

N3
070
Heading > 0100 Loop Shipper > N3

Address Information

RequiredMax 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 Shipper > N4

Geographic Location

RequiredMax 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 Shipper 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.

Ryder: The proper use of the AT7 segment for reporting events, event reasons and appointments is as follows:
Events- Use the AT7 01 for the actual event and the AT7 02 NS qualifier
Event Reason- Use the AT7 01 for the actual event and the AT7 02 NS qualifier Appointment- Use the AT7 03 for the actual event and the AT7 04 NA qualifier

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)

Code indicating the status of a shipment

Usage notes

At a minimum the carrier must be able to support the AF (Pick Up) and D1 (Delivered) status codes. If you are unable to support either of these status codes contact Ryder EDI so that you may be implemented on Ryder's web enabled tendering and status update applications.
The D1 and AF status codes are to be used for the actual event. These two code events are to be used to record the actual event day and time and will be used to update Ryder's tracking site accordingly.

A9
Shipment Damaged
AF
Carrier Departed Pick-up Location with Shipment
AG
Estimated Delivery
CD
Carrier Departed Delivery Location
D1
Completed Unloading at Delivery Location
J1
Delivered to Connecting Line
K1
Arrived at Customs
L1
Loading
OO
Paperwork Received - Did not Receive Shipment or Equipment
P1
Departed Terminal Location
PR
U.S. Customs Hold at In-Bond Location
R1
Received from Prior Carrier
S1
Trailer Spotted at Consignee's Location
SD
Shipment Delayed
X1
Arrived at Delivery Location
X2
Estimated Date and/or Time of Arrival at Consignee's Location
X3
Arrived at Pick-up Location
X4
Arrived at Terminal Location
X5
Arrived at Delivery Location Loading Dock
X6
En Route to Delivery Location
AT7-02
1651
Shipment Status or Appointment Reason Code
Optional
Identifier (ID)

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

A2
Incorrect Address
AD
Customer Requested Future Delivery
AG
Consignee Related
AH
Driver Related
AJ
Other Carrier Related
AM
Shipper Related
AN
Holiday - Closed
AO
Weather or Natural Disaster Related
AQ
Recipient Unavailable - Delivery Delayed
AS
Hold Due to Customs Documentation Problems
AX
Insufficient Pick-up Time
AY
Missed Pick-up
B1
Consignee Closed
B2
Trap for Customer
B5
Held for Consignee
B8
Improper Unloading Facility or Equipment
BB
Held per Shipper
BD
Border Clearance
BF
Carrier Keying Error
BH
Insufficient Time to Complete Delivery
BM
Flatcar Shortage
BP
Load Shifted
BQ
Shipment Overweight
BS
Refused by Customer
C5
Customer Strike
D1
Carrier Dispatch Error
D2
Driver Not Available
HB
Held Pending Appointment
NS
Normal Status
P4
Held for Full Carrier Load
RC
Reconsigned
S1
Delivery Shortage
T7
Insufficient Delivery Time
AT7-03
1652
Shipment Appointment Status Code
Optional
Identifier (ID)

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

Ryder: At a minimum the carrier must be able to support the AB (Delivery Appointment) and AA (Pick Up Appointment) status code. If you are unable to support this status code contact Ryder EDI so that you may be implemented on Ryder's web enabled tendering and status update applications.

AA - Pick Up Appointments Are Expected As Soon As They Are Made
AB - Delivery Appointments Are Expected As Soon As They Are Made

AA
Pick-up Appointment Date and/or Time
AB
Delivery Appointment Date and/or Time
AT7-04
1651
Shipment Status or Appointment Reason Code
Optional
Identifier (ID)

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

NA
Normal Appointment
AT7-05
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

AT7-06
337
Time
Required
Time (TM)
HHMM 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)

AT7-07
623
Time Code
Required
Identifier (ID)

Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow

  • If AT707 is not present then AT706 represents local time of the status.

Ryder: Please use the time zone for which the event occurred.

AT
Alaska Time
CT
Central Time
ET
Eastern Time
LT
Local Time
MT
Mountain Time
PT
Pacific Time
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
Only one of City Name (MS1-01) or Longitude Code (MS1-04) may be present
If either Longitude Code (MS1-04) or Latitude Code (MS1-05) is present, then the other is required
If Direction Identifier Code (MS1-06) is present, then Longitude Code (MS1-04) is required
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
If State or Province Code (MS1-02) is present, then City Name (MS1-01) is required
If Country Code (MS1-03) is present, then City Name (MS1-01) is required
If Direction Identifier Code (MS1-07) is present, then Latitude Code (MS1-05) is required
MS1-01
19
City Name
Optional
String (AN)
Min 2Max 30

Free-form text for city name

MS1-02
156
State or Province Code
Optional
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

MS1-04
1654
Longitude Code
Optional
Identifier (ID)
Min 7Max 7

Code indicating the longitude in degrees (3 positions), minutes (2 positions), and seconds (2 positions)

  • MS104 is the longitude expressed in Degrees, Minutes, and Seconds.
MS1-05
1655
Latitude Code
Optional
Identifier (ID)
Min 7Max 7

Code indicating the latitude in degrees (3 positions), minutes (2 positions), seconds (2 positions)

  • MS105 is the latitude expressed in Degrees, Minutes, and Seconds.
MS1-06
1280
Direction Identifier Code
Optional
Identifier (ID)

Code identifying geographic direction

  • MS106 may only be 'E' or 'W'.
E
East
W
West
MS1-07
1280
Direction Identifier Code
Optional
Identifier (ID)

Code identifying geographic direction

  • MS107 may only be 'N' or 'S'.
N
North
S
South
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

Usage notes

MS203 identifies the type for the equipment specified in MS202.

Example
If either Standard Carrier Alpha Code (MS2-01) or Equipment Number (MS2-02) is present, then the other is required
If Equipment Number Check Digit (MS2-04) is present, then Equipment Number (MS2-02) is required
MS2-01
140
Standard Carrier Alpha Code
Optional
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

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

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

MS2-03
40
Equipment Description Code
Optional
Identifier (ID)
Min 2Max 2

Code identifying type of equipment used for shipment

  • MS203 identifies the type for the equipment specified in MS202.
MS2-04
761
Equipment Number Check Digit
Optional
Numeric (N0)
Min 1Max 1

Number which designates the check digit applied to a piece of equipment

0205 Loop end
AT8
200
Heading > 0200 Loop > AT8

Shipment Weight, Packaging and Quantity Data

RequiredMax use 10

To specify shipment details in terms of weight, and quantity of handling units

Example
If either Volume Unit Qualifier (AT8-06) or Volume (AT8-07) is present, then the other is required
AT8-01
187
Weight Qualifier
Required
Identifier (ID)

Code defining the type of weight

A
Consolidated Weight
A1
Dimensional Weight
B
Billed Weight
F
Deficit Weight
G
Gross Weight
AT8-02
188
Weight Unit Code
Required
Identifier (ID)

Code specifying the weight unit

K
Kilograms
L
Pounds
AT8-03
81
Weight
Required
Decimal number (R)
Min 1Max 10

Numeric value of weight

AT8-04
80
Lading Quantity
Required
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity

  • AT804 is the quantity of handling units that are not unitized (for example a carton). When added to the quantity in AT805, it is the total quantity of handling units in the shipment.
AT8-06
184
Volume Unit Qualifier
Optional
Identifier (ID)

Code identifying the volume unit

E
Cubic Feet
AT8-07
183
Volume
Optional
Decimal number (R)
Min 1Max 8

Value of volumetric measure

0260 Loop
OptionalMax >1
EFI
423
Heading > 0200 Loop > 0260 Loop > EFI

Electronic Format Identification

RequiredMax use 1

To provide basic information about the electronic format of the interchange data

Example
If Program Identifier (EFI-05) is present, then Version Identifier (EFI-04) is required
If Interchange Format (EFI-07) is present, then Version Identifier (EFI-06) is required
If Compression Technique (EFI-09) is present, then Version Identifier (EFI-08) is required
If either Version Identifier (EFI-15) or Filter ID Code (EFI-16) is present, then the other is required
EFI-01
786
Security Level Code
Required
Identifier (ID)

Code indicating the level of confidentiality assigned by the sender to the information following

ZZ
Mutually Defined
EFI-02
933
Free-Form Message Text
Required
String (AN)
Min 1Max 264

Free-form message text

EFI-03
797
Security Technique Code
Optional
Identifier (ID)
Min 2Max 2

Code indicating that this element will be used to tell an EDI translator program which security technique to use

EFI-04
799
Version Identifier
Optional
String (AN)
Min 1Max 30

Revision level of a particular format, program, technique or algorithm

EFI-05
802
Program Identifier
Optional
String (AN)
Min 1Max 30

Identifies the name of the software program from which the technical data originates

EFI-06
799
Version Identifier
Optional
String (AN)
Min 1Max 30

Revision level of a particular format, program, technique or algorithm

EFI-07
801
Interchange Format
Optional
String (AN)
Min 1Max 30

Industry or proprietary standard used to identify the format of the data

EFI-08
799
Version Identifier
Optional
String (AN)
Min 1Max 30

Revision level of a particular format, program, technique or algorithm

EFI-09
800
Compression Technique
Optional
String (AN)
Min 1Max 30

Identifies the digital data compression means and the type

EFI-10
789
Drawing Sheet Size Code
Optional
String (AN)
Min 2Max 2

Code indicating the drawing size and orientation of a technical drawing as specified and described in the current version of standards ANSI Y14.1 and ISO 5457 (E); see the listed ANSI and ISO standards for the maximum lengths for rolled sheets *

EFI-11
803
File Name
Optional
String (AN)
Min 1Max 64

Name assigned or declared for a file or used by a program to identify a file; exact format of the name depends on the computer operating system being used; name also may be known as the file's "data set name"

EFI-12
804
Block Type
Optional
String (AN)
Min 1Max 4

Organization of a data block such as fixed length, variable length, spanned, etc. Synonym for "data format"

EFI-13
787
Record Length
Optional
Numeric (N)
Min 1Max 15

Quantity of characters or bytes in a record. Synonyms are "logical record length" and "record size"

EFI-14
788
Block Length
Optional
Numeric (N)
Min 1Max 5

Quantity of data elements in a block, usually specified in units such as records, words or characters; synonym for "block size"

EFI-15
799
Version Identifier
Optional
String (AN)
Min 1Max 30

Revision level of a particular format, program, technique or algorithm

EFI-16
1570
Filter ID Code
Optional
Identifier (ID)
Min 3Max 3

Code specifying the type of filter used to convert data code values

BIN
426
Heading > 0200 Loop > 0260 Loop > BIN

Binary Data

OptionalMax use 1

To transfer binary data in a single data segment and allow identification of the end of the data segment through a count; there is no identification of the internal structure of the binary data in this segment

Example
BIN-01
784
Length of Binary Data
Required
Numeric (N0)
Min 1Max 15

The length in integral octets of the binary data

BIN-02
785
Binary Data
Required
Binary (B)
Min 1Max 4000000000

A string of octets which can assume any binary pattern from hexadecimal 00 to FF

0260 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
String (AN)
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

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

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

LT Example

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231103*0255*U*00401*000000001*0*T*>~
GS*QM*SENDERGS*RECEIVERGS*20231103*025525*000000001*X*004010~
ST*214*099510001~
B10*4735103*5365205*SCAC~
L11*5365205*LO~
L11*01*QN~
L11*392651*PO~
L11*392651*PO~
N1*SH*HUHTAMAKI FSBU~
N3*5566 NEW VIENNA ROAD~
N4*NEW VIENNA*OH*45159*US~
N1*CN*HUHTAMAKI~
N3*100 HIGGENSON AVE~
N4*LINCOLN*RI*02865*US~
LX*1~
AT7***AA*NA*20080903*1600*ET~
MS1*NEW VIENNA*OH*US~
AT8*G*L*6240*402~
EFI*ZZ*NAME~
SE*18*099510001~
GE*1*000000001~
IEA*1*000000001~

LTL Example

ISA*00* *00* *02*SCAC *01*006922827USP1 *080903*1132*U*00401*000020832*0*P*>-
GS*QM*SCAC*006922827USP1*20080903*1132*20832*X*004010-
ST*214*208320001-
B10*082269732X*007018135*SCAC*3-
L11*1000713*PO-
L11*5335266*LO-
N1*SH*USPS-
N3*500 SW GARY ORMSBY DR-
N4*TOPEKA*KS*66624-
N1*CN*MAINT STOCKRM-
N3*7540 E 53RD PL-
N4*DENVER*CO*802660001-
LX*1-
AT7*A9*B2***20080903*1007*MT-
AT7*AG*B2***20080902*1007*MT-
AT8*B*L*305*2-
EFI*ZZ*NAME-
SE*16*208320001-
GE*1*20832-
IEA*1*000020832-

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.