Target Canada. Domestic 856 Ship Notice Manifest Distribution/Fulfillment Centers

Transcription

1 Target Canada Domestic 856 Ship Notice Manifest Distribution/Fulfillment Centers EDI Guideline Version: 5010 Draft Author: GXS Company: Target Canada Publication: 1/27/2012 Trading Partner: Distribution/Fulfillment Centers

2

3 Revision Date Author Purpose for Change /27/2013 GXS Updated BSN02 notes, Item level PO4 examples, PO401 and PO414 descriptions for no inner packs.

4

5 856 Ship Notice/Manifest Functional Group=SH Purpose: This X12 Transaction Set contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information. The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment. Please Note: You will see some elements listed as "Optional" per ANSI X12 Standard ("Req" column), but are considered "Mandatory" ("Usage" column) per Target Canada's business rules. 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 Canada requires a separate transaction set for each ship to DC 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). Not Defined: Pos Id Segment Name Req Max Use Repeat Notes Usage ISA Interchange Control Header M 1 Must use GS Functional Group Header M 1 Must use Heading: Pos Id Segment Name Req Max Use Repeat Notes Usage 0100 ST Transaction Set Header M 1 Must use 0200 BSN Beginning Segment for Ship Notice M 1 Must use Detail: Pos Id Segment Name Req Max Use Repeat Notes Usage LOOP ID - HL C2/0100L 0100 HL Hierarchical Level - Shipment M 1 C2/0100 Must use 1200 TD5 Carrier Details (Routing O 12 Used Sequence/Transit Time) 1500 REF Reference Information O >1 Must use LOOP ID - N N1 Party Identification O 1 Must use LOOP ID - HL C2/0100L 0100 HL Hierarchical Level - Order M 1 C2/0100 Must use 0500 PRF Purchase Order Reference O 1 Must use 1100 TD1 Carrier Details (Quantity and Weight) O 20 Used LOOP ID - N N1 Party Identification O 1 Used LOOP ID - HL C2/0100L 0100 HL Hierarchical Level - Tare O 1 C2/0100 Used 1900 MAN Marks and Numbers Information O >1 Used LOOP ID - HL C2/0100L 0100 HL Hierarchical Level - Pack M 1 C2/0100 Must use 1500 REF Reference Information O >1 Used 1900 MAN Marks and Numbers O >1 Must use Target Canada 1 Ver 5010

6 Information 2000 DTM Date/Time Reference O 10 Used LOOP ID - HL C2/0100L 0100 HL Hierarchical Level - Item M 1 C2/0100 Must use 0200 LIN Item Identification O 1 Must use 0300 SN1 Item Detail (Shipment) O 1 Must use 0600 PO4 Item Physical Details O 1 Must use 1500 REF Reference Information O >1 Used 2000 DTM Date/Time Reference O 10 Used Summary: Pos Id Segment Name Req Max Use Repeat Notes Usage 0100 CTT Transaction Totals O 1 N3/0100 Must use 0200 SE Transaction Set Trailer M 1 Must use Not Defined: Pos Id Segment Name Req Max Use Repeat Notes Usage GE Functional Group Trailer M 1 Must use IEA Interchange Control Trailer M 1 Must use 3/0100 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. Comments: 2/0100L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning. 2/0100 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning. 2/0100L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning. 2/0100 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning. 2/0100L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning. 2/0100 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning. 2/0100L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning. 2/0100 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning. 2/0100L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning. 2/0100 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning. Target Canada 2 Ver 5010

