856 Ship Notice/Manifest

Functional Group ID=SH

Introduction:

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.

Heading:

	Pos.	Seg.		Req.		Loop	Notes and
	No.	ID	Name	Des.	Max.Use	Repeat	Comments	
M | 010 | ST | Transaction Set Header | M | 1 | | | | | | | |
M | 020 | BSN | Beginning Segment for Ship Notice | M | 1 | | | | | | | |
| 040 | DTM | Date/Time Reference | O | 10 | | | | | | | |

Detail:

	Pos.	Seg.		Req.		Loop	Notes and
	No.	ID	Name	Des.	Max.Use	Repeat	Comments	
| | | LOOP ID - HL | | | 200000 | | | | | | |
M | 010 | HL | Hierarchical Level (SHIPMENT) | M | 1 | | c1 | | | | | |
| 110 | TD1 | Carrier Details (Quantity and Weight) | O | 20 | | | | | | | |
| 120 | TD5 | Carrier Details (Routing Sequence/Transit Time) | O | 12 | | | | | | | |
| 200 | DTM | Date/Time Reference | O | 10 | | | | | | | |
| | | LOOP ID - N1 | | | 200 | | | | | | |
| 220 | N1 | Name | O | 1 | | | | | | | |
| 240 | N3 | Address Information | O | 2 | | | | | | | |
| 250 | N4 | Geographic Location | O | 1 | | | | | | | |
M | 285 | HL | Hierarchical Level (ORDER) | M | 1 | | | | | | | |
| 288 | PRF | Purchase Order Reference | O | 1 | | | | | | | |
| 289 | REF | Reference Identification | O | 1 | | | | | | | |
| 289 | REF | Reference Identification | O | 1 | | | | | | | |
| 289 | REF | Reference Identification | O | 1 | | | | | | | |
| 290 | HL | Hierarchical Level | O | 1 | | | | | | | |
| 290 | MAN | Marks and Numbers | O | 1 | | | | | | | |
| 293 | HL | Hierarchical Level (ITEM) | O | >1 | | | | | | | |
| 294 | LIN | Item Identification | O | 1 | | | | | | | |
| 295 | SN1 | Item Detail (Shipment) | O | 1 | | | | | | | |

Summary:

	Pos.	Seg.		Req.		Loop	Notes and
	No.	ID	Name	Des.	Max.Use	Repeat	Comments	
| 010 | CTT | Transaction Totals | O | 1 | | n1 | | | | | |
M | 020 | SE | Transaction Set Trailer | M | 1 | | | | | | | |

Transaction Set Notes

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

Transaction Set Comments

1.	The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.

	Segment:	ST Transaction Set Header
	Position:	010
	Loop:
	Level:	Heading
	Usage:	Must Use
	Max Use:	1
	Purpose:	To indicate the start of a transaction set and to assign a control number
	Syntax Notes:
	Semantic Notes:	1	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).
	Comments:

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | ST01 | 143 | Transaction Set Identifier Code | M | | ID 3/3
| Code uniquely identifying a Transaction Set
| Refer to 004010 Data Element Dictionary for acceptable code values.
M | ST02 | 329 | Transaction Set Control Number | M | | AN 4/9
| Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

	Segment:	BSN Beginning Segment for Ship Notice
	Position:	020
	Loop:
	Level:	Heading
	Usage:	Must Use
	Max Use:	1
	Purpose:	To transmit identifying numbers, dates, and other basic data relating to the transaction set
	Syntax Notes:	1	If BSN07 is present, then BSN06 is required.
	Semantic Notes:	1	BSN03 is the date the shipment transaction set is created.
		2	BSN04 is the time the shipment transaction set is created.
		3	BSN06 is limited to shipment related codes.
	Comments:	1	BSN06 and BSN07 differentiate the functionality of use for the transaction set.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | BSN01 | 353 | Transaction Set Purpose Code | M | | ID 2/2
