Target 856 - DVS Ship Notice Manifest Specifications

Modified on Tue, May 26 at 9:45 AM

**These specifications are a base model. All customers are responsible for ensuring their map or EDI is compliant with their trading partner's most current specifications.

Target Corporation

EDI Guideline

Domestic

Target.com DVS Vendor

856

Ship Notice Manifest

Version 4010

Revised: July 2022

Change Log

Date	Change	Comments
July 2022	TD503 TD505 HL03 MAN	Updated note. Added Routing codes. Removed code ‘9’. Updated note.
January 2022	Revised note verbiage for N104
November 2020	Converted from .pdf to .docx file format	Changes to file format only – no change to content.
June 2019	Revised note for N104	“May start with a ‘T’” verbiage removed
September 2018	Updated codes to the TD505
June 2013	Updated codes to the TD505
April 2013	Added verbiage to the N104 regarding EDCs
March 2012	Made N1 segment mandatory
October 2011	Updated the EDC/Warehouse ID in the N1 segment example	Changed from TAFP to TTTT
September 2011	Updated the notes for codes M and U in TD504
July 2011	Updated the TD504 notes
February 2011	Remove ZZZZ structure option	Target.com will no longer accept the ZZZZ structure
February 2011	Added NS and SS to the TD512
February 2011	Added codes MP, PR and MI to TD505
February 2011	TD501 and TD511 were added for in transit days.	TD510 will contain qualifier SD. TD511 will contain the in transit days.

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.

Notes:

Vendors should NOT use the 856 to communicate rejected items by use of a zero quantity in the SN1. The 855 must be used to indicate rejected items. The 856 is to be used to indicate items being shipped.

Please Note:

Only one ship ID may be sent per 856 transaction set.

Multiple 856 transaction sets may be sent on one ISA.

Heading:

Pos. Seg. Req. Loop Notes and

No. ID Name Des. Max.Use Repeat Comments

010

Transaction Set Header

020

BSN

Beginning Segment for Ship Notice

Detail:

Pos. Seg. Req. Loop Notes and

No. ID Name Des. Max.Use Repeat Comments

LOOP ID - HLS

200000

010

Hierarchical Level - Shipment

Must Use

120

TD5

Carrier Details (Routing Sequence/Transit Time)

Must Use

150

REF

Reference Identification

Must Use

200

DTM

Date/Time Reference

LOOP ID - N1

200

Must Use

220

Name

LOOP ID - HLO

200000

010

Hierarchical Level - Order

Must Use

050

PRF

Purchase Order Reference

LOOP ID - HLI

200000

010

Hierarchical Level - Item

Must Use

020

LIN

Item Identification

Must Use

030

SN1

Item Detail (Shipment)

070

PID

Product/Item Description

200

Must Use

190

MAN

Marks and Numbers

Summary:

Pos. Seg. Req. Loop Notes and

No. ID Name Des. Max.Use Repeat Comments

010

CTT

Transaction Totals

020

Transaction Set Trailer

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

***********************

Sample ST Segment

______________________

ST*856*0001

Target Corporation requires a separate transaction set for each ship to location. A transaction set starts with a ST segment and ends with a SE segment.

************************

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
				856	Ship Notice/Manifest
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:

************************

Sample BSN Segment

______________________

BSN*00*234567*20090801*0142*0004

************************

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
				14	Advance Notification
M	BSN02	396	Shipment Identification			M	AN 2/30
			A unique control number assigned by the original shipper to identify a specific shipment
			Note: EDI Standards state that this should be a unique number. Unique per vendor in a given year.
M	BSN03	373	Date			M	DT 8/8
			Date expressed as CCYYMMDD
			Date this shipment transaction was created
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)
M	BSN05	1005	Hierarchical Structure Code			M	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
				0004	Shipment, Order, Item

Segment: HL Hierarchical Level - Shipment

Position: 010

Loop: HLS 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:

************************

Sample HL (Shipment Level) Segment

__________________________

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
	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
			Not used in the shipment level.
M	HL03	735	Hierarchical Level Code			M	ID 1/2
			Code defining the characteristic of a level in a hierarchical structure
				S	Shipment

