JCPenney 870 Order Status Report Version 4030

JCPenney 870 Order Status Report Version 4030 

TABLE OF CONTENTS 

Page 

JCPenney Mapping Differences between Versions 3060 and 4030 .................................................... 1.2 

Transaction Set Purpose....................................................................................................................... 1.3 

Order Status Report Segment Hierarchy.............................................................................................. 1.3 

+++++++++++++++++++++++++++++++++++++++ 

ISA -Envelope Segment...................................................................................................................... 2.1 

GS -Functional Group Segment......................................................................................................... 2.1 

ST -Start of Order Status Report Transaction Set............................................................................. 2.1 

BSR -Order Status Report Type, Reference Identification and Order/Item Code ............................... 2.2 

REF -JCPenney's Internal Supplier Number........................................................................................ 2.2 

N1 -Store or DFW Unit Number Report Is For................................................................................... 2.2 

HL -Start of Order Level..................................................................................................................... 2.3 

PRF -Purchase Order Number and Date............................................................................................. 2.3 

ISR -Ship/Order Status Code and Revised Ship Date........................................................................ 2.3 

DTM -Requested or Promised Ship Date ............................................................................................. 2.4 

REF -Subdivision Number.................................................................................................................... 2.4 

REF -Supplier's Order Number ............................................................................................................ 2.4 

HL -Start of Item Level....................................................................................................................... 2.5 

PO1 -SKU Number/Description/Quantity/Cost Price/Unit of Measure................................................. 2.5 

ISR -Ship/Order Status Code and Revised Ship Date........................................................................ 2.6 

QTY -Ship Quantity for Revised Ship Date .......................................................................................... 2.6 

CTT -Count of HL Segments................................................................................................................ 2.7 

SE -End of Order Status Report Transaction Set.............................................................................. 2.7 

GE -Functional Group Segment......................................................................................................... 2.7 

IEA -Envelope Segment...................................................................................................................... 2.7 

+++++++++++++++++++++++++++++++++++++++ 

Supplementary Catalog Documentation ............................................................................................... 3.1 

Supplementary Retail Documentation................................................................................................... 3.1 

HL Levels and Relationships................................................................................................................. 3.2 

+++++++++++++++++++++++++++++++++++++++ 

June 2003 Page 1.1 Section 26 

d:\My_Docs\4030\870 4030 F5 June 03


JCPENNEY MAPPING DIFFERENCES BETWEEN VERSIONS 3060 AND 4030 

Page(s) 

NOTE: 

Differences 

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. 

New Receiver ID for Factory Ship. 

2.2 D/E 127 in BSR03 has an X12 attribute change. 

D/E 127 in REF02 has an X12 attribute change. 

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.3 D/E 324 in PRF01 has a JCPenney attribute change. 

D/E 350 and 367 in PRF05 and 06 have been added for Retail contract. 

2.4 D/E 127 in REF02 has an X12 attribute change. 

2.5 D/E 350 in PO101 is opened for use by Factory Ship with a new comment. 

D/E 330 in PO102 has an X12 and JCPenney attribute change. 

D/E 212 in PO104 has a JCPenney attribute change and a new comment. 

D/E 639 in PO105 has a new code value. 

D/E 235 in PO106 has a new code value. 

D/E 234 in PO107 has an X12 and JCPenney attribute change. 

D/E 234 in PO109 and PO111 has an X12 attribute change. 

2.6 D/E 380 in QTY02 has a JCPenney attribute change. 

NOTE - Highlighted (shaded) areas of the document reflect changes from the previous version. 

June 2003 Page 1.2


SEGMENT HIERARCHY 

PURPOSE: Transaction provides a supplier the ability to report on all pertinent information relative to an entire 

purchase order or selected SKUs on a purchase order. The report format allows for the inclusion of reasons 

relative to the status of each SKU on the purchase order(s). This transaction could be a result of an 869 Order 

Status Inquiry forwarded to a supplier by JCPenney. It should also be used to inform JCPenney prior to 

JCPenney's requested ship date of any out of stock conditions or revised ship dates. It is also used upon receipt 

of a purchase order to confirm dates/quantities are acceptable as requested by JCPenney on their purchase 

order. 

ISA -INTERCHANGE CONTROL HEADER 

GS -FUNCTIONAL GROUP HEADER 

--------------------------------------------- Order Status Report Segment Hierarchy -------------------------------------------- 