| Code identifying purpose of transaction set
| 00 | | Original
M | BSN02 | 396 | Shipment Identification | M | | AN 2/30
| A unique control number assigned by the original shipper to identify a specific shipment
M | BSN03 | 373 | Date | M | | DT 8/8
| Date expressed as CCYYMMDD
M | BSN04 | 337 | Time | M | | TM 4/8
| 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)

	Segment:	DTM Date/Time Reference
	Position:	040
	Loop:
	Level:	Heading
	Usage:	Optional
	Max Use:	10
	Purpose:	To specify pertinent dates and times
	Syntax Notes:	1	At least one of DTM02 DTM03 or DTM05 is required.
		2	If DTM04 is present, then DTM03 is required.
		3	If either DTM05 or DTM06 is present, then the other is required.
	Semantic Notes:
	Comments:

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | DTM01 | 374 | Date/Time Qualifier | M | | ID 3/3
| Code specifying type of date or time, or both date and time
| 011 | | Shipped
| DTM02 | 373 | Date | X | | DT 8/8
| Date expressed as CCYYMMDD
| DTM03 | 337 | Time | X | | TM 4/8
| 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)

	Segment:	HL Hierarchical Level (SHIPMENT)
	Position:	010
	Loop:	HL        Optional
	Level:	Detail
	Usage:	Must Use
	Max Use:	1
	Purpose:	To identify dependencies among and the content of hierarchically related groups of data segments
	Syntax Notes:
	Semantic Notes:
	Comments:	1	The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
			The HL segment defines a top-down/left-right ordered structure.
		2	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.
		3	HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
		4	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.
		5	HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | HL01 | 628 | Hierarchical ID Number | M | | AN 1/12
| A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
M | HL03 | 735 | Hierarchical Level Code | M | | ID 1/2
| Code defining the characteristic of a level in a hierarchical structure
| Refer to 004010 Data Element Dictionary for acceptable code values.
| HL04 | 736 | Hierarchical Child Code | O | | ID 1/1
| Code indicating if there are hierarchical child data segments subordinate to the level being described
| Refer to 004010 Data Element Dictionary for acceptable code values.

	Segment:	TD1 Carrier Details (Quantity and Weight)
	Position:	110
	Loop:	HL        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	20
	Purpose:	To specify the transportation details relative to commodity, weight, and quantity
	Syntax Notes:	1	If TD101 is present, then TD102 is required.
		2	If TD103 is present, then TD104 is required.
		3	If TD106 is present, then TD107 is required.
		4	If either TD107 or TD108 is present, then the other is required.
		5	If either TD109 or TD110 is present, then the other is required.
	Semantic Notes:
	Comments:

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
| TD101 | 103 | Packaging Code | O | | AN 3/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
| Refer to 004010 Data Element Dictionary for acceptable code values.
| TD102 | 80 | Lading Quantity | X | | N0 1/7
| Number of units (pieces) of the lading commodity
| TD103 | 23 | Commodity Code Qualifier | O | | ID 1/1
| Code identifying the commodity coding system used for Commodity Code
| Refer to 004010 Data Element Dictionary for acceptable code values.
| TD104 | 22 | Commodity Code | X | | AN 1/30
| Code describing a commodity or group of commodities
| TD105 | 79 | Lading Description | O | | AN 1/50
| Description of an item as required for rating and billing purposes
| TD106 | 187 | Weight Qualifier | O | | ID 1/2
| Code defining the type of weight
| Refer to 004010 Data Element Dictionary for acceptable code values.
| TD107 | 81 | Weight | X | | R 1/10
| Numeric value of weight
| TD108 | 355 | Unit or Basis for Measurement Code | X | | ID 2/2
| Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
| Refer to 004010 Data Element Dictionary for acceptable code values.
| TD109 | 183 | Volume | X | | R 1/8
| Value of volumetric measure
| TD110 | 355 | Unit or Basis for Measurement Code | X | | ID 2/2
| Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
| Refer to 004010 Data Element Dictionary for acceptable code values.

	Segment:	TD5 Carrier Details (Routing Sequence/Transit Time)
	Position:	120
	Loop:	HL        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	12
	Purpose:	To specify the carrier and sequence of routing and provide transit time information
	Syntax Notes:	1	At least one of TD502 TD504 TD505 TD506 or TD512 is required.
		2	If TD502 is present, then TD503 is required.
		3	If TD507 is present, then TD508 is required.
		4	If TD510 is present, then TD511 is required.
		5	If TD513 is present, then TD512 is required.
		6	If TD514 is present, then TD513 is required.
		7	If TD515 is present, then TD512 is required.
	Semantic Notes:	1	TD515 is the country where the service is to be performed.
	Comments:	1	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.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
