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

X12 214 Transportation Carrier Shipment Status Message

X12 Release 6010

This X12 Transaction Set 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
  • ^ Repetition
EDI sample
  • Sample
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/grupo-logico/transportation-carrier-shipment-status-message/01GYW4XVMED7AK42VGQN31SZ6E
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
detail
1000 Loop
SE
2100
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 identifying 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 identifying 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

Code indicating 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

Code indicating 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
I65
Repetition Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

^
Repetition Separator
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

Code specifying the version number of the interchange control segments

00601
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2008
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 indicating sender's request for an interchange acknowledgment

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

Code indicating 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

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480

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

006010
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2008

Heading

ST
0100
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) is 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
0200
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
Only one of Reference Identification (B10-01) or Reference Identification Qualifier (B10-05) may be present
If either Reference Identification Qualifier (B10-05) or Reference Identification (B10-06) is present, then the other is required
B10-01
127
Reference Identification
Required
String (AN)
Min 1Max 80

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.
Usage notes

The carrier assigned reference number.
The carrier PRO number (CN).
Must match the value transmitted on the EDI 990 L11 001.

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)

Usage notes

The Logico Load ID.
Must match the Load ID issued on the EDI 204 B2 004.
If load was not tendered by Logico, set B10 002 = B10 001.

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.
Usage notes

Must match the SCAC issued on the EDI 204 B2 002.

B10-05
128
Reference Identification Qualifier
Optional
Identifier (ID)

Code qualifying the Reference Identification

Usage notes

If either B10 005 or B10 006 is present, then the other is required.

ZH
Carrier Assigned Reference Number

The interline carrier PRO number.

B10-06
127
Reference Identification
Optional
String (AN)
Min 1Max 80

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

  • B1006 is the carrier assigned bar code identification or another carrier assigned shipment identification, such as a manifest number.
Usage notes

The interline carrier PRO number.
If an interline carrier is being used, then you must report the interline carrier pro number here with a ZH qualifier.

MS3
0300
Heading > MS3

Interline Information

OptionalMax use 12

To identify the interline carrier and relevant data

Example
If State or Province Code (MS3-05) is present, then City Name (MS3-03) is required
MS3-01
140
Standard Carrier Alpha Code
Optional
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

  • MS301 is the Standard Carrier Alpha Code (SCAC) of the interline carrier.
Usage notes

SCAC for the interline carrier.
Must NOT be equal to SCAC transmitted in EDI 214 B10 003.

MS3-02
133
Routing Sequence Code
Required
Identifier (ID)

Code describing the relationship of a carrier to a specific shipment movement

1
1st Carrier after Origin Carrier
2
2nd Carrier after Origin Carrier
3
3rd Carrier after Origin Carrier
4
4th Carrier after Origin Carrier
MS3-03
19
City Name
Optional
String (AN)
Min 2Max 30

Free-form text for city name

  • MS303 is the city where the interline was performed.
Usage notes

The city where the interline transfer occurred.
If MS3 001 is present, then MS3 003 is required.

MS3-04
91
Transportation Method/Type Code
Optional
Identifier (ID)

Code specifying the method or type of transportation for the shipment

L
Contract Carrier

Truckload.

LT
Less Than Trailer Load (LTL)

Less Than Truckload.

MS3-05
156
State or Province Code
Optional
Identifier (ID)
Min 2Max 2

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

Usage notes

The state/province where the interline transfer occurred.
If MS3 003 or MS 005 is present, then the other is required.

Heading end

Detail

1000 Loop
RequiredMax >1
LX
0100
Detail > 1000 Loop > LX

Transaction Set Line 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

Usage notes

Number assigned for differentiation within a transaction set.
The first LX 001 value must be 1 and subsequent LX 001's must increment by 1.
Each LX Loop may contain only one set of detail segments within it (except for the L11 segment).
Each LX Loop must contain, at a minimum, two L11 segments.

L11
0200
Detail > 1000 Loop > L11

Business Instructions and Reference Number

RequiredMax use 999

To specify instructions in this business relationship or a reference number

Usage notes

To specify instructions or reference numbers pertaining to the specified stop (shipment) on a load.

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

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

Usage notes

