Meijer
/
Ship Notice/Manifest (4010DQSA)
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Meijer. Contact Meijer for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Meijer logo

X12 856 Ship Notice/Manifest (4010DQSA)

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
  • None included
View the latest version of this implementation guide as an interactive webpage
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
HL
010
Hierarchical Level
Max use 1
Required
TD1
110
Carrier Details (Quantity and Weight)
Max use 20
Optional
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
Optional
DTM
200
Date/Time Reference
Max use 10
Required
YNQ
335
Direct Purchase Statement
Max use 10
Optional
YNQ
335
Transaction Statement
Max use 10
Required
HL Loop
HL
010
Hierarchical Level
Max use 1
Required
PRF
050
Purchase Order Reference
Max use 1
Required
HL 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

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

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
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
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
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
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
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
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required

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

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
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
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
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
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

Code identifying a group of application related transaction sets

SH
Ship Notice/Manifest (856)
GS-02
142
Application Sender's Code
Required
Min 2Max 15

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

GS-03
124
Application Receiver's Code
Required
Min 2Max 15

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

GS-04
373
Date
Required
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
Required
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
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
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

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

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

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

Beginning Segment for Ship Notice

RequiredMax use 1

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

Usage notes

DTM Segment differs from the BSN segment when the Vendor’s ship date is 24 hours after the ASN is created.

Example
BSN-01
353
Transaction Set Purpose Code
Required

Code identifying purpose of transaction set

00
Original
BSN-02
396
Shipment Identification
Required
Min 2Max 30

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

Usage notes

Sender's internal number must be unique.

BSN-03
373
Date
Required
CCYYMMDD format

Date expressed as CCYYMMDD

  • BSN03 is the date the shipment transaction set is created.
BSN-04
337
Time
Required
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)

  • BSN04 is the time the shipment transaction set is created.
Usage notes

Format: HHMMSS

BSN-05
1005
Hierarchical Structure Code
Required

Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set

0001
Shipment, Order, Packaging, Item
0002
Shipment, Order, Item, Packaging

Detail

HL Loop
RequiredMax >1
HL
010

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

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

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

Carrier Details (Quantity and Weight)

OptionalMax use 20

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

Example
If Packaging Code (TD1-01) is present, then Lading Quantity (TD1-02) is required
TD1-01
103
Packaging Code
Optional
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
Optional
Min 1Max 7

Number of units (pieces) of the lading commodity

Usage notes

Number of packages in this shipment.

TD5
120

Carrier Details (Routing Sequence/Transit Time)

RequiredMax use 12

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

Example
TD5-01
133
Routing Sequence Code
Optional
Min 1Max 2

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

TD5-04
91
Transportation Method/Type Code
Optional
Min 1Max 2

Code specifying the method or type of transportation for the shipment

TD5-05
387
Routing
Optional
Min 1Max 35

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

Usage notes

Carrier Name

TD5-06
368
Shipment/Order Status Code
Required

Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction

CC
Shipment Complete on (Date)
PR
Partial Shipment
TD3
130

Carrier Details (Equipment)

OptionalMax use 12

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

Example
If Equipment Initial (TD3-02) is present, then Equipment Number (TD3-03) is required
TD3-01
40
Equipment Description Code
Optional

Code identifying type of equipment used for shipment

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

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

Usage notes

Send if available.

TD3-03
207
Equipment Number
Optional
Min 1Max 10

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

Usage notes

Trailer Number

REF
150

Reference Identification

OptionalMax use >1

To specify identifying information

Example
REF-01
128
Reference Identification Qualifier
Required

Code qualifying the Reference Identification

CN
Carrier's Reference Number (PRO/Invoice)
REF-02
127
Reference Identification
Optional
Min 1Max 30

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

DTM
200

Date/Time Reference

RequiredMax use 10

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required

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

011
Shipped
DTM-02
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

May be the same as the ASN Date, expressed as CCYYMMDD

DTM-03
337
Time
Optional
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