7 ISA Interchange Control Header Pos: Max: 1 Not Defined - Mandatory Loop: N/A Elements: 16 User Option (Usage): Must use Purpose: To start and identify an interchange of zero or more functional groups and interchange-related control segments ISA01 I01 Authorization Information Qualifier M ID 2/2 Must use Description: Code identifying the type of information in the Authorization Information All valid standard codes are used. (Total Codes: 7) ISA02 I02 Authorization Information M AN 10/10 Must use Description: Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01) ISA03 I03 Security Information Qualifier M ID 2/2 Must use Description: Code identifying the type of information in the Security Information All valid standard codes are used. (Total Codes: 2) ISA04 I04 Security Information M AN 10/10 Must use Description: This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03) ISA05 I05 Interchange ID Qualifier M ID 2/2 Must use Description: Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified All valid standard codes are used. (Total Codes: 41) ISA06 I06 Interchange Sender ID M AN 15/15 Must use Description: Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element ISA07 I05 Interchange ID Qualifier M ID 2/2 Must use Description: Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified CodeList Summary (Total Codes: 41, Included: 1) ZZ Mutually Defined ISA08 I07 Interchange Receiver ID M AN 15/15 Must use Description: Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them TGTCANDOMPOSD - Target Canada production ISA address for Post Distro. Domestic 856 TGTCANDOMPOSDT - Target Canada test ISA address for Post Distro Domestic 856 ISA09 I08 Interchange Date M DT 6/6 Must use Description: Date of the interchange ISA10 I09 Interchange Time M TM 4/4 Must use Description: Time of the interchange ISA11 I65 Repetition Separator M 1/1 Must use Description: Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a Target Canada 3 Ver 5010

8 composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator ISA12 I11 Interchange Control Version Number M ID 5/5 Must use Description: Code specifying the version number of the interchange control segments All valid standard codes are used. (Total Codes: 20) ISA13 I12 Interchange Control Number M N0 9/9 Must use Description: A control number assigned by the interchange sender ISA14 I13 Acknowledgment Requested M ID 1/1 Must use Description: Code indicating sender's request for an interchange acknowledgment All valid standard codes are used. (Total Codes: 2) ISA15 I14 Interchange Usage Indicator M ID 1/1 Must use Description: Code indicating whether data enclosed by this interchange envelope is test, production or information All valid standard codes are used. (Total Codes: 3) ISA16 I15 Component Element Separator M 1/1 Must use Description: Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator Target Canada 4 Ver 5010

9 GS Functional Group Header Pos: Max: 1 Not Defined - Mandatory Loop: N/A Elements: 8 User Option (Usage): Must use Purpose: To indicate the beginning of a functional group and to provide control information GS Functional Identifier Code M ID 2/2 Must use Description: Code identifying a group of application related transaction sets CodeList Summary (Total Codes: 260, Included: 1) SH Ship Notice/Manifest (856) GS Application Sender's Code M AN 2/15 Must use Description: Code identifying party sending transmission; codes agreed to by trading partners GS Application Receiver's Code M AN 2/15 Must use Description: Code identifying party receiving transmission; codes agreed to by trading partners TGTCANDOMPOSD - Target Canada production GS address for Post Distro Domestic 856 (same as ISA) TGTCANDOMPOSDT - Target Canada test GS address for Post Distro Domestic 856 (same as ISA) GS Date M DT 8/8 Must use Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year GS Time M TM 4/8 Must use Description: 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) GS06 28 Group Control Number M N0 1/9 Must use Description: Assigned number originated and maintained by the sender GS Responsible Agency Code M ID 1/2 Must use Description: Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480 CodeList Summary (Total Codes: 2, Included: 1) X Accredited Standards Committee X12 GS Version / Release / Industry Identifier Code M AN 1/12 Must use Semantics: 1. GS04 is the group date. Description: Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed CodeList Summary (Total Codes: 54, Included: 1) Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003 Target Canada 5 Ver 5010

10 2. GS05 is the group time. 3. The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02. Comments: 1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer. Target Canada 6 Ver 5010

11 ST Transaction Set Header Pos: 0100 Max: 1 Heading - Mandatory Loop: N/A Elements: 2 User Option (Usage): Must use Purpose: To indicate the start of a transaction set and to assign a control number *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 Canada requires a separate transaction set for each ship to location. (A transaction set starts with a ST segment and ends with a SE segment). ************************ ST Transaction Set Identifier Code M ID 3/3 Must use Description: Code uniquely identifying a Transaction Set CodeList Summary (Total Codes: 318, Included: 1) 856 Ship Notice/Manifest ST Transaction Set Control Number M AN 4/9 Must use Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Semantics: 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). 2. The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate implementation convention to match the transaction set definition. When used, this implementation convention reference takes precedence over the implementation reference specified in the GS08. Target Canada 7 Ver 5010

