X12 856 Ship Notice/Manifest

X12 Release 5010

This X12 Transaction Set 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
• ^ Repetition

ISA Interchange Control Header

Required · Max use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

ISA-01 · I01 · Authorization Information Qualifier · Required · Identifier (ID)

Code identifying the type of information in the Authorization Information

• 00: No Authorization Information Present (No Meaningful Information in I02)

ISA-02 · I02 · Authorization Information · Required · String (AN) · Min 10 Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03 · I03 · Security Information Qualifier · Required · Identifier (ID)

Code identifying the type of information in the Security Information

• 00: No Security Information Present (No Meaningful Information in I04)

ISA-04 · I04 · Security Information · Required · String (AN) · Min 10 Max 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)

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

• 01: Duns (Dun & Bradstreet)
• 12: Phone (Telephone Companies)
• ZZ: Mutually Defined

ISA-06 · I06 · Interchange Sender ID · Required · String (AN) · Min 15 Max 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)

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

• 01: Duns (Dun & Bradstreet)

ISA-08 · I07 · Interchange Receiver ID · Required · String (AN) · Min 15 Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09 · I08 · Interchange Date · Required · Date (DT) · YYMMDD format

Date of the interchange

ISA-10 · I09 · Interchange Time · Required · Time (TM) · HHMM format

Time of the interchange

ISA-11 · I65 · Repetition Separator · Required · String (AN) · Min 1 Max 1

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

• ^: Repetition Separator

ISA-12 · I11 · Interchange Control Version Number · Required · Identifier (ID)

Code specifying the version number of the interchange control segments

• 00501: Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003

ISA-13 · I12 · Interchange Control Number · Required · Numeric (N0) · Min 9 Max 9

A control number assigned by the interchange sender

ISA-14 · I13 · Acknowledgment Requested · Required · Identifier (ID)

Code indicating sender's request for an interchange acknowledgment

• 0: No Interchange Acknowledgment Requested

ISA-15 · I14 · Interchange Usage Indicator · Required · Identifier (ID) · Min 1 Max 1

Code indicating whether data enclosed by this interchange envelope is test, production or information

• I: Information
• P: Production Data
• T: Test Data

ISA-16 · I15 · Component Element Separator · Required · String (AN) · Min 1 Max 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

GS Functional Group Header

Required · Max use 1

To indicate the beginning of a functional group and to provide control information

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 2 Max 15

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

GS-03 · 124 · Application Receiver's Code · Required · String (AN) · Min 2 Max 15

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

GS-04 · 373 · Date · Required · Date (DT) · CCYYMMDD format

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

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

Assigned number originated and maintained by the sender

GS-07 · 455 · Responsible Agency Code · Required · Identifier (ID) · Min 1 Max 2

Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480

• T: Transportation Data Coordinating Committee (TDCC)
• X: Accredited Standards Committee X12

GS-08 · 480 · Version / Release / Industry Identifier Code · Required · String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

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

Heading

0100 Heading > ST

ST Transaction Set Header

Required · Max use 1

To indicate the start of a transaction set and to assign a control number

ST-01 · 143 · Transaction Set Identifier Code · Required · Identifier (ID)

Code uniquely identifying a Transaction Set

• The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

• 856: Ship Notice/Manifest

ST-02 · 329 · Transaction Set Control Number · Required · String (AN) · Min 4 Max 9

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

0200 Heading > BSN

BSN Beginning Segment for Ship Notice

Required · Max use 1

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

BSN-01 · 353 · Transaction Set Purpose Code · Required · Identifier (ID) · Min 2 Max 2

Code identifying purpose of transaction set

BSN-02 · 396 · Shipment Identification · Required · String (AN) · Min 2 Max 30

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

BSN-03 · 373 · Date · Required · Date (DT) · CCYYMMDD format

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

• BSN03 is the date the shipment transaction set is created.

BSN-04 · 337 · Time · 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

0400 Heading > DTM

DTM Date/Time Reference

Optional · Max use 2

To specify pertinent dates and times

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

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

• 011: Shipped
• 017: Estimated Delivery

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

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

DTM-03 · 337 · Time · Optional · Time (TM) · HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Detail

HL Loop Shipment Required Max >1

0100 Detail > HL Loop Shipment > HL

HL Hierarchical Level

Required · Max 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.

HL-01 · 628 · Hierarchical ID Number · Required · String (AN) · Min 1 Max 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.

1100 Detail > HL Loop Shipment > TD1

TD1 Carrier Details (Quantity and Weight)

Optional · Max use 20

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

If Commodity Code Qualifier (TD1-03) is present, then Commodity Code (TD1-04) is required

If Weight Qualifier (TD1-06) is present, then Weight (TD1-07) is required

If either Weight (TD1-07) or Unit or Basis for Measurement Code (TD1-08) 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
• PLT: Pallet

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

Number of units (pieces) of the lading commodity