Format: HHMMSSDD

N1 Buying Party (Purchaser)
RequiredMax >1
Variants (all may be used)
N1Selling PartyN1Ship FromN1Ship To
N1
220

Name

RequiredMax use 1

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

Usage notes

Map Buyer Name and Address Loop at the Shipment Segment Level.

Use this segment to give the final destination (e.g. Store, DC) of an order that was first sent to our DC.

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

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

BY
Buying Party (Purchaser)
N1-02
93
Name
Optional
Min 1Max 60

Free-form name

Usage notes

Final Destination

N1-03
66
Identification Code Qualifier
Optional

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

"006959555XXXX" where XXXX denotes the Meijer Final Destination.

N3
240

Address Information

RequiredMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
Min 1Max 55

Address information

N4
250

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

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

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

N4-04
26
Country Code
Optional
Min 2Max 3

Code identifying the country

N1 Selling Party
RequiredMax >1
N1
220

Name

RequiredMax use 1

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

Usage notes

Map Buyer Name and Address Loop at the Shipment Segment Level.

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

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

SE
Selling Party
N1-02
93
Name
Optional
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Min 1Max 2

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

N1-04
67
Identification Code
Optional
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.
N3
240

Address Information

RequiredMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
Min 1Max 55

Address information

N4
250

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

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

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

N4-04
26
Country Code
Optional
Min 2Max 3

Code identifying the country

N1 Ship From
RequiredMax >1
N1
220

Name

RequiredMax use 1

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

Usage notes

Map Ship From Name and Address Loop at the Shipment Segment Level.

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

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

SF
Ship From
N1-02
93
Name
Optional
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Min 1Max 2

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

N1-04
67
Identification Code
Optional
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.
N3
240

Address Information

OptionalMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
Min 1Max 55

Address information

N4
250

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Optional
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
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.
Usage notes

It is important that we receive “State” because it is used in conjunction with the DTM02 to calculate an arrival date for shipment.

N4-03
116
Postal Code
Optional
Min 3Max 15

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

N4-04
26
Country Code
Optional
Min 2Max 3

Code identifying the country

N1 Ship To
RequiredMax >1
N1
220

Name

RequiredMax use 1

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

Usage notes

Map Ship To Name and Address Loop at the Shipment Segment Level.

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

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

ST
Ship To
N1-02
93
Name
Optional
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional

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
11
Drug Enforcement Administration (DEA)
92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Optional
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

With qualifier 9 use "006959555XXXX" where XXXX denotes the Meijer Distribution Center, Store or Central Fill Unit 463.

With qualifier 92 use "0XXX" where XXX denotes the Meijer Distribution Center, Store or Central Fill Unit 463

With qualifier 11 use "PT0185276" where PT0185276 denotes Meijer DEA ID for DC90 (used for CSOS orders) or use the DEA ID for Meijer Store or Unit 463 Central Fill.

N3
240

Address Information

OptionalMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
Min 1Max 55

Address information

N4
250

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Optional
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
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.
Usage notes

It is important that we receive “State” because it is used in conjunction with the DTM02 to calculate an arrival date for shipment.

N4-03
116
Postal Code
Optional
Min 3Max 15

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

N4-04
26
Country Code
Optional
Min 2Max 3

Code identifying the country

YNQ
335

Direct Purchase Statement

OptionalMax use 10

To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition

Usage notes

Reference to manufacturer direct purchase statement at the shipment segment level.

Required for Exclusive Distributor and Indirect Distributor. Not required for Original Manufacturer.

Example
Variants (all may be used)
YNQTransaction Statement
YNQ-02
1073
Yes/No Condition or Response Code
Required

Code indicating a Yes or No condition or response

  • YNQ02 confirms or denies the statement made in YNQ01, YNQ09 or YNQ10. A "Y" indicates the statement is confirmed; an "N" indicates the statement is denied.
Y
Yes
YNQ-05
933
Free-Form Message Text
Optional
Min 1Max 264