12 BSN Beginning Segment for Ship Notice Pos: 0200 Max: 1 Heading - Mandatory Loop: N/A Elements: 5 User Option (Usage): Must use Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data. ************************ Sample BSN Segment BSN*00*234567* *0142*0001 (Pick Pack Format) Standard Pack format is not allowed for Target Canada. ************************ BSN Transaction Set Purpose Code M ID 2/2 Must use Description: Code identifying purpose of transaction set CodeList Summary (Total Codes: 66, Included: 3) 00 Original 05 Replace Used when sending a full re-transmission. 25 Incremental Used when sending a partial re-transmission. BSN Shipment Identification M AN 2/30 Must use Description: A unique control number assigned by the original shipper to identify a specific shipment Note that EDI Standards state that this should be a unique number. Target Canada applications have been written based on that. This number will be used to differentiate multiple 856s received from a supplier. This number must be 16 digits or less in length and should be different than the Purchase Order or Bill of Lading Number. BSN Date M DT 8/8 Must use Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year BSN Time M TM 4/8 Must use Description: 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) BSN Hierarchical Structure Code O ID 4/4 Must use Description: Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set CodeList Summary (Total Codes: 81, Included: 1) 0001 Shipment, Order, Packaging, Item Pick & Pack Format allows for multiple SKUs on pallet Syntax Rules: 1. C If BSN07 is present, then BSN06 is required. Target Canada 8 Ver 5010

13 Semantics: 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. Target Canada 9 Ver 5010

14 HL Hierarchical Level - Shipment Pos: 0100 Max: 1 Detail - Mandatory Loop: HL Elements: 3 User Option (Usage): Must use Purpose: To identify dependencies among and the content of hierarchically related groups of data segments *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data. ************************ Sample HL (Shipment Level) Segment HL*1**S ************************ HL Hierarchical ID Number M AN 1/12 Must use Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure HL Hierarchical Parent ID Number O AN 1/12 Not used Description: Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to Not used by Target Canada HL Hierarchical Level Code M ID 1/2 Must use Description: Code defining the characteristic of a level in a hierarchical structure CodeList Summary (Total Codes: 250, Included: 1) S Shipment 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. 2. The HL segment defines a top-down/left-right ordered structure. 3. 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. 4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. 5. 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. 6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment. Target Canada 10 Ver 5010

15 TD5 Carrier Details (Routing Sequence/Transit Time) Pos: 1200 Max: 12 Detail - Optional Loop: HL Elements: 5 User Option (Usage): Used Purpose: To specify the carrier and sequence of routing and provide transit time information ************************ Correct information is necessary for matching to the corresponding EDI 214 Carrier Shipment Status Message. Sample TD5 Segment TD5*B*2*SOCS*C*Consolidator Name (consolidator example) TD5*B*2*MIIW*M (truckload or LTL carrier example) TD5*B*2*UPSN*U*UPS (private parcel example) ************************ TD Routing Sequence Code O ID 1/2 Used Description: Code describing the relationship of a carrier to a specific shipment movement CodeList Summary (Total Codes: 23, Included: 1) B Origin/Delivery Carrier (Any Mode) TD Identification Code Qualifier X ID 1/2 Used Description: Code designating the system/method of code structure used for Identification Code (67) CodeList Summary (Total Codes: 241, Included: 1) 2 Standard Carrier Alpha Code (SCAC) TD Identification Code X AN 2/80 Used Description: Code identifying a party or other code Target requires the 4-character alpha SCAC code. The SCAC code must be sent in upper case. TD Transportation Method/Type Code X ID 1/2 Used Description: 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). TRANSPORTATION Mode of : TD504 REF01 REF02 Transportation Air A CN Carrier Ref.# (Carrier Tracking Number) Consolidation C MB Master Bill of Lading# (Optional) BM Underlying BOL (When used with MB) TL or LTL M BM Bill of Lading # Private Parcel U CN Carrier Ref.#<0xB> (Carrier Tracking Number). CodeList Summary (Total Codes: 80, Included: 4) A Air C Consolidation M Motor (Common Carrier) Truckload or LTL U Private Parcel Service Target Canada 11 Ver 5010