The SI was issued on the EDI 204 S5 Loop, L11 001 (SI qualifier) and is mandatory for all status messages where a load tender was issued.
The QN was issued on the EDI 204 S5 Loop, S5 001 and is mandatory for all status messages.
The BM must be provided starting with the AF (Departed Pickup Location with shipment) status message.

L11-02
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

BM
Bill of Lading Number

The shipper's bill of lading number.

QN
Stop Sequence Number

The stop sequence number.

SI
Shipper's Identifying Number for Shipment (SID)

The Logico Shipment Identifier.

Q7
0400
Detail > 1000 Loop > Q7

Lading Exception Status

OptionalMax use 10

To specify the status of the shipment in terms of lading exception information

Usage notes

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

Example
Q7-01
33
Lading Exception Code
Required
Identifier (ID)

Code indicating the condition of the shipment

A
All Short
D
Damaged
O
Overage
Q7-02
211
Packaging Form Code
Required
Identifier (ID)

Code for packaging form of the lading quantity

BDL
Bundle
BIN
Bin
BOX
Box
CNT
Container
CRT
Crate
DRM
Drum
LSE
Loose
PCS
Pieces
PLT
Pallet
RCK
Rack
ROL
Roll
TBN
Tote Bin
Q7-03
80
Lading Quantity
Required
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity

Usage notes

Number of units of the lading commodity expressed in the packaging form code.

K1
0500
Detail > 1000 Loop > K1

Remarks

OptionalMax use 10

To transmit information in a free-form format for comment or special instruction

Example
K1-01
61
Free-form Information
Required
String (AN)
Min 1Max 30

Free-form information

K1-02
61
Free-form Information
Optional
String (AN)
Min 1Max 30

Free-form information

AT8
0700
Detail > 1000 Loop > AT8

Shipment Weight, Packaging and Quantity Data

OptionalMax use 10

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

Usage notes

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.

Example
AT8-01
187
Weight Qualifier
Required
Identifier (ID)

Code defining the type of weight

FR
Freight 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

Usage notes

The total weight of the shipment.

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.
Usage notes

If unknown, set equal to the number of shipping containers/handling units (AT8 005).
Must be >= AT8.005.

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

Number of units (pieces) of the lading commodity

  • AT805 is the quantity of handling units that are unitized (for example on a pallet or slip sheet). When added to the quantity in AT804 it is the total quantity of handling units for the shipment.
Usage notes

The total number of shipping containers/handling units (e.g. pallets, racks, etc.) for the shipment.
Must be <= AT8.004.

1100 Loop
RequiredMax >1
AT7
0800
Detail > 1000 Loop > 1100 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.

Usage notes

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

Example
AT7-01
1650
Shipment Status Indicator
Required
Identifier (ID)

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.
A9
Shipment Damaged
AF
Carrier Departed Pickup Location with Shipment
D1
Completed Unloading at Delivery Location
P1
Departed Terminal Location
SD
Shipment Delayed
X1
Arrived at Delivery Location
X3
Arrived at Pickup Location
X4
Arrived at Terminal Location
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

Usage notes

If the shipment is being reported as delayed (AT7 001 = SD), then AT7 002 is required.

A5
Unable to Locate
AF
Accident
AI
Mechanical Breakdown
AM
Shipper Related
AO
Weather or Natural Disaster Related
AS
Hold Due to Customs Documentation Problems
B1
Consignee Closed
B5
Held for Consignee
B8
Improper Unloading Facility or Equipment
BB
Held per Shipper
BE
Road Conditions
BS
Refused by Customer
D1
Carrier Dispatch Error
P2
Waiting Inspection
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

Usage notes

The date of the event that is being reported on the status message.

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)

Usage notes

The time of the event that is being reported on the status message.

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.
Usage notes

All times must be presented in the time zone which corresponds to the location specified in the associated MS1 segment.
Logico takes an "all times local" approach and will interpret the date/time presented in AT7 005 and 006 as being expressed in the time zone that corresponds to the location being reported.

LT
Local Time

Only valid value for this element.

MS1
0900
Detail > 1000 Loop > 1100 Loop > MS1

Equipment, Shipment, or Real Property Location