| TD501 | 133 | Routing Sequence Code | O | | ID 1/2
| Code describing the relationship of a carrier to a specific shipment movement
| Refer to 004010 Data Element Dictionary for acceptable code values.
| TD502 | 66 | Identification Code Qualifier | X | | ID 1/2
| Code designating the system/method of code structure used for Identification Code (67)
| Refer to 004010 Data Element Dictionary for acceptable code values.
| TD503 | 67 | Identification Code | X | | AN 2/80
| Code identifying a party or other code
| TD504 | 91 | Transportation Method/Type Code | X | | ID 1/2
| Code specifying the method or type of transportation for the shipment
| Refer to 004010 Data Element Dictionary for acceptable code values.
| TD505 | 387 | Routing | X | | AN 1/35
| Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
| TD506 | 368 | Shipment/Order Status Code | X | | ID 2/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
| Refer to 004010 Data Element Dictionary for acceptable code values.
| TD507 | 309 | Location Qualifier | O | | ID 1/2
| Code identifying type of location
| Refer to 004010 Data Element Dictionary for acceptable code values.
| TD508 | 310 | Location Identifier | X | | AN 1/30
| Code which identifies a specific location
| TD509 | 731 | Transit Direction Code | O | | ID 2/2
| The point of origin and point of direction
| Refer to 004010 Data Element Dictionary for acceptable code values.
| TD510 | 732 | Transit Time Direction Qualifier | O | | ID 2/2
| Code specifying the value of time used to measure the transit time
| Refer to 004010 Data Element Dictionary for acceptable code values.
| TD511 | 733 | Transit Time | X | | R 1/4
| The numeric amount of transit time
| TD512 | 284 | Service Level Code | X | | ID 2/2
| Code indicating the level of transportation service or the billing service offered by the transportation carrier
| Refer to 004010 Data Element Dictionary for acceptable code values.
| TD513 | 284 | Service Level Code | X | | ID 2/2
| Code indicating the level of transportation service or the billing service offered by the transportation carrier
| Refer to 004010 Data Element Dictionary for acceptable code values.
| TD514 | 284 | Service Level Code | O | | ID 2/2
| Code indicating the level of transportation service or the billing service offered by the transportation carrier
| Refer to 004010 Data Element Dictionary for acceptable code values.
| TD515 | 26 | Country Code | O | | ID 2/3
| Code identifying the country

	Segment:	DTM Date/Time Reference
	Position:	200
	Loop:	HL        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	10
	Purpose:	To specify pertinent dates and times
	Syntax Notes:	1	At least one of DTM02 DTM03 or DTM05 is required.
		2	If DTM04 is present, then DTM03 is required.
		3	If either DTM05 or DTM06 is present, then the other is required.
	Semantic Notes:
	Comments:

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | DTM01 | 374 | Date/Time Qualifier | M | | ID 3/3
| Code specifying type of date or time, or both date and time
| Refer to 004010 Data Element Dictionary for acceptable code values.
| DTM02 | 373 | Date | X | | DT 8/8
| Date expressed as CCYYMMDD
| DTM03 | 337 | Time | X | | TM 4/8
| 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)
| DTM04 | 623 | Time Code | O | | ID 2/2
| Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
| Refer to 004010 Data Element Dictionary for acceptable code values.
| DTM05 | 1250 | Date Time Period Format Qualifier | X | | ID 2/3
| Code indicating the date format, time format, or date and time format
| Refer to 004010 Data Element Dictionary for acceptable code values.
| DTM06 | 1251 | Date Time Period | X | | AN 1/35
| Expression of a date, a time, or range of dates, times or dates and times

	Segment:	N1 Name
	Position:	220
	Loop:	N1        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To identify a party by type of organization, name, and code
	Syntax Notes:	1	At least one of N102 or N103 is required.
		2	If either N103 or N104 is present, then the other is required.
	Semantic Notes:
	Comments:	1	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.
		2	N105 and N106 further define the type of entity in N101.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | N101 | 98 | Entity Identifier Code | M | | ID 2/3
