JCPenney 832 Price/Sales Catalog (Out) Version 4030

Transcription

1 TABLE OF CONTENTS Page JCPenney Mapping Differences Between Versions 3060 and Purpose of 832 Transaction Set Price/Sales Catalog Segment Hierarchy ISA -Envelope Segment GS -Functional Group Segment ST -Start of Price/Sales Catalog Transaction Set BCT -Supplier's U.P.C./EAN Catalog ID, JCPenney's Profile ID, Purpose Code LIN -Supplier's Product ID CTT -Count of LIN Segments SE -End of Price/Sales Catalog Transaction Set GE -Functional Group Segment IEA -Envelope Segment Files Used with the 832 Transaction NRF Color Code versus Vendor's Color Code JCPenney Generated 832 Transactions Third Party Network or Supplier Generated 832 Transactions March 2002 Page 1.1 Section 15 d:\my_docs\4030\832 Outbound 4030 F5.DOC

2 JCPENNEY MAPPING DIFFERENCES BETWEEN VERSIONS 3060 AND 4030 Page(s) 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 234 in LIN03 has an X12 attribute change. D/E 235 in LIN02 has code value change. NOTE - Highlighted (shaded) areas of the document reflect changes from the previous version. March 2002 Page 1.2

3 SEGMENT HIERARCHY PURPOSE: This transaction is used by JCPenney and our trading partners to communicate data contents on the Supplier's U.P.C./EAN Catalog and JCPenney's U.P.C./EAN Profile. ISA -INTERCHANGE CONTROL HEADER GS -FUNCTIONAL GROUP HEADER Price/Sales Catalog Segment Hierarchy HEADER ST -Start of Price/Sales Catalog Transaction Set BCT -Supplier's U.P.C./EAN Catalog ID, JCPenney's Profile ID, Purpose Code Loop Max DETAIL Loop Max LIN -Supplier's Product ID >1 TRAILER CTT SE -Count Of LIN Segments -End Of Price/Sales Catalog Transaction Set GE -FUNCTIONAL GROUP TRAILER IEA -INTERCHANGE CONTROL TRAILER March 2002 Page 1.3

4 Segment: ISA - INTERCHANGE CONTROL HEADER Level: ENVELOPE 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 "08" (Communication ID) ISA06 I06 Interchange Sender ID M AN 15/15 See note. ISA07 I05 Interchange ID Qualifier M ID 2/2 Advise DUNS, Comm ID, or SCAC number. ISA08 I07 Interchange Receiver ID M AN 15/15 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 ISA06 - JCPenney will use the following Sender ID: (Retail). Segment: GS - FUNCTIONAL GROUP HEADER Level: GROUP PURPOSE: To start and identify a functional group of related transaction sets and provide control and application identification information. GS Functional ID M ID 2/2 "SC" (Price/Sales Catalog) GS Application Sender's Code M AN 2/15 M AN 10/10 Same ID as ISA06. GS Application Receiver's Code M AN 2/15 M AN 2/10 Same ID as ISA08. GS Date M DT 8/8 GS Time M TM 4/8 GS06 28 Group Control Number M N0 1/9 GS Responsible Agency Code M ID 1/2 GS Version M AN 1/12 Segment: ST - TRANSACTION SET HEADER Level: HEADER PURPOSE: To indicate the start of a purchase order transaction set and to assign a control number. ST Transaction Set ID M ID 3/3 "832" ST Transaction Set Control Number M AN 4/9 March 2002 Page 2.1