Free-form message text

YNQ-08
1270
Code List Qualifier Code
Optional

Code identifying a specific industry code list

99
Purpose Code
YNQ-09
1271
Industry Code
Required

Code indicating a code from a specific industry code list

DPS
Direct Purchase Statement
YNQ
335

Transaction Statement

RequiredMax use 10

To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition

Usage notes

Seller transaction statement at the shipment segment level.

Example
Variants (all may be used)
YNQDirect Purchase Statement
YNQ-02
1073
Yes/No Condition or Response Code
Required

Code indicating a Yes or No condition or response

  • YNQ02 confirms or denies the statement made in YNQ01, YNQ09 or YNQ10. A "Y" indicates the statement is confirmed; an "N" indicates the statement is denied.
Y
Yes
YNQ-05
933
Free-Form Message Text
Optional
Min 1Max 264

Free-form message text

YNQ-08
1270
Code List Qualifier Code
Optional

Code identifying a specific industry code list

99
Purpose Code
YNQ-09
1271
Industry Code
Required

Code indicating a code from a specific industry code list

TS
Transaction Statement
HL Loop
RequiredMax >1
Usage notes

If multiple purchase orders are being filled on this shipment, send an HL (order level) loop for each purchase order on the shipment.

HL
010

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

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

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

Purchase Order Reference

RequiredMax use 1

To provide reference to a specific purchase order

Example
PRF-01
324
Purchase Order Number
Required
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

Meijer PO Number (9 Digits)

HL Loop
OptionalMax >1
Usage notes

This HL loop is used to describe a vendor master shipping carton.

Required if using 128 labels.

Variants (all may be used)
HLHL Loop
HL
010

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

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

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.
PO4
060

Item Physical Details

OptionalMax use 1

To specify the physical qualities, packaging, weights, and dimensions relating to the item

Example
If either Gross Weight per Pack (PO4-06) or Unit or Basis for Measurement Code (PO4-07) is present, then the other is required
If Length (PO4-10) is present, then Unit or Basis for Measurement Code (PO4-13) is required
If Width (PO4-11) is present, then Unit or Basis for Measurement Code (PO4-13) is required
If Height (PO4-12) is present, then Unit or Basis for Measurement Code (PO4-13) is required
If Unit or Basis for Measurement Code (PO4-13) is present, then at least one of Length (PO4-10), Width (PO4-11) or Height (PO4-12) is required
PO4-01
356
Pack
Optional
Min 1Max 6

The number of inner containers, or number of eaches if there are no inner containers, per outer container

Usage notes

No. of inner packs, or No. of EA., if there are no inner packs.

PO4-06
384
Gross Weight per Pack
Optional
Min 1Max 9

Numeric value of gross weight per pack

Usage notes

Weight of master shipping carton in #'s.

PO4-07
355
Unit or Basis for Measurement Code
Optional

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

LB
Pound
PO4-10
82
Length
Optional
Min 1Max 8

Largest horizontal dimension of an object measured when the object is in the upright position

PO4-11
189
Width
Optional
Min 1Max 8

Shorter measurement of the two horizontal dimensions measured with the object in the upright position

PO4-12
65
Height
Optional
Min 1Max 8

Vertical dimension of an object measured when the object is in the upright position

PO4-13
355
Unit or Basis for Measurement Code
Optional

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

  • PO413 defines the unit of measure for PO410, PO411, and PO412.
IN
Inch
PO4-14
810
Inner Pack
Optional
Min 1Max 6

The number of eaches per inner container

Usage notes

No. of EA. within an inner pack.

MAN
190

Marks and Numbers

RequiredMax use >1

To indicate identifying marks and numbers for shipping containers

Usage notes

MAN01 & MAN02 must comply to the standards established by the Uniform Code Council (UCC). We must receive this segment in order to receive merchandise by scanning.

Example
MAN-01
88
Marks and Numbers Qualifier
Required

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

