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									

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 Level)	M	1		c1							
	030	SN1	Item Detail (Shipment)	O	1									
	110	TD1	Carrier Details (Quantity and Weight)	O	20									
Must Use	120	TD5	Carrier Details (Routing Sequence/Transit Time)	O	12									
Must Use	130	TD3	Carrier Details (Equipment)	O	12									
Must Use	150	REF	Reference Identification	O	>1									
Must Use	200	DTM	Date/Time Reference	O	10									
			LOOP ID - N1			200								
Must Use	220	N1	Name	O	1									
														
			LOOP ID - HL			200000								
M	010	HL	Hierarchical Level(Order Level)	M	1		c2							
Must Use	050	PRF	Purchase Order Reference	O	1									
														
			LOOP ID - HL			200000								
M	010	HL	Hierarchical Level(Pack Level)	M	1		c3							
Must Use	190	MAN	Marks and Numbers	O	>1									
														
			LOOP ID - HL			200000								
M	010	HL	Hierarchical Level(Item Level)	M	1		c4							
Must Use	020	LIN	Item Identification	O	1									
Must Use	030	SN1	Item Detail (Shipment/Line Level)	O	1									
Must Use	060	PO4	Item Physical Details	O	1									
Must Use	070	PID	Product/Item Description	O	200									
Must Use	110	TD1	Carrier Details (Quantity and Weight)	O	20									

Summary:

	Pos.	Seg.		Req.		Loop	Notes and
	No.	ID	Name	Des.	Max.Use	Repeat	Comments	
Must Use	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.
2.	The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
3.	The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
4.	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:	Mandatory
	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:
Notes:		Example: ST*856*000000004	

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:	Mandatory
	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.
Notes:		Example: BSN*00*1828458823*19980615*1454*0001	

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)	
	BSN05	1005	Hierarchical Structure Code	O		ID 4/4	
	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	

	Segment:	HL Hierarchical Level(Shipment Level)
	Position:	010
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Mandatory
	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.
Notes:		Example: HL*1**S	

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

	Segment:	SN1 Item Detail (Shipment)
	Position:	030
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To specify line-item detail relative to shipment
		(total number of units shipped in the 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.
Notes:		Example: SN1**9*EA	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
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	
 	EA		Each	

	Segment:	TD1 Carrier Details (Quantity and Weight)
	Position:	110
	Loop:	HL        Mandatory
	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:
Notes:		Example: TD1**60	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
	TD102	80	Lading Quantity	X		N0 1/7	
	Number of units (pieces) of the lading commodity	
	TD106	187	Weight Qualifier	O		ID 1/2	
	Code defining the type of weight	
 	G		Gross Weight	
	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	
 	LB		Pound	

	Segment:	TD5 Carrier Details (Routing Sequence/Transit Time)
	Position:	120
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional (Must Use)
	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.
Notes:		Example: TD5**2*WATK	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
	TD502	66	Identification Code Qualifier	X		ID 1/2	
	Code designating the system/method of code structure used for Identification Code (67)	
 	2		Standard Carrier Alpha Code (SCAC)	
	TD503	67	Identification Code	X		AN 2/80	
	Code identifying a party or other code	

	Segment:	TD3 Carrier Details (Equipment)
	Position:	130
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional (Must Use)
	Max Use:	12
	Purpose:	To specify transportation details relating to the equipment used by the carrier
	Syntax Notes:	1	Only one of TD301 or TD310 may be present.
		2	If TD302 is present, then TD303 is required.
		3	If TD304 is present, then TD305 is required.
		4	If either TD305 or TD306 is present, then the other is required.
	Semantic Notes:
	Comments:
Notes:		Example: TD3*TL**12345678	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
	TD301	40	Equipment Description Code	X		ID 2/2	
	Code identifying type of equipment used for shipment	
 	TL		Trailer (not otherwise specified)	
	TD303	207	Equipment Number	X		AN 1/10	
	Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)	

	Segment:	REF Reference Identification
	Position:	150
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional (Must Use)
	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:
Notes:		(Required)Example: REF*BM*BILLOFLADINGNUMBER
(Optional) Example: REF*CN*PROBILLNUMBER
(Optional) Example: REF*PK*PACKINGLISTNUMBER	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	BM		Bill of Lading Number	
 	CN		Carrier's Reference Number (PRO/Invoice)	
	Probill Number	
 	PK		Packing List 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:	DTM Date/Time Reference
	Position:	200
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional (Must Use)
	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:
Notes:		(Required)Example: DTM*067*19980715
(Optional) Example: DTM*011*19980710
(Optional) Example: DTM*371*19980716	

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	
	Date product shipped by the vendor(assigned by the vendor)	
 	067		Current Schedule Delivery	
	Scheduled delivery date assigned by Pep Boys on the purchase order	
 	371		Estimated Arrival Date	
	Estimated arrival date of product at the Pep Boys location(assigned by the vendor) 	
	DTM02	373	Date	X		DT 8/8	
	Date expressed as CCYYMMDD	

	Segment:	N1 Name
	Position:	220
	Loop:	N1        Optional (Must Use)
	Level:	Detail
	Usage:	Optional (Must Use)
	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.