TD1-03 · 23 · Commodity Code Qualifier · Optional · Identifier (ID) · Min 1 Max 1

Code identifying the commodity coding system used for Commodity Code

TD1-04 · 22 · Commodity Code · Optional · String (AN) · Min 1 Max 30

Code describing a commodity or group of commodities

TD1-05 · 79 · Lading Description · Optional · String (AN) · Min 1 Max 50

Description of an item as required for rating and billing purposes

TD1-06 · 187 · Weight Qualifier · Optional · Identifier (ID) · Min 1 Max 2

Code defining the type of weight

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

Numeric value of weight

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

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

1200 Detail > HL Loop Shipment > TD5

TD5 Carrier Details (Routing Sequence/Transit Time)

Required · Max use 12

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

If Identification Code Qualifier (TD5-02) is present, then at least one of Identification Code (TD5-03) or Routing (TD5-05) is required

At least one of Identification Code (TD5-03) or Routing (TD5-05) is required

TD5-01 · 133 · Routing Sequence Code · Optional · Identifier (ID) · Min 1 Max 2

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

TD5-02 · 66 · Identification Code Qualifier · Optional · Identifier (ID) · Min 1 Max 2

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.

TD5-03 · 67 · Identification Code · Optional · String (AN) · Min 2 Max 80

Code identifying a party or other code

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

Code specifying the method or type of transportation for the shipment

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

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

TD5-06 · 368 · Shipment/Order Status Code · Optional · Identifier (ID) · Min 2 Max 2

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

1500 Detail > HL Loop Shipment > REF

REF Reference Information

Optional · Max use 3

To specify identifying information

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

Code qualifying the Reference Identification

• 2I: Tracking Number
• BM: Bill of Lading Number
• CN: Carrier's Reference Number (PRO/Invoice)
• PK: Packing List Number

REF-02 · 127 · Reference Identification · Optional · String (AN) · Min 1 Max 50

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

2000 Detail > HL Loop Shipment > DTM

DTM Date/Time Reference

Required · Max use 10

To specify pertinent dates and times

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

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

• 011: Shipped
• 017: Estimated Delivery

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

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

DTM-03 · 337 · Time · Optional · Time (TM) · HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

N1 Loop Optional Max >1

Variants (all may be used)

N1 Loop Ship To

2200 Detail > HL Loop Shipment > N1 Loop > N1

N1 Party Identification

Required · Max use 1

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

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

• SE: Selling Party
• SF: Ship From

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 60

Free-form name

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID) · Min 1 Max 2

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

N1-04 · 67 · Identification Code · Optional · String (AN) · Min 2 Max 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.

2400 Detail > HL Loop Shipment > N1 Loop > N3

N3 Party Location

Required · Max use 2

To specify the location of the named party

N3-01 · 166 · Address Information · Required · String (AN) · Min 1 Max 55

Address information

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

Address information

2500 Detail > HL Loop Shipment > N1 Loop > N4

N4 Geographic Location

Required · Max use 1

To specify the geographic place of the named party

N4-01 · 19 · City Name · Optional · String (AN) · Min 2 Max 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 2 Max 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 3 Max 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 2 Max 3

Code identifying the country

N1 Loop Ship To Required Max >1

Variants (all may be used)

N1 Loop

2200 Detail > HL Loop Shipment > N1 Loop Ship To > N1

N1 Party Identification

Required · Max use 1

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

At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required

If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

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

• ST: Ship To

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 60

Free-form name

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID) · Min 1 Max 2

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

N1-04 · 67 · Identification Code · Optional · String (AN) · Min 2 Max 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.

2400 Detail > HL Loop Shipment > N1 Loop Ship To > N3

N3 Party Location

Required · Max use 2

To specify the location of the named party

N3-01 · 166 · Address Information · Required · String (AN) · Min 1 Max 55

Address information

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

Address information

2500 Detail > HL Loop Shipment > N1 Loop Ship To > N4

N4 Geographic Location

Required · Max use 1

To specify the geographic place of the named party

N4-01 · 19 · City Name · Optional · String (AN) · Min 2 Max 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 2 Max 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 3 Max 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 2 Max 3

Code identifying the country

HL Loop Order Required Max >1

0100 Detail > HL Loop Shipment > HL Loop Order > HL

HL Hierarchical Level

Required · Max 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.

HL-01 · 628 · Hierarchical ID Number · Required · String (AN) · Min 1 Max 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 1 Max 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.

• 1: Additional Subordinate HL Data Segment in This Hierarchical Structure.

0500 Detail > HL Loop Shipment > HL Loop Order > PRF

PRF Purchase Order Reference

Required · Max use 1

To provide reference to a specific purchase order

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

Identifying number for Purchase Order assigned by the orderer/purchaser

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

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

PRF-03 · 327 · Change Order Sequence Number · Optional · String (AN) · Min 1 Max 8

Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set