If MAN01 is "GM" then MAN02 must be 20 digits and unique, but need not be sequential. If MAN01 is "UC" then MAN02 must be 12 or 14 digits.

GM
SSCC-18 and Application Identifier
UC
U.P.C. Shipping Container Code
MAN-02
87
Marks and Numbers
Required
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.
Usage notes

Shipping Container Identifier

HL Loop
RequiredMax >1
HL
010

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

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

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

Item Identification

OptionalMax use 1

To specify basic item identification data

Usage notes

Map Mandatory NDC Number and Optional Lot Number at the Item Details Level.

Example
If either Product/Service ID Qualifier (LIN-06) or Product/Service ID (LIN-07) is present, then the other is required
If either Product/Service ID Qualifier (LIN-08) or Product/Service ID (LIN-09) is present, then the other is required
If either Product/Service ID Qualifier (LIN-10) or Product/Service ID (LIN-11) is present, then the other is required
LIN-01
350
Assigned Identification
Required
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • LIN01 is the line item identification
LIN-02
235
Product/Service ID Qualifier
Required

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.
N4
National Drug Code in 5-4-2 Format
ND
National Drug Code (NDC)
LIN-03
234
Product/Service ID
Required
Min 1Max 48

Identifying number for a product or service

Usage notes

(NDC) (5-4-2 Format, No Hyphens)

LIN-04
235
Product/Service ID Qualifier
Required

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

Usage notes

The product/service ID (UPC Number) or the NDC sent must match what was received in the purchase order data.

UP
U.P.C. Consumer Package Code (1-5-5-1)
LIN-05
234
Product/Service ID
Required
Min 1Max 48

Identifying number for a product or service

Usage notes

The product/service ID (UPC Number) or the NDC sent must match what was received in the purchase order data.

UCC12 (12 digits UPC number, No Hyphens)

LIN-06
235
Product/Service ID Qualifier
Optional

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

VC
Vendor's (Seller's) Catalog Number
VN
Vendor's (Seller's) Item Number
LIN-07
234
Product/Service ID
Optional
Min 1Max 48

Identifying number for a product or service

LIN-08
235
Product/Service ID Qualifier
Optional
Min 2Max 2

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

LIN-09
234
Product/Service ID
Optional
Min 1Max 48

Identifying number for a product or service

LIN-10
235
Product/Service ID Qualifier
Optional

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

LT
Lot Number
LIN-11
234
Product/Service ID
Optional
Min 1Max 48

Identifying number for a product or service

SN1
030

Item Detail (Shipment)

OptionalMax use 1

To specify line-item detail relative to shipment

Usage notes

Map Container Type and Number of Containers at the Item Detail Level.

Example
SN1-02
382
Number of Units Shipped
Required
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

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

Other values defaulted to CA.

If the SN103 unit of measure is not ‘EA’ we assume the SN103 ship quantity needs to be multiplied by the pack size quantity which is sent in the PO4 segment, so the ASN will be rejected if there is no PO4 segment.

CA
Case
DZ
Dozen
EA
Each
SN1-08
668
Line Item Status Code
Optional

Code specifying the action taken by the seller on a line item requested by the buyer

AC
Item Accepted and Shipped
PO4
060

Item Physical Details

OptionalMax use 1

To specify the physical qualities, packaging, weights, and dimensions relating to the item

Usage notes

To define the case pack being shipped.

Required for all products listed in the LIN Segment.

Required if unit of measure is not EA.

Example
PO4-01
356
Pack
Optional
Min 1Max 6

The number of inner containers, or number of eaches if there are no inner containers, per outer container

Usage notes

No. of inner pks., or No. of EA., if there are no inner pks.

PO4-14
810
Inner Pack
Optional
Min 1Max 6

The number of eaches per inner container

Usage notes

No. of EA. within an inner pack.

PID
070

Product/Item Description

RequiredMax use 200

To describe a product or process in coded or free-form format

Usage notes

