Computer Generated Solutions
/
Ship Notice/Manifest
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Computer Generated Solutions. Contact Computer Generated Solutions for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Computer Generated Solutions 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
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/computer-generated-solutions/ship-noticemanifest/01HJ3TKSCEJ7ETPBCMKZZNFR9F
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
PWK
090
Paperwork
Max use 25
Optional
TD5
120
Carrier Details (Routing Sequence/Transit Time)
Max use 12
Optional
REF
150
Reference Identification
Max use 1
Required
DTM
200
Date/Time Reference
Max use 10
Required
HL Loop Container
HL
010
Hierarchical Level
Max use 1
Required
TD1
110
Carrier Details (Quantity and Weight)
Max use 20
Optional
REF
150
Reference Identification
Max use 1
Required
DTM
200
Date/Time Reference
Max use 10
Optional
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

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

Code identifying purpose of transaction set

00
Original
05
Replace
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)
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.
BSN-05
1005
Hierarchical Structure Code
Required
Identifier (ID)

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
BSN-06
640
Transaction Type Code
Optional
Identifier (ID)

Code specifying the type of transaction

  • BSN06 is limited to shipment related codes.
  • BSN06 and BSN07 differentiate the functionality of use for the transaction set.
DS
Disposition
NO
Notice
SH
Shipment Status Notification
TH
Receipt Acknowledgment Advice
X1
Consolidator's Invoice
X2
X3
Heading end

Detail

HL Loop Shipment
RequiredMax >1
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.
PWK
090
Detail > HL Loop Shipment > PWK

Paperwork

OptionalMax use 25

To identify the type or transmission or both of paperwork or supporting information

Example
PWK-01
755
Report Type Code
Required
Identifier (ID)

Code indicating the title or contents of a document, report or supporting item

ZZ
Mutually Defined
PWK-07
352
Description
Required
String (AN)
Min 1Max 80

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

  • PWK07 may be used to indicate special information to be shown on the specified report.
TD5
120
Detail > HL Loop Shipment > TD5

Carrier Details (Routing Sequence/Transit Time)

OptionalMax use 12

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

Example
TD5-02
66
Identification Code Qualifier
Required
Identifier (ID)

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

  • When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
2
Standard Carrier Alpha Code (SCAC)
TD5-03
67
Identification Code
Required
String (AN)
Min 2Max 4

Code identifying a party or other code

TD5-04
91
Transportation Method/Type Code
Optional
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

TD5-07
309
Location Qualifier
Required
Identifier (ID)

Code identifying type of location

CA
Country of Origin
TD5-08
310
Location Identifier
Required
String (AN)
Min 1Max 30

Code which identifies a specific location

REF
150
Detail > HL Loop Shipment > REF

Reference Identification

RequiredMax use >1

To specify identifying information

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

Code qualifying the Reference Identification

6B
U.S. Customs Service (USCS) Entry Number
ABV
Book Number
BM
Bill of Lading Number
BSS
BST
FN
Forwarder's/Agent's Reference Number
FOB
POE
SH
Sender Defined Clause
UF1
UF2
UF3
UF4
UF5
UF6
V3
Voyage Number
WU
Vessel
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

DTM
200
Detail > HL Loop Shipment > DTM

Date/Time Reference

RequiredMax use 10

To specify pertinent dates and times

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

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

011
Shipped
371
Estimated Arrival Date
813
Customs Entry Date
AAG
Due Date
UD1
UD2
UD3
UD4
UD5
UD6
UD7
UD8
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

N1 Loop
RequiredMax >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

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

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

SF
Ship From
ST
Ship To
Optional
String (AN)
Min 1Max 35

Free-form name

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

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

97
Receiver's Code
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 17

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
Detail > HL Loop Shipment > N1 Loop > N3

Address Information

OptionalMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 35

Address information

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 35

Address information

N4
250
Detail > HL Loop Shipment > N1 Loop > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Optional
Identifier (ID)
Min 2Max 2

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

  • N402 is required only if city name (N401) is in the U.S. or Canada.
N4-03
116
Postal Code
Optional
Identifier (ID)
Min 3Max 15

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

N4-04
26
Country Code
Optional
Identifier (ID)
Min 2Max 3

Code identifying the country

N1 Loop end
HL Loop Container
RequiredMax >1
HL
010
Detail > HL Loop Shipment > HL Loop Container > 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.
CN
Container
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 Container > TD1

Carrier Details (Quantity and Weight)

OptionalMax use 20

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

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-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/1
CTN
Carton
TD1-02
80
Lading Quantity
Required
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity

TD1-06
187
Weight Qualifier
Optional
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)
Min 1Max 2

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

TD1-09
183
Volume
Optional
Decimal number (R)
Min 1Max 8

Value of volumetric measure

TD1-10
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)
Min 1Max 2

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

REF
150
Detail > HL Loop Shipment > HL Loop Container > REF

Reference Identification

RequiredMax use >1

To specify identifying information

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

Code qualifying the Reference Identification

6D
U.S. Customs Service (USCS) Statement Number
BCS
BCU
BM
Bill of Lading Number
ER
Container or Equipment Receipt Number
SN
Seal 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

DTM
200
Detail > HL Loop Shipment > HL Loop Container > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

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

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

AAG
Due Date
CCR
Customs Cargo Release
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

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

Name

RequiredMax use 1

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

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

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

SF
Ship From
ST
Ship To
Optional
String (AN)
Min 1Max 35

Free-form name

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

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

97
Receiver's Code
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 17

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
Detail > HL Loop Shipment > HL Loop Container > N1 Loop > N3

Address Information

OptionalMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 35

Address information

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 35

Address information

N4
250
Detail > HL Loop Shipment > HL Loop Container > N1 Loop > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Optional
Identifier (ID)
Min 2Max 2

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

  • N402 is required only if city name (N401) is in the U.S. or Canada.
N4-03
116
Postal Code
Optional
Identifier (ID)
Min 3Max 15

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

N4-04
26
Country Code
Optional
Identifier (ID)
Min 2Max 3

Code identifying the country

N1 Loop end
HL Loop Order
RequiredMax >1
HL
010
Detail > HL Loop Shipment > HL Loop Container > 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 Container > HL Loop Order > PRF

Purchase Order Reference

RequiredMax use 1

To provide reference to a specific purchase order

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

Identifying number for Purchase Order assigned by the orderer/purchaser

PRF-02
328
Release Number
Optional
String (AN)
Min 1Max 30

Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction

TD1
110
Detail > HL Loop Shipment > HL Loop Container > HL Loop Order > TD1

Carrier Details (Quantity and Weight)

OptionalMax use 20

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

Example
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/1
CTN
Carton
TD1-02
80
Lading Quantity
Required
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity

REF
150
Detail > HL Loop Shipment > HL Loop Container > HL Loop Order > REF

Reference Identification

OptionalMax use >1

To specify identifying information

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

Code qualifying the Reference Identification

BCN
BDV
BPT
IM
Intergovernmental Maritime Organization (IMO) 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

DTM
200
Detail > HL Loop Shipment > HL Loop Container > HL Loop Order > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

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

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

008
Purchase Order Received
135
Booking
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

HL Loop Pack
OptionalMax >1
HL
010
Detail > HL Loop Shipment > HL Loop Container > 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.
PO4
060
Detail > HL Loop Shipment > HL Loop Container > HL Loop Order > HL Loop Pack > PO4

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 Weight Qualifier (PO4-05) is present, then Gross Weight per Pack (PO4-06) is required
If either Gross Volume per Pack (PO4-08) or Unit or Basis for Measurement Code (PO4-09) is present, then the other is required
Optional
Numeric (N0)
Min 1Max 6

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

PO4-05
187
Weight Qualifier
Optional
Identifier (ID)
Min 1Max 2

Code defining the type of weight

PO4-06
384
Gross Weight per Pack
Optional
Decimal number (R)
Min 1Max 9

Numeric value of gross weight per pack

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

LB
Pound
PO4-08
385
Gross Volume per Pack
Optional
Decimal number (R)
Min 1Max 9

Numeric value of gross volume per pack

PO4-09
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
PO4-14
810
Inner Pack
Optional
Numeric (N0)
Min 1Max 6

The number of eaches per inner container

REF
150
Detail > HL Loop Shipment > HL Loop Container > HL Loop Order > HL Loop Pack > REF

Reference Identification

OptionalMax use >1

To specify identifying information

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

Code qualifying the Reference Identification

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

MAN
190
Detail > HL Loop Shipment > HL Loop Container > HL Loop Order > HL Loop Pack > MAN

Marks and Numbers

RequiredMax use >1

To indicate identifying marks and numbers for shipping containers

Example
If either Marks and Numbers Qualifier (MAN-04) or Marks and Numbers (MAN-05) is present, then the other is required
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 20Max 20

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.
MAN-03
87
Marks and Numbers
Optional
String (AN)
Min 1Max 48

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

  • MAN03 and/or MAN06 are only used when sending a range(s) of ID numbers.
  • When both MAN02/MAN03 and MAN05/MAN06 are used to send ranges of ID numbers, the integrity of the two ID numbers must be maintained.