16 Small Package Shipments TD Routing X AN 1/35 Used Description: Free-form description of the routing or requested routing for shipment, or the originating carrier's identity Syntax Rules: 1. R At least one of TD502, TD504, TD505, TD506 or TD512 is required. 2. C If TD502 is present, then TD503 is required. 3. C If TD507 is present, then TD508 is required. 4. C If TD510 is present, then TD511 is required. 5. C If TD513 is present, then TD512 is required. 6. C If TD514 is present, then TD513 is required. 7. C If TD515 is present, then TD512 is required. Semantics: 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. Target Canada 12 Ver 5010

17 REF Reference Information Pos: 1500 Max: >1 Detail - Optional Loop: HL Elements: 2 User Option (Usage): Must use Purpose: To specify identifying information *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data. ************************ This segment is critical for matching the Carrier's EDI 214 Carrier Status Message with your EDI 856 Ship Notice Message. Target Canada requires: A UNIQUE Bill of Lading (BOL) number for each shipment. Use the VICS (Voluntary Inter-Industry Commerce Standard) standard Bill of Lading document. Target Canada strongly recommends the use of the VICS standard 17-digit Bill of Lading number format. 1) When routing via Truckload (TL) or Less than Truckload (LTL) carrier, one unique BOL # is required per Target Canada ship to location. If constraints require BOL per Purchase Order, then a Master BOL must be used to summarize the underlying bills of lading. When a Master BOL # is used, be sure to transmit this number on the 856. The Master BOL # must be passed to the carrier as the Shipment BOL # for the corresponding Carrier EDI transmission. 2) When routing to a Target Canada consolidator, a Master BOL # must be used and sent on all 856's created per Purchase Order ship to location. The Master BOL # must reflect the actual BOL # given to the carrier on the VICS BOL. Do not transmit the individual (underlying) Bill of Lading numbers on the 856. Sample REF Segment REF*BM* (GS1 17-digit Bill of Lading number) (Does your shipment require a Master Bill of Lading #? **read above notes for proper Bill of Lading usage). ************************ REF Reference Identification Qualifier M ID 2/3 Must use Description: Code qualifying the Reference Identification The mode of transportation determines both the transportation method type code (TD504) and the REF segment qualifier (REF01). TRANSPORTATION Mode of : TD504 REF01 REF02 Transportation Air A CN Carrier Ref.# (Carrier Tracking Number) Consolidation C MB Master Bill of Lading# (Optional) BM Underlying BOL (When used with MB) TL or LTL M BM Bill of Lading # Private Parcel U CN Carrier Ref.#<0xB> (Carrier Tracking Number). CodeList Summary (Total Codes: 1731, Included: 3) BM Bill of Lading Number Required when shipping via motor carrier (TD504 equals "M"). CN Carrier's Reference Number (PRO/Invoice) Required when shipping parcel package shipments (TD504 equals U or A ). MB Master Bill of Lading Master Bill of Lading required for all consolidated shipments (TD504 equals C ). Please note: if the Master Bill of Lading (MB) and Bill of Lading (BM) are both sent, Target Canada will only use the Master Bill of Lading (MB) number. REF Reference Identification X AN 1/50 Must use Description: 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. When the mode of Target Canada 13 Ver 5010

18 transportation is for Consolidation, a unique Master BOL # is required for all ship to locations on that shipment. Syntax Rules: 1. R At least one of REF02 or REF03 is required. Semantics: 1. REF04 contains data relating to the value cited in REF02. Target Canada 14 Ver 5010

