Canadian Tire
/
Ship Notice/Manifest
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Canadian Tire. Contact Canadian Tire for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Canadian Tire logo

X12 856 Ship Notice/Manifest

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.

The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/canadian-tire/ship-noticemanifest/01HW5S55JKSKD4YW9N36M6EEPK
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
HL Loop Shipment
HL
010
Hierarchical Level
Max use 1
Required
TD1
110
Carrier Details (Quantity and Weight)
Max use 20
Required
TD5
120
Carrier Details (Routing Sequence/Transit Time)
Max use 12
Required
TD3
130
Carrier Details (Equipment)
Max use 12
Optional
REF
150
Reference Identification
Max use 1
Required
PER
151
Administrative Communications Contact
Max use 3
Required
DTM
200
Date/Time Reference
Max use 10
Required
N1 Loop
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

SH
Ship Notice/Manifest (856)
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

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).
856
Ship Notice/Manifest
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

BSN
020
Heading > BSN

Beginning Segment for Ship Notice

RequiredMax use 1

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

Usage notes

BSN01 - To correct or change an ASN, the Purpose code should be 07 for type "B" orders (REF02 of REF*PHC of 850=B) only. Otherwise, duplicate "00" ASNs will be be automatically rejected.

BSN02 - The Shipment Identification must always be unique for every ASN and must not contain any spaces.

ASNs must contain POs of the same Process Handling Type. Only one Process Handling type per ASN (850 – REF02 in the REF*PHC).

Example: BSN00TOR123456720030501165924

Example
BSN-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

00
Original
07
Duplicate (re-submission)
BSN-02
396
Shipment Identification
Required
String (AN)
Min 2Max 30

A unique control number assigned by the original shipper to identify a specific shipment

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BSN03 is the date the shipment transaction set is created.
Required
Time (TM)
HHMMSS 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)

  • BSN04 is the time the shipment transaction set is created.
Heading end

Detail

HL Loop Shipment
RequiredMax >1
Usage notes

Example: HL*1**S

HL
010
Detail > HL Loop Shipment > HL

Hierarchical Level

RequiredMax use 1

To identify dependencies among and the content of hierarchically related groups of data segments

  • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

  • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
S
Shipment
HL-04
736
Hierarchical Child Code
Optional
Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
TD1
110
Detail > HL Loop Shipment > TD1

Carrier Details (Quantity and Weight)

RequiredMax use 20

To specify the transportation details relative to commodity, weight, and quantity

Usage notes

Example: TD1PLT9020***G15546*LB

Example
If either Weight (TD1-07) or Unit or Basis for Measurement Code (TD1-08) is present, then the other is required
If Weight Qualifier (TD1-06) is present, then Weight (TD1-07) is required
TD1-01
103
Packaging Code
Required
String (AN)

Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required

Part 1/2
BAG
Bag
BBL
Barrel
BDL
Bundle
BOX
Box
BXI
Box, with inner container
CAN
Can
CAS
Case
COL
Coil
CRT
Crate
CTN
Carton
DRM
Drum
JAR
Jar
KIT
Kit
LIF
Lifts
PCS
Pieces
PKG
Package
PLT
Pallet
ROL
Roll
SLV
Sleeve
SPL
Spool
TBE
Tube
TRY
Tray
UNT
Unit
Part 2/2
90
Standard
TD1-02
80
Lading Quantity
Required
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity

TD1-06
187
Weight Qualifier
Required
Identifier (ID)

Code defining the type of weight

G
Gross Weight
TD1-07
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

TD1-08
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

KG
Kilogram
LB
Pound
TD5
120
Detail > HL Loop Shipment > TD5

Carrier Details (Routing Sequence/Transit Time)

RequiredMax use 12

To specify the carrier and sequence of routing and provide transit time information

Usage notes

Example: TD5***MCANADIAN TIRE

Example
TD5-04
91
Transportation Method/Type Code
Required
Identifier (ID)
Min 1Max 2

Code specifying the method or type of transportation for the shipment

TD5-05
387
Routing
Required
String (AN)
Min 1Max 35

Free-form description of the routing or requested routing for shipment, or the originating carrier's identity

TD3
130
Detail > HL Loop Shipment > TD3

Carrier Details (Equipment)

OptionalMax use 12

To specify transportation details relating to the equipment used by the carrier

Usage notes

If trailer number not available use 99NNNN (where NNNN is the Vendor ID, the same as REF02 in REF segment with ‘VR’ qualifier).