Map Prescription name, Strength and Dosage at the Item Detail Level.

Example: PIDF***GABAPENT CAP 100MG 100 NSTAR~

Example
PID-01
349
Item Description Type
Required

Code indicating the format of a description

  • If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
F
Free-form
PID-05
352
Description
Optional
Min 1Max 80

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

Usage notes

Description must include product Name, dosage form, strength, and container size.

Example: Ibuprofen Tablets 300 MG 70

N1 Loop
RequiredMax >1
Usage notes

Required for Exclusive Distributor and Indirect Distributor. Not required for Original Manufacturer

N1
220

Name

RequiredMax use 1

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

Usage notes

Map the Transactional History at the Item Detail Level.

Example
N1-01
98
Entity Identifier Code
Required

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

DS
Distributor
MF
Manufacturer of Goods
SU
Supplier/Manufacturer
N1-02
93
Name
Optional
Min 1Max 60

Free-form name

N3
240

Address Information

OptionalMax use 2

To specify the location of the named party

Usage notes

Optional for Exclusive Distributor, Indirect Distributor and Original Manufacturer

Example
N3-01
166
Address Information
Required
Min 1Max 55

Address information

N4
250

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Usage notes

Optional for Exclusive Distributor, Indirect Distributor and Original Manufacturer

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

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

N4-04
26
Country Code
Optional
Min 2Max 3

Code identifying the country

YNQ
335

Yes/No Question

OptionalMax use 10

To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition

Usage notes

Reference to manufacturer direct purchase statement at the shipment segment level.

Required as noted below for Exclusive Distributor and Indirect Distributor. Not required for Original Manufacturer.

Example
YNQ-01
1321
Condition Indicator
Optional

Code indicating a condition

3E
Letter of Certification
CX
Certification Status
YNQ-02
1073
Yes/No Condition or Response Code
Required

Code indicating a Yes or No condition or response

  • YNQ02 confirms or denies the statement made in YNQ01, YNQ09 or YNQ10. A "Y" indicates the statement is confirmed; an "N" indicates the statement is denied.
Y
Yes
YNQ-05
933
Free-Form Message Text
Optional
Min 1Max 264

Free-form message text

YNQ-08
1270
Code List Qualifier Code
Required

Code identifying a specific industry code list

99
Purpose Code
YNQ-09
1271
Industry Code
Required

Code indicating a code from a specific industry code list

DIR
Product Purchased Directly
RDPS
Received Direct Purchase Statement
HL Loop
OptionalMax >1
Usage notes

This HL loop is used to describe a vendor master shipping carton.

Required if using 128 labels.

Variants (all may be used)
HLHL Loop
HL
010

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

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

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.
LIN
020

Item Identification

OptionalMax use 1

To specify basic item identification data

Usage notes

Map Mandatory NDC Number and Optional Lot Number at the Item Details Level.

Example
If either Product/Service ID Qualifier (LIN-06) or Product/Service ID (LIN-07) is present, then the other is required
If either Product/Service ID Qualifier (LIN-08) or Product/Service ID (LIN-09) is present, then the other is required
If either Product/Service ID Qualifier (LIN-10) or Product/Service ID (LIN-11) is present, then the other is required
LIN-01
350
Assigned Identification
Required
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • LIN01 is the line item identification
LIN-02
235
Product/Service ID Qualifier
Required

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.
N4
National Drug Code in 5-4-2 Format
ND
National Drug Code (NDC)
LIN-03
234
Product/Service ID
Required
Min 1Max 48

Identifying number for a product or service

Usage notes

(NDC) (5-4-2 Format, No Hyphens)

LIN-04
235
Product/Service ID Qualifier
Required

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

Usage notes

The product/service ID (UPC Number) or the NDC sent must match what was received in the purchase order data.

UP
U.P.C. Consumer Package Code (1-5-5-1)
LIN-05
234
Product/Service ID
Required
Min 1Max 48

Identifying number for a product or service

