**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.
EDI Guideline
Domestic
856
Ship Notice Manifest
Direct Store Delivery Only
Version 4010
Revised: April 2024
Change Log
Date | Change | Comments |
April 2024 | REF | Updated segment comment verbiage. |
September 2022 | MAN MAN02 | Added verbiage to segment note. |
July 2022 | PO4 | Added verbiage to segment note. |
November 2020 | Converted from .pdf to .docx file format | Changes to file format only – no change to content. |
September 2017 | Added new PO format to the PRF segment.
| Starting in Dec 2017 Target will be phasing in a new PO format: 12345678901-1234 |
| Added ‘IN’ as a new item identifier in the LIN and SLN segments. |
|
856 Ship Notice/Manifest (Version 4010) for Direct To Store Delivery - Target Corporation **You must contact Target Supplier Performance Management before mapping via the Request Support form on Partners Online. Select 'EDI 856 and Carton Markings' as the Reason for Support.**
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:
An 856 transmission is to be sent within 60 minutes of the trailer closing at your shipping dock or at the time shipment is released to the carrier.
Target Corporation requires a separate transaction set for each ship to store location found in the N104 segment of the EDI 850 document. (A transaction set starts with a ST segment and ends with a SE segment). |
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 - HLS |
|
| 200000 |
|
|
|
|
|
|
|
M | 010 | HL | Hierarchical Level - Shipment | M | 1 |
| c1 |
|
|
|
|
|
|
Must Use | 120 | TD5 | Carrier Details (Routing Sequence/Transit Time) | 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 - HLO |
|
| 200000 |
|
|
|
|
|
|
|
M | 010 | HL | Hierarchical Level - Order | M | 1 |
|
|
|
|
|
|
|
|
Must Use | 050 | PRF | Purchase Order Reference | O | 1 |
|
|
|
|
|
|
|
|
Must Use | 110 | TD1 | Carrier Details (Quantity and Weight) | O | 20 |
|
|
|
|
|
|
|
|
|
|
| LOOP ID - HLT |
|
| 200000 |
|
|
|
|
|
|
|
| 010 | HL | Hierarchical Level - Tare | C | 1 |
|
|
|
|
|
|
|
|
| 190 | MAN | Marks and Numbers | C | >1 |
|
|
|
|
|
|
|
|
|
|
| LOOP ID - HLP |
|
| 200000 |
|
|
|
|
|
|
|
| 010 | HL | Hierarchical Level - Pack | C | 1 |
|
|
|
|
|
|
|
|
| 190 | MAN | Marks and Numbers | C | >1 |
|
|
|
|
|
|
|
|
|
|
| LOOP ID - HLI |
|
| 200000 |
|
|
|
|
|
|
|
M | 010 | HL | Hierarchical Level - Item | M | 1 |
|
|
|
|
|
|
|
|
Must Use | 020 | LIN | Item Identification | O | 1 |
|
|
|
|
|
|
|
|
Must Use | 030 | SN1 | Item Detail (Shipment) | O | 1 |
|
|
|
|
|
|
|
|
| 040 | SLN | Subline Item Detail | O | 1000 |
|
|
|
|
|
|
|
|
| 060 | PO4 | Item Physical Details | C | 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Summary:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
M | 010 | CTT | Transaction Totals | M | 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: 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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ 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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ Sample BSN Segment ______________________ BSN*00*234567*20040601*0142*0001 (Pick Pack Format) BSN*00*345678*20040605*1234*0002 (Standard Pack Format) ************************ |
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 |
| |||||||
| 05 |
| Replace |
| |||||||
| Used when sending a full re-transmission. |
| |||||||||
| 25 |
| Incremental |
| |||||||
| Used when sending a partial re-transmission. |
| |||||||||
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. Target Corporation applications have been written based on that. This number will be used to differentiate multiple 856s received from a supplier. This number should be different than the Purchase Order or Bill of Lading number. |
| |||||||||
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) |
| |||||||||
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 |
| |||||||||
| 0001 |
| Shipment, Order, Packaging, Item |
| |||||||
| Pick & Pack Format |
| |||||||||
| 0002 |
| Shipment, Order, Item, Packaging |
| |||||||
| Standard Pack Format |
| |||||||||
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: |
| *Warning: Segment includes critical data elements. Pease ensure accuracy to avoid document suspension and/or loss of data.
************************ 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 by the Retail Industry |
| ||||||||
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: |
| ************************ Sample TD5 Segment ___________________________ TD5*B*2*MIIW*M ************************ |
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 |
| ||||||||
| Target Corporation requires a 4-character alpha code managed by the National Motor Freight Traffic Association. See notes above. |
| ||||||||
M | TD504 | 91 | Transportation Method/Type Code | M |
| ID 1/2 | ||||
| Code specifying the method or type of transportation for the shipment |
| ||||||||
| M |
| Motor (Common Carrier) |
| ||||||
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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ Target Corporation requires: A UNIQUE Bill of Lading (BOL) number for each shipment.
Target requires the use of the GS1 US (VICS) standard 17-digit Bill of Lading number format to support stores' receipt operations.
Sample REF Segment _______________________ REF*BM*06141411234567890 (GS1 17-digit Bill of Lading number) ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | REF01 | 128 | Reference Identification Qualifier | M |
| ID 2/2 | ||||
| Code qualifying the Reference Identification |
| ||||||||
| BM |
| Bill of Lading 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 |
| ||||||||
| A unique Bill of Lading (BOL) number for each shipment is required. |
| ||||||||
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*20040602 ************************ |
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 |
| |||||||
| REQUIRED |
| |||||||||
| 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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ At least one N1 segment, containing an N101 of ST is required.
Sample N1 Segment ______________________ N1*ST**92*0001 ************************ |
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 |
| |||||||||
| ST |
| Ship To |
| |||||||
| REQUIRED |
| |||||||||
| N102 | 93 | Name | O |
| AN 1/35 | |||||
| Free-form name |
| |||||||||
| NOT USED BY TARGET CORPORATION |
| |||||||||
M | N103 | 66 | Identification Code Qualifier | M |
| ID 1/2 | |||||
| Code designating the system/method of code structure used for Identification Code (67) |
| |||||||||
| Per Target Corporation Standards: *N103 code '92' is only valid with an N101 equal to ST |
| |||||||||
| 91 |
| Assigned by Seller or Seller's Agent |
| |||||||
| 92 |
| Assigned by Buyer or Buyer's Agent |
| |||||||
M | N104 | 67 | Identification Code | M |
| AN 2/17 | |||||
| Code identifying a party or other code |
| |||||||||
| Target Corporation's four digit store location number. |
| |||||||||
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.
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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ 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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ NOTE: Starting in Dec 2017, Target will start phasing in a new PO format. The new format removes the 4 digit department number prefix and the purchase order number will be moving from 7 digits to 11 digits. No changes are being made to the location number. During this transition, your company needs to be able to receive both PO formats, as both may be received during transition. The same PO format received from Target will need to be returned on all EDI related documents for that PO to ensure no business interruption.
New Purchase Order Number Format: 12345678901-1234
Sample PRF Segment _______________________ PRF*0040-0434720
PRF*0040-0434720-0001
PRF*12345678909-0551
PRF*12345678909
************************ |
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 |
| |||||
| Identifying number sent on 850 Purchase Order in the BEG03 segment. |
| |||||
Segment: TD1 Carrier Details (Quantity and Weight)
Position: 110
Loop: HLO 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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ Sample TD1 Segment __________________________ TD1*CTN *60
TD1*CTN25*60 ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | TD101 | 103 | Packaging Code | M |
| AN 5/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 |
| |||||||||
| This data element contains 2 parts: Part 1 is the first 3 positions. It is alphabetic and the code valid for Target Corporation is listed below.
Part 2 is the final 2 positions and is numeric. Any legal code or spaces can be used for Part 2.
Note: some translator packages may not allow spaces for Part 2. Target Stores is only concerned with the Part 1 codes. See Sample TD1 segments above. |
| |||||||||
| CTN |
| Carton |
| |||||||
| 25 - Carton Corrugated 31 - Carton Fiber 76 - Carton Paper |
| |||||||||
M | TD102 | 80 | Lading Quantity | M |
| N0 1/7 | |||||
| Number of units (pieces) of the lading commodity |
| |||||||||
Segment: HL Hierarchical Level - Tare
Position: 010
Loop: HLT Conditional
Level: Detail
Usage: Conditional
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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ The Tare level must be used when the Pack level MAN segment contains the 'UC' (GTIN-14, SCC-14) or 'UP'/'EN' (GTIN-12/13 or U.P.C./EAN).
The Tare level is optional when the SSCC is used in the MAN segment at the Pack level.
This segment is not used by Target Corporation for DSD shipments.
Sample HL (Tare level) Segment __________________________ HL*3*2*T ************************ |
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 |
| ||||||||
| T |
| Shipping Tare |
| ||||||
Segment: MAN Marks and Numbers
Position: 190
Loop: HLT Conditional
Level: Detail
Usage: Conditional
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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ NOTE: If sending HL Tare Level, this Segment is required.
This segment is not used by Target Corporation for DSD shipments.
Sample MAN Segment ______________________ MAN*GM*00123456789876543211 MAN*AA*123456789876543217 ************************ |
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 |
| ||||||||
| When GM is present in MAN01, the value in this field must be 20 digits. When AA is present in MAN01, the value in this field must be 18 digits. |
| ||||||||
| MAN03 | 87 | Marks and Numbers | O |
| AN 1/48 | ||||
| Marks and numbers used to identify a shipment or parts of a shipment |
| ||||||||
| MAN04 | 88 | Marks and Numbers Qualifier | O |
| ID 1/2 | ||||
| Code specifying the application or source of Marks and Numbers (87) |
| ||||||||
| AA |
| SSCC-18 |
| ||||||
| GM |
| SSCC-18 and Application Identifier |
| ||||||
| MAN05 | 87 | Marks and Numbers | O |
| AN 1/48 | ||||
| Marks and numbers used to identify a shipment or parts of a shipment |
| ||||||||
| When GM is present in MAN01, the value in this field must be 20 digits. When AA is present in MAN01, the value in this field must be 18 digits. |
| ||||||||
| MAN06 | 87 | Marks and Numbers | O |
| AN 1/48 | ||||
| Marks and numbers used to identify a shipment or parts of a shipment |
| ||||||||
Segment: HL Hierarchical Level - Pack
Position: 010
Loop: HLP Conditional
Level: Detail
Usage: Conditional
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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ This segment is not used by Target Corporation for DSD shipments.
Sample HL (Pack Level) Segment ___________________________ 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 |
| ||||||||
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 |
| ||||||||
| P |
| Pack |
| ||||||
Segment: MAN Marks and Numbers
Position: 190
Loop: HLP Conditional
Level: Detail
Usage: Conditional
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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ This segment is not used by Target Corporation for DSD shipments.
MAN01 or MAN04 must be 'GM' or 'AA' at Pack Level when a Tare Segment is not present.
When used together, MAN01 and MAN04 CANNOT be the same (i.e. if MAN01 is 'GM', MAN04 cannot be GM).
Sample MAN Segments: ______________________ MAN*GM*00000123456789876754 (Must be a unique # per shipping container).
MAN*AA*000123456789876754 (Must be a unique # per shipping container).
GTIN-14: 14 digit Product Identification Code (aka SCC-14) MAN*UC*10012345655668 (14-digit carton case code)
GTIN-12/13: U.P.C./EAN on selling unit. Only valid if selling unit is shipping unit and case-pack equals 1. MAN*UP*000123456784 (12-digit selling unit UPC code)
Ranging MAN Segments:
MAN*GM*00000123456789987659*00000123456789988756 MAN02 = First carton barcode of an item. MAN03 = Last carton barcode of same item.
MAN*AA*000001234567899876*000001234567899887 MAN02 = First carton barcode of an item MAN03 = Last carton barcode of same item
See "Ship Carton and Pallet Markings Domestic" on POL (www.partnersonline.com) for labeling requirements. ************************ |
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) |
| |||||||||
| MAN01 or MAN04 must be 'GM' or 'AA' at Pack Level when a Tare Segment is not present. |
| |||||||||
| AA |
| SSCC-18 |
| |||||||
| EN |
| EAN European Article Number (2-5-5-1) |
| |||||||
| GM |
| SSCC-18 and Application Identifier |
| |||||||
| UC |
| U.P.C. Shipping Container Code |
| |||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| Used when case pack is one and selling unit is shipping unit. |
| |||||||||
M | MAN02 | 87 | Marks and Numbers | M |
| AN 1/48 | |||||
| Marks and numbers used to identify a shipment or parts of a shipment |
| |||||||||
| MAN03 | 87 | Marks and Numbers | O |
| AN 1/48 | |||||
| Marks and numbers used to identify a shipment or parts of a shipment |
| |||||||||
| MAN04 | 88 | Marks and Numbers Qualifier | O |
| ID 1/2 | |||||
| Code specifying the application or source of Marks and Numbers (87) |
| |||||||||
| MAN01 or MAN04 must be 'GM' or 'AA' at Pack Level when a Tare Segment is not present. |
| |||||||||
| AA |
| SSCC-18 |
| |||||||
| EN |
| EAN European Article Number (2-5-5-1) |
| |||||||
| GM |
| SSCC-18 and Application Identifier |
| |||||||
| UC |
| U.P.C. Shipping Container Code |
| |||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| Used when case pack is one and selling unit is shipping unit. |
| |||||||||
| MAN05 | 87 | Marks and Numbers | O |
| AN 1/48 | |||||
| Marks and numbers used to identify a shipment or parts of a shipment |
| |||||||||
| MAN06 | 87 | Marks and Numbers | O |
| AN 1/48 | |||||
| Marks and numbers used to identify a shipment or parts of a shipment |
| |||||||||
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.
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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ Sample HL (Item Level) Segment __________________________ HL*5*4*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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ NOTE: IN will be used as an item identifier for Target in the future. When this item identifier is sent by Target, your system must be capable of sending it back on inbound EDI documents to Target.
Always send either Target Corporation's DPCI number with a CB qualifier, the assigned UPC number with a UP qualifier, or the assigned EAN number with a EN qualifier.
Sample LIN Segment ______________________ LIN**CB*019060025*UP*039800088628
LIN**UP*039800088628
LIN**CB*019060025
LIN*EN*345645444777
If a full or partial substitution is being made for the original item on the PO, this segment must be used to indicate the original item. ************************ |
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) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| Target Corporation's 9 digit DPCI number |
| |||||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
M | LIN03 | 234 | Product/Service ID | M |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| 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) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
| LIN05 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| 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) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
| LIN07 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| LIN08 | 235 | Product/Service ID Qualifier | O |
| ID 2/2 | |||||
| Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
| LIN09 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ Sample SN1 Segment _________________________ SN1**75*EA
SN1**1*CA
SN1**0*EA (Indicates a full substitution is being sent. Also indicates the item cannot be fulfilled when no substitution is available)
Note: If a full item substitution has been made, the quantity in the SN1 should be zero. If a partial item substitution has been made, the quantity should indicate the amount of the original item being sent. ************************ |
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 by Retail Industry |
| ||||||||
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 |
| ||||||||
| Pharmacy vendors must send the "CA" in this field. |
| ||||||||
| CA |
| Case |
| ||||||
| EA |
| Each |
| ||||||
| LB |
| Pound |
| ||||||
Segment: SLN Subline Item Detail
Position: 040
Loop: HLI Mandatory
Level: Detail
Usage: Optional
Max Use: 1000
Purpose: To specify product subline detail item data
Syntax Notes: 1 If either SLN04 or SLN05 is present, then the other is required.
2 If SLN07 is present, then SLN06 is required.
3 If SLN08 is present, then SLN06 is required.
4 If either SLN09 or SLN10 is present, then the other is required.
5 If either SLN11 or SLN12 is present, then the other is required.
6 If either SLN13 or SLN14 is present, then the other is required.
7 If either SLN15 or SLN16 is present, then the other is required.
8 If either SLN17 or SLN18 is present, then the other is required.
9 If either SLN19 or SLN20 is present, then the other is required.
10 If either SLN21 or SLN22 is present, then the other is required.
11 If either SLN23 or SLN24 is present, then the other is required.
12 If either SLN25 or SLN26 is present, then the other is required.
13 If either SLN27 or SLN28 is present, then the other is required.
Semantic Notes: 1 SLN01 is the identifying number for the subline item.
2 SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials.
3 SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
4 SLN08 is a code indicating the relationship of the price or amount to the associated segment.
Comments: 1 See the Data Element Dictionary for a complete list of IDs.
2 SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
3 SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Notes: |
| ************************ NOTE: IN will be used as an item identifier for Target in the future. When this item identifier is sent by Target, your system must be capable of sending it back on inbound EDI documents to Target.
This segment is used to indicate either a full or partial substitution of the item in the LIN segment.
When using the SLN segment, the unit of measure must be EA in both the SN1 and SLN segments.
Sample SLN Segment _______________________ SLN*01**S*10*EA****CB*288021111 ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | SLN01 | 350 | Assigned Identification | M |
| AN 1/20 | |||||
| Alphanumeric characters assigned for differentiation within a transaction set |
| |||||||||
| Assigned ID must refer to LIN01 Assigned ID |
| |||||||||
| SLN02 | 350 | Assigned Identification | O |
| AN 1/20 | |||||
| Alphanumeric characters assigned for differentiation within a transaction set |
| |||||||||
| Not used by Retail Industry |
| |||||||||
M | SLN03 | 662 | Configuration Code | M |
| ID 1/1 | |||||
| Code indicating the relationship between entities |
| |||||||||
| S |
| Substituted |
| |||||||
Must Use | SLN04 | 380 | Quantity | O |
| R 1/15 | |||||
| Numeric value of quantity |
| |||||||||
M | SLN05 | C001 | Composite Unit of Measure | M |
|
| |||||
| To identify a composite unit of measure (See Figures Appendix for examples of use) |
| |||||||||
M | C00101 | 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 |
| |||||||||
| Pharmacy vendors must send "CA" in this field. |
| |||||||||
| CA |
| Case |
| |||||||
| EA |
| Each |
| |||||||
| LB |
| Pound |
| |||||||
| SLN06 | 212 | Unit Price | O |
| R 1/17 | |||||
| Price per unit of product, service, commodity, etc. |
| |||||||||
| Not used by Target Corporation |
| |||||||||
| SLN07 | 639 | Basis of Unit Price Code | O |
| ID 2/2 | |||||
| Code identifying the type of unit price for an item |
| |||||||||
| Not used by Target Corporation |
| |||||||||
| SLN08 | 662 | Relationship Code | O |
| ID 1/1 | |||||
| Code indicating the relationship between entities |
| |||||||||
| Not used by Target Corporation |
| |||||||||
| S |
| Substituted |
| |||||||
M | SLN09 | 235 | Product/Service ID Qualifier | M |
| ID 2/2 | |||||
| Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| Target Corporation's 9 digit DPCI number |
| |||||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
Must Use | SLN10 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| SLN11 | 235 | Product/Service ID Qualifier | O |
| ID 2/2 | |||||
| Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
| SLN12 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| SLN13 | 235 | Product/Service ID Qualifier | O |
| ID 2/2 | |||||
| Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
| SLN14 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| SLN15 | 235 | Product/Service ID Qualifier | O |
| ID 2/2 | |||||
| Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
| SLN16 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
Segment: PO4 Item Physical Details
Position: 060
Loop: HLI Mandatory
Level: Detail
Usage: Conditional
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: |
| ************************ NOTE: This segment is required when SN103 is "CA".
PO401 = The number of total units within the carton - OR - The number of inner packs within the outer carton. (The latter applies if PO4*14 was sent on the PO.)
PO414 = The number of units within an inner pack.
If the PO414 is sent on the PO, it is required to be sent back/returned on the EDI 856. If the PO414 is not sent on the PO, do not send back/return a PO4*14 on the EDI 856.
Sample PO4 Segments ________________________ PO4*12 (no inner packs) - Casepack = 12 individual units PO4*4*************6 - (inner packs, within a carton) Casepack = 24, with 4 inner packs of 6 units each ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | PO401 | 356 | Pack | M |
| N0 1/6 | |
| The number of inner containers, or number of eaches if there are no inner containers, per outer container |
| |||||
| PO402 | 357 | Size | O |
| R 1/8 | |
| Size of supplier units in pack |
| |||||
| NOT USED BY TARGET CORPORATION |
| |||||
| PO403 | 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 |
| |||||
| NOT USED BY TARGET CORPORATION |
| |||||
| PO404 | 103 | Packaging Code | X |
| 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 |
| |||||
| NOT USED BY TARGET CORPORATION |
| |||||
| PO405 | 187 | Weight Qualifier | O |
| ID 1/2 | |
| Code defining the type of weight |
| |||||
| NOT USED BY TARGET CORPORATION |
| |||||
| PO406 | 384 | Gross Weight per Pack | X |
| R 1/9 | |
| Numeric value of gross weight per pack |
| |||||
| NOT USED BY TARGET CORPORATION |
| |||||
| PO407 | 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 |
| |||||
| NOT USED BY TARGET CORPORATION |
| |||||
| PO408 | 385 | Gross Volume per Pack | X |
| R 1/9 | |
| Numeric value of gross volume per pack |
| |||||
| NOT USED BY TARGET CORPORATION |
| |||||
| PO409 | 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 |
| |||||
| NOT USED BY TARGET CORPORATION |
| |||||
| PO410 | 82 | Length | X |
| R 1/8 | |
| Largest horizontal dimension of an object measured when the object is in the upright position |
| |||||
| NOT USED BY TARGET CORPORATION |
| |||||
| PO411 | 189 | Width | X |
| R 1/8 | |
| Shorter measurement of the two horizontal dimensions measured with the object in the upright position |
| |||||
| NOT USED BY TARGET CORPORATION |
| |||||
| PO412 | 65 | Height | X |
| R 1/8 | |
| Vertical dimension of an object measured when the object is in the upright position |
| |||||
| NOT USED BY TARGET CORPORATION |
| |||||
| PO413 | 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 |
| |||||
| NOT USED BY TARGET CORPORATION |
| |||||
| PO414 | 810 | Inner Pack | O |
| N0 1/6 | |
| The number of eaches per inner container |
| |||||
| If inner cartons are being sent, this is the # of selling units within one of the inner cartons only. If the P0414 element is received on the PO, then it is required to be sent back on the 856. |
| |||||
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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ Sample CTT Segment __________________________ CTT*12 ************************ |
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: |
| *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
************************ 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 |
| |||||
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article