Appointment Vendors:
If your firm uses a prepaid carrier to send product to our distribution center, you will be given an appointment number. The appointment number must be entered in the trailer field (TD303) in the ASN. The correct format for the appointment number is A#####, where #### is the appointment number.
In order for the DC to be ready to receive your product at your scheduled dock time, we require your ASN the night before your appointment.
Put “COMC” in the TD505 segment to indicate that you are using a common carrier.
Example:
TD5**MCOMC
TD3*TL
*A12345

Example: TD3TLXYZ*998670

Example
TD3-01
40
Equipment Description Code
Required
Identifier (ID)

Code identifying type of equipment used for shipment

TL
Trailer (not otherwise specified)
TD3-02
206
Equipment Initial
Optional
String (AN)
Min 1Max 4

Prefix or alphabetic part of an equipment unit's identifying number

TD3-03
207
Equipment Number
Required
String (AN)
Min 1Max 10

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

REF
150
Detail > HL Loop Shipment > REF

Reference Identification

RequiredMax use >1

To specify identifying information

Usage notes

Example: REFVR9999

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

VR
Vendor ID Number
REF-02
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

PER
151
Detail > HL Loop Shipment > PER

Administrative Communications Contact

RequiredMax use 3

To identify a person or office to whom administrative communications should be directed

Usage notes

Example: PERDIDAVID ALEXANDERTE416-333-3333

Example
If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
PER-01
366
Contact Function Code
Required
Identifier (ID)

Code identifying the major duty or responsibility of the person or group named

DI
Delivery Instructions Contact
Required
String (AN)
Min 1Max 60

Free-form name

PER-03
365
Communication Number Qualifier
Required
Identifier (ID)

Code identifying the type of communication number

TE
Telephone
PER-04
364
Communication Number
Optional
String (AN)
Min 1Max 80

Complete communications number including country or area code when applicable

DTM
200
Detail > HL Loop Shipment > DTM

Date/Time Reference

RequiredMax use 10

To specify pertinent dates and times

Usage notes

Example: DTM01120030501

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

011
Shipped
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

N1 Loop
OptionalMax >1
N1
220
Detail > HL Loop Shipment > N1 Loop > N1

Name

RequiredMax use 1

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

Usage notes

Example: N1ST**92016136689003

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

ST
Ship To
N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

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

9
Distribution Center
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

CTC Distribution Centre or EAP Depot number from PO.

N1 Loop end
HL Loop Order
RequiredMax >1
Usage notes

Example: HL101*O

HL
010
Detail > HL Loop Shipment > HL Loop Order > HL

Hierarchical Level

RequiredMax use 1

To identify dependencies among and the content of hierarchically related groups of data segments

  • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

  • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

  • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
O
Order
HL-04
736
Hierarchical Child Code
Optional
Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
0
No Subordinate HL Segment in This Hierarchical Structure.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
PRF
050
Detail > HL Loop Shipment > HL Loop Order > PRF

Purchase Order Reference

RequiredMax use 1

To provide reference to a specific purchase order

Usage notes

Example: PRF99991234**20030214

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

Identifying number for Purchase Order assigned by the orderer/purchaser

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • PRF04 is the date assigned by the purchaser to purchase order.
TD1
110
Detail > HL Loop Shipment > HL Loop Order > TD1

Carrier Details (Quantity and Weight)

OptionalMax use 20

To specify the transportation details relative to commodity, weight, and quantity

Usage notes

Example: TD1PLT9020***G15546*LB

Example
If either Weight (TD1-07) or Unit or Basis for Measurement Code (TD1-08) is present, then the other is required
If Weight Qualifier (TD1-06) is present, then Weight (TD1-07) is required
TD1-01
103
Packaging Code
Required
String (AN)
Min 3Max 5

Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required

TD1-02
80
Lading Quantity
Required
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity

TD1-06
187
Weight Qualifier
Required
Identifier (ID)

Code defining the type of weight

G
Gross Weight
TD1-07
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

TD1-08
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

KG
Kilogram
LB
Pound
HL Loop Pack
OptionalMax >1
Usage notes

The Pack level is optional, but one of the Tare or the Pack level must be present. For cross-dock or direct ship PO's (850 BEG02 = RA or DS), the Pack level is MANDATORY.

Example: HL3020*P

Variants (all may be used)
HL Loop Shipping Tare
HL
010
Detail > HL Loop Shipment > HL Loop Order > HL Loop Pack > HL

Hierarchical Level

RequiredMax use 1

To identify dependencies among and the content of hierarchically related groups of data segments

  • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

  • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

  • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
P
Pack
HL-04
736
Hierarchical Child Code
Optional
Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
TD1
110
Detail > HL Loop Shipment > HL Loop Order > HL Loop Pack > TD1