Usage notes

The product/service ID (UPC Number) or the NDC sent must match what was received in the purchase order data.

UCC12 (12 digits UPC number, No Hyphens)

LIN-06
235
Product/Service ID Qualifier
Optional

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

VC
Vendor's (Seller's) Catalog Number
VN
Vendor's (Seller's) Item Number
LIN-07
234
Product/Service ID
Optional
Min 1Max 48

Identifying number for a product or service

LIN-08
235
Product/Service ID Qualifier
Optional
Min 2Max 2

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

LIN-09
234
Product/Service ID
Optional
Min 1Max 48

Identifying number for a product or service

LIN-10
235
Product/Service ID Qualifier
Optional

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

LT
Lot Number
LIN-11
234
Product/Service ID
Optional
Min 1Max 48

Identifying number for a product or service

SN1
030

Item Detail (Shipment)

OptionalMax use 1

To specify line-item detail relative to shipment

Usage notes

Map Container Type and Number of Containers at the Item Detail Level.

Example
SN1-02
382
Number of Units Shipped
Required
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

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

Other values defaulted to CA.

If the SN103 unit of measure is not ‘EA’ we assume the SN103 ship quantity needs to be multiplied by the pack size quantity which is sent in the PO4 segment, so the ASN will be rejected if there is no PO4 segment.

CA
Case
DZ
Dozen
EA
Each
SN1-08
668
Line Item Status Code
Optional

Code specifying the action taken by the seller on a line item requested by the buyer

AC
Item Accepted and Shipped
PO4
060

Item Physical Details

OptionalMax use 1

To specify the physical qualities, packaging, weights, and dimensions relating to the item

Usage notes

Required for all products listed in the LIN Segment.

Required if unit of measure in not EA.

To define the case pack being shipped.

Example
PO4-01
356
Pack
Optional
Min 1Max 6

The number of inner containers, or number of eaches if there are no inner containers, per outer container

Usage notes

No. of inner packs, or No. of EA., if there are no inner packs.

PO4-14
810
Inner Pack
Optional
Min 1Max 6

The number of eaches per inner container

Usage notes

No. of EA. within an inner pack.

PID
070

Product/Item Description

RequiredMax use 200

To describe a product or process in coded or free-form format

Usage notes

Map Prescription name, Strength and Dosage at the Item Detail Level.

Example: PIDF***GABAPENT CAP 100MG 100 NSTAR~

Example
PID-01
349
Item Description Type
Required

Code indicating the format of a description

  • If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
F
Free-form
PID-05
352
Description
Optional
Min 1Max 80

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

Usage notes

Description must include product Name, dosage form, strength, and container size.

Example: Ibuprofen Tablets 300 MG 70

N1 Loop
RequiredMax >1
Usage notes

Required for Exclusive Distributor and Indirect Distributor. Not required for Original Manufacturer

N1
220

Name

RequiredMax use 1

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

Usage notes

Map the Transactional History at the Item Detail Level.

Example
N1-01
98
Entity Identifier Code
Required

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

DS
Distributor
MF
Manufacturer of Goods
SU
Supplier/Manufacturer
N1-02
93
Name
Optional
Min 1Max 60

Free-form name

N3
240

Address Information

OptionalMax use 2

To specify the location of the named party

Usage notes

Optional for Exclusive Distributor, Indirect Distributor and Original Manufacturer

Example
N3-01
166
Address Information
Required
Min 1Max 55

Address information

N4
250

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Usage notes

Optional for Exclusive Distributor, Indirect Distributor and Original Manufacturer

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

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

N4-04
26
Country Code
Optional
Min 2Max 3

Code identifying the country

YNQ
335

Yes/No Question

OptionalMax use 10

To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition

Usage notes

Reference to manufacturer direct purchase statement at the shipment segment level.

Required as noted below for Exclusive Distributor and Indirect Distributor. Not required for Original Manufacturer.