RequiredMax 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 or postal code

Usage notes

There can only be one MS1 segment per LX loop.

Example
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 Direction Identifier Code (MS1-07) is present, then Latitude Code (MS1-05) is required
MS1-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

Usage notes

The name of the city where the status event being reported occurred.

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

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

Usage notes

The state/province where the status event being reported occurred.
See Mexican State Codes list for valid values when reporting Mexican locations.

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

Code identifying the country

Usage notes

ISO-3166 three character code.
The country where the status event being reported occurred.

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.
Usage notes

The longitude where the status event being reported occurred.

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.
Usage notes

The latitude where the status event being reported occurred.

MS1-06
1280
Direction Identifier Code
Optional
Identifier (ID)

Code identifying geographic direction

  • MS106 may only be 'E' or 'W'.
Usage notes

If either MS1 004 or MS1 006 is present, then the other is required.

E
East
W
West
MS1-07
1280
Direction Identifier Code
Optional
Identifier (ID)

Code identifying geographic direction

  • MS107 may only be 'N' or 'S'.
Usage notes

If either MS1 005 or MS1 007 is present, then the other is required.

N
North
S
South
MS1-08
116
Postal Code
Optional
Identifier (ID)
Min 3Max 15

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

Usage notes

The postal code where the status event being reported occurred. Canadian postal codes must have a single blank space between the first three characters and the last three characters (e.g. N7M 5J9).

MS2
1000
Detail > 1000 Loop > 1100 Loop > MS2

Equipment or Container Owner and Type

OptionalMax use 2

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

Usage notes

There can only be one MS2 segment per LX loop.

Example
If either Standard Carrier Alpha Code (MS2-01) or Equipment Number (MS2-02) is present, then the other 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 15

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

Usage notes

Carrier equipment unit number (i.e. trailer number).

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

Code identifying type of equipment used for shipment

  • MS203 identifies the type for the equipment specified in MS202.
Usage notes

The equipment description code for the corresponding load tender was provided on the EDI 204 in N7 011.

02
Minivan
2B
20' Ocean Container
4B
40' Ocean Container
5A
53' Deck Van
5B
Refrigerated Van
5C
53' Rail Container
5D
53' Drop Frame Van
5Q
53' Quad
5T
53' Tridem
10
10' Cargo Van
11
12' Straight Truck
12
12' Van - Sprinter
16
16' Van - Sprinter
17
16' Straight Truck
18
18' Straight Truck
24
24' Straight Truck
28
28' Straight Truck
48
48' Dry Van
53
53' Air Ride Van
61
727
62
Boeing 737
63
Convair Aircraft
64
DC 3
65
DC 9
66
Falcon 20
67
Helicopter
68
King Air 90
69
Lear 24
70
Lear 25
71
Lear 35 / Metroliner
72
EMB 120 Brasilia / Shorts Aircraft
81
Tractor for Spotting
82
Warehouse
DD
Flatbed - Double Drop
DP
Dump Trailer
F2
Flatbed - Step Deck
FR
Flatbed - w/Side Kits
FT
Flat Bed Trailer
LU
Self Unloader
OT
Flatbed - Conestoga
ST
Flatbed - Curtainside
T1
Tanker
T2
Tow Truck
TC
Car Hauler
TP
Dry Bulk Pneumatic
1100 Loop end
1200 Ship From
RequiredMax >1
Variants (all may be used)
Ship To
N1
1300
Detail > 1000 Loop > Ship From > N1

Party Identification

RequiredMax use 1

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

Usage notes

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.

Example
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

Usage notes

Used to indicate the physical location of the ship-from for the shipment that the status message applies to.

SF
Ship From
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

Location 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.
Usage notes

Logico Location Identifier.
This value was provided on the EDI 204 S5 Loop, N1 Loop, N1 004 with a qualifier of 93 and a matching entity identifier code of either SF or ST.

N3
1500
Detail > 1000 Loop > Ship From > N3

Party Location

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

N4
1600
Detail > 1000 Loop > Ship From > 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

Usage notes

See Mexican State Codes list for valid values when reporting Mexican locations.

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
Required
Identifier (ID)
Min 2Max 3

Code identifying the country

Usage notes