| Code identifying an organizational entity, a physical location, property or an individual
| SF | | Ship From
| ST | | Ship To
| N102 | 93 | Name | X | | AN 1/60
| Free-form name
| N103 | 66 | Identification Code Qualifier | X | | ID 1/2
| Code designating the system/method of code structure used for Identification Code (67)
| 91 | | Assigned by Seller or Seller's Agent
| N104 | 67 | Identification Code | X | | AN 2/80
| Code identifying a party or other code

	Segment:	N3 Address Information
	Position:	240
	Loop:	N1        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	2
	Purpose:	To specify the location of the named party
	Syntax Notes:
	Semantic Notes:
	Comments:

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | N301 | 166 | Address Information | M | | AN 1/55
| Address information
| N302 | 166 | Address Information | O | | AN 1/55
| Address information

	Segment:	N4 Geographic Location
	Position:	250
	Loop:	N1        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To specify the geographic place of the named party
	Syntax Notes:	1	If N406 is present, then N405 is required.
	Semantic Notes:
	Comments:	1	A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
		2	N402 is required only if city name (N401) is in the U.S. or Canada.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
| N401 | 19 | City Name | O | | AN 2/30
| Free-form text for city name
| N402 | 156 | State or Province Code | O | | ID 2/2
| Code (Standard State/Province) as defined by appropriate government agency
| N403 | 116 | Postal Code | O | | ID 3/15
| Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
| N404 | 26 | Country Code | O | | ID 2/3
| Code identifying the country
| N405 | 309 | Location Qualifier | X | | ID 1/2
| Code identifying type of location
| Refer to 004010 Data Element Dictionary for acceptable code values.
| N406 | 310 | Location Identifier | O | | AN 1/30
| Code which identifies a specific location

	Segment:	HL Hierarchical Level (ORDER)
	Position:	285
	Loop:	HL        Optional
	Level:	Detail
	Usage:	Must Use
	Max Use:	1
	Purpose:	To identify dependencies among and the content of hierarchically related groups of data segments
	Syntax Notes:
	Semantic Notes:
	Comments:	1	The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
			The HL segment defines a top-down/left-right ordered structure.
		2	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.
		3	HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
		4	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.
		5	HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | HL01 | 628 | Hierarchical ID Number | M | | AN 1/12
| A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
| HL02 | 734 | Hierarchical Parent ID Number | O | | AN 1/12
| Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
M | HL03 | 735 | Hierarchical Level Code | M | | ID 1/2
| Code defining the characteristic of a level in a hierarchical structure
| O | | Order
| HL04 | 736 | Hierarchical Child Code | O | | ID 1/1
| Code indicating if there are hierarchical child data segments subordinate to the level being described
| Refer to 004010 Data Element Dictionary for acceptable code values.

	Segment:	PRF Purchase Order Reference
	Position:	288
	Loop:	HL        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To provide reference to a specific purchase order
	Syntax Notes:
	Semantic Notes:	1	PRF04 is the date assigned by the purchaser to purchase order.
	Comments:

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | PRF01 | 324 | Purchase Order Number | M | | AN 1/22
| Identifying number for Purchase Order assigned by the orderer/purchaser
| PRF04 | 373 | Date | O | | DT 8/8
| Date expressed as CCYYMMDD

	Segment:	REF Reference Identification
	Position:	289
	Loop:	HL        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | REF01 | 128 | Reference Identification Qualifier | M | | ID 2/3
| Code qualifying the Reference Identification
| CN | | Carrier's Reference Number (PRO/Invoice)
| REF02 | 127 | Reference Identification | X | | AN 1/30
| Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

	Segment:	REF Reference Identification
	Position:	289
	Loop:	HL        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | REF01 | 128 | Reference Identification Qualifier | M | | ID 2/3