Segment: TD5 Carrier Details (Routing Sequence/Transit Time)

Position: 120

Loop: HLS 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:

Information for this segment should be returned as received in TD5 on the 850.

************************

Sample TD5 Segment

_______________________

TD5*B*2*UPSN*U*NS*****SD*3*G2

***********************

Data Element Summary

Ref. Data

Des. Element Name Attributes

M	TD501	133	Routing Sequence Code			M	ID 1/2
			Code describing the relationship of a carrier to a specific shipment movement
				B	Origin/Delivery Carrier (Any Mode)
M	TD502	66	Identification Code Qualifier			M	ID 1/2
			Code designating the system/method of code structure used for Identification Code (67)
				2	Standard Carrier Alpha Code (SCAC)
M	TD503	67	Identification Code			M	AN 4/80
			Code identifying a party or other code
			SCAC Code See list of DVS Shipping Setup \| EDI Routing Codes on Partners Online.
M	TD504	91	Transportation Method/Type Code			M	ID 1/2
			Code specifying the method or type of transportation for the shipment
			The mode of transportation determines both the transportation method type code (TD504) and the REF segment qualifier (REF01). The mode of transportation determines the transportation method type code (TD504). ____________________________________ Mode of : TD504 Transportation ____________________________________ Air A _________________ ___________________ TL or LTL M ___________________________________ Private Parcel U
				A	Air
				M	Motor (Common Carrier)
					Used for larger quantity shipments Truckload or LTL. SCAC code EFWW should be used with "M".
				U	Private Parcel Service
					Parcel Package used for small package or small quantities. SCAC codes UPSN, UPSM, USPS, FDE, FDEG and FXSP should be used with "U".
Must Use	TD505	387	Routing			X	AN 1/35
			Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
			Use only codes from this list. Send the code only. The description is present for information only. Code Description Transport Type NS No Signature Required UPS / FedEx SG Signature Required UPS / FedEx SP SurePost UPS TD To the Door LTL IS Through the Door with Signature Required LTL RS Room of Choice with Signature Required LTL WS White Glove with Signature Required LTL AS White Glove Assembly with Signature Required LTL MI Mail Innovations/MIP/MM UPS NDS Next Day Air with No Signature Required UPS/FedEx NDSS Next Day Air with Signature Required UPS/FedEx HD Home Delivery with No Signatured Required FedEx HDS Home Delivery with Signature Required FedEx SMP SmartPost with No Signature Required FedEx SMPU Signature FedEx PON Priority Overnight FedEx PONS Priority Signature FedEx
	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
			Not used
	TD507	309	Location Qualifier			O	ID 1/2
			Code identifying type of location
			Not used
	TD508	310	Location Identifier			X	AN 1/30
			Code which identifies a specific location
			Not used
	TD509	731	Transit Direction Code			O	ID 2/2
			The point of origin and point of direction
			Not used
	TD510	732	Transit Time Direction Qualifier			O	ID 2/2
			Code specifying the value of time used to measure the transit time
				SD	Surface Days
	TD511	733	Transit Time			X	R 1/4
			The numeric amount of transit time
			Time in transit in days.
Must Use	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
			A code must be sent. Use only codes listed. Unless previously negotiated with Target.com, DS will represent LTL and G2, ND, and SC will represent UPS/FedEx.
				DS	Door Service
				G2	Standard Service
				ND	Next Day Air
					Delivery during business day hours of next business day
				NS	Not Served
					****NOTE: this value will be used to indicate Next Day Saturday*****
				PO	P.O. Box/Zip Code
				SC	Second Day Air
					Delivery during business day hours no later than second business day
				SS	2 Day Saturday

Segment: REF Reference Identification

Position: 150

Loop: HLS 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:

************************

Sample REF Segment

_______________________

REF*VR*12345

************************

Data Element Summary

Ref. Data

Des. Element Name Attributes

M	REF01	128	Reference Identification Qualifier			M	ID 2/2
			Code qualifying the Reference Identification
				VR	Vendor ID Number
M	REF02	127	Reference Identification			M	AN 1/30
			Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
			Target.com assigned vendor number (minimum of 4 digits).

Segment: DTM Date/Time Reference