Carrier Details (Quantity and Weight)

OptionalMax use 20

To specify the transportation details relative to commodity, weight, and quantity

Usage notes

Example: TD1***G15546*LB1245CF

Example
If either Weight (TD1-07) or Unit or Basis for Measurement Code (TD1-08) is present, then the other is required
If Weight Qualifier (TD1-06) is present, then Weight (TD1-07) is required
If either Volume (TD1-09) or Unit or Basis for Measurement Code (TD1-10) is present, then the other is required
TD1-06
187
Weight Qualifier
Required
Identifier (ID)

Code defining the type of weight

G
Gross Weight
TD1-07
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

TD1-08
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

KG
Kilogram
LB
Pound
TD1-09
183
Volume
Required
Decimal number (R)
Min 1Max 8

Value of volumetric measure

TD1-10
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

CF
Cubic Feet
CR
Cubic Meter
MAN
190
Detail > HL Loop Shipment > HL Loop Order > HL Loop Pack > MAN

Marks and Numbers

OptionalMax use >1

To indicate identifying marks and numbers for shipping containers

Usage notes

If the Pack level is used without the Tare level, the MAN segment must appear in the Pack level. The MAN segment is mandatory and must appear in EITHER the Tare level or the Pack level.

For cross-dock and direct ship PO's (850 BEG02 = RA or DS), the MAN segment at the Pack level is MANDATORY.

Example: MANGM00000999990000123464

Example
MAN-01
88
Marks and Numbers Qualifier
Required
Identifier (ID)

Code specifying the application or source of Marks and Numbers (87)

  • MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
  • When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
GM
SSCC-18 and Application Identifier
MAN-02
87
Marks and Numbers
Required
String (AN)
Min 1Max 48

Marks and numbers used to identify a shipment or parts of a shipment

  • When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
N1 Loop
OptionalMax >1
N1
220
Detail > HL Loop Shipment > HL Loop Order > HL Loop Pack > N1 Loop > N1

Name

RequiredMax use 1

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

Usage notes

This iteration of the N1 segment will only be sent for Cross Dock or Direct Ship orders (850 BEG02 = RA or DS). For Cross Dock and Direct Ship this segment is mandatory.

