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

X12 214 Transportation Carrier Shipment Status Message

X12 Release 5010

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 samples
  • Sample 1
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/rite-aid/transportation-carrier-shipment-status-message/01H3CCM0G44HT16ABDABSMHB5D
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
LX
0100
Transaction Set Line Number
Max use 1
Required
L11
0200
Equipment Number
Max use 999
Optional
L11
0200
Purchase Order Number
Max use 999
Optional
AT8
0700
Shipment Weight, Packaging and Quantity Data
Max use 10
Optional
Consignee
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

00501
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
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

005010
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003

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
B10-01
127
Reference Identification
Required
String (AN)
Min 1Max 50

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

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

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

L11
0200
Detail > 1000 Loop > L11

Equipment Number

OptionalMax use 999

To specify instructions in this business relationship or a reference number

Example
Variants (all may be used)
L11Purchase Order Number
L11-01
127
Reference Identification
Optional
String (AN)
Min 1Max 50

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

EQ
Equipment Number
L11
0200
Detail > 1000 Loop > L11

Purchase Order Number

OptionalMax use 999

To specify instructions in this business relationship or a reference number

Example
Variants (all may be used)
L11 Equipment Number
L11-01
127
Reference Identification
Optional
String (AN)
Min 1Max 50

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

PO
Purchase Order Number
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

AT804 and AT805 when added together should represent total quantity of
handling units in shipment.

Example
If either Weight Qualifier (AT8-01), Weight Unit Code (AT8-02) or Weight (AT8-03) are present, then the others are required
AT8-01
187
Weight Qualifier
Optional
Identifier (ID)

Code defining the type of weight

A3
Shippers Weight
B
Billed Weight
E
Estimated Net Weight
G
Gross Weight
L
Legal Weight
N
Actual Net Weight
AT8-02
188
Weight Unit Code
Optional
Identifier (ID)

Code specifying the weight unit

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

Numeric value of weight

AT8-04
80
Lading Quantity
Optional
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

Quantity of handling units that are not unitized (for example a carton).

AT8-05
80
Lading Quantity
Optional
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

Quantity of handling units that are unitized (for example on a pallet).

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.

Example
If Shipment Status or Appointment Reason Code (AT7-02) is present, then Shipment Status Indicator (AT7-01) is required
If Time (AT7-06) is present, then Date (AT7-05) is required
If Time Code (AT7-07) is present, then Time (AT7-06) is required
AT7-01
1650
Shipment Status Indicator
Optional
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.
A3
Shipment Returned to Shipper
A7
Refused by Consignee
AF
Carrier Departed Pickup Location with Shipment
AG
Estimated Delivery
AH
Attempted Delivery
AI
Shipment has been Reconsigned
AJ
Tendered for Delivery
AM
Loaded on Truck
AV
Available for Delivery
B6
Estimated to Arrive at Carrier Terminal
C1
Estimated to Depart Terminal Location
CA
Shipment Cancelled
CD
Carrier Departed Delivery Location
CL
Trailer Closed Out
D1
Completed Unloading at Delivery Location
J1
Delivered to Connecting Line
L1
Loading
OO
Paperwork Received - Did not Receive Shipment or Equipment
P1
Departed Terminal Location
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 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

A1
Missed Delivery
A2
Incorrect Address
A3
Indirect Delivery
AA
Mis-sort
AD
Customer Requested Future Delivery
AG
Consignee Related
AH
Driver Related
AI
Mechanical Breakdown
AJ
Other Carrier Related
AK
Damaged, Rewrapped in Hub
AL
Previous Stop
AM
Shipper Related
AO
Weather or Natural Disaster Related
AQ
Recipient Unavailable - Delivery Delayed
AR
Improper International Paperwork
AV
Exceeds Service Limitations
AX
Insufficient Pickup Time
AY
Missed Pickup
B1
Consignee Closed
NS
Optional
Date (DT)
CCYYMMDD format

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

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)

AT7-07
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

  • If AT707 is not present then AT706 represents local time of the status.
ET
Eastern Time
PT
Pacific Time
1100 Loop end
1200 Consignee
OptionalMax >1
Variants (all may be used)
Shipper
N1
1300
Detail > 1000 Loop > Consignee > N1

Party Identification

RequiredMax use 1

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

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

9
D-U-N-S+4, D-U-N-S Number with Four Character Suffix
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.
N4
1600
Detail > 1000 Loop > Consignee > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Optional
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
Optional
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
Optional
Identifier (ID)
Min 3Max 15

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

1200 Consignee end
1200 Shipper
OptionalMax >1
Variants (all may be used)
Consignee
N1
1300
Detail > 1000 Loop > Shipper > N1

Party Identification

RequiredMax use 1

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

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