ISO-3166 three character code.

G62
1700
Detail > 1000 Loop > Ship From > G62

Date/Time

RequiredMax use 1

To specify pertinent dates and times

  • The G62 segment shall not be used to report shipment status dates and/or times.
Example
If either Date Qualifier (G62-01) or Date (G62-02) is present, then the other is required
At least one of Date Qualifier (G62-01) or Time Qualifier (G62-03) is required
If either Time Qualifier (G62-03) or Time (G62-04) is present, then the other is required
G62-01
432
Date Qualifier
Optional
Identifier (ID)

Code specifying type of date

86
Actual Pickup Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

Usage notes

Provide the actual pickup date for the shipment.

G62-03
176
Time Qualifier
Optional
Identifier (ID)

Code specifying the reported time

8
Actual Pickup Time
Optional
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)

Usage notes

Provide the actual pickup time for the shipment.

G62-05
623
Time Code
Optional
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

Usage notes

All times must be presented in the time zone which corresponds to the location specified in the associated N1 segment.
Logico takes an "all times local" approach and will interpret the date/time presented in G62 002 and 004 as being expressed in the time zone that corresponds to the location being reported.

LT
Local Time

Only valid value for this element.

1200 Ship From end
1200 Ship To
RequiredMax >1
Variants (all may be used)
Ship From
N1
1300
Detail > 1000 Loop > Ship To > N1

Party Identification

RequiredMax use 1

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

Usage notes

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.

Example
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

Usage notes

Used to indicate the physical location of the ship-to for the shipment that the status message applies to.

ST
Ship To
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

Location 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.
Usage notes

Logico Location Identifier.
This value was provided on the EDI 204 S5 Loop, N1 Loop, N1 004 with a qualifier of 93 and a matching entity identifier code of either SF or ST.

N3
1500
Detail > 1000 Loop > Ship To > N3

Party Location

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

N4
1600
Detail > 1000 Loop > Ship To > 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

Usage notes

See Mexican State Codes list for valid values when reporting Mexican locations.

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
Required
Identifier (ID)
Min 2Max 3

Code identifying the country

Usage notes

ISO-3166 three character code.

G62
1700
Detail > 1000 Loop > Ship To > G62

Date/Time

RequiredMax use 1

To specify pertinent dates and times

  • The G62 segment shall not be used to report shipment status dates and/or times.
Example
If either Date Qualifier (G62-01) or Date (G62-02) is present, then the other is required
At least one of Date Qualifier (G62-01) or Time Qualifier (G62-03) is required
If either Time Qualifier (G62-03) or Time (G62-04) is present, then the other is required
G62-01
432
Date Qualifier
Optional
Identifier (ID)

Code specifying type of date

70
Scheduled Delivery Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

Usage notes

Provide the scheduled delivery date for the shipment.

G62-03
176
Time Qualifier
Optional
Identifier (ID)

Code specifying the reported time

X
Scheduled Delivery Time
Optional
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)

Usage notes

Provide the scheduled delivery time for the shipment.

G62-05
623
Time Code
Optional
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

Usage notes

All times must be presented in the time zone which corresponds to the location specified in the associated N1 segment.
Logico takes an "all times local" approach and will interpret the date/time presented in G62 002 and 004 as being expressed in the time zone that corresponds to the location being reported.

LT
Local Time

Only valid value for this element.

1200 Ship To end
1000 Loop end
SE
2100
Detail > 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

Detail 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

Sample

ST*214*897293~
B10*210807*2118386*XXXX~
LX*1~
L11*022822124*BM~
L11*1*QN~
L11*3729238*SI~
AT8*FR*L*226*1*1~
AT7*AF****20220228*1144*LT~
MS1*Rockford*MI*USA*0853313*0004375*W*N*49341~
MS2*XXXX*124C~
N1*SF*Adhezion~
N3*7730 Childsdale Ave NE~
N4*Rockford*MI*49341*USA~
G62*86*20220228*8*1130*LT~
N1*ST*Antolin St Clair - DUNS 117778503~
N3*4662 PUTTYGUT RD~
N4*China Township*MI*48054*USA~
G62*70*20220228*X*1800*LT~
SE*19*897293~

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.