Notes:		Example: N1*ST**92*14011	

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	
 	ST		Ship To	
	N103	66	Identification Code Qualifier	X		ID 1/2	
	Code designating the system/method of code structure used for Identification Code (67)	
 	92		Assigned by Buyer or Buyer's Agent	
	N104	67	Identification Code	X		AN 2/80	
	Code identifying a party or other code	

	Segment:	HL Hierarchical Level(Order Level)
	Position:	010
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Mandatory
	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.
Notes:		Example: HL*2*1*O	

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	

	Segment:	PRF Purchase Order Reference
	Position:	050
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional (Must Use)
	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:
Notes:		Example: PRF*S3482451	

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	

	Segment:	HL Hierarchical Level(Pack Level)
	Position:	010
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Mandatory
	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.
Notes:		Example: HL*3*2*P	

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

	Segment:	MAN Marks and Numbers
	Position:	190
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional (Must Use)
	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.
Notes:		Example: MAN*GM*00007940530000190343	

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)	
 	AA		SSCC-18	
 	GM		SSCC-18 and Application Identifier	
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 Level)
	Position:	010
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Mandatory
	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.
Notes:		Example: HL*4*3*I	

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	

	Segment:	LIN Item Identification
	Position:	020
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional (Must Use)
	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.
Notes:		Example: LIN**UP*0794053018326*IN*8400211	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
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)	
 	UP		U.P.C. Consumer Package Code (1-5-5-1)	
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)	
 	IN		Buyer's Item Number	
	Pep Boys SKU Number	
	LIN05	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	

	Segment:	SN1 Item Detail (Shipment/Line Level)
	Position:	030
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional (Must Use)
	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.
Notes:		Example: SN1**5*EA	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
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	
 	EA		Each	

	Segment:	PO4 Item Physical Details
	Position:	060
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional (Must Use)
	Max Use:	1
	Purpose:	To specify the physical qualities, packaging, weights, and dimensions relating to the item
	Syntax Notes:	1	If either PO402 or PO403 is present, then the other is required.
		2	If PO405 is present, then PO406 is required.
		3	If either PO406 or PO407 is present, then the other is required.
		4	If either PO408 or PO409 is present, then the other is required.
		5	If PO410 is present, then PO413 is required.
		6	If PO411 is present, then PO413 is required.
		7	If PO412 is present, then PO413 is required.
		8	If PO413 is present, then at least one of PO410 PO411 or PO412 is required.
		9	If PO417 is present, then PO416 is required.
		10	If PO418 is present, then PO404 is required.
	Semantic Notes:	1	PO415 is used to indicate the relative layer of this package or range of packages within the layers of packaging. Relative Position 1 (value R1) is the innermost package.
		2	PO416 is the package identifier or the beginning package identifier in a range of identifiers.
		3	PO417 is the ending package identifier in a range of identifiers.
		4	PO418 is the number of packages in this layer.
	Comments:	1	PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack (PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the carton contains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element 357 = "12"; Data element 355 = "OZ".
		2	PO413 defines the unit of measure for PO410, PO411, and PO412.
Notes:		Example: PO4*2	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
	PO401	356	Pack	O		N0 1/6	
	The number of inner containers, or number of eaches if there are no inner containers, per outer container	

	Segment:	PID Product/Item Description
	Position:	070
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional (Must Use)
	Max Use:	200
	Purpose:	To describe a product or process in coded or free-form format
	Syntax Notes:	1	If PID04 is present, then PID03 is required.
		2	At least one of PID04 or PID05 is required.
		3	If PID07 is present, then PID03 is required.
		4	If PID08 is present, then PID04 is required.
		5	If PID09 is present, then PID05 is required.
	Semantic Notes:	1	Use PID03 to indicate the organization that publishes the code list being referred to.
		2	PID04 should be used for industry-specific product description codes.
		3	PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the specified attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate.
		4	PID09 is used to identify the language being used in PID05.
	Comments:	1	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.
		2	Use PID06 when necessary to refer to the product surface or layer being described in the segment.
		3	PID07 specifies the individual code list of the agency specified in PID03.
Notes:		Example: PID*F****PART DESCRIPTION	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	PID01	349	Item Description Type	M		ID 1/1	
	Code indicating the format of a description	
 	F		Free-form	
	PID05	352	Description	X		AN 1/80	
	A free-form description to clarify the related data elements and their content	

	Segment:	TD1 Carrier Details (Quantity and Weight)
	Position:	110
	Loop:	HL        Mandatory
	Level:	Detail
	Usage:	Optional (Must Use)
	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:
Notes:		Example: TD1**57****G*437*LB	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
	TD102	80	Lading Quantity	X		N0 1/7	
	Number of units (pieces) of the lading commodity	
	TD106	187	Weight Qualifier	O		ID 1/2	
	Code defining the type of weight	
 	G		Gross Weight	
	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	
 	LB		Pound	

	Segment:	CTT Transaction Totals
	Position:	010
	Loop:
	Level:	Summary
	Usage:	Optional (Must Use)
	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.
Notes:		Example: CTT*25	

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:	Mandatory
	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.
Notes:		Example: SE*42*000000004	

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