Position: 200

Loop: HLS 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:

**************************

Sample DTM Segment

____________________

DTM*011*20090801

**************************

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	DTM01	374	Date/Time Qualifier			O	ID 3/3
			Code specifying type of date or time, or both date and time
				011	Shipped
Must Use	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:

*********************

Sample N1 Segment

___________________

N1*SF**93*TTTT

*********************

Data Element Summary

Ref. Data

Des. Element Name Attributes

M	N101	98	Entity Identifier Code			M	ID 2/2
			Code identifying an organizational entity, a physical location, property or an individual
				SF	Ship From
	N102	93	Name			O	AN 1/35
			Free-form name
M	N103	66	Identification Code Qualifier			M	ID 1/2
			Code designating the system/method of code structure used for Identification Code (67)
				93	Code assigned by the organization originating the transaction set
M	N104	67	Identification Code			M	AN 2/17
			Code identifying a party or other code
			A code which identifies a vendor's specific Warehouse location. A minimum of 4 characters, an EDC is an alpha and/or numeric code that may start with a 'T'. Alpha characters must be sent in upper case.

Segment: HL Hierarchical Level - Order

Position: 010

Loop: HLO 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.

3 HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

5 HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

Notes:

************************

Sample HL (Order Level) Segment

_______________________

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
M	HL02	734	Hierarchical Parent ID Number			M	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: HLO 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:

************************

Sample PRF Segment

_______________________

PRF*1234567890

************************

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
			Contains the Release ID. This value will be 10 digits.

Segment: HL Hierarchical Level - Item

Position: 010

Loop: HLI 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.

3 HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

5 HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

Notes:

*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.

************************

Sample HL (Item Level) Segment

_______________________

HL*3*2*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
M	HL02	734	Hierarchical Parent ID Number			M	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: HLI 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:

**********************

Sample LIN Segment

______________________

LIN*1*SK*821927~

Note: The manufacturer style number is required to be sent on the 856.

LIN01 cannot be duplicated in the 856 - only one line 1, line 2, etc.

Vendors should not use the 856 to communicate rejected items by use of a zero quantity in the SN1. The 855 must be used to indicate rejected items. The 856 is to be used to indicate items being shipped.

If a line item is not being shipped, do NOT send an LIN and SN1 for that item.