5 Segment: BCT - BEGINNING SEGMENT Level: HEADER PURPOSE: To identify supplier's U.P.C./EAN Catalog ID, JCPenney Profile ID, and purpose codes. BCT Catalog Purpose Code M ID 2/2 BCT Catalog Number O AN 1/15 Supplier's U.P.C./EAN Catalog ID. BCT Catalog Version Number O AN 1/15 Not used by JCP. BCT Catalog Revision Number O AN 1/6 Not used by VICS. BCT Unit of Measurement Code O ID 2/2 Not used by VICS. BCT Catalog Number O AN 1/15 JCP U.P.C./EAN Profile ID. BCT Catalog Version Number O AN 1/15 Not used by VICS. BCT Catalog Revision Number O AN 1/6 Not used by VICS. BCT Description O AN 1/80 Not used by JCP. BCT Transaction Set Purpose Code O ID 2/2 M ID 2/2 "02" (Add) "03" (Delete) "13" (Request) BCT06 - If BCT10 is "02" or "03", data element contains JCPenney Retail Comm ID (number in ISA06). If BCT10 is "13", data element is not sent. NOTE - Transaction set purpose code is used as follows: "02" - Add supplier's product ID specified in LIN03 to JCPenney profile. "03" - Delete supplier's product ID specified in LIN03 from JCPenney profile. "13" - Send JCPenney via the 832 transaction set, all U.P.C./EAN codes associated with the supplier's product ID specified in LIN03. Segment: LIN - ITEM IDENTIFICATION DETAIL Level: DETAIL Loop: LIN Max Use: 1 Usage: REQUIRED PURPOSE: To specify supplier's product ID. LIN Assigned Identification O AN 1/20 Not used by JCP. LIN Product/Service ID Qualifier M ID 2/2 "VN" (Vendor's (Seller s) Item Number)) LIN Product/Service ID M AN 1/48 Supplier's product ID number. March 2002 Page 2.2

6 Segment: CTT - TRANSACTION TOTALS Level: TRAILER Loop: Max Use: 1 Usage: OPTIONAL PURPOSE: Count of LIN segments in Price/Sales Catalog transaction set. CTT Number of Line Items M N0 1/6 Segment: SE - TRANSACTION SET TRAILER Level: TRAILER PURPOSE: To indicate the end of a Price/Sales Catalog 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. SE Transaction Set Control Number M AN 4/9 Same number as in ST02 Segment: GE - FUNCTIONAL GROUP TRAILER Level: GROUP 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 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. March 2002 Page 2.3

7 832 REFERENCE INFORMATION Files Used with the 832 Transaction Supplier's U.P.C./EAN Catalog File contains U.P.C./EAN codes of all national brand products a supplier offers to JCPenney. File resides at a third party network or at a supplier's location. JCPenney will request data at the supplier's product ID level or U.P.C./EAN level. JCPenney's U.P.C./EAN Profile File contains the product IDs JCPenney desires automatic U.P.C./EAN updates on. File resides at a third party network or at a supplier's location. JCPenney will add or delete product IDs on the U.P.C./EAN profile. For those product IDs specified on the U.P.C./EAN profile, JCPenney will receive automatic updates whenever U.P.C./EAN codes are added, changed, replaced, deleted, or reissued. NRF Color Code versus Vendor's Color Code VICS guidelines no longer support vendor color codes, and now only recommends NRF color codes. Although JCPenney supports NRF color codes over vendor color codes, we recognize that many suppliers may require a significant amount of time and effort to change over to NRF color codes. Therefore, JCPenney will continue to allow the use of vendor color codes for now. However, it is our intent to discontinue vendor color codes in an upcoming version. March 2002 Page 3.1

8 JCPenney Generated 832 Transactions The following illustrates key contents of various 832 segments for specific JCPenney data requests to the supplier's U.P.C./EAN catalog file and JCPenney's U.P.C./EAN profile. A) Request existing U.P.C./EAN codes on supplier's U.P.C./EAN catalog for a specific product-id BCT06 (retailer ID number) = blank BCT10 (transaction set purpose code) = "13" (Request) LIN02 (product/service ID qualifier) = "VN" (Vendor's (Seller s) Item Number)) LIN03 (product/service ID) = supplier's product ID NOTE - No SSS segment is sent. B) Add supplier's product ID to JCPenney's U.P.C./EAN profile BCT06 (retailer ID number) = " " (JCPenney Retail Comm ID) BCT10 (transaction set purpose code) = "02" (Add) LIN02 (Product/Service ID qualifier) = "VN" (Vendor's (Seller s) Item Number)) LIN03 (Product/Service ID) = supplier's product ID to be added to JCPenney's U.P.C./EAN Profile. NOTE - No SSS segment is sent. NOTE - JCPenney will only request additions to its U.P.C./EAN profile at the supplier's product ID level. C) Delete supplier's product ID from JCPenney's U.P.C./EAN Profile BCT06 (retailer ID number) = " " (JCPenney Retail COMM ID) BCT10 (transaction set purpose code) = "03" (Delete) LIN02 (Product/Service ID qualifier) = "VN" (Vendor's (Seller s) Item Number)) LIN03 (Product/Service ID) = supplier's product ID to be deleted from JCPenney's U.P.C./EAN Profile. NOTE - No SSS segment is sent. NOTE - JCPenney will only request deletions from its U.P.C./EAN profile at the supplier's product ID level. Third Party Network or Supplier Generated 832 Transactions The following illustrates key contents of various 832 segments generated by third party networks or suppliers in response to JCPenney generated 832 U.P.C./EAN related transactions. A) Per JCPenney request (see JCPenney generated example A), send existing U.P.C./EAN codes for a specific product-id on supplier's U.P.C./EAN Catalog. BCT03 (selection code) = selection code BCT06 (retailer ID number) = blank BCT09 (selection code description) = selection code description BCT10 (transaction set purpose code) = "11" (response) March 2002 Page 3.2