PRF-04 · 373 · Date · Optional · Date (DT) · CCYYMMDD format

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

• PRF04 is the date assigned by the purchaser to purchase order.

PRF-05 · 350 · Assigned Identification · Optional · String (AN) · Min 1 Max 20

Alphanumeric characters assigned for differentiation within a transaction set

HL Loop Part Required Max >1

0100 Detail > HL Loop Shipment > HL Loop Order > HL Loop Part > HL

HL Hierarchical Level

Required · Max 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.

HL-01 · 628 · Hierarchical ID Number · Required · String (AN) · Min 1 Max 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 1 Max 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.

1900 Detail > HL Loop Shipment > HL Loop Order > HL Loop Part > MAN

MAN Marks and Numbers Information

Required · Max use >1

To indicate identifying marks and numbers for shipping containers

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.

• CP: Carrier-Assigned Package ID Number
• GM: EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier

MAN-02 · 87 · Marks and Numbers · Required · String (AN) · Min 1 Max 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.

Note: MAN-02 is the tracking number

HL Loop Item Required Max >1

0100 Detail > HL Loop Shipment > HL Loop Order > HL Loop Part > HL Loop Item > HL

HL Hierarchical Level

Required · Max 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.

HL-01 · 628 · Hierarchical ID Number · Required · String (AN) · Min 1 Max 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 1 Max 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.

0200 Detail > HL Loop Shipment > HL Loop Order > HL Loop Part > HL Loop Item > LIN

LIN Item Identification

Required · Max use 1

To specify basic item identification data

If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required

LIN-01 · 350 · Assigned Identification · Optional · String (AN) · Min 1 Max 20

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.

• VC: Vendor's (Seller's) Catalog Number

LIN-03 · 234 · Product/Service ID · Required · String (AN) · Min 1 Max 48

Identifying number for a product or service

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

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

• SK: Stock Keeping Unit (SKU)

LIN-05 · 234 · Product/Service ID · Optional · String (AN) · Min 1 Max 48

Identifying number for a product or service

0300 Detail > HL Loop Shipment > HL Loop Order > HL Loop Part > HL Loop Item > SN1

SN1 Item Detail (Shipment)

Required · Max use 1

To specify line-item detail relative to shipment

If either Quantity (SN1-05) or Unit or Basis for Measurement Code (SN1-06) is present, then the other is required

SN1-01 · 350 · Assigned Identification · Optional · String (AN) · Min 1 Max 20

Alphanumeric characters assigned for differentiation within a transaction set

• SN101 is the ship notice line-item identification.

SN1-02 · 382 · Number of Units Shipped · Required · Decimal number (R) · Min 1 Max 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

SN1-04 · 646 · Quantity Shipped to Date · Optional · Decimal number (R) · Min 1 Max 15

Number of units shipped to date

SN1-05 · 380 · Quantity · Optional · Decimal number (R) · Min 1 Max 15

Numeric value of quantity

• SN105 is quantity ordered.

SN1-06 · 355 · Unit or Basis for Measurement Code · Optional · Identifier (ID) · Min 2 Max 2

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

SN1-07 · 728 · Returnable Container Load Make-Up Code · Optional · Identifier (ID) · Min 1 Max 2

Code identifying the load make-up of the returnable containers in the shipment

SN1-08 · 668 · Line Item Status Code · Optional · Identifier (ID) · Min 2 Max 2

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

0700 Detail > HL Loop Shipment > HL Loop Order > HL Loop Part > HL Loop Item > PID

PID Product/Item Description

Optional · Max use 200

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

PID-01 · 349 · Item Description Type · Required · Identifier (ID)

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 · Required · String (AN) · Min 1 Max 80

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

Summary

0100 Summary > CTT

CTT Transaction Totals

Optional · Max 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.

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

Total number of line items in the transaction set

CTT-02 · 347 · Hash Total · Optional · Decimal number (R) · Min 1 Max 10

Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.

## Example:
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
18E2 Fifth occurrence of value being hashed.

1873 Hash Total

0200 Summary > SE

SE Transaction Set Trailer

Required · Max 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)

SE-01 · 96 · Number of Included Segments · Required · Numeric (N0) · Min 1 Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02 · 329 · Transaction Set Control Number · Required · String (AN) · Min 4 Max 9

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

GE Functional Group Trailer

Required · Max use 1

To indicate the end of a functional group and to provide control information

GE-01 · 97 · Number of Transaction Sets Included · Required · Numeric (N0) · Min 1 Max 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 1 Max 9

Assigned number originated and maintained by the sender

IEA Interchange Control Trailer

Required · Max use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

IEA-01 · I16 · Number of Included Functional Groups · Required · Numeric (N0) · Min 1 Max 5

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

IEA-02 · I12 · Interchange Control Number · Required · Numeric (N0) · Min 9 Max 9

A control number assigned by the interchange sender