| Code qualifying the Reference Identification
| OQ | | Order Number
| Qualifies a code that identifies the authorizing documentation for a household goods
| ***FOR GHX CUSTOMERS ONLY***
| REF02 | 127 | Reference Identification | X | | AN 1/30
| Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

	Segment:	REF Reference Identification
	Position:	289
	Loop:	HL        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | REF01 | 128 | Reference Identification Qualifier | M | | ID 2/3
| Code qualifying the Reference Identification
| VN | | Vendor Order Number
| REF02 | 127 | Reference Identification | X | | AN 1/30
| Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

	Segment:	HL Hierarchical Level
	Position:	290
	Loop:	HL        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To identify dependencies among and the content of hierarchically related groups of data segments
	Syntax Notes:
	Semantic Notes:
	Comments:	1	The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
			The HL segment defines a top-down/left-right ordered structure.
		2	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.
		3	HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
		4	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.
		5	HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | HL01 | 628 | Hierarchical ID Number | M | | AN 1/12
| A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
| HL02 | 734 | Hierarchical Parent ID Number | O | | AN 1/12
| Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
M | HL03 | 735 | Hierarchical Level Code | M | | ID 1/2
| Code defining the characteristic of a level in a hierarchical structure
| I | | Item
| HL04 | 736 | Hierarchical Child Code | O | | ID 1/1
| Code indicating if there are hierarchical child data segments subordinate to the level being described
| Refer to 004010 Data Element Dictionary for acceptable code values.

	Segment:	MAN Marks and Numbers
	Position:	290
	Loop:	HL        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To indicate identifying marks and numbers for shipping containers
	Syntax Notes:	1	If either MAN04 or MAN05 is present, then the other is required.
		2	If MAN06 is present, then MAN05 is required.
	Semantic Notes:	1	MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
		2	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.
		3	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.
	Comments:	1	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.
		2	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.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | MAN01 | 88 | Marks and Numbers Qualifier | M | | ID 1/2
| Code specifying the application or source of Marks and Numbers (87)
| SM | | Shipper Assigned
| ZZ | | Mutually Defined
M | MAN02 | 87 | Marks and Numbers | M | | AN 1/48
| Marks and numbers used to identify a shipment or parts of a shipment

	Segment:	HL Hierarchical Level (ITEM)
	Position:	293
	Loop:	HL        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	Purpose:	To identify dependencies among and the content of hierarchically related groups of data segments
	Syntax Notes:
	Semantic Notes:
	Comments:	1	The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
			The HL segment defines a top-down/left-right ordered structure.
		2	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.
		3	HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
		4	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.
		5	HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | HL01 | 628 | Hierarchical ID Number | M | | AN 1/12
| A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
| HL02 | 734 | Hierarchical Parent ID Number | O | | AN 1/12
| Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
M | HL03 | 735 | Hierarchical Level Code | M | | ID 1/2
| Code defining the characteristic of a level in a hierarchical structure
| Refer to 004010 Data Element Dictionary for acceptable code values.
| HL04 | 736 | Hierarchical Child Code | O | | ID 1/1
| Code indicating if there are hierarchical child data segments subordinate to the level being described
| Refer to 004010 Data Element Dictionary for acceptable code values.

	Segment:	LIN Item Identification
	Position:	294
	Loop:	HL        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To specify basic item identification data
	Syntax Notes:	1	If either LIN04 or LIN05 is present, then the other is required.
		2	If either LIN06 or LIN07 is present, then the other is required.
		3	If either LIN08 or LIN09 is present, then the other is required.
		4	If either LIN10 or LIN11 is present, then the other is required.
		5	If either LIN12 or LIN13 is present, then the other is required.
		6	If either LIN14 or LIN15 is present, then the other is required.
		7	If either LIN16 or LIN17 is present, then the other is required.
		8	If either LIN18 or LIN19 is present, then the other is required.
		9	If either LIN20 or LIN21 is present, then the other is required.
		10	If either LIN22 or LIN23 is present, then the other is required.
		11	If either LIN24 or LIN25 is present, then the other is required.
		12	If either LIN26 or LIN27 is present, then the other is required.
		13	If either LIN28 or LIN29 is present, then the other is required.
		14	If either LIN30 or LIN31 is present, then the other is required.
	Semantic Notes:	1	LIN01 is the line item identification
	Comments:	1	See the Data Dictionary for a complete list of IDs.
		2	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.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