HEADER 

Loop Max 

ST -Start of Order Status Report Transaction Set 

BSR -Order Status Report Type, Reference Identification and Order/Item Code 

REF -JCPenney's Internal Supplier Number 1 

N1 -Store or DFW Unit Number Report Is For 1 

DETAIL 

Order 

HL -Start of Order Level 1,000 

PRF -Purchase Order Number and Date 

ISR -Ship/Order Status Code and Revised Ship Date 100 

DTM -Requested or Promised Ship Date 

REF -Subdivision Number 1 

REF -Supplier's Order Number 1 

HL -Start of Item Level 1,000 

PO1 -SKU Number/Description/Quantity/Cost Price/Unit of Measure 1,000 

ISR -Ship/Order Status Code and Revised Ship Date 100 

QTY -Ship Quantity for Revised Ship Date 

Item 

TRAILER 

CTT 

SE 

-Count of HL Segments 

-End of Order Status Report Transaction Set 

----------------------------------------------------------------------------------------------------------------------------------------------- 

GE -FUNCTIONAL GROUP TRAILER 

IEA -INTERCHANGE CONTROL TRAILER 

June 2003 Page 1.3


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. 

Data Element Number & Name ANSI X12 JCPenney Codes & Comments 

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-ID’s: 6111355007 (Catalog), 6111355012 (Retail), 

6111355013 (DFW), 6111355028 (Factory Ship). 

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. 


GS01 479 Functional ID M ID 2/2 "RS" (Order Status Information) 

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 


PURPOSE: To indicate the start of a Order Status Report transaction set and to assign a control number. 


ST01 143 Transaction Set ID M ID 3/3 "870" 

ST02 329 Transaction Set Control Number M AN 4/9 

June 2003 Page 2.1


Segment: BSR - BEGINNING SEGMENT 

Level: HEADER 


PURPOSE: To identify Order Status Report type, Reference Identification and Order/Item code. 


BSR01 850 Status Report Code M ID 1/2 See note. 

BSR02 847 Order/Item Code M ID 1/2 M ID 2/2 "PA" (Selected Orders - All Items) 

"PP" (Selected Orders - Selected Items) 

BSR03 127 Reference Identification M AN 1/50 M AN 8/8 See note. 

BSR04 373 Date M DT 8/8 

BSR01 - DFW suppliers will respond to DFW orders with an 870 document, and only use code ‘2 Prearranged 

Schedule or Agreement’ in this data element field. 

BSR03 - To process an 870 accurately and to insure that none are lost, we must process in the sequence in which 

they were created. The Reference Identification in BSR03 is used to achieve this required control. The 

Reference Identification is to be assigned sequentially beginning with "00000001" for the very first 870 

transaction sent and incrementing by 1 with each BSR sent. 

Segment: REF - REFERENCE IDENTIFICATION 

Level: HEADER 

Loop: REF Max Use: 1 Usage: REQUIRED 

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

Level: HEADER 

Loop: N1 Max Use: 1 Usage: REQUIRED 

PURPOSE: To identify the store number or the DFW unit number the Order Status Report is for. 


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 plus check digit. See note. 

NOTE - Segment is only sent for Retail and DFW orders. 

June 2003 Page 2.2


Segment: HL - HIERARCHICAL LEVEL 

Level: ORDER 

Loop: HL Max Use: 1 Usage: MANDATORY 

PURPOSE: To identify the start of the order level. 


HL01 628 Hierarchical ID Number M AN 1/12 See note. 

HL02 734 Hierarchical Parent ID Number O AN 1/12 Not used by VICS. 

HL03 735 Hierarchical Level Code M ID 1/2 M ID 1/1 "O" (Order) 

HL01 - The value assigned to the first HL segment in the transaction will be "1", and is incremented by one for 

each subsequent HL segment within the transaction set. 

Segment: PRF - PURCHASE ORDER REFERENCE 

Level: ORDER 

Loop: HL Max Use: 1 Usage: REQUIRED 

PURPOSE: To identify purchase order number and date. 


PRF01 324 Purchase Order Number M AN 1/22 M AN 8/9 

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 M DT 8/8 

PRF05 350 Assigned Identification O AN 1/20 Not used by VICS. 

PRF06 367 Contract Number O AN 1/30 O N0 12/12 

Segment: ISR - ITEM STATUS REPORT 

Level: ORDER 