Example
YNQ-01
1321
Condition Indicator
Optional

Code indicating a condition

3E
Letter of Certification
CX
Certification Status
YNQ-02
1073
Yes/No Condition or Response Code
Required

Code indicating a Yes or No condition or response

  • YNQ02 confirms or denies the statement made in YNQ01, YNQ09 or YNQ10. A "Y" indicates the statement is confirmed; an "N" indicates the statement is denied.
Y
Yes
YNQ-05
933
Free-Form Message Text
Optional
Min 1Max 264

Free-form message text

YNQ-08
1270
Code List Qualifier Code
Required

Code identifying a specific industry code list

99
Purpose Code
YNQ-09
1271
Industry Code
Required

Code indicating a code from a specific industry code list

DIR
Product Purchased Directly
RDPS
Received Direct Purchase Statement
HL Loop
OptionalMax >1
Usage notes

Required if using 128 labels.

This HL loop is used to describe a vendor master shipping carton.

HL
010

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

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

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.
PO4
060

Item Physical Details

OptionalMax use 1

To specify the physical qualities, packaging, weights, and dimensions relating to the item

Example
If either Gross Weight per Pack (PO4-06) or Unit or Basis for Measurement Code (PO4-07) is present, then the other is required
If Length (PO4-10) is present, then Unit or Basis for Measurement Code (PO4-13) is required
If Width (PO4-11) is present, then Unit or Basis for Measurement Code (PO4-13) is required
If Height (PO4-12) is present, then Unit or Basis for Measurement Code (PO4-13) is required
If Unit or Basis for Measurement Code (PO4-13) is present, then at least one of Length (PO4-10), Width (PO4-11) or Height (PO4-12) is required
PO4-01
356
Pack
Optional
Min 1Max 6

The number of inner containers, or number of eaches if there are no inner containers, per outer container

Usage notes

No. of inner packs, or No. of EA., if there are no inner packs .

PO4-06
384
Gross Weight per Pack
Optional
Min 1Max 9

Numeric value of gross weight per pack

Usage notes

Weight of master shipping carton in #'s.

PO4-07
355
Unit or Basis for Measurement Code
Optional

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

LB
Pound
PO4-10
82
Length
Optional
Min 1Max 8

Largest horizontal dimension of an object measured when the object is in the upright position

PO4-11
189
Width
Optional
Min 1Max 8

Shorter measurement of the two horizontal dimensions measured with the object in the upright position

PO4-12
65
Height
Optional
Min 1Max 8

Vertical dimension of an object measured when the object is in the upright position

PO4-13
355
Unit or Basis for Measurement Code
Optional

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

  • PO413 defines the unit of measure for PO410, PO411, and PO412.
IN
Inch
PO4-14
810
Inner Pack
Optional
Min 1Max 6

The number of eaches per inner container

Usage notes

No. of EA. within an inner pack.

MAN
190

Marks and Numbers

RequiredMax use >1

To indicate identifying marks and numbers for shipping containers

Usage notes

MAN01 & MAN02 must comply to the standards established by the Uniform Code Council (UCC). We must receive this segment in order to receive merchandise by scanning.

Example
MAN-01
88
Marks and Numbers Qualifier
Required

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

If MAN01 is "GM" then MAN02 must be 20 digits and unique, but need not be sequential. If MAN01 is "UC" then MAN02 must be 12 or 14 digits.

GM
SSCC-18 and Application Identifier
UC
U.P.C. Shipping Container Code
MAN-02
87
Marks and Numbers
Required
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.
Usage notes

Shipping Container Identifier

Summary

CTT
010

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.
Example
CTT-01
354
Number of Line Items
Required
Min 1Max 6

Total number of line items in the transaction set

Usage notes

Count of all HL Segments (No.)

SE
020

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
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
Min 4Max 9

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

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
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
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
Min 1Max 5

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

IEA-02
I12
Interchange Control Number
Required
Min 9Max 9

A control number assigned by the interchange sender

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.