MAN-04
88
Marks and Numbers Qualifier
Optional
Identifier (ID)

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

W
Pallet Number
MAN-05
87
Marks and Numbers
Optional
String (AN)
Min 1Max 48

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

  • When both MAN05 and MAN06 are used, MAN05 is the starting number of a sequential range, and MAN06 is the ending number of that range.
HL Loop Item
RequiredMax >1
HL
010
Detail > HL Loop Shipment > HL Loop Container > 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 Container > HL Loop Order > HL Loop Pack > HL Loop Item > LIN

Item Identification

RequiredMax use 1

To specify basic item identification data

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
If either Product/Service ID Qualifier (LIN-12) or Product/Service ID (LIN-13) is present, then the other is required
If either Product/Service ID Qualifier (LIN-14) or Product/Service ID (LIN-15) is present, then the other is required
If either Product/Service ID Qualifier (LIN-16) or Product/Service ID (LIN-17) is present, then the other is required
LIN-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 10

Alphanumeric characters assigned for differentiation within a transaction set

  • LIN01 is the line item identification
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.
UP
U.P.C. Consumer Package Code (1-5-5-1)
LIN-03
234
Product/Service ID
Required
String (AN)
Min 12Max 12

Identifying number for a product or service

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

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

PL
Purchaser's Order Line Number
LIN-05
234
Product/Service ID
Required
String (AN)
Min 1Max 20

Identifying number for a product or service

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

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

ST
Style Number
LIN-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 12

Identifying number for a product or service

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

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

CL
Color
LIN-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 10

Identifying number for a product or service

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

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

BL
Brand/Label
LIN-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 10

Identifying number for a product or service

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

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

DM
Committee for Uniform Security Identification Procedure Number (CUSIP) Number
LIN-13
234
Product/Service ID
Optional
String (AN)
Min 1Max 10

Identifying number for a product or service

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

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

IZ
Buyer's Size Code
LIN-15
234
Product/Service ID
Optional
String (AN)
Min 1Max 10

Identifying number for a product or service

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

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

LI
LIN-17
234
Product/Service ID
Optional
String (AN)
Min 1Max 10

Identifying number for a product or service

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

Item Detail (Shipment)

RequiredMax use 1

To specify line-item detail relative to shipment

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
SLN
040
Detail > HL Loop Shipment > HL Loop Container > HL Loop Order > HL Loop Pack > HL Loop Item > SLN

Subline Item Detail

OptionalMax use 1000

To specify product subline detail item data

Example
SLN-01
350
Assigned Identification
Required
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • SLN01 is the identifying number for the subline item.
  • SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
SLN-03
662
Relationship Code
Required
Identifier (ID)

Code indicating the relationship between entities

  • SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
O
Information Only
SLN-06
212
Unit Price
Required
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

SLN-07
639
Basis of Unit Price Code
Required
Identifier (ID)

Code identifying the type of unit price for an item

PE
Price per Each
MEA
080
Detail > HL Loop Shipment > HL Loop Container > HL Loop Order > HL Loop Pack > HL Loop Item > MEA

Measurements

OptionalMax use 40

To specify physical measurements or counts, including dimensions, tolerances, variances, and weights

(See Figures Appendix for example of use of C001)

Example
MEA-01
737
Measurement Reference ID Code
Optional
Identifier (ID)

Code identifying the broad category to which a measurement applies

CT
Counts
PD
Physical Dimensions
WT
Weights
MEA-02
738
Measurement Qualifier
Required
Identifier (ID)

Code identifying a specific product or process characteristic to which a measurement applies

G
Gross Weight
HT
Height
LN
Length
SQ
Shipped Quantity
VOL
Volume
WD
Width
MEA-03
739
Measurement Value
Required
Decimal number (R)
Min 1Max 10

The value of the measurement

MEA-04
C001
Composite Unit of Measure
RequiredMax use 1
To identify a composite unit of measure (See Figures Appendix for examples of use)
C001-01
355
Unit or Basis for Measurement Code
Required
Identifier (ID)
Min 2Max 2

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

REF
150
Detail > HL Loop Shipment > HL Loop Container > HL Loop Order > HL Loop Pack > HL Loop Item > REF

Reference Identification

OptionalMax use >1

To specify identifying information

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

Code qualifying the Reference Identification

DL
Seller's Debit Memo
UI1
UI2
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

HL Loop Item end
HL Loop Pack end
HL Loop Order end
HL Loop Container 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.
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

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.