9
D-U-N-S+4, D-U-N-S Number with Four Character Suffix
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.
N4
1600
Detail > 1000 Loop > Shipper > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Optional
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
Optional
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
Optional
Identifier (ID)
Min 3Max 15

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

G62
1700
Detail > 1000 Loop > Shipper > G62

Date/Time

OptionalMax 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

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)

1200 Shipper 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 1

ST*214*322080001~
B10*05406220680*10808165*ODFL*2~
LX*1~
L11*0001747038*PO~
L11*0082390352*PO~
L11*5082143*PO~
AT8*A3*L*10170*6~
AT7*AG*NS***20110120*1600*ET~
AT7*AM*NS***20110118*2105*ET~
AT7*X6*NS***20110118*2155*ET~
N1*SH*DR PEPPER SNAPPLE GROUP~
N4*JACKSONVILLE*FL*32220~
G62*86*20110118*8*23550332~
N1*CN**9*0145788920035~
N4*TUSCALOOSA*AL*35406~
SE*16*322080001~

Sample 2

ST*214*322080002~
B10*06909054881*00493530051327147*ODFL*2~
LX*1~
L11*5084290*PO~
AT8*A3*L*1998*1~
AT7*X4*NS***20110118*2159*ET~
N1*SH*M Z BERGER AND CO~
N4*EDISON*NJ*08817~
G62*86*20110117*8*23550332~
N1*CN**9*0145788920088~
N4*LANCASTER*CA*93536~
SE*12*322080002~

Sample 3

ST*214*322080003~
B10*08215912885*SO503874*ODFL*2~
LX*1~
L11*5071901*PO~
AT8*A3*L*1915*2~
AT7*X6*NS***20110118*2201*ET~
N1*SH*JOHN B SANFILIPPO~
N4*ELGIN*IL*60123~
G62*86*20110117*8*23550332~
N1*CN**9*0145788920060~
N4*ROME*NY*13440~
SE*12*322080003~

Sample 4

ST*214*322080004~
B10*09908623811*00712870002900275*ODFL*2~
LX*1~
L11*5076763*PO~
L11*5079523*PO~
AT8*A3*L*8605*13~
AT7*X4*NS***20110118*2305*ET~
N1*SH*BN ROCKLINE INDUSTRIES~
N4*BOONEVILLE*AR*72927~
G62*86*20110117*8*23550332~
N1*CN**9*0145788920010~
N4*PERRYMAN*MD*21130~
SE*13*322080004~

Sample 5

ST*214*322080005~
B10*11003725840*303E0000789*ODFL*2~
LX*1~
L11*5086361*PO~
AT8*A3*L*1166*2~
AT7*AG*NS***20110125*1600*ET~
N1*SH*IOVATE HEALTH SCIENCES INTL INC~
N4*BLASDELL*NY*14219~
G62*86*20110118*8*23550332~
N1*CN**9*0145788920081~
N4*WOODLAND*CA*95695~
SE*12*322080005~

Sample 6

ST*214*322080006~
B10*12201281016*226245*ODFL*2~
LX*1~
L11*508199301457889*PO~
AT8*A3*L*2105*3~
AT7*X4*NS***20110118*2229*PT~
N1*SH*WEBSTER INDUSTRIES~
N4*MONTGOMERY*AL*36117~
G62*86*20110114*8*23550332~
N1*CN**9*0145788920081~
N4*WOODLAND*CA*95695~
SE*12*322080006~

Sample 7

ST*214*322080007~
B10*28700820559*00710810001726195*ODFL*2~
LX*1~
L11*5079078*PO~
AT8*A3*L*90*1~
AT7*X4*NS***20110118*2229*PT~
N1*SH*DYNO MERCHANDISE~
N4*POMPANO BEACH*FL*33064~
G62*86*20110113*8*23550332~
N1*CN**9*0145788920081~
N4*WOODLAND*CA*95695~
SE*12*322080007~

Sample 8

ST*214*322080008~
B10*82940123522*HYI155744*ODFL*2~
LX*1~
L11*5081253*PO~
AT8*A3*L*1110*2~
AT7*X6*NS***20110118*2113*ET~
N1*SH*HYLANDS INC~
N4*CARSON*CA*90745~
G62*86*20110114*8*23550332~
N1*CN**9*0145788920010~
N4*PERRYMAN*MD*21130~
SE*12*322080008~

Sample 9

ST*214*322080009~
B10*99950346784*00192009320262006*ODFL*2~
LX*1~
L11*5080503*PO~
AT8*A3*L*982*2~
AT7*AM*NS***20110118*2308*ET~
N1*SH*RECKITT BENCKISER~
N4*PENDERGRASS*GA*30567~
G62*86*20110118*8*23550332~
N1*CN**9*0145788920035~
N4*TUSCALOOSA*AL*35406~
SE*12*322080009~

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.