9 Third Party Network or Supplier Generated 832 Transactions (continued) LIN02 (product/service ID qualifier) = "VN" (Vendor's (Seller s) Item Number))* LIN03 (product/service ID) = supplier's product ID ** LIN04 (product/service ID qualifier) = "UP" (Universal Product Code) or "EN" (European Article Number)* LIN05 (product/service ID) = U.P.C. or EAN number ** LIN06 (product/service ID qualifier) = "CM" (NRF color code) * LIN07 (product/service ID) = NRF color code ** LIN08 (product/service ID qualifier) = "SM" (size code) * LIN09 (product/service ID) = NRF size code ** * Data can be in LIN02, LIN04, LIN06, OR LIN08. ** Data can be in LIN03, LIN05, LIN07, OR LIN09. B) Per JCPenney's U.P.C./EAN profile, send new U.P.C./EAN codes which have been added to the supplier's U.P.C./EAN catalog. BCT03 (selection code) = selection code BCT06 (retailer ID number) = blank BCT09 (selection code description) = selection code description BCT10 (transaction set purpose code) = "02" (Add) LIN02 (product/service ID qualifier) = "VN" (Vendor's (Seller s) Item Number))* LIN03 (product/service ID) = supplier's product ID ** LIN04 (product/service ID qualifier) = "UP" (Universal Product Code) or "EN" (European Article Number)* LIN05 (product/service ID) = U.P.C. or EAN number ** LIN06 (product/service ID qualifier) = "CM" (NRF color code) * LIN07 (product/service ID) = NRF color code ** LIN08 (product/service ID qualifier) = "SM" (size code) * LIN09 (product/service ID) = NRF size code ** * Data can be in LIN02, LIN04, LIN06, OR LIN08. ** Data can be in LIN03, LIN05, LIN07, OR LIN09. C) Per JCPenney's U.P.C./EAN profile, send U.P.C./EAN codes which are being physically deleted from the supplier's U.P.C./EAN catalog. BCT03 (selection code) = selection code BCT06 (retailer ID number) = blank BCT09 (selection code description) = selection code description BCT10 (transaction set purpose code) = "03" (Delete) LIN02 (product/service ID qualifier) = "VN" (Vendor's (Seller s) Item Number))* LIN03 (product/service ID) = supplier's product ID ** LIN04 (product/service ID qualifier) = "UP" (Universal Product Code) or "EN" (European Article Number)* LIN05 (product/service ID) = U.P.C. or EAN number ** LIN06 (product/service ID qualifier) = "CM" (NRF color code) * LIN07 (product/service ID) = NRF color code ** LIN08 (product/service ID qualifier) = "SM" (size code) * LIN09 (product/service ID) = NRF size code ** * Data can be in LIN02, LIN04, LIN06, OR LIN08. ** Data can be in LIN03, LIN05, LIN07, OR LIN09. NOTE - Prior to physically deleting a U.P.C./EAN code from the U.P.C./EAN catalog, supplier should have previously entered a change, replace, or reissue transaction which specified a discontinue date. March 2002 Page 3.3

10 Third Party Network or Supplier Generated 832 Transactions (continued) D) Per JCPenney's U.P.C./EAN profile, send U.P.C./EAN codes which had one or more descriptive data changes applied to the supplier's U.P.C./EAN catalog BCT03 (selection code) = selection code BCT06 (retailer ID number) = blank BCT09 (selection code description) = selection code description BCT10 (transaction set purpose code) = "04" (change), or "05" (replace), or "18" (reissue). LIN02 (product/service ID qualifier) = "VN" (Vendor's (Seller s) Item Number))* LIN03 (product/service ID) = supplier's product ID ** LIN04 (product/service ID qualifier) = "UP" (Universal Product Code) or "EN" (European Article Number)* LIN05 (product/service ID) = U.P.C. or EAN number ** LIN06 (product/service ID qualifier) = "CM" (NRF color code) * LIN07 (product/service ID) = NRF color code ** LIN08 (product/service ID qualifier) = "SM" (size code) * LIN09 (product/service ID) = NRF size code ** DTM01 (date/time qualifier) = "036" (discontinue date) DTM02 (date) = discontinue date * Data can be in LIN02, LIN04, LIN06, OR LIN08. ** Data can be in LIN03, LIN05, LIN07, OR LIN09. NOTE - Send all other 832 segments. JCPenney will use the data contents of these segments to overlay their existing data contents. E) Per JCPenney's one time verbal request, send existing supplier's U.P.C./EAN cross reference file of JCPenney retail SKU numbers. BCT03 (selection code) = selection code BCT06 (retailer ID number) = "cross reference" BCT09 (selection code description) = selection code description BCT10 (transaction set purpose code) = "11" (response) LIN02 (product/service ID qualifier) = "VN" (Vendor's (Seller s) Item Number))* LIN03 (product/service ID) = SUPPLIER'S PRODUCT ID ** LIN04 (product/service ID qualifier) = "UP" (Universal Product Code) or "EN" (European Article Number)* LIN05 (product/service ID) = U.P.C. or EAN number ** LIN06 (product/service ID qualifier) = "CM" (NRF color code) * LIN07 (product/service ID) = NRF color code ** LIN08 (product/service ID qualifier) = "SM" (size code) * LIN09 (product/service ID) = NRF size code ** LIN10 (product/service ID qualifier) = "IN" (Buyer's Item Number) * LIN11 (product/service ID) = "AAABBBBCCCCDDDDD" (AAA = subdivision number, BBBB = lot number, CCCC = line number, DDDDD = size description) ** * Data can be in LIN02, LIN04, LIN06, LIN08, OR LIN10. ** Data can be in LIN03, LIN05, LIN07, LIN09, OR LIN11. NOTE - Segments for above function are only sent by suppliers. March 2002 Page 3.4