Loop: HL/ISR Max Use: 1 Usage: OPTIONAL 

PURPOSE: To specify Ship/Order Status code and revised ship date. 


ISR01 368 Shipment/Order Status Code M ID 2/2 

ISR02 373 Date O DT 8/8 See note. 

ISR02 - If ISR01 contains code 'BP' (Shipment Partial, Back Order to Ship On), 'CC' (Shipment Complete On), 

'CP' (Partial Shipment On, Considered No Back Order), 'ED' (Expect To Ship By), 'EW' (Expect To Ship 

Week Of), 'RD' (Revised Expect to Ship By) or 'RW' (Revised Expect to Ship Week Of), ISR02 is 

required. 

NOTE - The ISR segment is generated at either the order or item level but not at both levels. If the ISR is 

generated at this order level, it must not be generated at the item level. You may only generate an ISR at 

the order level if the order status code and revised ship date are the same for all of the SKUs (items) 

within the purchase order. 

NOTE - This segment is not used for DFW orders. 

June 2003 Page 2.3


Segment: DTM - DATE/TIME REFERENCE 

Level: ORDER 

Loop: HL/ISR Max Use: 1 Usage: OPTIONAL 

PURPOSE: To specify requested or promised ship date. 


DTM01 374 Date/Time Qualifier M ID 3/3 "010" (Requested Ship) 

DTM02 373 Date C DT 8/8 M DT 8/8 Requested or Promised ship date. 

NOTE - This segment is not used for DFW orders. 


Level: ORDER 

Loop: HL/REF Max Use: 1 Usage: REQUIRED 

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. 


Level: ORDER 

Loop: HL/REF Max Use: 1 Usage: REQUIRED 

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 AN 1/15 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. 

For example; your order number is 12345678901234567, we will return 345678901234567on subsequent 

869's. This limitation applies to Catalog orders. 

June 2003 Page 2.4


When BSR02 is "PA" (Selected Orders - All Items), and the status and ship date at the order level applies 

to all items, the item level need not be sent. If the status or ship date of the various line items differ, then 

the item level is required and all line items must be sent. 

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 M ID 1/1 "I" (Item) 

HL01 - The value assigned to the first HL segment in the transaction 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: PO1 - PURCHASE ORDER BASELINE ITEM DATA 

Level: ITEM 

Loop: HL/PO1 Max Use: 1 Usage: OPTIONAL 

PURPOSE: To specify SKU number/description/quantity/cost price/unit of measure. 


PO101 350 Assigned Identification O AN 1/20 Line item number assigned on the P.O. 

PO!02 330 Quantity Ordered C R 1/15 M N0 1/10 Original SKU quantity (number of saleable 

units) less supplier cancellations. 

PO103 355 Unit of Measurement Code 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) 

PO104 212 Unit Price C R 1/17 M R2 1/17 SKU cost price. 

PO105 639 Basis of Unit Price Code O ID 2/2 M ID 2/2 “WH” (Wholesale) 

PO106 235 Product/Service ID Qualifier O ID 2/2 M ID 2/2 "IN" (Buyers Item Number) 

PO107 234 Product/Service ID C AN 1/48 M AN 4/16 Retail. See note. 

M N0 11/11 Catalog. 

PO108 235 Product/Service ID Qualifier C ID 2/2 "UP" (U.P.C. Consumer Package Code) 

PO109 234 Product/Service ID C AN 1/48 C AN 12/12 U.P.C. number. 

PO110 235 Product/Service ID Qualifier C ID 2/2 "EN" (European Article Number) 

PO111 234 Product/Service ID C AN 1/48 C AN 13/13 EAN13 number. 

PO101 - Data element is only sent for Catalog Factory Ship orders and is required. 

PO104 - This D/E is only used for DFW order responses. 

PO105 - This D/E is only used for DFW order responses. 

PO107 - If report is for Retail or DFW merchandise, send lot/line/size description in the following format: 

AAAABBBBCCCCC where AAAA = lot number, BBBB = line number, CCCCC = size description. 

For Catalog merchandise, send lot/sku in the following format: AAAAAAABBBB where 

AAAAAAA = lot number, BBBB = SKU number. 

NOTE - There is one PO1 segment for each SKU. 

June 2003 Page 2.5


Segment: ISR - ITEM STATUS REPORT 

Level: ITEM 

Loop: HL/PO1/ISR Max Use: 1 Usage: OPTIONAL 