| LIN01 | 350 | Assigned Identification | O | | AN 1/20
| Alphanumeric characters assigned for differentiation within a transaction set
M | LIN02 | 235 | Product/Service ID Qualifier | M | | ID 2/2
| Code identifying the type/source of the descriptive number used in Product/Service ID (234)
| Refer to 004010 Data Element Dictionary for acceptable code values.
M | LIN03 | 234 | Product/Service ID | M | | AN 1/48
| Identifying number for a product or service
| LIN04 | 235 | Product/Service ID Qualifier | X | | ID 2/2
| Code identifying the type/source of the descriptive number used in Product/Service ID (234)
| Refer to 004010 Data Element Dictionary for acceptable code values.
| LIN05 | 234 | Product/Service ID | X | | AN 1/48
| Identifying number for a product or service
| LIN06 | 235 | Product/Service ID Qualifier | X | | ID 2/2
| Code identifying the type/source of the descriptive number used in Product/Service ID (234)
| Refer to 004010 Data Element Dictionary for acceptable code values.
| LIN07 | 234 | Product/Service ID | X | | AN 1/48
| Identifying number for a product or service
| LIN08 | 235 | Product/Service ID Qualifier | X | | ID 2/2
| Code identifying the type/source of the descriptive number used in Product/Service ID (234)
| Refer to 004010 Data Element Dictionary for acceptable code values.
| LIN09 | 234 | Product/Service ID | X | | AN 1/48
| Identifying number for a product or service
| LIN10 | 235 | Product/Service ID Qualifier | X | | ID 2/2
| Code identifying the type/source of the descriptive number used in Product/Service ID (234)
| Refer to 004010 Data Element Dictionary for acceptable code values.
| LIN11 | 234 | Product/Service ID | X | | AN 1/48
| Identifying number for a product or service
| LIN12 | 235 | Product/Service ID Qualifier | X | | ID 2/2
| Code identifying the type/source of the descriptive number used in Product/Service ID (234)
| Refer to 004010 Data Element Dictionary for acceptable code values.
| LIN13 | 234 | Product/Service ID | X | | AN 1/48
| Identifying number for a product or service
| LIN14 | 235 | Product/Service ID Qualifier | X | | ID 2/2
| Code identifying the type/source of the descriptive number used in Product/Service ID (234)
| Refer to 004010 Data Element Dictionary for acceptable code values.
| LIN15 | 234 | Product/Service ID | X | | AN 1/48
| Identifying number for a product or service
| LIN16 | 235 | Product/Service ID Qualifier | X | | ID 2/2
| Code identifying the type/source of the descriptive number used in Product/Service ID (234)
| Refer to 004010 Data Element Dictionary for acceptable code values.
| LIN17 | 234 | Product/Service ID | X | | AN 1/48
| Identifying number for a product or service
| LIN18 | 235 | Product/Service ID Qualifier | X | | ID 2/2
| Code identifying the type/source of the descriptive number used in Product/Service ID (234)
| Refer to 004010 Data Element Dictionary for acceptable code values.
| LIN19 | 234 | Product/Service ID | X | | AN 1/48
| Identifying number for a product or service
| LIN20 | 235 | Product/Service ID Qualifier | X | | ID 2/2
| Code identifying the type/source of the descriptive number used in Product/Service ID (234)
| Refer to 004010 Data Element Dictionary for acceptable code values.
| LIN21 | 234 | Product/Service ID | X | | AN 1/48
| Identifying number for a product or service
| LIN22 | 235 | Product/Service ID Qualifier | X | | ID 2/2
| Code identifying the type/source of the descriptive number used in Product/Service ID (234)
| Refer to 004010 Data Element Dictionary for acceptable code values.
| LIN23 | 234 | Product/Service ID | X | | AN 1/48
| Identifying number for a product or service
| LIN24 | 235 | Product/Service ID Qualifier | X | | ID 2/2
| Code identifying the type/source of the descriptive number used in Product/Service ID (234)
| Refer to 004010 Data Element Dictionary for acceptable code values.
| LIN25 | 234 | Product/Service ID | X | | AN 1/48
| Identifying number for a product or service
| LIN26 | 235 | Product/Service ID Qualifier | X | | ID 2/2
| Code identifying the type/source of the descriptive number used in Product/Service ID (234)
| Refer to 004010 Data Element Dictionary for acceptable code values.
| LIN27 | 234 | Product/Service ID | X | | AN 1/48
| Identifying number for a product or service
| LIN28 | 235 | Product/Service ID Qualifier | X | | ID 2/2
| Code identifying the type/source of the descriptive number used in Product/Service ID (234)
| Refer to 004010 Data Element Dictionary for acceptable code values.
| LIN29 | 234 | Product/Service ID | X | | AN 1/48
| Identifying number for a product or service
| LIN30 | 235 | Product/Service ID Qualifier | X | | ID 2/2
| Code identifying the type/source of the descriptive number used in Product/Service ID (234)
| Refer to 004010 Data Element Dictionary for acceptable code values.
| LIN31 | 234 | Product/Service ID | X | | AN 1/48
| Identifying number for a product or service

	Segment:	SN1 Item Detail (Shipment)
	Position:	295
	Loop:	HL        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To specify line-item detail relative to shipment
	Syntax Notes:	1	If either SN105 or SN106 is present, then the other is required.
	Semantic Notes:	1	SN101 is the ship notice line-item identification.
	Comments:	1	SN103 defines the unit of measurement for both SN102 and SN104.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