19 N1 Party Identification Pos: 2200 Max: 1 Detail - Optional Loop: N1 Elements: 4 User Option (Usage): Must use Purpose: To identify a party by type of organization, name, and code *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*3831 ************************ N Entity Identifier Code M ID 2/3 Must use Description: Code identifying an organizational entity, a physical location, property or an individual CodeList Summary (Total Codes: 1500, Included: 1) ST Ship To REQUIRED N Name X AN 1/60 Not used Description: Free-form name Not used by Target Canada N Identification Code Qualifier X ID 1/2 Must use Description: Code designating the system/method of code structure used for Identification Code (67) CodeList Summary (Total Codes: 241, Included: 1) 92 Assigned by Buyer or Buyer's Agent N Identification Code X AN 2/80 Must use Description: Code identifying a party or other code When N101 = ST, this will be a four digit Target Canada DC location number. Syntax Rules: 1. R At least one of N102 or N103 is required. 2. P If either N103 or N104 is present, then the other is required. 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. Target Canada 15 Ver 5010

20 HL Hierarchical Level - Order Pos: 0100 Max: 1 Detail - Mandatory Loop: HL Elements: 3 User Option (Usage): Must use Purpose: To identify dependencies among and the content of hierarchically related groups of data segments *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 ************************ HL Hierarchical ID Number M AN 1/12 Must use Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure HL Hierarchical Parent ID Number O AN 1/12 Must use Description: Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to HL Hierarchical Level Code M ID 1/2 Must use Description: Code defining the characteristic of a level in a hierarchical structure CodeList Summary (Total Codes: 250, Included: 1) O Order 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. 2. The HL segment defines a top-down/left-right ordered structure. 3. 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. 4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. 5. 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. 6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment. Target Canada 16 Ver 5010

21 PRF Purchase Order Reference Pos: 0500 Max: 1 Detail - Optional Loop: HL Elements: 1 User Option (Usage): Must use Purpose: To provide reference to a specific purchase order *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data. ************************ Target Canada: Sample PRF Segment PRF* ************************ PRF Purchase Order Number M AN 1/22 Must use Description: Identifying number for Purchase Order assigned by the orderer/purchaser Identifying number sent on 850 Purchase Order in the BEG03 segment. Note: Target Canada s original purchase order number is a 10 digit alpha numeric field. Semantics: 1. PRF04 is the date assigned by the purchaser to purchase order. Target Canada 17 Ver 5010

22 TD1 Carrier Details (Quantity and Weight) Pos: 1100 Max: 20 Detail - Optional Loop: HL Elements: 2 User Option (Usage): Used Purpose: To specify the transportation details relative to commodity, weight, and quantity ************************ Sample TD1 Segment TD1*CTN *60 TD1*CTN25*60 Note: TD101 must be 5 characters. If only CTN is sent, it should be followed by 2 spaces. ************************ TD Packaging Code O AN 3/5 Used Description: 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 those codes valid for Target Canada are the first 3 listed below. Part 2 is the final 2 positions and is numeric. See example part one = CTN. Target Canada is only concerned with the Part 1 codes. Any legal code or spaces can be used for Part 2. Note though that some translator packages may not allow spaces for Part 2. See Sample TD1 segments above. CodeList Summary (Total Codes: 212, Included: 4) 25 Corrugated or Solid Part 2 31 Fibre Part 2 76 Paper Part 2 CTN Carton Part 1 TD Lading Quantity X N0 1/7 Used Description: Number of units (pieces) of the lading commodity Syntax Rules: 1. C If TD101 is present, then TD102 is required. 2. C If TD103 is present, then TD104 is required. 3. C If TD106 is present, then TD107 is required. 4. P If either TD107 or TD108 is present, then the other is required. 5. P If either TD109 or TD110 is present, then the other is required. Target Canada 18 Ver 5010

