TABLE OF CONTENTS JCPenney Mapping Differences between Versions 3060 and 4030... 1.2 Transaction Set Purpose... 1.3 Pick Pack Shipment Segment Hierarchy... 1.3 Standard Pack Shipment Segment Hierarchy... 1.4 HL Levels and Segment Hierarchy... 1.5 Supplementary 856 Catalog Division Documentation... 1.5 +++++++++++++++++++++++++++++++++++++++ ISA -Envelope Segment... 2.1 GS -Functional Group Segment... 2.1 ST -Start of Ship Notice/Manifest Transaction Set... 2.1 BSN -Ship Notice Number, Date and Time and HL Code... 2.2 HL -Start of Shipment Level and HL Dependencies... 2.2 TD1 -Transportation Packaging, Weight, and Cartons... 2.2 TD5 -Carrier and Sequence of Routing, Port of Discharge... 2.3 REF -Bill of Lading Number... 2.3 REF -Carrier Reference Number (Pro Number)... 2.3 REF -JCP Load ID... 2.3 PER -Vendor Contact... 2.4 DTM -Supplier's Ship Date and Time... 2.4 DTM -Supplier's Estimated Shipment Arrival Date... 2.4 N1 -Initial Ship-To Location Code... 2.4 N1 -Ship From Location or Port of Origin... 2.5 N4 -Ship From City/State/Zipcode... 2.5 HL -Start of Order Level and HL Dependencies... 2.5 PRF -Purchase Order Number and Date, International Import Contract Number... 2.5 PID -Fair Labor Standards Act Compliance... 2.6 TD5 -Shipment Order Status Code... 2.6 REF -JCPenney's Internal Supplier Number... 2.6 REF -Subdivision Number... 2.6 REF -Supplier's Order Number... 2.7 REF -Supplier's Invoice Number... 2.7 REF -Inspection Report Number... 2.7 N1 -Mark-For Location Code... 2.7 N3 -Mark-For Street Address... 2.7 N4 -Mark-For City/State/Zipcode... 2.8 N1 -Bill To Location Code... 2.8 HL -Start of Tare Level and HL Dependencies... 2.9 MAN -Ocean Shipping Container Number... 2.9 HL -Start of Pack Level and HL Dependencies... 2.10 SLN -Individual Component SKUs in a Standard Pack Set... 2.10 PKG -Retail Procedures Compliance Indicator or Catalog Color Coordinate Number... 2.11 MAN -UCC 128 Shipping Container Code Number... 2.11 HL -Start of Item Level and HL Dependencies... 2.11 LIN -SKU Numbers On Ship Notice... 2.12 SN1 -SKU Quantity Shipped and Original Order Quantity... 2.12 SLN -SKUs Within An Assortment... 2.13 TD5 -Shipment Item Status Code... 2.13 CTT -Count of HL Segments... 2.14 SE -End of Ship Notice/Manifest Transaction Set... 2.14 GE -Functional Group Segment... 2.14 IEA -Envelope Segment... 2.14 +++++++++++++++++++++++++++++++++++++++ Pick Pack Shipments... 3.1 Pick Pack Shipment Example... 3.1 Standard Pack Shipments... 3.2 Standard Pack Shipment Example... 3.2 856 Business Examples... 3.3 +++++++++++++++++++++++++++++++++++++++ June 2003 Page 1.1 Section 20 d:\my_docs\4030\856 4030 POM F5 June 03 Page
Page(s) JCPENNEY MAPPING DIFFERENCES BETWEEN VERSIONS 3060 and 4030 Differences NOTE: Beginning with version 4010 of the Standards, all DATE data elements (373) have changed to a min/max of 8/8. The format is CCYYMMDD. Also, note that the maximum use of a segment may have changed due to the explicit declaration of the loop maximum on the Segment Hierarchy page (1.3). 2.1 D/E I10 in ISA11 has been replaced with D/E I65. D/E I14 in ISA15 has been renamed. 2.2 D/E 1005 in BSN05 has a JCP attribute change. 2.3 Segment TD1 usage count has changed. D/E 67 in TD503 has an X12 and JCP attribute change. D/E 127 in the first REF02 has an X12 and JCP attribute change. D/E 127 in REF02 has an X12 attribute change. 2.4 Segment PER has been added. D/E 337 in DTM03 has been added for time D/E 98 in N101 has an X12 attribute change. D/E 93 in N102 has an X12 attribute change. D/E 67 in N104 has an X12 attribute change. 2.5 D/E 367 in PRF06 has a JCP attribute change. D/E 67 in TD503 has an X12 attribute change. 2.6 Segment PID and TD5 have been added. D/E 127 in REF02 has an X12 attribute change. 2.7 D/E 127 in REF02 has an X12 and JCP attribute change. Segment REF has been added for inspection report number. Segment N1, N3 N4 has been added to identify the mark for party. 2.8 D/E 98 in N101 has an X12 attribute change and a new code value. D/E 93 in N102 has an X12 attribute change. D/E 67 in N104 has an X12 attribute change. 2.9 D/E 88 in MAN01 has a new code value. 2.10 D/E 350 in SLN01 has a change to the comment field. D/E 380 in SLN04 has an X12 and JCP attribute change. Composite 0001 in SLN05 has an X12 attribute change. D/E 235 in SLN09 has a new code value. D/E 234 in SLN10, SLN12 and SLN14 has an X12 attribute change. 2.11 Segment PKG has been added. 2.12 D/E 235 in LIN02 has a new code value. D/E 234 in LIN03, LIN05 and LIN07 has an X12 attribute change. D/E 382 in SN102 has a JCP attribute change. D/E 646 in SN104 has an X12 attribute change. D/E 330 in SN105 has an X12 and JCP attribute change. 2.13 D/E 350 in SLN01 has a change to the comment field. D/E 380 in SLN04 has an X12 and JCP attribute change. Composite 0001 in SLN05 has an X12 attribute change. D/E 639 in SLN07 has a new code value. D/E 235 in SLN09 has a new code value. D/E 234 in SLN10, SLN12 and SLN14 has an X12 attribute change. D/E 67 in TD503 has an X12 attribute change. NOTE - Highlighted (shaded) areas of the document reflect changes from the previous version. June 2003 Page 1.2
SEGMENT HIERARCHY Purpose: The 856 is used by a supplier to notify a retailer that merchandise for a specific purchase order has been shipped. Transaction contains information relating to the supplier's shipment, retailer's original order, and also identifies any differences in order quantities requested and actual quantities shipped. ISA -INTERCHANGE CONTROL HEADER GS -FUNCTIONAL GROUP HEADER -------------------------------------Ship Notice/Manifest Segment Hierarchy (Pick Pack)------------------------------------ HEADER Loop Max ST -Start of Purchase Order Transaction Set BSN -Ship Notice Number, Date and Time, and Hierarchical Structure Code DETAIL Shipment HL -Start of Shipment Level and HL Dependencies 200,000 TD1 -Transportation Packaging, Weight, and Cartons TD5 -Carrier and Sequence of Routing, Port of Discharge REF -Bill of Lading Number REF -Carrier Reference Number (Pro Number) REF -JCP Load ID PER -Vendor Contact DTM -Supplier's Ship Date and Time DTM -Supplier's Estimated Shipment Arrival Date N1 -Initial Ship-To Location Code 1 N1 -Ship From Location or Port of Origin 1 N4-Ship From City/State/Zipcode Order HL -Start of Order Level and HL Dependencies 200,000 PRF -Purchase Order Number and Date PID -Fair Labor Standards Act Compliance TD5 -Shipment Order Status Code REF -JCPenney's Internal Supplier Number REF -Subdivision Number REF -Supplier's Order Number REF -Supplier's Invoice Number REF -Inspection Report Number N1 -Mark For Location Code 1 N3-Mark For Street Address N4-Mark For City/State/Zipcode N1 -Bill To Location Code 1 Tare HL -Start of Tare Level and HL Dependencies 200,000 MAN-Ocean Shipping Container Number Pack HL -Start of Pack Level and HL Dependencies 200,000 PKG -Retail Procedures Compliance Indicator or Catalog Color Coordinate Number MAN-UCC 128 Shipping Container Code Number Item HL -Start of Item Level and HL Dependencies 200,000 LIN -SKU Numbers On Ship Notice SN1 -SKU Quantity Shipped and Original Order Quantity SLN -SKUs Within An Assortment TD5 -Shipment Item Status Code TRAILER CTT -Count of HL Segments ----------------------------------------------------------------------------------------------------------------------------------------------- SE -End of Ship Notice/Manifest Transaction Set GE -FUNCTIONAL GROUP TRAILER IEA -INTERCHANGE CONTROL TRAILER June 2003 Page 1.3
SEGMENT HIERARCHY ISA -INTERCHANGE CONTROL HEADER GS -FUNCTIONAL GROUP HEADER --------------------------------- Ship Notice/Manifest Segment Hierarchy (Standard Pack) -------------------------------- HEADER Loop Max ST -Start of Purchase Order Transaction Set BSN -Ship Notice Number, Date and Time, and Hierarchical Structure Code DETAIL Shipment HL -Start of Shipment Level and HL Dependencies 200,000 TD1 -Transportation Packaging, Weight, and Cartons TD5 -Carrier and Sequence of Routing, Port of Discharge REF -Bill of Lading Number REF -Carrier Reference Number (Pro Number) REF -JCP Load ID PER -Vendor Contact DTM -Supplier's Ship Date and Time DTM -Supplier's Estimated Shipment Arrival Date N1 -Initial Ship-To Location Code 1 N1 -Ship From Location or Port of Origin 1 N4-Ship From City/State/Zipcode Order HL -Start of Order Level and HL Dependencies 200,000 PRF -Purchase Order Number and Date PID -Fair Labor Standards Act Compliance TD5 -Shipment Order Status Code REF -JCPenney's Internal Supplier Number REF -Subdivision Number REF -Supplier's Order Number REF -Supplier's Invoice Number REF -Inspection Report Number N1 -Mark For Location Code 1 N3-Mark For Street Address N4-Mark For City/State/Zipcode N1 -Bill To Location Code 1 Tare HL -Start of Tare Level and HL Dependencies 200,000 MAN-Ocean Shipping Container Number Item HL -Start of Item Level and HL Dependencies 200,000 LIN -SKU Numbers On Ship Notice SN1 -SKU Quantity Shipped and Original Order Quantity SLN -SKUs Within An Assortment TD5 -Shipment Item Status Code Pack HL -Start of Pack Level and HL Dependencies 200,000 SLN -Individual Component SKUs in a Standard Pack Set PKG -Retail Procedures Compliance Indicator or Catalog Color Coordinate Number MAN-UCC 128 Shipping Container Code Number TRAILER CTT -Count of HL Segments ----------------------------------------------------------------------------------------------------------------------------------------------- SE -End of Ship Notice/Manifest Transaction Set GE -FUNCTIONAL GROUP TRAILER IEA -INTERCHANGE CONTROL TRAILER June 2003 Page 1.4
HL Levels and Segment Hierarchy PROCEDURES AND REQUIREMENTS The sequence in which the various segments are generated will vary depending on whether the shipment is "Pick Pack" or "Standard Pack" structure. Within an 856 shipment (ST to SE) the structure must be the same, either pick pack or standard pack. A specific 856 transaction set can contain data relating to multiple purchase orders, multiple cartons shipped for each purchase order, and multiple SKUs within each carton. An HL (hierarchical) segment is used to identify the different levels of data (e.g., shipment, order, carton, item level). BSN05 identifies whether the shipment is pick pack or standard pack structure. Supplementary 856 Catalog Division Documentation Examples of how the ship notice/manifest (856), order status inquiry (869), and order status report (870) are used in relationship to JCPenney Catalog purchase orders are explained in a separate document called "Catalog Purchase Order Follow Up (POF) Supplier Procedures". If you have any questions, call JCPenney EDI Support (972-431-7301). June 2003 Page 1.5
Segment: ISA - INTERCHANGE CONTROL HEADER Level: ENVELOPE Loop: Max Use: 1 Usage: MANDATORY PURPOSE: To start and identify an interchange of one or more functional groups and interchange related control. ISA01 I01 Authorization Information Qualifier M ID 2/2 "00" (No Authorization Information) ISA02 I02 Authorization Information M AN 10/10 Ten blank positions. ISA03 I03 Security Information Qualifier M ID 2/2 "00" (No Security Information) ISA04 I04 Security Information M AN 10/10 Ten blank positions. ISA05 I05 Interchange ID Qualifier M ID 2/2 Advise DUNS, Comm ID or SCAC number. ISA06 I06 Interchange Sender ID M AN 15/15 ISA07 I05 Interchange ID Qualifier M ID 2/2 "08" (Communication ID) ISA08 I07 Interchange Receiver ID M AN 15/15 See note. ISA09 I08 Interchange Date M DT 6/6 ISA10 I09 Interchange Time M TM 4/4 ISA11 I65 Repetition Separator M ID 1/1 ISA12 I11 Interchange Version ID M ID 5/5 ISA13 I12 Interchange Control Number M N0 9/9 ISA14 I13 Acknowledgment Requested M ID 1/1 0 (No Acknowledgment Requested) ISA15 I14 Usage Indicator M ID 1/1 ISA16 I15 Component Element Separator M AN 1/1 ISA08 - JCPenney will use the following Receiver-IDs: 6111355005 (Retail), 6111355006 (Catalog), 6111355016 (Indirect Imports), 6111355017 (DFW). Segment: GS - FUNCTIONAL GROUP HEADER Level: GROUP Loop: Max Use: 1 Usage: MANDATORY PURPOSE: To start and identify a functional group of related transaction sets and provide control and application identification information. GS01 479 Functional ID M ID 2/2 "SH" (Ship Notice/Manifest) GS02 142 Application Sender's Code M AN 2/15 M AN 2/10 Same ID as ISA06. GS03 124 Application Receiver's Code M AN 2/15 M AN 10/10 Same ID as ISA08. GS04 373 Date M DT 8/8 GS05 337 Time M TM 4/8 GS06 28 Group Control Number M N0 1/9 GS07 455 Responsible Agency Code M ID 1/2 GS08 480 Version M AN 1/12 Segment: ST - TRANSACTION SET HEADER Level: HEADER Loop: Max Use: 1 Usage: MANDATORY PURPOSE: To indicate the start of a Ship Notice/Manifest transaction set and to assign a control number. ST01 143 Transaction Set ID M ID 3/3 "856" ST02 329 Transaction Set Control Number M AN 4/9 June 2003 Page 2.1
Segment: BSN - BEGINNING SEGMENT Level: HEADER Loop: Max Use: 1 Usage: MANDATORY PURPOSE: To identify ship notice number, date, time, and hierarchical structure code. BSN01 353 Transaction Set Purpose Code M ID 2/2 "00" (Original) BSN02 396 Shipment Identification M AN 2/30 Ship notice number BSN03 373 Date M DT 8/8 Ship Notice Date BSN04 337 Time M TM 4/8 Ship Notice Time BSN05 1005 Hierarchical Structure Code O ID 4/4 M ID 4/4 "0001" (Shipment, Order, Packaging, Item) "0002" (Shipment, Order, Item, Packaging) BSN05 - Code '0001' is used for Pick and Pack Structure; code '0002' for Standard Carton Pack Structure. Segment: HL - HIERARCHICAL LEVEL Loop: HL Max Use: 1 Usage: MANDATORY PURPOSE: To identify the start of the shipment level and hierarchical level dependencies. HL01 628 Hierarchical ID Number M AN 1/12 Shipment level is "1". HL02 734 Hierarchical Parent ID Number O AN 1/12 Not used by VICS. HL03 735 Hierarchical Level Code M ID 1/2 "S" (Shipment) NOTE - HL02 is not used for the first HL segment of the transaction set, since it has no parent relationship. It is used in the other HL levels of the transaction. Segment: TD1 - CARRIER DETAILS Loop: HL Max Use: 20 Usage: REQUIRED PURPOSE: To specify transportation packaging, weight, and number of cartons shipped. TD101 103 Packaging Code O AN 3/5 M AN 3/5 TD102 80 Lading Quantity C N0 1/7 M N0 1/7 TD103 23 Commodity Code Qualifier O ID 1/1 Not used by VICS. TD104 22 Commodity Code C AN 1/30 Not used by VICS. TD105 79 Lading Description O AN 1/50 Not used by VICS. TD106 187 Weight Qualifier O ID 1/2 M ID 1/1 "G" (Gross Weight) TD107 81 Weight C R 1/10 M R2 1/8 TD108 355 Unit of Measure Code C ID 2/2 M ID 2/2 "LB" (Pounds) June 2003 Page 2.2
Segment: TD5 - CARRIER DETAILS PURPOSE: To specify the carrier, sequence of routing and port of discharge. TD501 133 Routing Sequence Code O ID 1/2 TD502 66 Identification Code Qualifier C ID 1/2 M ID 1/2 "2" (Standard Carrier Alpha Code) "91" (Assigned by Seller) See note. TD503 67 Identification Code C AN 2/80 M AN 2/80 SCAC code. See note. TD504 91 Transportation Method/Type Code C ID 1/2 See note. TD505 387 Routing C AN 1/35 M AN 1/35 Original carrier. TD506 368 Shipment/Order Status Code C ID 2/2 Not used by JCP. TD507 309 Location Qualifier O ID 1/2 O ID 2/2 "PE" Port of Entry TD508 310 Location Identifier C AN 1/30 Port of discharge TD502 - Code "91" is only used for Indirect Imports, and is limited to identifying ocean vessel carriers. TD503 - To obtain the SCAC code list for all carriers contact: National Motor Freight Trucking Association 2200 Mill Road Alexandria, VA 22314 TD504 - If utilizing a parcel service (UPS, FedEx, etc.), use code "U" (Private Parcel Service). For ocean vessel shipments to JCP Wholesale Distribution Centers, use code "S" (Ocean). TD507&8 - Used only for Indirect Imports, and is limited to ocean vessel shipments referencing port of discharge. Segment: REF - REFERENCE IDENTIFICATION PURPOSE: To specify bill of lading number. REF01 128 Reference Identification Qualifier M ID 2/3 "BM" (Bill of Lading Number) REF02 127 Reference Identification C AN 1/50 M AN 1/17 Bill of lading number. REF02 - Bill of lading number is "0" if TD504 is code "U" (Private Parcel Service). Segment: REF - REFERENCE IDENTIFICATION Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To specify carrier reference number (PRO number). REF01 128 Reference Identification Qualifier M ID 2/3 "CN" (Carrier's Reference Number) REF02 127 Reference Identification C AN 1/50 M AN 1/10 Carrier reference number. Segment: REF - REFERENCE IDENTIFICATION Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To specify the JCP load identification or Authorization number. REF01 128 Reference Identification Qualifier M ID 2/3 PUA (Pick Up Appointment Number); REF02 127 Reference Identification C AN 1/50 JCP load ID or Authorization number. June 2003 Page 2.3
Segment: PER - ADMINISTRATIVE COMMUNICATION CONTACT Loop: Max Use: 1 Usage: REQUIRED PURPOSE: To specify the Supplier contact information. PER01 366 Contact Function Code M ID 2/2 "IC" (Information Contact) PER02 93 Name O AN 1/60 PER03 365 Communication Number Qualifier C ID 2/2 M ID 2/2 "EM" (Electronic Mail) PER04 364 Communication Number C AN 1/256 M AN 1/80 Segment: DTM - DATE/TIME REFERENCE PURPOSE: To specify supplier's ship date. DTM01 374 Date/Time Qualifier M ID 3/3 "011" (Shipped) DTM02 373 Date C DT 8/8 M DT 8/8 Date shipped. DTM03 337 Time C TM 4/8 M TM 4/4 Time shipped (HHMM). Segment: DTM - DATE/TIME REFERENCE Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To specify supplier's estimated shipment arrival date. DTM01 374 Date/Time Qualifier M ID 3/3 "067" (Current Schedule Delivery) DTM02 373 Date C DT 8/8 M DT 8/8 Estimated shipment arrival date. Segment: N1 - NAME Loop: HL/N1 Max Use: 1 Usage: REQUIRED PURPOSE: To specify initial ship to (ST) location code for the shipment. N101 98 Entity Identifier Code M ID 2/3 "ST" (Ship To) N102 93 Name C AN 1/60 Not used by JCP. N103 66 Identification Code Qualifier C ID 1/2 M ID 2/2 "92" (Assigned By Buyer) N104 67 Identification Code C AN 2/80 M AN 5/6 Ship to location. See note. N104 - The ship to location code specified at this shipment level should contain the same ship to location code as specified at the order level if the shipment is sent directly to the ship to location as specified on the purchase order. If the shipment is not sent directly to the ship to location code on the purchase order, then this location code should identify the initial shipping location code (PEPS center, consolidator, etc.). June 2003 Page 2.4
Segment: N1 - NAME Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To identify supplier ship point location, or.the actual port of origin for the shipment N101 98 Entity Identifier Code M ID 2/3 "SF" (Ship From) N102 93 Name C AN 1/60 N103 66 Identification Code Qualifier C ID 1/2 M ID 2/2 "92" (Assigned By Buyer) N104 67 Identification Code C AN 2/80 M AN 2/17 Port of origin. N103&04 Fields are only used for Indirect Imports to specify the originating location of the ocean shipment, e.g. actual port of origin. Segment: N4 - GEOGRAPHIC LOCATION Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To identify the supplier geographic ship point. N401 19 City Name O AN 2/30 M AN 2/19 N402 156 State/Province Code O ID 2/2 M ID 2/2 N403 116 Postal Code O ID 3/15 M ID 5/9 N404 26 Country Code O ID 2/3 O ID 2/2 Segment: HL - HIERARCHICAL LEVEL Loop: HL Max Use: 1 Usage: MANDATORY PURPOSE: To identify the start of the order level and hierarchical level dependencies. HL01 628 Hierarchical ID Number M AN 1/12 See note. HL02 734 Hierarchical Parent ID Number O AN 1/12 M AN 1/12 See note. HL03 735 Hierarchical Level Code M ID 1/2 "O" (Order) HL01 - The value assigned to the first HL segment (Shipment level) will be "1", and is incremented by one for each subsequent HL segment within the transaction set. HL02 - Identifies the hierarchical ID number of the HL segment which the current HL segment is subordinate to (child of). Segment: PRF - PURCHASE ORDER REFERENCE PURPOSE: To identify purchase order number and date, and specify international import contract number. PRF01 324 Purchase Order Number M AN 1/22 M AN 8/12 See note. PRF02 328 Release Number O AN 1/30 Not used by JCP. PRF03 327 Change Order Sequence Number O AN 1/8 Not used by VICS. PRF04 373 Date O DT 8/8 Date is optional. PRF05 350 Assigned Identification O AN 1/20 Not used by JCP. PRF06 367 Contract Number O AN 1/30 O AN 12/12 See note. PRF01 For core furniture orders only, add the string 0500 to the end of the PO number. PRF06 - International orders may not have a purchase order number, only an import contract number. In this event, place a "0" in PRF01 and the appropriate import contract number in PRF06. June 2003 Page 2.5
Segment: PID - PRODUCT/ITEM DESCRIPTION Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To specify Fair Labor Standards compliance for all products in order. PIDO1 349 Item Description Type M ID 1/1 "S" (Structured (From Industry Code List)) PIDO2 750 Product Characteristic Code O ID 2/3 Not used by VICS. PIDO3 559 Agency Qualifier Code C ID 2/2 M ID 2/2 "VI" (VICS) PIDO4 751 Product Description Code C AN 1/12 M AN 2/2 FL (Compliant with Fair Labor Standards Act) Segment: TD5 - CARRIER DETAILS Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To specify shipment order status for a purchase order. TD501 133 Routing Sequence Code O ID 1/2 Not used by VICS. TD502 66 Identification Code Qualifier C ID 1/2 Not used by VICS. TD503 67 Identification Code C AN 2/80 Not used by VICS. TD504 91 Transportation Method/Type Code C ID 1/2 Not used by VICS. TD505 387 Routing C AN 1/35 Not used by VICS. TD506 368 Shipment/Order Status Code C ID 2/2 M ID 2/2 "BP" (Shipment partial, back order to follow) "CC" (Shipment complete) "CP" (Partial shipment, considered no back order) "CS" (Shipment complete with substitution) "DE" (Deleted Order) LS (Last Shipment) "SS" (Split Shipment) Segment: REF - REFERENCE IDENTIFICATION PURPOSE: To identify JCPenney's internal supplier number. REF01 128 Reference Identification Qualifier M ID 2/3 "IA" (Internal Vendor Number) REF02 127 Reference Identification C AN 1/50 M N0 6/6 JCP six digit supplier number. Segment: REF - REFERENCE IDENTIFICATION PURPOSE: To identify subdivision number. REF01 128 Reference Identification Qualifier M ID 2/3 "DP" (Department Number) REF02 127 Reference Identification C AN 1/50 M N0 3/3 Subdivision number. June 2003 Page 2.6
Segment: REF - REFERENCE IDENTIFICATION PURPOSE: To identify suppliers order number. REF01 128 Reference Identification Qualifier M ID 2/3 "VN" (Vendor Order Number) REF02 127 Reference Identification C AN 1/50 M N0 1/50 Suppliers order number. See note. REF02 - If the order number you send is more than 15 positions, we will return the right most 15 positions to you in an Order Status Inquiry transaction (869). For example, if your order number is 12345678901234567 we will send 345678901234567. NOTE - For retail orders this segment is optional. Segment: REF - REFERENCE IDENTIFICATION Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To identify suppliers invoice number. REF01 128 Reference Identification Qualifier M ID 2/3 "IV" (Seller's Invoice Number) REF02 127 Reference Identification C AN 1/50 M N0 1/50 Suppliers invoice number. Segment: REF - REFERENCE IDENTIFICATION Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To identify the QC inspection report number for indirect imports. REF01 128 Reference Identification Qualifier M ID 2/3 "IP" (Inspection Report Number) REF02 127 Reference Identification C AN 1/50 NOTE This segment is used for indirect import orders only. Segment: N1 - NAME Loop: HL/N1 Max Use: 1 Usage: REQUIRED PURPOSE: To identify the mark for party. N101 98 Entity Identifier Code M ID 2/3 "Z7" (Mark-for Party) N102 93 Name C AN 1/60 Not used by JCP. N103 66 Identification Code Qualifier C ID 1/2 M ID 2/2 "92" (Assigned By Buyer) N104 67 Identification Code C AN 2/80 M N0 5/6 Store number. NOTE - This segment is optional for Indirect Imports to JCP Wholesale Distribution Centers. Segment: N3 - ADDRESS INFORMATION Loop: N1 Max Use: 2 Usage: OPTIONAL PURPOSE: To specify the mark for party address. N301 166 Address Information M AN 1/55 N302 166 Address Information O AN 1/55 June 2003 Page 2.7
Segment: N4 - GEOGRAPHIC LOCATION Loop: N1 Max Use: 1 Usage: OPTIONAL PURPOSE: To specify the mark for party geographic location. N401 19 City Name O AN 2/30 M AN 2/19 N402 156 State/Province Code O ID 2/2 M ID 2/2 N403 116 Postal Code O ID 3/15 M ID 5/9 N404 26 Country Code O ID 2/3 O ID 2/2 Segment: N1 - NAME Loop: HL/N1 Max Use: 1 Usage: REQUIRED PURPOSE: To identify the Bill-To party for the purchase order. N101 98 Entity Identifier Code M ID 2/3 "BT" (Bill-to-Party) N102 93 Name C AN 1/60 Not used by JCP. N103 66 Identification Code Qualifier C ID 1/2 M ID 2/2 "92" (Assigned By Buyer) N104 67 Identification Code C AN 2/80 M N0 5/6 Store number. See note. N104 - For Factory Ship or DFW Furniture, data element will contain the store number of where the order originated; i.e., 91322. June 2003 Page 2.8
NOTE The TARE LEVEL is only used and required for Indirect Import Ocean Shipments. Segment: HL - HIERARCHICAL LEVEL Level: TARE Loop: HL Max Use: 1 Usage: MANDATORY PURPOSE: To identify the start of the tare level and hierarchical level dependencies. HL01 628 Hierarchical ID Number M AN 1/12 See note. HL02 734 Hierarchical Parent ID Number O AN 1/12 M AN 1/12 See note. HL03 735 Hierarchical Level Code M ID 1/2 "T" (Shipping Tare) HL01 - The value assigned to the first HL segment (Shipment level) will be "1", and is incremented by one for each subsequent HL segment within the transaction set. HL02 - Identifies the hierarchical ID number of the HL segment which the current HL segment is subordinate to (child of). Segment: MAN - MARKS AND NUMBERS Level: TARE PURPOSE: To identify the Indirect Import Ocean Shipping Container number. MAN01 88 Marks and Numbers Qualifier M ID 1/2 M ID 2/2 "SM" (Shipper Assigned) MAN02 87 Marks and Numbers M AN 1/48 M AN 1/30 Unique number for each Ocean Shipping Container. June 2003 Page 2.9
IMPORTANT NOTE The segment specification pages have been listed in the sequence required for pick pack shipments. If the shipment is standard pack, the pack level segments "HL" and "MAN" are sent after the item level segments. Segment: HL - HIERARCHICAL LEVEL Level: PACK Loop: HL Max Use: 1 Usage: MANDATORY PURPOSE: To identify the start of the pack level and hierarchical level dependencies. HL01 628 Hierarchical ID Number M AN 1/12 See note. HL02 734 Hierarchical Parent ID Number O AN 1/12 M AN 1/12 See note. HL03 735 Hierarchical Level Code M ID 1/2 "P" (Pack) HL01 - The value assigned to the first HL segment (Shipment level) will be "1", and is incremented by one for each subsequent HL segment within the transaction set. HL02 - Identifies the hierarchical ID number of the HL segment which the current HL segment is subordinate to (child of). Segment: SLN - SUBLINE ITEM DETAIL Level: PACK Loop: HL Max Use: 100 Usage: OPTIONAL PURPOSE: To specify the individual component of the item identified in the LIN segment in the previous item level. This segment is only used in a Standard Pack Structure for sets of items packed in different cartons (lamp and shade). SLN01 350 Assigned ID M AN 1/20 Increment by one starting with one (1). SLN02 350 Assigned ID O AN 1/20 Not used by VICS. SLN03 662 Relationship Code M ID 1/1 "I" (Included) SLN04 380 Quantity C R 1/15 M N0 1/10 SLN05 C001 Composite Unit of Measure C C Composite. -1 355 Unit/Basis for Measurement Code M ID 2/2 "ST" (Set) SLN06 212 Unit Price C R 1/17 Not used by VICS. SLN07 639 Basis of Unit Price Code O ID 2/2 Not used by VICS. SLN08 662 Relationship Code O ID 1/1 Not used by VICS. SLN09 235 Product/Service ID Qualifier C ID 2/2 M ID 2/2 "IN" (Buyers Item Number) SLN10 234 Product/Service ID C AN 1/48 M AN 9/13 Retail. See note. SLN11 235 Product/Service ID Qualifier C ID 2/2 "UP" (U.P.C. Consumer Package Code) SLN12 234 Product/Service ID C AN 1/48 C AN 12/12 U.P.C. number assigned to SKU in SLN10. SLN13 235 Product/Service ID Qualifier C ID 2/2 "EN" (European Article Number) SLN14 234 Product/Service ID C AN 1/48 C AN 13/13 EAN number assigned to SKU in SLN10. SLN10 - If SLN is being sent to denote an individual component, send the lot/line/size description in the following format: AAAABBBBCCCCC where AAAA = lot number, BBBB = line number, CCCCC = size desc. NOTE - This segment, when used in a Standard Carton Pack Structure at the Pack Level, may only be used to specify an individual component of the item identified in the LIN segment in the previous item level. The quantity specified in SN102, at the Item Level, represents the number of sets, and SN103 will contain code ST, to identify it as a set. Each subsequent MAN Segment, within this PACK Level, identifies the carton ID for each component identified in the SLN Segment. Additional Pack Level SLN segments and MAN segments are used to represent each different component of the SKU. June 2003 Page 2.10
Segment: PKG MARKING, PACKAGING, LOADING Level: PACK Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To identify Catalog s Color Coordinate number or Retail s floor ready procedures compliance. PKG01 349 Item Description Type C ID 1/1 M ID 1/1 F (Free-Form) PKG02 753 Packaging Characteristic Code O ID 1/5 OPI (Optional Procedure Indicator) PKG03 559 Agency Qualifier Code C ID 2/2 Not used by JCP. PKG04 754 Packaging Description Code C AN 1/7 Not used by JCP. PKG05 352 Description C AN 1/80 M N0 1/2 Retail - Y Catalog - 45 or 50 or 55 NOTE Retail shipments will use PKG01, PKG02 and PKG05. Catalog shipments for Color Coordinate program will use PKG01 and PKG05. Segment: MAN - MARKS AND NUMBERS Level: PACK PURPOSE: To identify the UCC 128 serial shipping container code number. MAN01 88 Marks and Numbers Qualifier M ID 1/2 "GM" (UCC 128 Serial Shipping Container Code Format) MAN02 87 Marks and Numbers M AN 1/48 M AN 20/20 Unique number for each 128 label. See note. MAN02 - The format of the UCC 128 shipping container number is 'AABCCCCCCCDDDDDDDDDE', where AA = UCC 128 serial shipping container code qualifier, B = extension digit, CCCCCCC = UCC manufacturing ID number (including number system character preceded by zero), DDDDDDDDD = shipping container serial number, E = mod 10 check digit character. NOTE - For Retail shipments, we will not accept an 856 if you do not have the ability to identify each carton with a scannable UCC 128 shipping container serial number. For a detail write-up on scannable UCC 128 shipping container code number specifications, contact the Uniform Code Council (800-543-8137). Segment: HL - HIERARCHICAL LEVEL Level: ITEM Loop: HL Max Use: 1 Usage: MANDATORY PURPOSE: To identify the start of the item level and hierarchical level dependencies. HL01 628 Hierarchical ID Number M AN 1/12 See note. HL02 734 Hierarchical Parent ID Number O AN 1/12 M AN 1/12 See note. HL03 735 Hierarchical Level Code M ID 1/2 "I" (Item) HL01 - The value assigned to the first HL segment (Shipment level) will be "1", and is incremented by one for each subsequent HL segment within the transaction set. HL02 - Identifies the hierarchical ID number of the HL segment which the current HL segment is subordinate to (child of). June 2003 Page 2.11
Segment: LIN - ITEM IDENTIFICATION Level: ITEM PURPOSE: To specify SKU number, and U.P.C. or EAN numbers. There is one LIN segment for each SKU. LIN01 350 Assigned ID O AN 1/20 Not used by JCP. LIN02 235 Product/Service ID Qualifier M ID 2/2 "IN" (Buyers Item Number) LIN03 234 Product/Service ID M AN 1/48 M AN 9/13 Retail. See note. M AN 11/11 Catalog. LIN04 235 Product/Service ID Qualifier C ID 2/2 "UP" (U.P.C. Consumer Package Code) Note LIN05 234 Product/Service ID C AN 1/48 C AN 12/12 U.P.C. number. LIN06 235 Product/Service ID Qualifier C ID 2/2 "EN" (European Article Number). See note. LIN07 234 Product/Service ID C AN 1/48 C AN 13/13 EAN number. LIN03 - If purchase order is for Retail merchandise, send the lot/line/size description in the following format: AAAABBBBCCCCC where AAAA = lot number, BBBB = line number, CCCCC = size description. For Catalog merchandise, we will send lot/sku in the following format: AAAAAAABBBB where AAAAAAA = lot number, BBBB = SKU number. LIN04 - U.P.C. numbers are used on a selective basis. U.P.C. numbers will only be sent for Retail orders and correspond to the SKU in LIN03. LIN06 - EAN numbers are used on a selective basis. EAN numbers will only be sent for Retail orders and correspond to the SKU in LIN03. Do not send both EAN and U.P.C. numbers, only one or the other. Segment: SN1 - ITEM DETAIL (SHIPMENT) Level: ITEM PURPOSE: To specify SKU quantity shipped and original purchase order quantity. SN101 350 Assigned ID O AN 1/20 Not used by VICS. SN102 382 Number of Units Shipped M R 1/10 M N0 1/10 Number of sellable units. SN103 355 Unit Of Measure Code M ID 2/2 "AS" (Assortment); "BX" (Box); "CA" (Case); "EA" (Each); "FT" (Feet); "PK" (Package); "PC" (Piece); "PR" (Pair); "RL" (Roll); "ST" (Set); "YD" (Yard) SN104 646 Quantity Shipped to Date O R 1/15 Not used by JCP. SN105 330 Quantity Ordered C R 1/15 O N0 1/10 Original quantity ordered less cancellations. SN106 355 Unit Of Measure Code C ID 2/2 O ID 2/2 "AS" (Assortment); "BX" (Box); "CA" (Case); "EA" (Each); "FT" (Feet); "PK" (Package); "PC" (Piece); "PR" (Pair); "RL" (Roll); "ST" (Set); "YD" (Yard) SN105 -The quantity ordered comes from the original quantity on the purchase order, less any cancellations the supplier makes to the original quantity. This D/E and SN106 are required for Catalog. June 2003 Page 2.12
Segment: SLN - SUBLINE ITEM DETAIL Level: ITEM Loop: HL Max Use: 100 Usage: OPTIONAL PURPOSE: To specify the component SKUs within an assortment. There is one SLN segment for each SKU within an assortment. The component number is specified in the preceding LIN segment. SLN01 350 Assigned ID M AN 1/20 Increment by one starting with one (1). SLN02 350 Assigned ID O AN 1/20 Not used by VICS. SLN03 662 Relationship Code M ID 1/1 "I" (Included) SLN04 380 Quantity C R 1/15 M N0 1/10 See note. SLN05 C001 Composite Unit of Measure C C Composite. -1 355 Unit or Basis for Measurement Code M ID 2/2 "AS" (Assortment); "BX" (Box); "CA" (Case); "EA" (Each); "FT" (Feet); "PK" (Package); "PC" (Piece); "PR" (Pair); "RL" (Roll); "ST" (Set); "YD" (Yard) SLN06 212 Unit Price C R 1/17 C R2 1/17 SLN07 639 Basis of Unit Price Code O ID 2/2 WH (Wholesale) SLN08 662 Relationship Code O ID 1/1 Not used by VICS. SLN09 235 Product/Service ID Qualifier C ID 2/2 M ID 2/2 "IN" (Buyers Item Number) SLN10 234 Product/Service ID C AN 1/48 M AN 9/13 Retail. See note. SLN11 235 Product/Service ID Qualifier C ID 2/2 "UP" (U.P.C. Consumer Package Code) Note SLN12 234 Product/Service ID C AN 1/48 C AN 12/12 U.P.C. number assigned to SKU in SLN10. SLN13 235 Product/Service ID Qualifier C ID 2/2 "EN" (European Article Number). See note. SLN14 234 Product/Service ID C AN 1/48 C AN 13/13 EAN number assigned to SKU in SLN10. SLN04 - The quantity should reflect the number of sellable units and not the physical count of items. SLN10 - If SLN is being sent to denote a component, send component's lot/line/size description in the following format: AAAABBBBCCCCC where AAAA = lot number, BBBB = line number, CCCCC = size desc. NOTE - Segment is only sent for Retail merchandise. Segment: TD5 - CARRIER DETAILS Level: ITEM PURPOSE: To specify ship/order status code for SKUs that have not been shipped per the original purchase order. TD501 133 Routing Sequence Code O ID 1/2 Not used by VICS. TD502 66 Identification Code Qualifier C ID 1/2 Not used by VICS. TD503 67 Identification Code C AN 2/80 Not used by VICS. TD504 91 Transportation Method/Type Code C ID 1/2 Not used by VICS. TD505 387 Routing C AN 1/35 Not used by VICS. TD506 368 Shipment/Order Status Code C ID 2/2 M ID 2/2 "BP" (Shipment partial, back order to follow) "CC" (Shipment complete) "CP" (Partial shipment, considered no back order) "CS" (Shipment complete with substitution) IC (Item canceled) June 2003 Page 2.13
Segment: CTT - TRANSACTION TOTALS Level: TRAILER Loop: Max Use: 1 Usage: REQUIRED PURPOSE: Count of HL segments in ship notice/manifest transaction set. CTT01 354 Number Of Line Items M N0 1/6 Number of HL segments in the transaction. Segment: SE - TRANSACTION SET TRAILER Level: TRAILER Loop: Max Use: 1 Usage: MANDATORY PURPOSE: To indicate the end of a Ship Notice/Manifest transaction set and provide a count of the transmitted segments, including the beginning (ST) and ending (SE) segments. SE01 96 Number Of Included Segments M N0 1/10 Count of all segments including ST and SE. SE02 329 Transaction Set Control Number M AN 4/9 Same number as in ST02. Segment: GE - FUNCTIONAL GROUP TRAILER Level: GROUP Loop: Max Use: 1 Usage: MANDATORY PURPOSE: To define the end of a functional group of related transaction sets. GE01 97 No. of Included Transaction Sets M N0 1/6 GE02 28 Group Control Number M N0 1/9 Same number as in GS06. Segment: IEA - INTERCHANGE CONTROL TRAILER Level: ENVELOPE Loop: Max Use: 1 Usage: MANDATORY PURPOSE: To define the end of an interchange of one or more functional groups and interchange related control. IEA01 I16 Number Of Included Groups M N0 1/5 IEA02 I12 Interchange Control Number M N0 9/9 Same number as in ISA13. June 2003 Page 2.14
MERCHANDISE SHIPMENT PACKAGING STRUCTURES Pick Pack Shipments This type of shipment is most prevalent in the soft goods area. The pick pack environment is where different items are picked to fill a carton. An example would be a carton containing multiple colors and sizes of a specific style women's dress, with variable quantities for each color and size. Pick Pack Shipment Example The illustration below shows the sequence in which various HL segments should be generated for a pick pack type shipment. The illustration assumes that the shipment was for 2 purchase orders. The first purchase order has 2 cartons with 3 unique SKUs in the first carton and 2 unique SKUs in the second carton. The second purchase order has 3 cartons with 3 unique SKUs in the first 2 cartons and 1 SKU in the last carton. Each box represents one hierarchical level (one HL segment followed by data elements). The number in the top left corner is the hierarchical sequence number (the number in HL01). The number in the top right corner is the parent ID (the number in HL02). 01 Shipment 02 01 10 01 Order 1 Order 2 03 02 07 02 11 10 15 10 19 10 Carton 1 Carton 2 Carton 3 Carton 4 Carton 5 04 SKU A 03 08 07 12 11 16 15 20 19 SKU D SKU P SKU S SKU V 05 03 09 07 13 11 17 15 SKU B SKU E SKU Q SKU T 06 03 SKU C 14 11 SKU R 18 15 SKU U June 2003 Page 3.1
Standard Pack Shipments This type of shipment is most prevalent in the hard goods area. The standard pack environment is where a carton has been pre-packed and usually contains one or more pieces of a specific item. An example would be a carton containing 10 bowls of a specific style. If a shipment was for 70 bowls, there would be 7 standard pack cartons required for the shipment. Standard Pack Shipment Example The illustration below shows the sequence in which various HL segments should be generated for a standard pack type shipment. The illustration assumes that the shipment was for 2 purchase orders. The first purchase order contained 5 cartons (cartons 1 to 5), the second purchase order contained 7 cartons (cartons 6 to 12). The contents of cartons 1, 2 and 3 were identical, each of these cartons contained identical quantities of SKU A. Cartons 4 and 5, contain identical quantities of SKU B. Cartons 6, 7, and 8, contain identical quantities of SKU C. Cartons 9, 10, and 11, contain identical quantities of SKU D, and carton 12 contains SKU E. Each box represents one hierarchical level (one HL segment followed by data elements). The number in each box (top left corner) is the hierarchical sequence number (the number in HL01). The number in the top right corner is the parent ID (the number in HL02). 01 Shipment 02 01 10 01 Order 1 Order 2 03 02 07 02 11 10 15 10 19 10 SKU A SKU B SKU C SKU D SKU E 04 03 08 07 12 11 16 15 20 19 Carton 1 Carton 4 Carton 6 Carton 9 Carton 12 05 03 09 07 13 11 17 15 Carton 2 Carton 5 Carton 7 Carton 10 06 03 14 11 18 15 Carton 3 Carton 8 Carton 11 June 2003 Page 3.2
HL RELATIONSHIPS IN THE 856 Business examples for the HL segments used in a Pick Pack structure NOTE - The data element separator is represented by a, the segment terminator is. 1 - ABC supplier has received one purchase order from a single store for 24 pants, all of the same size and color, which are inventoried under 1 SKU number. He picks the 24 pants and can get them in two cartons. His ship notice to the retailer reflects 6 HL segments. HL 1 S Shipment level with hierarchical ID number of 1 (one). HL02 is not used, there is no parent. HL 2 1 O Order level with hierarchical ID number of 2 and HL parent ID number of 1. HL 3 2 P Pack level with hierarchical ID number of 3 and HL parent ID number of 2. HL 4 3 I Item level with hierarchical ID number of 4 and HL parent ID number of 3. HL 5 2 P Pack level with hierarchical ID number of 5 and HL parent ID number of 2. HL 6 5 I Item level with hierarchical ID number of 6 and HL parent ID number of 5. 2 - ABC supplier has received one purchase order from a single store for 12 pants, all of different sizes and colors, which are inventoried under 12 SKU numbers. He picks the 12 pants and can get all of them in one carton. His ship notice to the retailer reflects 15 HL segments. HL 1 S Shipment level with hierarchical ID number of 1 (one). HL02 is not used, there is no parent. HL 2 1 O Order level with hierarchical ID number of 2 and HL parent ID number of 1. HL 3 2 P Pack level with hierarchical ID number of 3 and HL parent ID number of 2. HL 4 3 I Item level (SKU 1) with hierarchical ID number of 4 and HL parent ID number of 3. HL 5 3 I Item level (SKU 2) with hierarchical ID number of 5 and HL parent ID number of 3. HL 6 3 I Item level (SKU 3) with hierarchical ID number of 6 and HL parent ID number of 3. HL 7 3 I Item level (SKU 4) with hierarchical ID number of 7 and HL parent ID number of 3. HL 8 3 I Item level (SKU 5) with hierarchical ID number of 8 and HL parent ID number of 3. HL 9 3 I Item level (SKU 6) with hierarchical ID number of 9 and HL parent ID number of 3. HL 10 3 I Item level (SKU 7) with hierarchical ID number of 10 and HL parent ID number of 3. HL 11 3 I Item level (SKU 8) with hierarchical ID number of 11 and HL parent ID number of 3. HL 12 3 I Item level (SKU 9) with hierarchical ID number of 12 and HL parent ID number of 3. HL 13 3 I Item level (SKU 10) with hierarchical ID number of 13 and HL parent ID number of 3. HL 14 3 I Item level (SKU 11) with hierarchical ID number of 14 and HL parent ID number of 3. HL 15 3 I Item level (SKU 12) with hierarchical ID number of 15 and HL parent ID number of 3. June 2003 Page 3.3
Business examples for the HL segments used in a Pick Pack structure (continued) 3 - ABC supplier has received three purchase orders from the same store for 144 shirts. The first order is 24 white shirts and 24 blue shirts. The second order is for 6 red shirts, 6 orange shirts, 6 yellow shirts, 6 purple shirts, 6 brown shirts, and 6 green shirts. The third order is for 60 black shirts. The orders represent 9 SKU numbers in his inventory. He fills all three orders and can put 12 shirts in a carton. He packs 4 cartons for the first order (12 white, 12 white, 12 blue, 12 blue), 3 cartons for the second order (6 red + 6 orange, 6 yellow + 6 purple, 6 brown + 6 green), and 5 cartons (12 black, 12 black, 12 black, 12 black, 12 black) for the third order. His ship notice to the retailer will reflect 31 HL segments. HL 1 S Shipment level with hierarchical ID number of 1. HL02 is not used, there is no parent. HL 2 1 O Order level (1st order) with hierarchical ID number of 2 and HL parent ID number of 1. HL 3 2 P Pack level (1st order 1st carton) with hierarchical ID number of 3 and HL parent ID number of 2. HL 4 3 I Item level (1st order 1st carton 12 white) with hierarchical ID number of 4 and HL parent ID number of 3. HL 5 2 P Pack level (1st order 2nd carton) with hierarchical ID number of 5 and HL parent ID number of 2. HL 6 5 I Item level (1st order 2nd carton 12 white) with hierarchical ID number of 6 and HL parent ID number of 5. HL 7 2 P Pack level (1st order 3rd carton) with hierarchical ID number of 7 and HL parent ID number of 2. HL 8 7 I Item level (1st order 3rd carton 12 blue) with hierarchical ID number of 8 and HL parent ID number of 7. HL 9 2 P Pack level (1st order 4th carton) with hierarchical ID number of 9 and HL parent ID number of 2. HL 10 9 I Item level (1st order 4th carton 12 blue) with hierarchical ID number of 10 and HL parent ID number of 9. HL 11 1 O Order level (2nd order) with hierarchical ID number of 11 and HL parent ID number of 1. HL 12 11 P Pack level (2nd order 1st carton) with hierarchical ID number of 12 and HL parent ID number of 11. HL 13 12 I Item level (2nd order 1st carton 6 red) with hierarchical ID number of 13 and HL parent ID number of 12. HL 14 12 I Item level (2nd order 1st carton 6 orange) with hierarchical ID number of 14 and HL parent ID number of 12. HL 15 11 P Pack level (2nd order 2nd carton) with hierarchical ID number of 15 and HL parent ID number of 11. HL 16 15 I Item level (2nd order 2nd carton 6 yellow) with hierarchical ID number of 16 and HL parent ID number of 15. HL 17 15 I Item level (2nd order 2nd carton 6 purple) with hierarchical ID number of 17 and HL parent ID number of 15. HL 18 11 P Pack level (2nd order 3rd carton) with hierarchical ID number of 18 and HL parent ID number of 11. HL 19 18 I Item level (2nd order 3rd carton 6 brown) with hierarchical ID number of 19 and HL parent ID number of 18. HL 20 18 I Item level (2nd order 3rd carton 6 green) with hierarchical ID number of 20 and HL parent ID number of 18. HL 21 1 O Order level (3rd order) with hierarchical ID number of 21 and HL parent ID number of 1. HL 22 21 P Pack level (3rd order 1st carton) with hierarchical ID number of 22 and HL parent ID number of 21. HL 23 22 I Item level (3rd order 1st carton 12 black) with hierarchical ID number of 23 and HL parent ID number of 22. HL 24 21 P Pack level (3rd order 2nd carton) with hierarchical ID number of 24 and HL parent ID number of 21. HL 25 24 I Item level (3rd order 2nd carton 12 black) with hierarchical ID number of 25 and HL parent ID number of 24. HL 26 21 P Pack level (3rd order 3rd carton) with hierarchical ID number of 26 and HL parent ID number of 21. HL 27 26 I Item level (3rd order 3rd carton 12 black) with hierarchical ID number of 27 and HL parent ID number of 26. HL 28 21 P Pack level (3rd order 4th carton) with hierarchical ID number of 28 and HL parent ID number of 21. HL 29 28 I Item level (3rd order 4th carton 12 black) with hierarchical ID number of 29 and HL parent ID number of 28. HL 30 21 P Pack level (3rd order 5th carton) with hierarchical ID number of 30 and HL parent ID number of 21. HL 31 30 I Item level (3rd order 5th carton 12 black) with hierarchical ID number of 31 and HL parent ID number of 30. June 2003 Page 3.4