| SN101 | 350 | Assigned Identification | O | | AN 1/20
| Alphanumeric characters assigned for differentiation within a transaction set
M | SN102 | 382 | Number of Units Shipped | M | | R 1/10
| Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
M | SN103 | 355 | Unit or Basis for Measurement Code | M | | ID 2/2
| Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
| Refer to 004010 Data Element Dictionary for acceptable code values.
| SN104 | 646 | Quantity Shipped to Date | O | | R 1/15
| Number of units shipped to date
| SN105 | 330 | Quantity Ordered | X | | R 1/15
| Quantity ordered
| SN106 | 355 | Unit or Basis for Measurement Code | X | | ID 2/2
| Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
| Refer to 004010 Data Element Dictionary for acceptable code values.
| SN107 | 728 | Returnable Container Load Make-Up Code | O | | ID 1/2
| Code identifying the load make-up of the returnable containers in the shipment
| Refer to 004010 Data Element Dictionary for acceptable code values.
| SN108 | 668 | Line Item Status Code | O | | ID 2/2
| Code specifying the action taken by the seller on a line item requested by the buyer
| Refer to 004010 Data Element Dictionary for acceptable code values.

	Segment:	CTT Transaction Totals
	Position:	010
	Loop:
	Level:	Summary
	Usage:	Optional
	Max Use:	1
	Purpose:	To transmit a hash total for a specific element in the transaction set
	Syntax Notes:	1	If either CTT03 or CTT04 is present, then the other is required.
		2	If either CTT05 or CTT06 is present, then the other is required.
	Semantic Notes:
	Comments:	1	This segment is intended to provide hash totals to validate transaction completeness and correctness.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | CTT01 | 354 | Number of Line Items | M | | N0 1/6
| Total number of line items in the transaction set

	Segment:	SE Transaction Set Trailer
	Position:	020
	Loop:
	Level:	Summary
	Usage:	Must Use
	Max Use:	1
	Purpose:	To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
	Syntax Notes:
	Semantic Notes:
	Comments:	1	SE is the last segment of each transaction set.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M | SE01 | 96 | Number of Included Segments | M | | N0 1/10
| Total number of segments included in a transaction set including ST and SE segments
M | SE02 | 329 | Transaction Set Control Number | M | | AN 4/9
| Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set