23 N1 Party Identification Pos: 2200 Max: 1 Detail - Optional Loop: N1 Elements: 4 User Option (Usage): Used Purpose: To identify a party by type of organization, name, and code *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data. ************************ Sample N1 Segment N1*BY**92*3831 ************************ N Entity Identifier Code M ID 2/3 Must use Description: Code identifying an organizational entity, a physical location, property or an individual CodeList Summary (Total Codes: 1500, Included: 1) BY Buying Party (Purchaser) N Name X AN 1/60 Not used Description: Free-form name Not Used by Target Canada N Identification Code Qualifier X ID 1/2 Must use Description: Code designating the system/method of code structure used for Identification Code (67) CodeList Summary (Total Codes: 241, Included: 1) 92 Assigned by Buyer or Buyer's Agent N Identification Code X AN 2/80 Must use Description: Code identifying a party or other code This will be a four digit location number Syntax Rules: 1. R At least one of N102 or N103 is required. 2. P If either N103 or N104 is present, then the other is required. 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. Target Canada 19 Ver 5010

24 HL Hierarchical Level - Tare Pos: 0100 Max: 1 Detail - Optional Loop: HL Elements: 3 User Option (Usage): Used Purpose: To identify dependencies among and the content of hierarchically related groups of data segments *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. Sample HL (Tare level) Segment HL*3*2*T ************************ HL Hierarchical ID Number M AN 1/12 Must use Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure HL Hierarchical Parent ID Number O AN 1/12 Must use Description: Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to HL Hierarchical Level Code M ID 1/2 Must use Description: Code defining the characteristic of a level in a hierarchical structure CodeList Summary (Total Codes: 250, Included: 1) T Shipping Tare 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. 2. The HL segment defines a top-down/left-right ordered structure. 3. 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. 4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. 5. 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. 6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment. Target Canada 20 Ver 5010

25 MAN Marks and Numbers Information Pos: 1900 Max: >1 Detail - Optional Loop: HL Elements: 3 User Option (Usage): Used Purpose: To indicate identifying marks and numbers for shipping containers *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. 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). Sample MAN Segment MAN*GM* MAN*AA* ************************ MAN01 88 Marks and Numbers Qualifier M ID 1/2 Must use Description: Code specifying the application or source of Marks and Numbers (87) CodeList Summary (Total Codes: 21, Included: 2) AA EAN.UCC Serial Shipping Container Code (SSCC) GM EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier MAN02 87 Marks and Numbers M AN 1/48 Must use Description: Marks and numbers used to identify a shipment or parts of a shipment When GM is present in the MAN01, the value in this field must be 20 digits. MAN03 87 Marks and Numbers O AN 1/48 Used Description: Marks and numbers used to identify a shipment or parts of a shipment Caution: Must ensure range is sequential and accounts for all pallets shipped. The last digit of the barcode number is the check digit and should not be included in number sequencing. Syntax Rules: 1. P If either MAN04 or MAN05 is present, then the other is required. 2. C If MAN06 is present, then MAN05 is required. Semantics: 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/MAN MAN03 and/or MAN06 are only used when sending a range(s) of ID numbers. 3. 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. Target Canada 21 Ver 5010

26 HL Hierarchical Level - Pack Pos: 0100 Max: 1 Detail - Mandatory Loop: HL Elements: 3 User Option (Usage): Must use Purpose: To identify dependencies among and the content of hierarchically related groups of data segments *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data. ************************ Sample HL (Pack Level) Segment HL*3*2*P ************************ HL Hierarchical ID Number M AN 1/12 Must use Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure HL Hierarchical Parent ID Number O AN 1/12 Must use Description: Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to HL Hierarchical Level Code M ID 1/2 Must use Description: Code defining the characteristic of a level in a hierarchical structure CodeList Summary (Total Codes: 250, Included: 1) P Pack 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. 2. The HL segment defines a top-down/left-right ordered structure. 3. 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. 4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. 5. 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. 6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment. Target Canada 22 Ver 5010