A new store will have a prefix of "7" in front of the original store number to differentiate between to the current and new locations. (eg. current store # 0126 new store # 70126).

Example: N1MA**920126

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

MA
Party for whom Item is Ultimately Intended
N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

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

92
Assigned by Buyer or Buyer's Agent (Store)
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

Format: (NNNN – existing store or NNNNN – New store)

N1 Loop end
HL Loop Item
RequiredMax >1
Usage notes

Example: HL4030*I

HL
010
Detail > HL Loop Shipment > HL Loop Order > HL Loop Pack > HL Loop Item > HL

Hierarchical Level

RequiredMax use 1

To identify dependencies among and the content of hierarchically related groups of data segments

  • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

  • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

  • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
I
Item
HL-04
736
Hierarchical Child Code
Optional
Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
0
No Subordinate HL Segment in This Hierarchical Structure.
LIN
020
Detail > HL Loop Shipment > HL Loop Order > HL Loop Pack > HL Loop Item > LIN

Item Identification

RequiredMax use 1

To specify basic item identification data

Usage notes

For country of origin use ISO 3166-1 alpha 2 codes.

For United States use ISO 3166-2 extension codes to indicate the state of origin.
Example codes:
Canada CA
China CN
Mexico MX
US- Illinois US-IL
US- Ohio US-OH

If a product has some from one country and some from another then separate for each country of origin.

Example: LIN1SK099-9999-6*CHCA

Example
If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required
If either Product/Service ID Qualifier (LIN-06) or Product/Service ID (LIN-07) is present, then the other is required
LIN-01
350
Assigned Identification
Required
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • LIN01 is the line item identification
Usage notes

PO101 of 850 PO.

LIN-02
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

  • LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
SK
Stock Keeping Unit (SKU)
LIN-03
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Format: (NNN-NNNN-N)

LIN-04
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

EN
European Article Number (EAN) (2-5-5-1)
UP
U.P.C. Consumer Package Code (1-5-5-1)
LIN-05
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-06
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

CH
Country of Origin Code
LIN-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

SN1
030
Detail > HL Loop Shipment > HL Loop Order > HL Loop Pack > HL Loop Item > SN1

Item Detail (Shipment)

RequiredMax use 1

To specify line-item detail relative to shipment

Usage notes

Example: SN1*24EA

Example
SN1-02
382
Number of Units Shipped
Required
Decimal number (R)
Min 1Max 10

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

SN1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

  • SN103 defines the unit of measurement for both SN102 and SN104.
EA
Each
DTM
200
Detail > HL Loop Shipment > HL Loop Order > HL Loop Pack > HL Loop Item > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

Usage notes

The DTM segment is MANDATORY for Legacy PO's (850 REFPHC, when REF02 = B) and optional for AOM POs (850 REFPHC, when REF02=A).

Example: DTM01020030501

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

010
Requested Ship
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

HL Loop Item end
HL Loop Pack end
HL Loop Shipping Tare
OptionalMax >1
Usage notes

The Tare level is optional, but one of the Tare or the Pack level must be present. For cross-dock and direct ship PO's (850 BEG02 = RA or DS), the Pack level is MANDATORY.

Example: HL2010*T

Variants (all may be used)
HL Loop Pack
HL
010
Detail > HL Loop Shipment > HL Loop Order > HL Loop Shipping Tare > HL

Hierarchical Level

RequiredMax use 1

To identify dependencies among and the content of hierarchically related groups of data segments

  • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

  • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

  • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
T
Shipping Tare
HL-04
736
Hierarchical Child Code
Optional
Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
0
No Subordinate HL Segment in This Hierarchical Structure.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
TD1
110
Detail > HL Loop Shipment > HL Loop Order > HL Loop Shipping Tare > TD1

Carrier Details (Quantity and Weight)

OptionalMax use 20

To specify the transportation details relative to commodity, weight, and quantity

Usage notes

Example: TD1***G15546*LB1245CF

Example
If either Weight (TD1-07) or Unit or Basis for Measurement Code (TD1-08) is present, then the other is required
If Weight Qualifier (TD1-06) is present, then Weight (TD1-07) is required
If either Volume (TD1-09) or Unit or Basis for Measurement Code (TD1-10) is present, then the other is required
TD1-06
187
Weight Qualifier
Required
Identifier (ID)

Code defining the type of weight

G
Gross Weight
TD1-07
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

TD1-08
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

KG
Kilogram
LB
Pound
TD1-09
183
Volume
Required
Decimal number (R)
Min 1Max 8

Value of volumetric measure

TD1-10
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

CF
Cubic Feet
CR
Cubic Meter
MAN
190
Detail > HL Loop Shipment > HL Loop Order > HL Loop Shipping Tare > MAN

Marks and Numbers

OptionalMax use >1

To indicate identifying marks and numbers for shipping containers

Usage notes

The MAN segment within the Tare level indicates a pallet is present.

If the Tare level is used without the Pack level, the MAN segment must appear in the Tare level. The MAN segment is mandatory and must appear in EITHER the Tare level or the Pack level.

The MAN segment at the Tare level is optional. For cross-dock and direct ship PO's (850 BEG02 = RA or DS), the MAN segment at the Pack level is MANDATORY.

Example: MANGM00000999990000123456

Example
MAN-01
88
Marks and Numbers Qualifier
Required
Identifier (ID)

Code specifying the application or source of Marks and Numbers (87)

  • MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
  • When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
GM
SSCC-18 and Application Identifier
MAN-02
87
Marks and Numbers
Required
String (AN)
Min 1Max 48

Marks and numbers used to identify a shipment or parts of a shipment

  • When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
HL Loop Item
OptionalMax >1
Usage notes

Example: HL4030*I

Variants (all may be used)
HL Loop Pack
HL
010
Detail > HL Loop Shipment > HL Loop Order > HL Loop Shipping Tare > HL Loop Item > HL

Hierarchical Level

RequiredMax use 1

To identify dependencies among and the content of hierarchically related groups of data segments

  • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

  • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

  • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
I
Item
HL-04
736
Hierarchical Child Code
Optional
Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
0
No Subordinate HL Segment in This Hierarchical Structure.
LIN
020
Detail > HL Loop Shipment > HL Loop Order > HL Loop Shipping Tare > HL Loop Item > LIN

Item Identification

RequiredMax use 1

To specify basic item identification data

Usage notes

For country of origin use ISO 3166-1 alpha 2 codes.

For United States use ISO 3166-2 extension codes to indicate the state of origin.
Example codes:
Canada CA
China CN
Mexico MX
US- Illinois US-IL
US- Ohio US-OH

If a product has some from one country and some from another then separate for each country of origin.

Example: LIN1SK099-9999-6*CHCA

Example
If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required
If either Product/Service ID Qualifier (LIN-06) or Product/Service ID (LIN-07) is present, then the other is required
LIN-01
350
Assigned Identification
Required
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • LIN01 is the line item identification
Usage notes

PO101 of 850 PO.

LIN-02
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

  • LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
SK
Stock Keeping Unit (SKU)
LIN-03
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Format: (NNN-NNNN-N)

LIN-04
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

EN
European Article Number (EAN) (2-5-5-1)
UP
U.P.C. Consumer Package Code (1-5-5-1)
LIN-05
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-06
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

CH
Country of Origin Code
LIN-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

SN1
030
Detail > HL Loop Shipment > HL Loop Order > HL Loop Shipping Tare > HL Loop Item > SN1

Item Detail (Shipment)

RequiredMax use 1

To specify line-item detail relative to shipment

Usage notes

Example: SN1*24EA

Example
SN1-02
382
Number of Units Shipped
Required
Decimal number (R)
Min 1Max 10

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

SN1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

  • SN103 defines the unit of measurement for both SN102 and SN104.
EA
Each
DTM
200
Detail > HL Loop Shipment > HL Loop Order > HL Loop Shipping Tare > HL Loop Item > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

Usage notes

The DTM segment is MANDATORY for Legacy PO's (850 REFPHC, when REF02 = B) and optional for AOM POs (850 REFPHC, when REF02=A).

Example: DTM01020030501

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

010
Requested Ship
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

HL Loop Item end
HL Loop Pack
OptionalMax >1
Usage notes

The Pack level is optional, but one of the Tare or the Pack level must be present. For cross-dock or direct ship PO's (850 BEG02 = RA or DS), the Pack level is MANDATORY.

Example: HL3020*P

Variants (all may be used)
HL Loop Item
HL
010
Detail > HL Loop Shipment > HL Loop Order > HL Loop Shipping Tare > HL Loop Pack > HL

Hierarchical Level

RequiredMax use 1

To identify dependencies among and the content of hierarchically related groups of data segments

  • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

  • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

  • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
P
Pack
HL-04
736
Hierarchical Child Code
Optional
Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
TD1
110
Detail > HL Loop Shipment > HL Loop Order > HL Loop Shipping Tare > HL Loop Pack > TD1

Carrier Details (Quantity and Weight)

OptionalMax use 20

To specify the transportation details relative to commodity, weight, and quantity

Usage notes

Example: TD1***G15546*LB1245CF

Example
If either Weight (TD1-07) or Unit or Basis for Measurement Code (TD1-08) is present, then the other is required
If Weight Qualifier (TD1-06) is present, then Weight (TD1-07) is required
If either Volume (TD1-09) or Unit or Basis for Measurement Code (TD1-10) is present, then the other is required
TD1-06
187
Weight Qualifier
Required
Identifier (ID)

Code defining the type of weight

G
Gross Weight
TD1-07
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

TD1-08
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

KG
Kilogram
LB
Pound
TD1-09
183
Volume
Required
Decimal number (R)
Min 1Max 8

Value of volumetric measure

TD1-10
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

CF
Cubic Feet
CR
Cubic Meter
MAN
190
Detail > HL Loop Shipment > HL Loop Order > HL Loop Shipping Tare > HL Loop Pack > MAN

Marks and Numbers

OptionalMax use >1

To indicate identifying marks and numbers for shipping containers

Usage notes

If the Pack level is used without the Tare level, the MAN segment must appear in the Pack level. The MAN segment is mandatory and must appear in EITHER the Tare level or the Pack level.

For cross-dock and direct ship PO's (850 BEG02 = RA or DS), the MAN segment at the Pack level is MANDATORY.

Example: MANGM00000999990000123464

Example
MAN-01
88
Marks and Numbers Qualifier
Required
Identifier (ID)

Code specifying the application or source of Marks and Numbers (87)

  • MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
  • When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
GM
SSCC-18 and Application Identifier
MAN-02
87
Marks and Numbers
Required
String (AN)
Min 1Max 48

Marks and numbers used to identify a shipment or parts of a shipment

  • When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
N1 Loop
OptionalMax >1
N1
220
Detail > HL Loop Shipment > HL Loop Order > HL Loop Shipping Tare > HL Loop Pack > N1 Loop > N1

Name

RequiredMax use 1

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

Usage notes

This iteration of the N1 segment will only be sent for Cross Dock or Direct Ship orders (850 BEG02 = RA or DS). For Cross Dock and Direct Ship this segment is mandatory.

A new store will have a prefix of "7" in front of the original store number to differentiate between to the current and new locations. (eg. current store # 0126 new store # 70126).

Example: N1MA**920126

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

MA
Party for whom Item is Ultimately Intended
N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

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

92
Assigned by Buyer or Buyer's Agent (Store)
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

Format: (NNNN – existing store or NNNNN – New store)

N1 Loop end
HL Loop Item
RequiredMax >1
Usage notes

Example: HL4030*I

HL
010
Detail > HL Loop Shipment > HL Loop Order > HL Loop Shipping Tare > HL Loop Pack > HL Loop Item > HL

Hierarchical Level

RequiredMax use 1

To identify dependencies among and the content of hierarchically related groups of data segments

  • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

  • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

  • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
I
Item
HL-04
736
Hierarchical Child Code
Optional
Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
0
No Subordinate HL Segment in This Hierarchical Structure.
LIN
020
Detail > HL Loop Shipment > HL Loop Order > HL Loop Shipping Tare > HL Loop Pack > HL Loop Item > LIN

Item Identification

RequiredMax use 1

To specify basic item identification data

Usage notes

For country of origin use ISO 3166-1 alpha 2 codes.

For United States use ISO 3166-2 extension codes to indicate the state of origin.
Example codes:
Canada CA
China CN
Mexico MX
US- Illinois US-IL
US- Ohio US-OH

If a product has some from one country and some from another then separate for each country of origin.

Example: LIN1SK099-9999-6*CHCA

Example
If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required
If either Product/Service ID Qualifier (LIN-06) or Product/Service ID (LIN-07) is present, then the other is required
LIN-01
350
Assigned Identification
Required
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • LIN01 is the line item identification
Usage notes

PO101 of 850 PO.

LIN-02
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

  • LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
SK
Stock Keeping Unit (SKU)
LIN-03
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Format: (NNN-NNNN-N)

LIN-04
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

EN
European Article Number (EAN) (2-5-5-1)
UP
U.P.C. Consumer Package Code (1-5-5-1)
LIN-05
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-06
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

CH
Country of Origin Code
LIN-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

SN1
030
Detail > HL Loop Shipment > HL Loop Order > HL Loop Shipping Tare > HL Loop Pack > HL Loop Item > SN1

Item Detail (Shipment)

RequiredMax use 1

To specify line-item detail relative to shipment

Usage notes

Example: SN1*24EA

Example
SN1-02
382
Number of Units Shipped
Required
Decimal number (R)
Min 1Max 10

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

SN1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

  • SN103 defines the unit of measurement for both SN102 and SN104.
EA
Each
DTM
200
Detail > HL Loop Shipment > HL Loop Order > HL Loop Shipping Tare > HL Loop Pack > HL Loop Item > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

Usage notes

The DTM segment is MANDATORY for Legacy PO's (850 REFPHC, when REF02 = B) and optional for AOM POs (850 REFPHC, when REF02=A).

Example: DTM01020030501

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

010
Requested Ship
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

HL Loop Item end
HL Loop Pack end
HL Loop Shipping Tare end
HL Loop Order end
HL Loop Shipment end
Detail end

Summary

CTT
010
Summary > CTT

Transaction Totals

RequiredMax use 1

To transmit a hash total for a specific element in the transaction set

  • Number of line items (CTT01) is the accumulation of the number of HL segments.
    If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
Usage notes

Example: CTT*5

Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

SE
020
Summary > 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

Summary 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

Direct Ship Channel Multiple Stores Multiple Cartons Multiple SKU's MAN Segment at Pack

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240507*1858*U*00401*000000001*0*T*>~
GS*SH*SENDERGS*RECEIVERGS*20240507*185839*000000001*X*004010~
BSN*00*CAL1234568*20030501*165924~
HL*1**S~
TD1*CTN90*5****G*46*LB~
TD5****M*CANADIAN TIRE~
TD3*TL*XYZ*38670~
REF*VR*9999~
PER*DI*DAVID ALEXANDER*TE*416-333-3333~
DTM*011*20030501~
HL*2*1*O~
PRF*01132460***20030214~
HL*3*2*P~
MAN*GM*00000999990000123463~
N1*MA**92*70042~
HL*4*3*I~
LIN*1*SK*099-9998-8***CH*CA~
SN1**5*EA~
HL*5*2*P~
MAN*GM*00000999990000123470~
N1*MA**92*70042~
HL*6*5*I~
LIN*2*SK*099-9999-6***CH*CA~
SN1**10*EA~
HL*7*2*P~
MAN*GM*00000999990000123487~
N1*MA**92*0126~
HL*8*7*I~
LIN*3*SK*099-9999-6***CH*CA~
SN1**10*EA~
HL*9*2*P~
MAN*GM*00000999990000123494~
N1*MA**92*0126~
HL*10*9*I~
LIN*3*SK*099-9999-6***CH*CA~
SN1**10*EA~
HL*11*2*P~
MAN*GM*00000999990000123500~
N1*MA**92*0419~
HL*12*11*I~
LIN*4*SK*099-9998-8***CH*CA~
SN1**5*EA~
HL*13*11*I~
LIN*5*SK*099-9999-6***CH*CA~
SN1**5*EA~
CTT*13~
GE*1*000000001~
IEA*1*000000001~

Multiple cartons Multiple items Multiple items in one carton MAN Segment at Pack Level

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240507*1853*U*00401*000000001*0*T*>~
GS*SH*SENDERGS*RECEIVERGS*20240507*185356*000000001*X*004010~
BSN*00*TOR1234567*20030501*165924~
HL*1**S~
TD1*CTN90*3****G*149*LB~
TD5****M*CANADIAN TIRE~
TD3*TL*XYZ*38670~
REF*VR*9999~
PER*DI*DAVID ALEXANDER*TE*416-333-3333~
DTM*011*20030501~
N1*ST**9*2016136689003~
HL*10*1*O~
PRF*99991235***20030214~
HL*20*10*P~
MAN*GM*00000999990000123463~
HL*30*20*I~
LIN*1*SK*099-9997-0***CH*CA~
SN1**48*EA~
DTM*010*20030501~
HL*40*10*P~
MAN*GM*00000999990000123470~
HL*50*40*I~
LIN*1*SK*099-9997-0***CH*CA~
SN1**24*EA~
DTM*010*20030501~
HL*60*40*I~
LIN*1*SK*099-9999-6***CH*CA~
SN1**24*EA~
DTM*010*20030501~
HL*70*10*P~
MAN*GM*00000999990000123487~
HL*80*70*I~
LIN*1*SK*099-9998-8***CH*CA~
SN1**48*EA~
DTM*010*20030501~
CTT*9~
GE*1*000000001~
IEA*1*000000001~

Multiple pallets Multiple cartons One item MAN Segment at Tare 1

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240507*1854*U*00401*000000001*0*T*>~
GS*SH*SENDERGS*RECEIVERGS*20240507*185453*000000001*X*004010~
BSN*00*TOR1234567*20030501*165924~
HL*1**S~
TD1*CTN90*36****G*300*LB~
TD5****M*CANADIAN TIRE~
TD3*TL*XYZ*38670~
REF*VR*9999~
PER*DI*DAVID ALEXANDER*TE*416-333-3333~
DTM*011*20030501~
N1*ST**9*2016136689003~
HL*10*1*O~
PRF*99991235***20030214~
HL*20*10*T~
MAN*GM*00000999990000123463~
HL*30*20*I~
LIN*1*SK*099-9999-6***CH*CA~
SN1**400*EA~
DTM*010*20030501~
HL*40*10*T~
MAN*GM*00000999990000123472~
HL*50*40*I~
LIN*1*SK*099-9999-6***CH*CA~
SN1**400*EA~
DTM*010*20030501~
HL*60*10*T~
MAN*GM*00000999990000123487~
HL*70*60*I~
LIN*1*SK*099-9999-6***CH*CA~
SN1**400*EA~
DTM*010*20030501~
CTT*8~
GE*1*000000001~
IEA*1*000000001~

Multiple pallets Multiple cartons One item MAN Segment at Tare 2

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240507*1859*U*00401*000000001*0*T*>~
GS*SH*SENDERGS*RECEIVERGS*20240507*185935*000000001*X*004010~
BSN*00*TOR1234567*20030501*165924~
HL*1**S~
TD1*CTN90*36****G*300*LB~
TD5****M*CANADIAN TIRE~
TD3*TL*XYZ*38670~
REF*VR*9999~
PER*DI*DAVID ALEXANDER*TE*416-333-3333~
DTM*011*20030501~
N1*ST**9*2016136689003~
HL*10*1*O~
PRF*99991235***20030214~
HL*20*10*T~
MAN*GM*00000999990000123463~
HL*30*20*I~
LIN*1*SK*099-9999-6***CH*CN~
SN1**400*EA~
DTM*010*20030501~
HL*40*10*T~
MAN*GM*00000999990000123472~
HL*50*40*I~
LIN*1*SK*099-9999-6***CH*CN~
SN1**400*EA~
DTM*010*20030501~
HL*60*10*T~
MAN*GM*00000999990000123487~
HL*70*60*I~
LIN*1*SK*099-9999-6***CH*VN~
SN1**400*EA~
DTM*010*20030501~
CTT*8~
GE*1*000000001~
IEA*1*000000001~

Multiple Stores Multiple Cartons Multiple SKU's MAN Segment at Pack

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240507*1856*U*00401*000000001*0*T*>~
GS*SH*SENDERGS*RECEIVERGS*20240507*185601*000000001*X*004010~
BSN*00*CAL1234567*20030501*165924~
HL*1**S~
TD1*CTN90*5****G*46*LB~
TD5****M*CANADIAN TIRE~
TD3*TL*XYZ*38670~
REF*VR*9999~
PER*DI*DAVID ALEXANDER*TE*416-333-3333~
DTM*011*20030501~
N1*ST**9*2016136689007~
HL*2*1*O~
PRF*01132459***20030214~
HL*3*2*P~
TD1******G*9*LB*2*CF~
MAN*GM*00000999990000123463~
N1*MA**92*70042~
HL*4*3*I~
LIN*1*SK*099-9998-8***CH*CA~
SN1**10*EA~
HL*5*2*P~
MAN*GM*00000999990000123470~
N1*MA**92*70042~
HL*6*5*I~
LIN*2*SK*099-9999-6***CH*CA~
SN1**10*EA~
HL*7*2*P~
MAN*GM*00000999990000123487~
N1*MA**92*0126~
HL*8*7*I~
LIN*3*SK*099-9998-8***CH*CA~
SN1**10*EA~
HL*9*2*P~
MAN*GM*00000999990000123494~
N1*MA**92*0126~
HL*10*9*I~
LIN*3*SK*099-9998-8***CH*CA~
SN1**10*EA~
HL*11*2*P~
MAN*GM*00000999990000123500~
N1*MA**92*0419~
HL*12*11*I~
LIN*4*SK*099-9998-8***CH*CA~
SN1**5*EA~
HL*13*11*I~
LIN*5*SK*099-9999-6***CH*CA~
SN1**5*EA~
CTT*13~
GE*1*000000001~
IEA*1*000000001~

One Carton Multiple PO's Multiple SKU's MAN Segment at Pack

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240507*1857*U*00401*000000001*0*T*>~
GS*SH*SENDERGS*RECEIVERGS*20240507*185726*000000001*X*004010~
BSN*00*TOR1234567*20030501*165924~
HL*1**S~
TD1*CTN90*1****G*20*LB~
TD5****M*CANADIAN TIRE~
TD3*TL*XYZ*38670~
REF*VR*9999~
PER*DI*KATHY SMITH*TE*416-333-3333~
DTM*011*20030501~
N1*ST**9*2016136689003~
HL*10*1*O~
PRF*99991235***20030214~
HL*20*10*P~
MAN*GM*00000999990000123463~
HL*30*20*I~
LIN*1*SK*099-9997-0***CH*CA~
SN1**10*EA~
DTM*010*20030501~
HL*40*1*O~
PRF*99991236***20030214~
HL*50*40*P~
MAN*GM*00000999990000123463~
HL*60*50*I~
LIN*1*SK*099-9998-8***CH*CA~
SN1**5*EA~
DTM*010*20030501~
HL*70*1*O~
PRF*99991237***20030214~
HL*80*70*P~
MAN*GM*00000999990000123463~
HL*90*80*I~
LIN*1*SK*099-9999-6***CH*CA~
SN1**5*EA~
DTM*010*20030501~
CTT*10~
GE*1*000000001~
IEA*1*000000001~

Sample 1

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240507*1901*U*00401*000000001*0*T*>~
GS*SH*SENDERGS*RECEIVERGS*20240507*190113*000000001*X*004010~
BSN*00*TOR1234567*20030501*165924~
HL*1**S~
TD1*PLT90*20****G*15546*LB~
TD5****M*CANADIAN TIRE~
TD3*TL*XYZ*998670~
REF*VR*9999~
PER*DI*DAVID ALEXANDER*TE*416-333-3333~
DTM*011*20030501~
N1*ST**9*2016136689003~
HL*10*1*O~
PRF*99991234***20030214~
TD1*PLT90*20****G*15546*LB~
HL*20*10*T~
TD1******G*15546*LB*1245*CF~
MAN*GM*00000999990000123456~
HL*30*20*P~
TD1******G*15546*LB*1245*CF~
MAN*GM*00000999990000123464~
HL*40*30*I~
LIN*1*SK*099-9999-6***CH*CA~
SN1**24*EA~
DTM*010*20030501~
CTT*5~
GE*1*000000001~
IEA*1*000000001~

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