************************

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	LIN01	350	Assigned Identification			O	AN 1/20
			Alphanumeric characters assigned for differentiation within a transaction set
			LIN01 must reflect what is received in PO101 of the 850
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)
				EN	European Article Number (EAN) (2-5-5-1)
				EO	EAN/UCC 8
				IB	International Standard Book Number (ISBN)
				IN	Buyer's Item Number
				SK	Stock Keeping Unit (SKU)
				UA	U.P.C./EAN Case Code (2-5-5)
				UK	U.P.C./EAN Shipping Container Code (1-2-5-5-1)
					A 14-digit code that uniquely identifies the manufacturer's shipping unit, including the packaging indicator and check digit; the first digit is the packaging indicator, the next two digits are the number system characters, the next five digits are the manufacturer ID number, the second five digits are the item code, and the final digit is the check digit
				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
			When LIN02 = SK, this contains the Manufacturer's style number When LIN02 = IN, this contains the Target.com item number (6 - 8 digits) When LIN02 = UP, this contains the UPC (12 digits) When LIN02 = EO, this value is the 8 digit EAN When LIN02 = EN, this value is the 13 digit EAN When LIN02= IB, this value is the ISBN When LIN02 = UK, this value is the 14 digit barcode
	LIN04	235	Product/Service ID Qualifier			O	ID 2/2
			Code identifying the type/source of the descriptive number used in Product/Service ID (234)
				EN	European Article Number (EAN) (2-5-5-1)
				EO	EAN/UCC 8
				IB	International Standard Book Number (ISBN)
				IN	Buyer's Item Number
				SK	Stock Keeping Unit (SKU)
				UA	U.P.C./EAN Case Code (2-5-5)
				UK	U.P.C./EAN Shipping Container Code (1-2-5-5-1)
					A 14-digit code that uniquely identifies the manufacturer's shipping unit, including the packaging indicator and check digit; the first digit is the packaging indicator, the next two digits are the number system characters, the next five digits are the manufacturer ID number, the second five digits are the item code, and the final digit is the check digit
				UP	U.P.C. Consumer Package Code (1-5-5-1)
	LIN05	234	Product/Service ID			X	AN 1/48
			Identifying number for a product or service
			When LIN02 = SK, this contains the Manufacturer's style number When LIN04 = IN, this contains the Target.com item number(6 - 8 digits) When LIN04 = UP, this contains the UPC (12 digits) When LIN04 = EO, this value is the 8 digit EAN When LIN04 = EN, this value is the 13 digit EAN When LIN04= IB, this value is the ISBN When LIN04 = UK, this value is the 14 digit barcode
	LIN06	235	Product/Service ID Qualifier			O	ID 2/2
			Code identifying the type/source of the descriptive number used in Product/Service ID (234)
				EN	European Article Number (EAN) (2-5-5-1)
				EO	EAN/UCC 8
				IB	International Standard Book Number (ISBN)
				IN	Buyer's Item Number
				SK	Stock Keeping Unit (SKU)
				UA	U.P.C./EAN Case Code (2-5-5)
				UK	U.P.C./EAN Shipping Container Code (1-2-5-5-1)
					A 14-digit code that uniquely identifies the manufacturer's shipping unit, including the packaging indicator and check digit; the first digit is the packaging indicator, the next two digits are the number system characters, the next five digits are the manufacturer ID number, the second five digits are the item code, and the final digit is the check digit
				UP	U.P.C. Consumer Package Code (1-5-5-1)
	LIN07	234	Product/Service ID			X	AN 1/48
			Identifying number for a product or service
			When LIN02 = SK, this contains the Manufacturer's style number When LIN06 = IN, this contains the Target.com item number(6 - 8 digits) When LIN06 = UP, this contains the UPC (12 digits) When LIN06 = EO, this value is the 8 digit EAN When LIN06 = EN, this value is the 13 digit EAN When LIN06= IB, this value is the ISBN When LIN06 = UK, this value is the 14 digit barcode

Segment: SN1 Item Detail (Shipment)

Position: 030

Loop: HLI 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:

*************************

Sample SN1 Segment

_______________________

SN1**2*EA

If a line item is not being shipped, do NOT send an LIN and SN1 for that item.

************************

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
			Not used
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
			This quantity must be greater than zero. A quantity of zero will not be accepted by Target.com.
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
	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
				EA	Each

Segment: PID Product/Item Description

Position: 070

Loop: HLI Mandatory

Level: Detail

Usage: Optional

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:

**************************

PID Segment Example

_____________________

PID*F****Description

NOTE: The PID segment is optional, but for some vendors it needs to be included for packing slip printing.

***************************

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
	PID02	750	Product/Process Characteristic Code			O	ID 2/3
			Code identifying the general class of a product or process characteristic
			Not used
	PID03	559	Agency Qualifier Code			X	ID 2/2
			Code identifying the agency assigning the code values
			Not used
	PID04	751	Product Description Code			X	AN 1/12
			A code from an industry code list which provides specific data about a product characteristic
			Not used
Must Use	PID05	352	Description			X	AN 1/80
			A free-form description to clarify the related data elements and their content
			Product description

Segment: MAN Marks and Numbers

Position: 190

Loop: HLI 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:

***************************

Sample MAN Segments

______________________

MAN*ZZ*123456789876751

In most instances there will be only one MAN segment per line.

There could be multiple if the item shipped in separate cartons or if there are multiple items on one line that shipped in separate cartons.

If multiple MAN segments are needed for 1 line number, these can be listed in the next segment below the first MAN segment.

For example, where a lamp base and shade are considered one item and the lamp base is in one carton and the lamp shade in a second.

****************************

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)
				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
			Tracking Number

Segment: CTT Transaction Totals

Position: 010

Loop:

Level: Summary

Usage: Mandatory

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:

************************

Sample CTT Segment

______________________

CTT*4

************************

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
			The number of HL segments present 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:

************************

Sample SE Segment

_____________________

SE*10*0002

************************

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