27 REF Reference Information Pos: 1500 Max: >1 Detail - Optional Loop: HL Elements: 2 User Option (Usage): Used Purpose: To specify identifying information ***************************** REF Segment Example REF*LT* Prefer lot number at pack level, will accept at item level **************************** REF Reference Identification Qualifier M ID 2/3 Must use Description: Code qualifying the Reference Identification CodeList Summary (Total Codes: 1731, Included: 1) LT Lot Number REF Reference Identification X AN 1/50 Used Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Syntax Rules: 1. R At least one of REF02 or REF03 is required. Semantics: 1. REF04 contains data relating to the value cited in REF02. Target Canada 23 Ver 5010

28 MAN Marks and Numbers Information Pos: 1900 Max: >1 Detail - Optional Loop: HL Elements: 3 User Option (Usage): Must use Purpose: To indicate identifying marks and numbers for shipping containers *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data. ************************ MAN01 must be 'GM' or AA at Pack Level when a Tare Segment is not present. Sample MAN Segments: MAN*GM* (Must be a unique # per shipping container). MAN*AA* (Must be a unique # per shipping container). GTIN-14: 14 digit Product Identification Code (aka SCC-14) MAN*UC* (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* (12-digit selling unit UPC code) Ranging MAN Segments: MAN*GM* * MAN02 = First carton barcode of an item. MAN03 = Last carton barcode of same item. ************************ MAN01 88 Marks and Numbers Qualifier M ID 1/2 Must use Description: Code specifying the application or source of Marks and Numbers (87) CodeList Summary (Total Codes: 22, Included: 5) AA EAN.UCC Serial Shipping Container Code (SSCC) EN EAN European Article Number ( ) EAN-13/GTIN-13 Used when case pack is one and selling unit is shipping unit This is a custom Target Canada Code that is not in the original X Code List GM EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier UC U.P.C. Shipping Container Code SCC-14/GTIN-14 UP U.P.C. Consumer Package Code ( ) UCC-12/GTIN-12 Used when case pack is one and selling unit is shipping unit MAN02 87 Marks and Numbers M AN 1/48 Must use Description: Marks and numbers used to identify a shipment or parts of a shipment When GM is present in the MAN01, the value in this field must be 20 digits. MAN03 87 Marks and Numbers O AN 1/48 Used Description: Marks and numbers used to identify a shipment or parts of a shipment Syntax Rules: 1. P If either MAN04 or MAN05 is present, then the other is required. 2. C If MAN06 is present, then MAN05 is required. Semantics: 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. Target Canada 24 Ver 5010

29 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/MAN MAN03 and/or MAN06 are only used when sending a range(s) of ID numbers. 3. 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. Target Canada 25 Ver 5010

30 DTM Date/Time Reference Pos: 2000 Max: 10 Detail - Optional Loop: HL Elements: 2 User Option (Usage): Used Purpose: To specify pertinent dates and times ************************* Sample DTM Segment DTM*036* Prefer expiration date at pack level, will accept at item level ************************* DTM Date/Time Qualifier M ID 3/3 Must use Description: Code specifying type of date or time, or both date and time CodeList Summary (Total Codes: 1280, Included: 1) 036 Expiration Description: Date coverage expires DTM Date X DT 8/8 Used Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year Syntax Rules: 1. R At least one of DTM02, DTM03 or DTM05 is required. 2. C If DTM04 is present, then DTM03 is required. 3. P If either DTM05 or DTM06 is present, then the other is required. Target Canada 26 Ver 5010

31 HL Hierarchical Level - Item Pos: 0100 Max: 1 Detail - Mandatory Loop: HL Elements: 3 User Option (Usage): Must use Purpose: To identify dependencies among and the content of hierarchically related groups of data segments *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 ************************ HL Hierarchical ID Number M AN 1/12 Must use Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure HL Hierarchical Parent ID Number O AN 1/12 Must use Description: Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to HL Hierarchical Level Code M ID 1/2 Must use Description: Code defining the characteristic of a level in a hierarchical structure CodeList Summary (Total Codes: 250, Included: 1) I Item 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. 2. The HL segment defines a top-down/left-right ordered structure. 3. 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. 4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. 5. 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. 6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment. Target Canada 27 Ver 5010

32 LIN Item Identification Pos: 0200 Max: 1 Detail - Optional Loop: HL Elements: 7 User Option (Usage): Must use Purpose: To specify basic item identification data *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data. ************************ Always send either Target Canada Article number with a CB qualifier or the assigned U.P.C./EAN number with required qualifier. Sample LIN Segment LIN**CB* LIN**CB* *UP* LIN**UP* ************************ LIN Assigned Identification O AN 1/20 Used Description: Alphanumeric characters assigned for differentiation within a transaction set Must equal the PO101 data element (350) from original 850 PO data for actual article shipped. LIN Product/Service ID Qualifier M ID 2/2 Must use Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) CodeList Summary (Total Codes: 519, Included: 5) CB Buyer's Catalog Number Target Canada Article number in 18 digit format as sent on 850. EN EAN/UCC - 13 Description: Data structure for the 13 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Identification Number (GTIN) EO EAN/UCC - 8 Description: Data structure for the 8 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Identification Number (GTIN) UK GTIN 14-digit Data Structure Description: Data structure for the 14 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Item Number (GTIN) UP UCC - 12 Description: Data structure for the 12 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Identification Number (GTIN). Also known as the Universal Product Code (U.P.C.) LIN Product/Service ID M AN 1/48 Must use Description: Identifying number for a product or service LIN Product/Service ID Qualifier X ID 2/2 Used Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) CodeList Summary (Total Codes: 519, Included: 5) CB Buyer's Catalog Number Target Canada Article number in 18 digit format as sent on 850. EN EAN/UCC - 13 Description: Data structure for the 13 digit EAN.UCC (EAN International.Uniform Target Canada 28 Ver 5010

33 Code Council) Global Trade Identification Number (GTIN) EO EAN/UCC - 8 Description: Data structure for the 8 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Identification Number (GTIN) UK GTIN 14-digit Data Structure Description: Data structure for the 14 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Item Number (GTIN) UP UCC - 12 Description: Data structure for the 12 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Identification Number (GTIN). Also known as the Universal Product Code (U.P.C.) LIN Product/Service ID X AN 1/48 Used Description: Identifying number for a product or service LIN Product/Service ID Qualifier X ID 2/2 Used Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) CodeList Summary (Total Codes: 519, Included: 5) CB Buyer's Catalog Number Target Canada Article number in 18 digit format as sent on 850. EN EAN/UCC - 13 Description: Data structure for the 13 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Identification Number (GTIN) EO EAN/UCC - 8 Description: Data structure for the 8 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Identification Number (GTIN) UK GTIN 14-digit Data Structure Description: Data structure for the 14 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Item Number (GTIN) UP UCC - 12 Description: Data structure for the 12 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Identification Number (GTIN). Also known as the Universal Product Code (U.P.C.) LIN Product/Service ID X AN 1/48 Used Description: Identifying number for a product or service Syntax Rules: 1. P If either LIN04 or LIN05 is present, then the other is required. 2. P If either LIN06 or LIN07 is present, then the other is required. 3. P If either LIN08 or LIN09 is present, then the other is required. 4. P If either LIN10 or LIN11 is present, then the other is required. 5. P If either LIN12 or LIN13 is present, then the other is required. 6. P If either LIN14 or LIN15 is present, then the other is required. 7. P If either LIN16 or LIN17 is present, then the other is required. 8. P If either LIN18 or LIN19 is present, then the other is required. 9. P If either LIN20 or LIN21 is present, then the other is required. 10. P If either LIN22 or LIN23 is present, then the other is required. 11. P If either LIN24 or LIN25 is present, then the other is required. 12. P If either LIN26 or LIN27 is present, then the other is required. 13. P If either LIN28 or LIN29 is present, then the other is required. 14. P If either LIN30 or LIN31 is present, then the other is required. Target Canada 29 Ver 5010