PURPOSE: To specify Ship/Order Status code and revised ship date. 


ISR01 368 Shipment/Order Status Code M ID 2/2 

ISR02 373 Date O DT 8/8 See note. 

ISR02 - If ISR01 contains code 'BP' (Shipment Partial, Back Order to Ship On), 'CC' (Shipment Complete On), 

'CP' (Partial Shipment On, Considered No Back Order), 'ED' (Expect To Ship By), 'EW' (Expect To Ship 

Week Of), 'RD' (Revised Expect to Ship By) or 'RW' (Revised Expect to Ship Week Of), ISR02 is 

required. For DFW order response, only code ‘ED’ (Expect To Ship By) is used. 

NOTE - The ISR segment is generated at either the order or item level but not at both levels. If the ISR was not 

generated at the order level it must be generated at the item level. 

Segment: QTY - QUANTITY 

Level: ITEM 

Loop: HL/PO1/ISR Max Use: 1 Usage: OPTIONAL 

PURPOSE: To specify ship quantity for revised ship date. 


QTY01 673 Quantity Qualifier M ID 2/2 

QTY02 380 Quantity M R 1/15 M N0 1/10 

QTY03 C001 Composite Unit Of Measure O Composite. 

-1 355 Unit Of 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) 

NOTE - If QTY segment is sent, then segment ISR at the Item level is required. 

June 2003 Page 2.6


Segment: CTT - TRANSACTION TOTALS 

Level: TRAILER 

Loop: Max Use: 1 Usage: OPTIONAL 

PURPOSE: Count of HL segments in Order Status Report 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 


PURPOSE: To indicate the end of a Order Status Report 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 


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. 

June 2003 Page 2.7


Supplementary 870 Catalog Documentation 

REFERENCE INFORMATION 

Examples of how the Order Status Inquiry (869), Order Status Report (870), and the Ship Notice/Manifest 

(856) are used in relationship to Catalog purchase orders are in the separate document "Catalog Purchase 

Order Follow-up (POF) Supplier Procedures". If you have any questions relating to "POF Supplier Procedures" 

go to our supplier WEB site at supplier.jcpenney.com. 

Supplementary 870 Retail Documentation 

Retail supplementary documentation for how the order status inquiry (869), order status report (870), and the 

ship notice/manifest (856) are used in relationship to Retail purchase orders will be published later under 

separate cover. If you have any questions relating to usage go to our supplier WEB site at 

supplier.jcpenney.com. 

June 2003 Page 3.1


HL Relationships in the 870 

An 870 transaction set can contain reports for multiple JCPenney purchase orders. However, the order level in 

this transaction refers to the vendor's order. For example, a supplier has received two JCPenney purchase 

orders from a store, and generates three vendor orders in his system. We send an Order Status Inquiry asking 

about both of our orders, and the supplier would generate three order levels in the Order Status Report 

response back to JCPenney. 

The first illustration shows the numbering sequence of the HL segments if the Order Status Report is for 

selected purchase orders and selected items within these orders. The transaction set contains two JCPenney 

purchase orders. PO#87654321 has two vendor orders and the other, PO#11223344 has one vendor order. 

The number in each box (top left corner) is the hierarchical sequence number (HL01). The number in the top 

right corner is the parent ID (HL02). 

Report 

BSR02 is "PP" (Selected Orders - Selected Items) 

Order 1 


01 05 

09 


JCPenney PO #87654321 JCPenney PO #87654321 

JCPenney PO #11223344 

02 

SKU A 

03 

SKU B 

01 

01 

04 01 

SKU C 

06 

SKU D 

07 

SKU E 

05 

05 

08 05 

SKU F 

10 09 13 09 

SKU P 

SKU Q 

SKU S 

11 09 14 09 

12 09 

SKU R 

SKU T 

15 09 

SKU U 

This illustration shows the numbering sequence of the HL segments if the Order Status Report is for all items 

(status and ship date are the same) in one purchase order from JCPenney. The supplier has generated four 

vendor orders for the one JCPenney order. 

Report 

BSR02 is "PA" (Selected Orders - All Items) 

01 


02 


03 


04 


JCPenney PO #12345678 JCPenney PO #12345678 JCPenney PO #12345678 JCPenney PO #12345678 

June 2003 Page 3.2

JCPenney 870 Order Status Report Version 4030

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?