870 Order Status Report - iconnect-corp.com · 870 Order Status Report ... Status Codes:...

870 Order Status ReportVICS EDI/V4030/870: 870 Order Status Report

Modified: 10/18/2006

Notes: __________________________________________________________________________________________________J. C. Penney Co Proprietary and Confidential

V4030 Order Status Report - 870

J. C. Penney Co Proprietary and Confidential

i

Table of Contents Order Status Report Overview……………………………………………………………………………… 1

+++++ ISA - Interchange Control Header………………………………………………………………………….. 3 GS - Functional Group Header……………………………………………………………………………… 6 ST - Transaction Set Header………………………………………………………………………………… 8 BSR - Beginning Segment for Order Status Report……………………………………………………. 9 REF - Reference Identification……………………………………………………………………………… 10 N1 - Name………………………………………………………………………………………………………. 11 HL - Hierarchical Level………………………………………………………………………………………. 12 PRF - Purchase Order Reference………………………………………………………………………….. 13 ISR - Item Status Report……………………………………………………………………………………… 14 DTM - Date/Time Reference…………………………………………………………………………………. 15 REF - Reference Identification……………………………………………………………………………… 16 HL - Hierarchical Level……………………………………………………………………………………….. 17 PO1 - Baseline Item Data…………………………………………………………………………………….. 18 ISR - Item Status Report……………………………………………………………………………………… 21 QTY - Quantity…………………………………………………………………………………………………. 22 CTT - Transaction Totals…………………………………………………………………………………….. 23 SE - Transaction Set Trailer…………………………………………………………………………………. 24 GE - Functional Group Trailer………………………………………………………………………………. 25 IEA - Interchange Control Trailer…………………………………………………………………………… 26

+++++ Business Rules: Catalog………………………………………………………………………………………… 27 Business Example: Catalog (Unsolicited)…………………………………………………………………… 29 Business Example: Catalog (Response to 869 – All items)………………………………………………. 32 Business Example: Catalog (Response to 869 – Select items)………………………………………….. 34 Business Example: Catalog (Cancellations)………………………………………………………………… 39 Business Rules: Catalog Factory Ship……………………………………………………………………….. 43 Business Example: Catalog Factory Ship (Revised Ship Date)………………………………………….. 45 Business Example: Catalog Factory Ship (Cancellations)………………………………………………… 46 Business Rules: Furniture (DFW)…………………………………………………………………………....... 47 Business Example: Furniture (DFW) - All Items……………………………………………………............. 49 Business Example: Furniture (DFW) - Select Items………………………………………………………… 50 Business Rules: Liquidation(Outlet Stores)………………………………………………………………….. 52 Status Codes: Liquidation (Outlet Stores)…………………………………………………………………….. 54 Business Example: Liquidation (Outlet Stores) - Unsolicited……………………………………………… 56 Business Example: Liquidation (Outlet Stores) – Quantity Decrease…………………………………… 57 Business Example: Liquidation (Outlet Stores) - Cancelled Order………………………………………. 59


J.C. Penney Co. Proprietary and Confidential 1

870 Order Status ReportFunctional Group=RS

This Draft Standard for Trial Use contains the format and establishes the data contents of the Order Status ReportTransaction Set (870) for use within the context of an Electronic Data Interchange (EDI) environment. Thetransaction set can be used to report on the current status of a requirement forecast, an entire purchase order,selected line items on a purchase order, selected products/services on a purchase order, or purchase orders for aspecific customer in their entirety or on a selection basis. The transaction set can also be used to report on thecurrent status of single or multiple requisitions. The report format allows for the inclusion of "reasons" relative to thestatus. This transaction set may also be used to update the supplier's scheduled shipment or delivery dates. Thistransaction set can result from either an inquiry or a prearranged schedule agreed to by the trading partners.

Not Defined:Pos Id Segment Name Req Max Use Repeat Notes

ISA Interchange Control Header M 1 GS Functional Group Header M 1

Heading:Pos Id Segment Name Req Max Use Repeat Notes0100 ST Transaction Set Header M 1 0200 BSR Beginning Segment for Order Status Report M 1

LOOP ID - REF >1 LOOP ID - REF >1

0460 REF Reference Identification M 1

LOOP ID - N1 200 LOOP ID - N1 200

0500 N1 Name O 1

Detail:Pos Id Segment Name Req Max Use Repeat Notes

LOOP ID - HL 1000 LOOP ID - HL 1000

0100 HL Hierarchical Level M 1 0200 PRF Purchase Order Reference O 1

LOOP ID - ISR 104 LOOP ID - ISR 104

0300 ISR Item Status Report O 1 0800 DTM Date/Time Reference O 10

LOOP ID - REF >1 LOOP ID - REF >1

0870 REF Reference Identification O 1

LOOP ID - HL 1000 LOOP ID - HL 1000

0100 HL Hierarchical Level M 1 LOOP ID - PO1 1000 LOOP ID - PO1 1000

1500 PO1 Baseline Item Data O 1 LOOP ID - ISR 104 LOOP ID - ISR 104

2100 ISR Item Status Report O 1 2300 QTY Quantity O 4

Summary:



Pos Id Segment Name Req Max Use Repeat Notes0100 CTT Transaction Totals O 1 0200 SE Transaction Set Trailer M 1

Not Defined:Pos Id Segment Name Req Max Use Repeat Notes

GE Functional Group Trailer M 1 IEA Interchange Control Trailer M 1



ISA Interchange Control Header Pos: Max: 1Not Defined - Mandatory

Loop: N/A Elements: 16

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Element Summary: Ref Id Element Name Req Type Min/MaxISA01 I01 Authorization Information Qualifier

Description: Code identifying the type of information in theAuthorization Information

M ID 2/2

Code Name00 No Authorization Information Present (No Meaningful Information in I02)

ISA02 I02 Authorization Information

Description: Information used for additional identification orauthorization of the interchange sender or the data in theinterchange; the type of information is set by the AuthorizationInformation Qualifier (I01)User Note 1: Ten blank positions.User Note 1: Ten blank positions.

M AN 10/10

ISA03 I03 Security Information Qualifier

Description: Code identifying the type of information in theSecurity Information

M ID 2/2

Code Name00 No Security Information Present (No Meaningful Information in I04)

ISA04 I04 Security Information

Description: This is used for identifying the security informationabout the interchange sender or the data in the interchange; thetype of information is set by the Security Information Qualifier(I03)User Note 1: Ten blank positions.User Note 1: Ten blank positions.

M AN 10/10

ISA05 I05 Interchange ID Qualifier

Description: Code indicating the system/method of codestructure used to designate the sender or receiver ID elementbeing qualified

M ID 2/2

Code Name01 Duns (Dun & Bradstreet)02 SCAC (Standard Carrier Alpha Code)08 UCC EDI Communications ID (Comm ID)12 Phone (Telephone Companies)14 Duns Plus Suffix

ISA06 I06 Interchange Sender ID

Description: Identification code published by the sender forother parties to use as the receiver ID to route data to them; thesender always codes this value in the sender ID element

M AN 15/15


Ref Id Element Name Req Type Min/Max


ISA07 I05 Interchange ID Qualifier

Description: Code indicating the system/method of codestructure used to designate the sender or receiver ID elementbeing qualified

M ID 2/2

Code Name08 UCC EDI Communications ID (Comm ID)

ISA08 I07 Interchange Receiver ID

Description: Identification code published by the receiver of thedata; When sending, it is used by the sender as their sendingID, thus other parties sending to them will use this as areceiving ID to route data to themUser Note 1: JCPenney Receiver IDs by business entities:6111355007 - Catalog6111355012 - Retail6111355013 - DFW6111355015 - Liquidation6111355028 - Factory Ship

User Note 1: JCPenney Receiver IDs by business entities:6111355007 - Catalog6111355012 - Retail6111355013 - DFW6111355015 - Liquidation6111355028 - Factory Ship

M AN 15/15

ISA09 I08 Interchange Date

Description: Date of the interchange

M DT 6/6

ISA10 I09 Interchange Time

Description: Time of the interchange

M TM 4/4

ISA11 I65 Repetition Separator

Description: Type is not applicable; the repetition separator isa delimiter and not a data element; this field provides thedelimiter used to separate repeated occurrences of a simpledata element or a composite data structure; this value must bedifferent than the data element separator, component elementseparator, and the segment terminator

M 1/1

ISA12 I11 Interchange Control Version Number

Description: Code specifying the version number of theinterchange control segments

M ID 5/5

Code Name00403 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures

Review Board through October 1999

ISA13 I12 Interchange Control Number

Description: A control number assigned by the interchangesender

M N0 9/9

ISA14 I13 Acknowledgment Requested

Description: Code indicating sender's request for aninterchange acknowledgment

M ID 1/1

Code Name0 No Acknowledgment Requested

ISA15 I14 Usage Indicator M ID 1/1




Description: Code indicating whether data enclosed by thisinterchange envelope is test, production or information

Code NameP Production DataT Test Data

ISA16 I15 Component Element Separator

Description: Type is not applicable; the component elementseparator is a delimiter and not a data element; this fieldprovides the delimiter used to separate component dataelements within a composite data structure; this value must bedifferent than the data element separator and the segmentterminator

M 1/1



GS Functional Group Header Pos: Max: 1Not Defined - Mandatory


To indicate the beginning of a functional group and to provide control information

Element Summary: Ref Id Element Name Req Type Min/MaxGS01 479 Functional Identifier Code

Description: Code identifying a group of application relatedtransaction sets

M ID 2/2

Code NameRS Order Status Information (869, 870)

GS02 142 Application Sender's Code

Description: Code identifying party sending transmission;codes agreed to by trading partnersUser Note 1: Same ID number as in ISA06.User Note 1: Same ID number as in ISA06.

M AN 2/15

GS03 124 Application Receiver's Code

Description: Code identifying party receiving transmission;codes agreed to by trading partnersUser Note 1: Same ID number as in ISA08.User Note 1: Same ID number as in ISA08.

M AN 2/15

GS04 373 Date

Description: Date expressed as CCYYMMDD where CCrepresents the first two digits of the calendar year

M DT 8/8

GS05 337 Time

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 areexpressed as follows: D = tenths (0-9) and DD = hundredths(00-99)

M TM 4/8

GS06 28 Group Control Number

Description: Assigned number originated and maintained bythe sender

M N0 1/9

GS07 455 Responsible Agency Code

Description: Code identifying the issuer of the standard; thiscode is used in conjunction with Data Element 480

M ID 1/2

Code NameX Accredited Standards Committee X12

GS08 480 Version / Release / Industry Identifier Code

Description: Code indicating the version, release, subrelease,and industry identifier of the EDI standard being used, includingthe 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

M AN 1/12




4-6 are the release and subrelease, level of the version; andpositions 7-12 are the industry or trade association identifiers(optionally assigned by user); if code in DE455 in GS segmentis T, then other formats are allowed

Code Name004030 Draft Standards Approved for Publication by ASC X12 Procedures Review Board

through October 1999

Semantics: 1. GS04 is the group date.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.



ST Transaction Set Header Pos: 0100 Max: 1Heading - Mandatory


To indicate the start of a transaction set and to assign a control number

Element Summary: Ref Id Element Name Req Type Min/MaxST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying a Transaction Set

M ID 3/3

Code Name870 Order Status Report

ST02 329 Transaction Set Control Number

Description: Identifying control number that must be uniquewithin the transaction set functional group assigned by theoriginator for a transaction setUser Note 1: The number is sequentially assigned by thesender, starting with one within each functional group. For eachfunctional group, the first transaction set control number will be0001 and incremented by one for each additional transactionset within the group.

User Note 1: The number is sequentially assigned by thesender, starting with one within each functional group. For eachfunctional group, the first transaction set control number will be0001 and incremented by one for each additional transactionset within the group.

M AN 4/9

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).



BSR Beginning Segment forOrder Status Report

Pos: 0200 Max: 1Heading - Mandatory


To indicate the beginning of an Order Status Report Transaction Set

Element Summary: Ref Id Element Name Req Type Min/MaxBSR01 850 Status Report Code

Description: Code indicating the reason for sending the reportUser Note 1: DFW suppliers will respond to DFW orders withan 870 document and only use code 2 (Prearranged Scheduleor Agreement).

User Note 1: DFW suppliers will respond to DFW orders withan 870 document and only use code 2 (Prearranged Scheduleor Agreement).

M ID 1/2

Code Name1 Response to an Order Status Inquiry (869)2 Prearranged Schedule or Agreement3 Unsolicited Report

BSR02 847 Order/Item Code

Description: Code identifying a group of orders and items

M ID 1/2

Code NamePA Selected Orders - All ItemsPP Selected Orders - Selected Items

BSR03 127 Reference Identification

Description: Reference information as defined for a particularTransaction Set or as specified by the Reference IdentificationQualifierUser Note 1: Number assigned by the sender to identify therequest within their application system.User Note 1: Number assigned by the sender to identify therequest within their application system.User Note 2: The Reference Identification is to be assignedsequentially beginning with "00000001" for the very first BSRsegment sent and incrementing by 1 with each BSR.

User Note 2: The Reference Identification is to be assignedsequentially beginning with "00000001" for the very first BSRsegment sent and incrementing by 1 with each BSR.

M AN 1/50

BSR04 373 Date


M DT 8/8

Semantics: 1. BSR03 indicates a status report document number assigned by the sender.2. BSR04 indicates the date of this report from the sender.

Notes:Notes:When BSR02 is "PA" and the status and ship date at the order level applies to all items, item level data is notrequired. Only send item level data if the status or ship date is different for individual items.When BSR02 is "PA" and the status and ship date at the order level applies to all items, item level data is notrequired. Only send item level data if the status or ship date is different for individual items.



REF Reference Identification Pos: 0460 Max: 1Heading - Mandatory

Loop: REF Elements: 2

To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/MaxREF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference Identification

M ID 2/3

Code NameIA Internal Vendor Number

REF02 127 Reference Identification

Description: Reference information as defined for a particularTransaction Set or as specified by the Reference IdentificationQualifierUser Note 1: JCPenney assigned six digit supplier number.User Note 1: JCPenney assigned six digit supplier number.

X AN 1/50



N1 Name Pos: 0500 Max: 1Heading - Optional

Loop: N1 Elements: 3

To identify a party by type of organization, name, and code

Element Summary: Ref Id Element Name Req Type Min/MaxN101 98 Entity Identifier Code

Description: Code identifying an organizational entity, aphysical location, property or an individual

M ID 2/3

Code NameZ7 Mark-for Party

N103 66 Identification Code Qualifier

Description: Code designating the system/method of codestructure used for Identification Code (67)

X ID 1/2

Code Name92 Assigned by Buyer or Buyer's Agent

N104 67 Identification Code

Description: Code identifying a party or other codeUser Note 1: This is the location code as defined by N103. Thelocation refers to a store, warehouse, distribution center, plant,etc. Location codes are used to alleviate the need to sendcomplete names and addresses.

User Note 1: This is the location code as defined by N103. Thelocation refers to a store, warehouse, distribution center, plant,etc. Location codes are used to alleviate the need to sendcomplete names and addresses.User Note 2: Five-digit JCPenney unit number.User Note 2: Five-digit JCPenney unit number.

X AN 2/80

Syntax Rules: 1. P0304 - If either N103 or N104 is present, then the other is required.



HL Hierarchical Level Pos: 0100 Max: 1Detail - Mandatory

Loop: HL Elements: 2

To identify dependencies among and the content of hierarchically related groups of data segments

Element Summary: Ref Id Element Name Req Type Min/MaxHL01 628 Hierarchical ID Number

Description: A unique number assigned by the sender toidentify a particular data segment in a hierarchical structureUser Note 1: The value assigned to the first HL segment in thetransaction will be "1", and is incremented by one for eachsubsequent HL segment within the transaction set.

User Note 1: The value assigned to the first HL segment in thetransaction will be "1", and is incremented by one for eachsubsequent HL segment within the transaction set.

M AN 1/12

HL03 735 Hierarchical Level Code

Description: Code defining the characteristic of a level in ahierarchical structure

M ID 1/2

Code NameO 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 whichcase the value of HL01 would be "1" for the initial HL segment and would be incremented by one in eachsubsequent 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 subsequentsegments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

Notes:Notes:The HL segment is used to identify levels of detail information using a hierarchical structure.HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The valueassigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within thetransaction set. HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted forthe order level HL segment (HL03 contains code O), since it has no parent. HL03 identifies the applicationcontext of the series of segments following the current HL segment up to the next occurrence of an HL segment,or the CTT or SE segment, e.g., Order and Item.

The HL segment is used to identify levels of detail information using a hierarchical structure.HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The valueassigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within thetransaction set. HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted forthe order level HL segment (HL03 contains code O), since it has no parent. HL03 identifies the applicationcontext of the series of segments following the current HL segment up to the next occurrence of an HL segment,or the CTT or SE segment, e.g., Order and Item.



PRF Purchase Order Reference Pos: 0200 Max: 1Detail - Optional


To provide reference to a specific purchase order

Element Summary: Ref Id Element Name Req Type Min/MaxPRF01 324 Purchase Order Number

Description: Identifying number for Purchase Order assignedby the orderer/purchaserUser Note 1: Retailer's original purchase order number (8-9characters in length).User Note 1: Retailer's original purchase order number (8-9characters in length).

M AN 1/22

PRF04 373 Date

Description: Date expressed as CCYYMMDD where CCrepresents the first two digits of the calendar yearUser Note 1: Retailer's original purchase order dateUser Note 1: Retailer's original purchase order dateUser Note 2: This data element is required by Catalog FactoryShip.User Note 2: This data element is required by Catalog FactoryShip.

O DT 8/8

PRF06 367 Contract Number

Description: Contract numberUser Note 1: Twelve digit contract number.User Note 1: Twelve digit contract number.

O AN 1/30

Semantics: 1. PRF04 is the date assigned by the purchaser to purchase order.



ISR Item Status Report Pos: 0300 Max: 1Detail - Optional

Loop: ISR Elements: 2

To specify detailed purchase order/item status

Element Summary: Ref Id Element Name Req Type Min/MaxISR01 368 Shipment/Order Status Code

Description: Code indicating the status of an order or shipmentor the disposition of any difference between the quantity orderedand the quantity shipped for a line item or transaction

M ID 2/2

Code NameBP Shipment Partial, Back Order to Ship on (Date)CC Shipment Complete on (Date)CP Partial Shipment on (Date), Considered No BackorderDE Deleted OrderED Expect to Ship By (Date)NN Not in Process - No Shipping ScheduleRD Revised Expect to Ship By (Date)

ISR02 373 Date

Description: Date expressed as CCYYMMDD where CCrepresents the first two digits of the calendar yearUser Note 1: If ISR01 contains code BP, CC, CP, ED, or RD, ISR02 is required.User Note 1: If ISR01 contains code BP, CC, CP, ED, or RD, ISR02 is required.

O DT 8/8

Semantics: 1. If ISR01 specifies a date, ISR02 is required.

Notes:Notes:The ISR segment is generated at either the order or item level but not at both levels. If the ISR is generated at theorder level, it must not be generated at the item level. You may only generate an ISR at the order level if theorder status code and revised ship date are the same for all of the SKUs (items) within the purchase order.

The ISR segment is generated at either the order or item level but not at both levels. If the ISR is generated at theorder level, it must not be generated at the item level. You may only generate an ISR at the order level if theorder status code and revised ship date are the same for all of the SKUs (items) within the purchase order.



DTM Date/Time Reference Pos: 0800 Max: 10Detail - Optional


To specify pertinent dates and times

Element Summary: Ref Id Element Name Req Type Min/MaxDTM01 374 Date/Time Qualifier

Description: Code specifying type of date or time, or both dateand time

M ID 3/3

Code Name010 Requested Ship

DTM02 373 Date


X DT 8/8

Notes:Notes:This segment is not used for DFW orders.This segment is not used for DFW orders.



REF Reference Identification Pos: 0870 Max: 1Detail - Optional

Loop: REF Elements: 2

To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/MaxREF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference Identification

M ID 2/3

Code NameDP Department NumberVN Vendor Order Number

REF02 127 Reference Identification

Description: Reference information as defined for a particularTransaction Set or as specified by the Reference IdentificationQualifier

X AN 1/50

Notes:Notes:Two REF loops are required to be generated at this position for each of the Reference Identification Qualifierslisted in REF01:

Department Number (DP) specifying the three digit JCPenney subdivision number.

The second REF loop will contain the Vendor's Order Number (VN). If the order number is more than 15characters in length, we will return the right most 15 characters to you. For example, your order number is12345678901234567, we will return 345678901234567 on subsequent 869s. This limitation applies to Catalogorders.

Two REF loops are required to be generated at this position for each of the Reference Identification Qualifierslisted in REF01:

Department Number (DP) specifying the three digit JCPenney subdivision number.

The second REF loop will contain the Vendor's Order Number (VN). If the order number is more than 15characters in length, we will return the right most 15 characters to you. For example, your order number is12345678901234567, we will return 345678901234567 on subsequent 869s. This limitation applies to Catalogorders.



HL Hierarchical Level Pos: 0100 Max: 1Detail - Mandatory


To identify dependencies among and the content of hierarchically related groups of data segments

Element Summary: Ref Id Element Name Req Type Min/MaxHL01 628 Hierarchical ID Number

Description: A unique number assigned by the sender toidentify a particular data segment in a hierarchical structure

M AN 1/12

HL02 734 Hierarchical Parent ID Number

Description: Identification number of the next higherhierarchical data segment that the data segment beingdescribed is subordinate to

M AN 1/12

HL03 735 Hierarchical Level Code

Description: Code defining the characteristic of a level in ahierarchical structure

M ID 1/2

Code NameI 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 whichcase the value of HL01 would be "1" for the initial HL segment and would be incremented by one in eachsubsequent 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 subsequentsegments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

Notes:Notes:The HL segment is used to identify levels of detail information using a hierarchical structure.HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The valueassigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within thetransaction set. HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted forthe order level HL segment (HL03 contains code O), since it has no parent. HL03 identifies the applicationcontext of the series of segments following the current HL segment up to the next occurrence of an HL segment,or the CTT or SE segment, e.g., Order and Item.

The HL segment is used to identify levels of detail information using a hierarchical structure.HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The valueassigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within thetransaction set. HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted forthe order level HL segment (HL03 contains code O), since it has no parent. HL03 identifies the applicationcontext of the series of segments following the current HL segment up to the next occurrence of an HL segment,or the CTT or SE segment, e.g., Order and Item.



PO1 Baseline Item Data Pos: 1500 Max: 1Detail - Optional

Loop: PO1 Elements: 11

To specify basic and most frequently used line item data

Element Summary: Ref Id Element Name Req Type Min/MaxPO101 350 Assigned Identification

Description: Alphanumeric characters assigned fordifferentiation within a transaction setUser Note 1: Data element is only required for Catalog FactoryShip orders and will have the line item number assigned on thePO.

User Note 1: Data element is only required for Catalog FactoryShip orders and will have the line item number assigned on thePO.

O AN 1/20

PO102 330 Quantity Ordered

Description: Quantity orderedUser Note 1: Original SKU quantity from the purchase order.User Note 1: Original SKU quantity from the purchase order.

X R 1/15

PO103 355 Unit or Basis for Measurement Code

Description: Code specifying the units in which a value is beingexpressed, or manner in which a measurement has been taken

O ID 2/2

Code NameAS AssortmentBX BoxCA CaseEA EachFT FootPC PiecePK PackagePR PairRL RollST SetYD Yard

PO104 212 Unit Price

Description: Price per unit of product, service, commodity, etc.User Note 1: The price is sent with a decimal point only whenneeded, e.g., $15.95 would be sent as ``15.95'', and $29.00would be sent as ``29''.To indicate a no charge item or free goods, PO104 will contain asingle zero (0) and PO105 will contains code NC.

User Note 1: The price is sent with a decimal point only whenneeded, e.g., $15.95 would be sent as ``15.95'', and $29.00would be sent as ``29''.To indicate a no charge item or free goods, PO104 will contain asingle zero (0) and PO105 will contains code NC.User Note 2: This data element is only used for DFW orderresponses.User Note 2: This data element is only used for DFW orderresponses.

X R 1/17

PO105 639 Basis of Unit Price Code

Description: Code identifying the type of unit price for an itemUser Note 1: This data element is used to clarify or alter thebasis of unit price. The unit price expressed in PO104 is alwaysin the same terms as the unit of measure in PO103, unless

User Note 1: This data element is used to clarify or alter thebasis of unit price. The unit price expressed in PO104 is alwaysin the same terms as the unit of measure in PO103, unless

O ID 2/2




otherwise specified in PO105.otherwise specified in PO105.User Note 2: This data element is only used for DFW orderresponses.User Note 2: This data element is only used for DFW orderresponses.

Code NameNC No ChargeWH Wholesale

PO106 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the descriptivenumber used in Product/Service ID (234)

M ID 2/2

Code NameIN Buyer's Item Number

PO107 234 Product/Service ID

Description: Identifying number for a product or serviceUser Note 1: JCPenney item number.User Note 1: JCPenney item number.User Note 2: If report is for Retail or DFW merchandise, sendlot/line/size description in the following format:AAAABBBBCCCCC where AAAA = lot number, BBBB = linenumber, CCCCC = size description.For Catalog and Factory Ship merchandise, send lot/sku in thefollowing format: AAAAAAABBBB where AAAAAAA = lotnumber, BBBB = SKU number.

User Note 2: If report is for Retail or DFW merchandise, sendlot/line/size description in the following format:AAAABBBBCCCCC where AAAA = lot number, BBBB = linenumber, CCCCC = size description.For Catalog and Factory Ship merchandise, send lot/sku in thefollowing format: AAAAAAABBBB where AAAAAAA = lotnumber, BBBB = SKU number.

X AN 1/48



X ID 2/2

Code NameUP UCC - 12


Description: Identifying number for a product or serviceUser Note 1: UPC number.User Note 1: UPC number.

X AN 1/48



C ID 2/2

Code NameEN EAN/UCC - 13


Description: Identifying number for a product or serviceUser Note 1: EAN number.User Note 1: EAN number.

X AN 1/48

Syntax Rules: 1. C0302 - If PO103 is present, then PO102 is required.2. C0504 - If PO105 is present, then PO104 is required.3. P0607 - If either PO106 or PO107 is present, then the other is required.



4. P0809 - If either PO108 or PO109 is present, then the other is required.5. P1011 - If either PO110 or PO111 is present, then the other is required.

Comments: 1.

Notes:Notes:There can be only one iteration of the PO1 loop at the item level to maintain a one-to-one relation between thePO1 segment and the item level HL segment.There can be only one iteration of the PO1 loop at the item level to maintain a one-to-one relation between thePO1 segment and the item level HL segment.

User Note 2:User Note 2:Either the UPC or EAN number can be sent. It's one or the other; not both. Either the UPC or EAN number can be sent. It's one or the other; not both.



ISR Item Status Report Pos: 2100 Max: 1Detail - Optional


To specify detailed purchase order/item status

Element Summary: Ref Id Element Name Req Type Min/MaxISR01 368 Shipment/Order Status Code

Description: Code indicating the status of an order or shipmentor the disposition of any difference between the quantity orderedand the quantity shipped for a line item or transaction

M ID 2/2

Code NameBP Shipment Partial, Back Order to Ship on (Date)CC Shipment Complete on (Date)CP Partial Shipment on (Date), Considered No BackorderED Expect to Ship By (Date)IC Item CanceledNN Not in Process - No Shipping ScheduleRD Revised Expect to Ship By (Date)SC Shipment Quantity Decrease

ISR02 373 Date

Description: Date expressed as CCYYMMDD where CCrepresents the first two digits of the calendar yearUser Note 1: If ISR01 contains code BP, CC, CP, ED, or RD,ISR02 is required.User Note 1: If ISR01 contains code BP, CC, CP, ED, or RD,ISR02 is required.

O DT 8/8

Semantics: 1. If ISR01 specifies a date, ISR02 is required.

Notes:Notes:The ISR segment is generated at either the order or item level but not at both levels. If the ISR was notgenerated at the order level it must be generated at the item level.The ISR segment is generated at either the order or item level but not at both levels. If the ISR was notgenerated at the order level it must be generated at the item level.



QTY Quantity Pos: 2300 Max: 4Detail - Optional


To specify quantity information

Element Summary: Ref Id Element Name Req Type Min/MaxQTY01 673 Quantity Qualifier

Description: Code specifying the type of quantity

M ID 2/2

Code Name01 Discrete Quantity

QTY02 380 Quantity

Description: Numeric value of quantity

M R 1/15

QTY03 C001 Composite Unit of Measure

Description: To identify a composite unit of measure.

O Comp

355 Unit or Basis for Measurement Code

Description: Code specifying the units in which a value is beingexpressed, or manner in which a measurement has been takenUser Note 1: See Section III for code list.User Note 1: See Section III for code list.

M ID 2/2

Code NameAS AssortmentBX BoxCA CaseEA EachFT FootPC PiecePK PackagePR PairQT QuartRL RollST SetYD Yard

Notes:Notes:This represents the quantity associated with the previous ISR segment.This represents the quantity associated with the previous ISR segment.



CTT Transaction Totals Pos: 0100 Max: 1Summary - Optional


To transmit a hash total for a specific element in the transaction set

Element Summary: Ref Id Element Name Req Type Min/MaxCTT01 354 Number of Line Items

Description: Total number of line items in the transaction setUser Note 1: The number of HL segments present in thetransaction setUser Note 1: The number of HL segments present in thetransaction set

M N0 1/6



SE Transaction Set Trailer Pos: 0200 Max: 1Summary - Mandatory


To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning(ST) and ending (SE) segments)

Element Summary: Ref Id Element Name Req Type Min/MaxSE01 96 Number of Included Segments

Description: Total number of segments included in atransaction set including ST and SE segments

M N0 1/10

SE02 329 Transaction Set Control Number

Description: Identifying control number that must be uniquewithin the transaction set functional group assigned by theoriginator for a transaction setUser Note 1: This must be the same number as is in the STsegment (ST02) for the transaction set.User Note 1: This must be the same number as is in the STsegment (ST02) for the transaction set.

M AN 4/9

Comments: 1. SE is the last segment of each transaction set.



GE Functional Group Trailer Pos: Max: 1Not Defined - Mandatory


To indicate the end of a functional group and to provide control information

Element Summary: Ref Id Element Name Req Type Min/MaxGE01 97 Number of Transaction Sets Included

Description: Total number of transaction sets included in thefunctional group or interchange (transmission) group terminatedby the trailer containing this data element

M N0 1/6

GE02 28 Group Control Number

Description: Assigned number originated and maintained bythe sender

M N0 1/9

Semantics: 1. The data interchange control number GE02 in this trailer must be identical to the same data element in the

associated functional group header, GS06.

Comments: 1. The use of identical data interchange control numbers in the associated functional group header and trailer is

designed to maximize functional group integrity. The control number is the same as that used in thecorresponding header.



IEA Interchange Control Trailer Pos: Max: 1Not Defined - Mandatory


To define the end of an interchange of zero or more functional groups and interchange-related control segments

Element Summary: Ref Id Element Name Req Type Min/MaxIEA01 I16 Number of Included Functional Groups

Description: A count of the number of functional groupsincluded in an interchange

M N0 1/5

IEA02 I12 Interchange Control Number

Description: A control number assigned by the interchangesenderUser Note 1: This must be the same number as is in the ISAsegment (ISA13).User Note 1: This must be the same number as is in the ISAsegment (ISA13).

M N0 9/9

J. C. Penney Co Proprietary and Confidential 27

870 ORDER STATUS REPORT BUSINESS RULES (CATALOG) The purpose of this document is to provide an understanding of JCPenney's use of some of the major sections of the 870 Order Status Report. The 870 may be sent as an unsolicited report or in response to an 869 Order Status Inquiry. The 870 is an advisory that the supplier will use to send JCPenney Catalog a promise-to-ship date, or the cancellation of SKU quantities (merchandise) that are unavailable for shipment by the requested ship date. The promise-to-ship date is considered a reliable date and is used to capture backorders in the Catalog Inventory system. HEADER LEVEL BEGINNING SEGMENT (BSR) The purpose of the BSR segment is to identify the Order Status Report type. Status Report codes [BSR01] accepted are: 1 [Response to an Order Status Inquiry], 2 [Prearranged Schedule or Agreement], and 3 [Unsolicited Report]. The trading partner will send Order code "PA" (Selected Order - All Items) in the BSR02 when reporting the status of an entire purchase order. The item code "PP" (Selected Order - Selected Items) is sent to advise the status of a specific item (Lot/Sku) on a selected order. When using the Order code "PA" only order level details are required. The trading partner should never use code a "PA" with item level details. The 870 must be processed in the sequence in which they are created. In BSR03 the reference identification number is used to synchronize the 870 and insure that none are lost. The reference number should be assigned sequentially beginning with "00000001” for the very first 870 transaction sent and incremented by 1 with each BSR sent. ORDER LEVEL ITEM STATUS REPORT (ISR) The ISR segment is generated at either the order level or the item level but not at both levels. The purpose of the ISR segment is to specify the order status code and the revised or promise-to-ship ship date for a selected order and all items on that order. In ISR01 [Shipment/Order Status Code], the status codes processed by the Catalog system are: BP (Shipment Partial, Back Order to Ship On), ED (Expected-To Ship By), RD (Revised Expect to Ship By) and DE (Deleted Order). These codes used at the order level will indicate that all items on the selected order will have the same by the status action. The revised or promise-to-ship ship date [ISR02] is required and should always be a future date on Catalog orders. This ship date is determined by the trading partner as to when goods will be available for shipment to JCPenney Catalog. If the order is canceled, ISR02 should contain the current day's date or the next day as the date that you are advising JCPenney Catalog of the cancellation. REFERENCE IDENTIFICATION (REF) Reference Identification Qualifier "VN" (Vendor Order Number) [REF01] and identification number [REF02] are required on a Catalog 870 transmission. The trading partner must assign a unique reference number to identify the order number and the associated revised or promise-to-ship ship date the supplier has assigned


to the JCPenney Catalog purchase order. Do not duplicate the REF VN number when sending multiple updates against a selected order. Each new date should have its own unique number. Note: The REF 'VN' number may contain alpha/numeric characters. Please do not send all zeroes. This reference number will be returned on subsequent 869(s). ITEM LEVEL PURCHASE ORDER BASELINE ITEM DATA (PO1) The purpose of this segment is to identify the SKU number (item) and quantity that will be shipped by the revised or promise-to-ship ship date. PO102 contains the SKU quantity from the original purchase order less cancellations. In the event of a cancellation, the canceled quantity is subtracted from the original SKU quantity and the new amount is sent in PO102 (Quantity Ordered) which will equal the number of saleable units. ITEM STATUS REPORT (ISR) The ISR segment is generated at either the order level or the item level but not at both levels. The purpose of the ISR segment is to specify the order status code and the revised or promise-to-ship ship date for a selected order and selected items on that order. In ISR01 [Shipment/Order Status Code], the status codes processed by the Catalog system are: BP (Shipment Partial, Back Order to Ship On), ED (Expected-To Ship By), RD (Revised Expect to Ship By) and IC (Item Canceled). These codes used at the item level will indicate that a specific item or items on the selected order will be affected by the status. The revised or promise-to-ship ship date [ISR02] is required and should always be a future date on Catalog orders. This ship date is determined by the trading partner as to when goods will be available for shipment to JCPenney Catalog. If the item is canceled, ISR02 should contain the current day's date or the next day as the date that you are advising JCPenney Catalog of the cancellation. QUANTITY (QTY) The purpose of this segment is to specify the number of units of the selected item to be shipped by the revised or promised-to-ship ship date. The Quantity qualifier [QTY01] is always 01 [Discrete Quantity]. QTY02 is the number of units to be shipped by the revised or promise-to ship date. On cancellations, the quantity is zero.


870 - ORDER STATUS REPORT (CATALOG)

Business Example: Unsolicited Report (Selected Order-All Items)

The following is an example of an unsolicited 870 - Order Status Report. JCPenney Supplier Acme Towel Company (JCPenney assigned supplier number 234567) received re-buy on Lot/SKU numbers 74012340042 and 74012340067 (a 3-piece bath towel set in colors Aqua (0042) and Beige (0067)) from sub 740 (Towels) for a total of 600 units. Purchase orders 1234567R, 1234678C, 1234789K, 23450123H and 2345234A were generated on April 20, 2002 with an at once ship date of April 22, 2002 and a cancel by date of May 3, 2002. Due to an unforeseen circumstance, the trading partner is unable to ship the merchandise by cancel date. Acme Towel Company transmitted an unsolicited 870 on April 23, 2002, providing JCPenney an 'expected to ship' by date of May 10, 2002 for all orders and items.

EDI TRANSMISSION DATA EXPLANATION HEADER

ST 870 234567891 234567891: Transaction Set Control Number BSR 3 PA 00000001 20020423 3: Status Report Code PA: Order Code - Selected

Order-All Items. 00000001: Reference Identification. 20020423: Date of report (04/23/2002).

LOOP: REF REF IA 234567 IA: Reference Identification Qualifier (Internal

Supplier Number). 234567: JCPenney's assigned supplier number.

ORDER LOOP: HL HL 1 O 1: Hierarchical ID Number. O: Hierarchical Level

Code (Order). PRF 1234567R 20020420 1234567R: JCPenney Catalog purchase order

number. 20020420: Purchase order date (04/20/2002).

LOOP: HL/ISR ISR ED 20020510 ED: Order Status Code - 'Expect to Ship By'.

20020510: Expected to ship by date (05/10/2002) LOOP: HL/REF REF DP 740 DP: Reference Identification Qualifier (Department

Number) 740: JCPenney Subdivision Number. REF VN 12345678910 VN: Reference Identification Qualifier (Vendor

Order Number) 12345678910: Supplier's order number.

2nd ORDER LOOP: HL HL 2 O 2: Hierarchical ID Number. O: Hierarchical Level

Code (Order). PRF 1234678C 20020420 1234678C: JCPenney Catalog purchase order



20020510: Expected to ship by date (05/10/2002) LOOP: HL/REF


REF DP 740 DP: Reference Identification Qualifier (Department Number). 740: JCPenney Subdivision Number.

REF VN 12345678911 VN: Reference Identification Qualifier (Vendor Order Number) 12345678911: Supplier's order number.

3rd ORDER LOOP: HL HL 3 O 3: Hierarchical ID Number. O: Hierarchical Level

Code (Order). PRF 1234789K 20020420 1234789K: JCPenney Catalog purchase order




Number).740: JCPenney Subdivision Number. REF VN 12345678912 12345678912: Supplier's order number.

4th ORDER LOOP: HL HL 4 O 4: Hierarchical ID Number. O: Hierarchical Level

Code (Order). PRF 2345123H 20020420 2345123H: JCPenney Catalog purchase order




Number). 740: JCPenney Subdivision Number. REF VN 12345678913 VN: Reference Identification Qualifier.

12345678913: Supplier's order number. 5th ORDER

LOOP: HL HL 5 O 5: Hierarchical ID Number. O: Hierarchical Level

Code (Order). PRF 2345234A 20020420

2345234A: JCPenney Catalog purchase order number. 20020420: Purchase order date (04/20/2002).

LOOP: HL/ISR ISR ED 20020510

ED: Order Status Code - 'Expect to Ship By'. 20020510: Expected to ship by date (05/10/2002)

LOOP: HL/REF REF DP 740

DP: Reference Identification Qualifier (Department Number). 740: JCPenney Subdivision Number.

REF VN 12345678914 VN: Reference Identification Qualifier (Vendor


Order Number).12345678914: Supplier's order number.

TRAILER CTT 5 5: Number of HL segments in the transaction. SE 30 234567891 30: Count of all segments including ST and SE.

234567891: Transaction Set Control Number (same as ST02).


870 - ORDER STATUS REPORT (Catalog)

Business Example: Response to 869 Order Status Inquiry (Selected Order - All Items)

This is an example of an 870 Order Status Report in response to an 869 Order Status Inquiry. JCPenney Catalog issued an 869 inquiry to Acme Shirt Company [JCPenney assigned supplier number 234567] on March 16, 2002 for all items on purchase orders 1234567A, 2345678K and 3456789C. These orders were created on 02/18/2002 with an early ship date of 2/19/02 and a ship by date of 03/08/02. These orders are past the cancel date and JCPenney Catalog is requesting an update on the status of these orders.

Acme Shirt Company transmitted an 870 on March 18, 2002 with an 'expected to ship' by date of 03/22/02 on all of the above orders and all items.


ST 870 978645312 870: Transaction Set ID 978645312: Transaction Set Control Number

BSR 1 PA 00000001 20020318

1: Status Report Code "Response to an Order Status Inquiry - 869". PA: Selected Order - All Items. 00000001: Reference Identification.20020318: Transmission date (03/18/2002).


Supplier number) .234567: JCPenney assigned supplier number.


Code - "Order" PRF 1234567A 20020218

1234567A: JCPenney Catalog purchase order number. 20020218: Purchase order date (02/18/2002)

LOOP: HL/ISR ISR ED 20020322 ED: Expected to Ship By. 20020322: Expected to

ship by date (03/22/2002). LOOP: HL/REF REF DP 531 DP: Reference Identification Qualifier (Department

Number) 531: Subdivision number (Department number)

REF VN 34567891 VN: Reference Identification Qualifier (Vendor Order Number) 34567891: Supplier's Order number.

2nd ORDER LOOP: HL HL 2 O 2: Hierarchical ID Number. O: Hierarchical Level

Code - "Order" PRF 2345678K 20020218

2345678K: JCPenney Catalog purchase order number. 20020218: Purchase order date (02/18/2002)



ship by date (03/22/2002). LOOP: HL/REF REF DP 531 DP: Reference Identification Qualifier 531:

Subdivision number (Department number) REF VN 42132152 VN: Reference Identification Qualifier 42132152:

Supplier's Order number. 3rd ORDER


Code - "Order" PRF 3456789C 20020218

3456789C: JCPenney Catalog purchase order number. 20020218: Purchase order date (02/18/2002)


ship by date (03/22/2002). LOOP: HL/REF REF DP 531 DP: 531: Subdivision number (Department number)REF VN 53243233 VN: Reference Identification Qualifier 53243233:

Supplier's Order number. TRAILER

CTT 3 3: Number of HL segments in the transaction. SE 20 978645312

20: Count of all segments including ST and SE. 978645312: Transaction Set Control number (same as ST02).



Business Example: Response to an 869 Order Status Inquiry (Selected Order-Selected Items, Two Shipments)

The following example is an 870 in response to an 869 Order Status Inquiry. JCPenney Catalog systems issued an 869 Order Status Inquiry to Acme Shirt Company [JCPenney assigned supplier number 234567] on March 16, 2002 for items 5311234 0059 (Men’s Small Tee) and 5311234 0125 Men's X-Large Tee) on purchase orders 7654321H, 8765432R and 9876543A from sub 531. These orders were created on 2/18/2002 with an early ship date of 02/19/2002 and a ship by date of 03/08/2002.

Acme Shirt Company transmitted an 870 response to the 869 inquiry on March 19,2002, advising JCPenney of expected ship by dates of March 22, 2002 for item 5311234 0059 and March 29, 2002 for item 5311234 0125.

Purchase Order Number Lot/Sku Numbers on Inquiry Original Quantity on

Order Qty to be shipped by expected ship date

7654321H 5311234 0059 25 25 5311234 0125 30 30

8765432R 5311234 0059 25 25 5311234 0125 35 35

9876-543A 5311234 0059 30 30 5311234 0125 35 35


ST 870 765432189 870: Transaction Set ID. 765432189: Transaction Set Control Number

BSR 1 PP 00000001 20020319 1: Status Report Code "Response to an Order Status Inquiry - 869". PP: Selected Order - Selected Items. 00000001: Reference Identification. 20020319: Report date (03/19/2002).


Vendor Number) 234567: JCPenney assigned supplier number.


Code - "Order" PRF 7654321H 20020218 7654321H: JCPenney Catalog purchase order

number. 20020218: Purchase order date (02/18/2002)

LOOP: HL/REF REF DP 531 DP: Reference Identification Qualifier (Department

Number) 531: Subdivision number.



ITEM LOOP: HL HL 2 1 I 2: Hierarchical ID Number. 1: Hierarchical Parent ID

number. I: Hierarchical Level Code. LOOP: HL/PO1 PO1 25 EA IN 53112340059 25: Quantity Ordered. EA: Unit of Measurement

Code. IN: Buyer's Item Number. 53112340059: Catalog Lot/SKU number (item number).

LOOP: HL/PO1/ISR ISR ED 20020322 ED: Expected to Ship By. 20020322: Expected to

ship by date (03/22/2002). QTY 01 25 EA 01: Discrete quantity. 25: Quantity to be shipped by

the expected ship date. EA: Unit of measurement. ORDER


Code - "Order" PRF 7654321H 20020218 7654321H: JCPenney Catalog purchase order



Number)531: Subdivision number (Department number)


2nd ITEM LOOP: HL HL 4 3 I 4: Hierarchical ID Number. 3: Hierarchical Parent ID





the expected ship date. EA: Unit of measurement. 2nd ORDER


Code - "Order"


PRF 8765432R 20020218 8765432R: JCPenney Catalog purchase order number. 20020218: Purchase order date (02/18/2002)











Code - "Order" PRF 8765432R 20020218 8765432R: JCPenney Catalog purchase order





2nd ITEM LOOP: HL HL 8 7 I 8: Hierarchical ID Number. 7: Hierarchical Parent ID




ship by date (03/29/2002).


QTY 01 35 EA 01: Discrete quantity. 35: Quantity to be shipped by the expected ship date. EA: Unit of measurement.

3rd ORDER LOOP: HL HL 9 O 9: Hierarchical ID Number. O: Hierarchical Level

Code - "Order" PRF 9876543A 20020218 9876543A: JCPenney Catalog purchase order


LOOP: HL/REF REF DP 531 DP: Reference Identification Number (Department


REF VN 12345680 VN: Reference Identification Qualifier (Vendor Order Number)12345680: Supplier's Order number.

ITEM LOOP: HL HL 10 9 I 10: Hierarchical ID Number. 9: Hierarchical Parent

ID number. I: Hierarchical Level Code. LOOP: HL/PO1 PO1 30 EA IN 53112340059 30: Quantity Ordered. EA: Unit of Measurement








LOOP: HL/REF REF DP 531 DP: Hierarchical ID Number. 531: Subdivision

number (Department number) REF VN 123456801 VN: Reference Identification Qualifier (Vendor

Order Number)123456801: Supplier's Order number.

2nd ITEM LOOP: HL HL 12 11 I 12: Hierarchical ID Number. 11: Hierarchical Parent

ID number. I: Hierarchical Level Code. LOOP: HL/PO1 PO1 35 EA IN 53112340125 35: Quantity Ordered. EA: Unit of Measurement





the expected ship date. EA: Unit of measurement. TRAILER

CTT 12 12: Number of HL segments in the transaction. SE 53 765432189 53: Count of all segments including ST and SE.

765432189: Transaction Set Control number (same as ST02).



Business Example: Cancellations (Select Order-All Items and Selected Order-Selected Items)

This example illustrates a cancellation of the entire purchase order, unshipped SKU quantities on selected items, the balance left from a partial shipment and a reduction of the original ordered quantity with a revised ship date.

On April 22, 2002 Acme Shirt Company (JCPenney assigned supplier number 234567) transmitted two 870's, canceling the following:

PO# Lot/SKU to be Canceled

Order Date

Early Ship Date

Ship By (Cancel)

Date

Orig. Qty Ordered Qty Canceled

1243687A all SKUs 04/13/02 04/15/02 04/26/02 all quantities all quantities 2345789A 5311111 0067 03/30/02 04/01/02 04/12/02 30 12

5311111 0265 10 10 3456891C 5311234 0059 03/18/02 03/19/02 04/19/02 47 1 4567123K 5311234 0042 04/06/02 04/08/02 04/19/02 15 3

5311234 0059 17 3 5311234 0067 23 3

On purchase order 2345789A, Acme Shirt Company shipped 18 units of SKU 5311111 0067 and is canceling the open balance of 12 units. SKU 5311111 0265 was out of stock and the entire quantity is being canceled.

An 870 was previously transmitted against purchase order number 4567123K with a 'promise-to-ship' date of 04/26/02. The trading partner has revised the date to 05/03/02 and has also reduced the original ordered quantities. There has not been a shipment against this purchase order.



BSR 3 PA 00000001 20020422 3: Status Report Code "Unsolicited Response". PA: Selected Order - All Items. 00000001: Reference Identification.20020422: Report date (04/22/2002).


Supplier number). 234567: JCPenney assigned supplier number.




LOOP: HL/ISR ISR DE 20020422 DE: Deleted Order. 20020422: Date order was


canceled (04/22/02). LOOP: HL/REF REF DP 531 DP: Reference Identification Qualifier (Department

Number). 531: Subdivision number (Department number)

REF VN 12345678 VN: Reference Identification Qualifier (Vendor Number) 12345678: Supplier's Order number.

TRAILER CTT 1 1: Number of HL segments in the transaction SE 10 678901234 10: Count of all segments including ST and SE.

678901234: Transaction Control Number (same as ST02)

2nd 870 HEADER ST 870 678901235 870: Transaction Set ID. 678901235: Transaction

Control Number. BSR 3 PP 00000002 20020422 3: Status Report Code "Unsolicited Report. PP:

Selected Order-Selected Item. 000000002: Reference Identification. 20020422: Report Date.

REF IA 234567 IA: Reference Identification Qualifier (Internal Supplier number). 234567: JCPenney assigned supplier number.

1st ORDER in 2nd 870 LOOP: HL HL 1 O 1: Hierarchical ID number. O: Hierarchical Level



LOOP: HL/REF REF DP 531 DP: Reference Identification Qualifier. 531:

Subdivision number (Department number) REF VN 123456783 VN: Reference Identification Qualifier (Vendor Order

Number). 123456783: Supplier's Order number. ITEM

LOOP: HL HL 2 1 I 2: Hierarchical ID Number. 1: Hierarchical Parent ID


Code. IN: Buyer's Item Number. 53111110067: Catalog SKU number.

LOOP: HL/PO1/ISR ISR IC 20020422 IC: Item Cancelled. 20020422: Date shipped

(04/22/2002). QTY 01 0 EA 01: Discrete quantity. 0: Quantity to be shipped. EA:

Unit of measurement. 2nd ITEM


number. I: Hierarchical Level Code.


LOOP: HL/PO1 PO1 0 EA IN 53111110265 0: Quantity Ordered. EA: Unit of Measurement


LOOP: HL/PO1/ISR ISR IC 20020422 IC: Item Canceled. 20020422: Date in which item

was canceled (04/22/2002). QTY 01 0 EA 01: Discrete quantity. 0: Quantity to be shipped by

the expected ship date. EA: Unit of measurement. 2nd ORDER


Code - "Order" PRF 3456891C 20020318 3456891C: JCPenney Catalog purchase order



number). 531: Subdivision number REF VN 123456784 VN: Reference Identification Qualifier (Vendor Order

Number ) 123456784: Supplier's Order number. ITEM




LOOP: HL/PO1/ISR ISR IC 20020422 IC: Item Cancelled. 20020422: Date shipped

(04/22/2002). QTY 01 0 EA 01: Discrete quantity. 0: Quantity to be shipped by

the expected ship date. EA: Unit of measurement. 3rd ORDER

LOOP: HL HL 6 O 6: Hierarchical ID number. O: Hierarchical Level

Code - "Order" PRF 4567123K 20020218 4567123K: JCPenney Catalog purchase order



number). 531: Subdivision number. REF VN 12345677 VN: Reference Identification Qualifier (Vendor Order

Number). 12345677: Supplier's Order number. ITEM


number. I: Hierarchical Level Code. LOOP: HL/PO1


PO1 12 EA IN 53112340042 12: Quantity Ordered. EA: Unit of Measurement Code. IN: Buyer's Item Number. 53112340042: Catalog SKU number.

LOOP: HL/PO1/ISR ISR RD 20020503 RD: Revised Expected to Ship By. 20020503:

Revised expected to ship by date (05/3/2002). QTY 01 12 EA 01: Discrete quantity. 12: Quantity to be shipped by

the expected ship date. EA: Unit of measurement. 2nd ITEM




LOOP: HL/PO1/ISR ISR RD 20020503 RD: Revised Expected to Ship By. 20020503: Date

of partial shipment (05/03/2002). QTY 01 14 EA 01: Discrete quantity. 14: Quantity to be shipped by

the expected ship date. EA: Unit of measurement. 3rd ITEM




LOOP: HL/PO1/ISR ISR RD 20020503 RD: Revised Expected to Ship By. 20020503: Date

of partial shipment (05/03/2002). QTY 01 20 EA 01: Discrete quantity. 20: Quantity to be shipped by





870 - ORDER STATUS REPORT BUSINESS RULES (FACTORY SHIP) [revised 03/2006] The purpose of this document is to provide an understanding of JCPenney's use of some of the major sections in the 870 Order Status Report document. The 870 may be sent as an unsolicited report or in response to an 869 Order Status Inquiry. The 870 is an advisory that the supplier will use to send JCPenney Catalog Factory Ship a confirmation of shipment, an expected or revised ship date, or the cancellation of SKU quantities (merchandise) that are unavailable for shipment by the requested ship date. HEADER LEVEL BEGINNING SEGMENT (BSR) The purpose of the BSR segment is to identify the Order Status Report type. Status Report codes [BSR01] accepted by Factory Ship are: 1 (Response to an Order Status Inquiry) and 3 (Unsolicited Report). Factory Ship will process an Order/Item Code of 'PP' (Selected Order - Selected Item) in BSR02. Order code 'PA' will not be used on responses to Catalog Factory Ship inquiries. The 870 must be processed in the sequence in which they are created. In BSR03 the reference identification number is used to synchronize the 870 and insure that none are lost. The reference number should be assigned sequentially beginning with "00000001" for the very first 870 transaction sent and incremented by 1 with each BSR sent. NAME (N1) This segment is not used by Catalog Factory Ship. ORDER LEVEL PURCHASE ORDER REFERENCE This segment is used to identify the Retailer’s original purchase order. PRF04 (Retailer’s original purchase order date) is required by Catalog Factory Ship. REFERENCE IDENTIFICATION [REF VN] This segment is not used by Catalog Factory Ship. ITEM LEVEL PURCHASE ORDER BASELINE ITEM DATA (PO1) The purpose of this segment is to identify the SKU number (item) and quantity that will be shipped by the revised or promise-to-ship ship date. The Assigned Identification number in PO101 is a 20-digit number ID number found in the PO101 (Assigned ID) data field of the 850 document. PO102 contains the SKU quantity from the original purchase order. In the event of a cancellation, the canceled quantity is subtracted from the original SKU quantity and the new amount is sent in PO102 (Quantity Ordered) which will equal the number of saleable units. This data field will contain a zero (0) if the entire SKU quantity is canceled. ITEM STATUS REPORT (ISR)


The purpose of the ISR segment is to specify the order status code and the revised or expected to ship by date for a selected order and selected items on that order. In ISR01 (Shipment/Order Status Code), the status codes processed by the Catalog Factory Ship system are: CC (Shipment Complete On), ED (Expected-To Ship By), RD (Revised Expect to Ship By) and IC (Item Canceled). These codes used at the item level will indicate that a specific item or items on the selected order will be affected by the status. The revised or expected to ship by date (ISR02) is required and should always be a future date on status codes of 'RD or ED'. This ship date is determined by the trading partner as to when goods will be available for shipment to JCPenney Catalog. If the item is canceled, ISR02 should contain the current day's date or the next day as the date that you are advising JCPenney Catalog of the cancellation. When using status code CC (Shipment Complete On), ISR02 should contain the shipment date of the item. Note: Catalog Factory Ship doesn't allow partial shipments against an order; therefore the use of status code BP (Shipment Partial, Backorder to Ship On) is not acceptable. If the entire order can not be shipped on one shipment, the entire order must be canceled. QUANTITY (QTY) The purpose of this segment is to specify the number of units of the selected item to be shipped by the revised or expected to ship by date. The Quantity qualifier (QTY01) is always 01 (Discrete Quantity). QTY02 is the number of units to be shipped by the revised or expected to ship by date. On cancellations, the quantity is zero.


870 - ORDER STATUS REPORT (FACTORY SHIP)

Business Example: Revised Ship Date

The following example is an 870 in response to an 869 Order Status Inquiry. The Acme Appliance Company [JCPenney assigned supplier number 234567] received PO #123445678 on 6/16/03. An 869 inquiry was sent to the supplier on 6/20/03. Due to the manufacturer's delay in producing item number 85712340000 [sub 857], Acme creates an 870 on 6/20/03, revising the ship date to 7/8/03.







Code - "Order" PRF 123445678 20030616 123445678: JCPenney Catalog purchase order



Number) 857: Subdivision number. ITEM


number. I: Hierarchical Level Code. LOOP: HL/PO1 PO1 00000000000000000456 1 EA

IN 85712340000 00000000000000000456: Assigned ID. Line item number assigned on the PO. 1: Quantity Ordered. EA: Unit of Measurement Code. IN: Buyer's Item Number. 85712340000: Catalog Factory Ship Lot/SKU number (item number).

LOOP: HL/PO1/ISR ISR RD 20030708 RD: Revised Expect to Ship By. 20030708:

Expected to ship by date (07/08/03). QTY 01 1 EA 01: Discrete quantity. 1: Quantity to be shipped by





870 - ORDER STATUS REPORT (FACTORY SHIP)

Business Example: Cancellation

The following example is an 870 in response to an 869 Order Status Inquiry. The Acme Appliance Company [JCPenney assigned supplier number 234567] received PO #123445678 on 6/16/03. An 869 inquiry was sent to the supplier on 6/20/03. Due to the manufacturer's delay in producing item number 85712340000 [sub 857], Acme creates an 870 on 6/20/03, canceling the order.







Code - "Order" PRF 123445678 20030616 123445678: JCPenney Catalog purchase order



Number) 857: Subdivision number. ITEM

LOOP: HL HL 2 1 I 2: Hierarchical ID Number. 1: Hierarchical Parent

ID number. I: Hierarchical Level Code. LOOP: HL/PO1 PO1 00000000000000000456 0 EA IN 85712340000

00000000000000000456: Assigned ID. Line item number assigned on the PO. 0: Quantity Ordered. EA: Unit of Measurement Code. IN: Buyer's Item Number. 85712340000: Catalog Factory Ship Lot/SKU number (item number).

LOOP: HL/PO1/ISR ISR IC 20030620 IC: Revised Expect to Ship By. 20030620:

Expected to ship by date (06/20/03). QTY 01 0 EA 01: Discrete quantity. 0: Quantity to be shipped by





870 ORDER STATUS REPORT BUSINESS RULES (DFW (Furniture)) The 870 for DFW is an unsolicited report. It is not used in response to transaction set 869 Order Status Inquiry. The 870 is used to confirm merchandise cost, to provide an estimated ship by date and to cancel an entire purchase order or unshipped balances. The purpose of this document is to provide an explanation of JCPenney’s use of some of the major sections in the 870 Order Status Report document. HEADER LEVEL BEGINNING SEGMENT (BSR) The purpose of the BSR segment is to identify the type of Order Status Report. DFW suppliers will always send Status Report Code 2 (Prearranged Scheduled or Agreement) in data field BSR01. Order/Item Codes “PA” (Selected Orders – All Items) and “PP” (Selected Orders – Selected Items) in data field BSR02 are used to identify the structure of the 870. Order/Item Code ‘PA’ is used when reporting the status of an entire purchase order. Item level details are not sent when using this code. Order/Item Code ‘PP’ is used when reporting item level details of a selected order. To process the 870 accurately and to insure that none are lost, JCPenney will process the 870 in the sequence in which it was 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 first 870 transaction set sent and incrementing by 1 with each BSR sent within the interchange. NAME (N1) This segment is used to identify the DFW unit number in data field N104. This unit number is found in data field N104 (where N101 = ST) of the 850 Purchase Order. The entity identifier code (N101) is ‘Z7’ (Mark-for Party). ORDER LEVEL ITEM STATUS REPORT (ISR) The purpose of the ISR segment at the order level is to indicate the order status code which best identifies the status of all items on a selected order. The only Order Level status code (ISR01) accepted and processed by DFW (Furniture) systems is: DE (Delete). ISR02 (Date) is not required for status code ‘DE’. Transmission of this status code will cancel the all items and quantities on the purchase order. The ISR segment is generated at either the order or item level but not at both levels. REFERENCE IDENTIFICATION (REF) Reference Identification Qualifier ‘VN’ (Vendor Order Number) [REF01] and identification number [REF02] are used to identify the supplier’s internal order number assigned to the original JCPenney purchase order. ITEM LEVEL PURCHASE ORDER BASELINE ITEM DATA (PO1) The purpose of this segment is to identify the JCPenney product number and the quantity ordered. Data fields PO104 (Unit Price) and P0105 (Basis of Unit Price Code) are required by DFW to confirm the merchandise cost (PO104). The JCPenney product number sent in data field PO107 should be in the


following format: AAAABBBBCCCCC where AAAA = lot number, BBBB = line number, CCCCC = size description. There is one PO1 segment for each item. ITEM STATUS REPORT (ISR) The purpose of the ISR segment at the item level is to indicate the item status code which best identifies the status of selected items on an order. Item Level status codes (ISR01) accepted and processed by DFW systems are: 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), RW (Revised Expect to Ship Week Of), RD (Revised Expect to Ship By), and IC (Item Cancel). Data field ISR02 is required except for status code ‘IC’. The date contained in ISR02 must reflect the estimated ship by date for the item indicated in P0107. The ISR segment is generated at either the order or item level but not at both levels. QUANTITY (QTY) This segment is used to specify the number of units to be shipped by the estimated ship date indicated in ISR02. The quantity qualifier (QTY01) is always ‘01’ (Discrete Quantity). This segment is sent only, if item level details are transmitted in the 870.


870 ORDER STATUS REPORT [DFW] Business Example: PA (Selected Order- All Items) Scenario: On 8/16/2004, the ACME Furniture Company [JCPenney supplier number 234567] sent an 870 canceling purchase order 11145678. The DFW unit number is 95596; the subdivision is 792, and the Supplier’s Order number 00792002. EDI TRANSACTION EXPLANATION

HEADER ST 870 000000001 870: Transaction Set ID. 000000001: Transaction

Set Control Number. BSR 2 PA 00000001 20040816 2: Status Report Code [Prearranged Schedule or

Agreement]. PA: Order/Item Code [Selected Orders – All Items]. 00000001: Reference Identification. 20040816: Date [8/16/04].

REF IA 234567 IA: Reference Identification Qualifier. 234567: Reference Identification.

N1 Z7 92 95596 Z7: Entity Identifier Code. 92: Identification Code Qualifier. 95596: Identification Code.

ORDER Loop: HL HL 1 O 1: Hierarchical ID Number O: Hierarchical Level

Code [Order]. PRF 11145678 20040802 11145678: Purchase Order Number. 20040802:

Date [08/02/2004]. ISR DE DE: Shipment/Order Status Code [Delete] REF DP 792 DP: Reference Identification Qualifier [Department

Number]. 792: Reference Identification [Subdivision number].

REF VN 00792002 VN: Reference Identification Qualifier [Vendor Order Number]. 00792002: Reference Identification [Supplier’s Order Number].

TRAILER CTT 1 1: Number of Line Items [Number of HL segments

in the transaction]. SE 11 000000001 11: Number of Included Segments [Count of all

segments including ST and SE]. 000000001: Transaction Set Control Number.


870 ORDER STATUS REPORT [DFW] Business Example: PP (Selected Order-Selected Items) Scenario: The ACME Furniture Company [JCPenney supplier number 234567] sent an 870 on two purchase orders, confirming the cost of the merchandise and advising JCPenney to expect these orders to be shipped by 8/27/04. The first order 11123456, contained item number 12345678*ONLY, quantity ordered 1, merchandise cost $160.00 and item number 23456789*ONLY, quantity ordered 2, merchandise cost $55.00. The second order 11134567, was for item number 34567890*ONLY, quantity ordered 1, merchandise cost $230.00. The 870 is for DFW unit number 95596. The subdivision is 792. EDI TRANSACTION EXPLANATION

HEADER ST 870 000000001 870: Transaction Set ID. 000000001: Transaction

Set Control Number. BSR 2 PP 00000001 20040816 2: Status Report Code [Prearranged Schedule or

Agreement]. PP: Order/Item Code [Selected Orders – Selected Items]. 00000001: Reference Identification. 20040816: Date [8/16/04].

REF IA 234567 IA: Reference Identification Qualifier. 234567: Reference Identification.

N1 Z7 92 95596 Z7: Entity Identifier Code. 92: Identification Code Qualifier. 95596: Identification Code.

ORDER Loop: HL HL 1 O 1: Hierarchical ID Number O: Hierarchical Level


Date [08/02/2004]. REF DP 792 DP: Reference Identification Qualifier [Department



ITEM Loop: HL HL 2 1 I 2: Hierarchical ID Number. 1: Hierarchical Parent ID

Number. I: Hierarchical Level Code (Item). PO1 1 EA 160 WH IN 12345678*ONLY 1: Quantity Ordered. EA: Unit of Measurement

Code. 160: Unit Price [SKU cost] $160.00. WH: Basis of Unit Price Code [Wholesale]. IN: Product/Service ID Qualifier [Buyers Item Number]. 12345678*ONLY: Product/Service ID [JCP lot/line/size description].

ISR ED 20040827 ED: Shipment/Order Status Code [Expected To Ship By]. 20040827: Date [08/27/2004].

QTY 01 1 EA 01: Quantity Qualifier [Discrete Quantity]. 1: Quantity. EA: Unite of Measurement Code [Each].

ITEM # 2


Loop: HL HL 3 1 I 3: Hierarchical ID Number. 1: Hierarchical Parent ID





ORDER #2 Loop: HL HL 4 O 4: Hierarchical ID Number O : Hierarchical Level


Date [08/02/2004]. REF DP 792 DP: Reference Identification Qualifier [Department



ITEM Loop: HL HL 5 4 I 5: Hierarchical ID Number. 4: Hierarchical Parent ID





TRAILER CTT 5 5: Number of Line Items [Number of HL segments in

the transaction]. SE 26 000000001 26: Number of Included Segments [Count of all

segments including ST and SE]. 000000001: Transaction Set Control Number [Same number as in ST02].


870 ORDER STATUS REPORT BUSINESS RULES – Liquidation (Outlet Stores) The purpose of this document is to provide an explanation of JCPenney's use of some of the major sections in the 870 Order Status Report document for the Liquidation (Catalog Outlet) department. The 870 is an advisory that the supplier will use to send JCPenney Liquidation an expected or revised ship date, or a cancellation of an entire PO or selected SKU quantities that are unavailable for shipment by the requested ship date. HEADER LEVEL BEGINNING SEGMENT (BSR) The purpose of the BSR segment is to identify the Order Status Report type. Status Report code [BSR01] accepted by Liquidation: 3 (Unsolicited Report). Liquidation will process an Order/Item Code of ‘PA’ (Selected Order – All Items) or 'PP' (Selected Order - Selected Item) in BSR02. The 870 must be processed in the sequence in which they are created. In BSR03 the reference identification number is used to synchronize the 870 and insure that none are lost. The reference number should be assigned sequentially beginning with "00000001" for the very first 870 transaction sent and incremented by 1 with each BSR sent. NAME (N1) This segment is used to identify the Mark-For Party [Z7]. The Mark-For Party is found in the N1 [Z7] segment of the 850 document. ORDER LEVEL REFERENCE IDENTIFICATION [REF VN] This segment identifies the Vendor Order number. The Vendor Order number or Supplier’s Order Number is assigned by the trading partner. ITEM STATUS REPORT (ISR) The purpose of the ISR segment is to identify the order/item status codes. Status codes processed at the item level can be found in the ISR segment at the order level. A date in ISR02 is required if the status code indicated in ISR01 is BP, CC, CP, ED, or RD. A status code of CC [Shipment Complete On] advises when a shipment was shipped complete. An ASN should have already been sent for this shipment. The 870 does not replace the 856 [ASN] for reporting shipments. ITEM LEVEL PURCHASE ORDER BASELINE ITEM DATA (PO1) The purpose of this segment is to identify the SKU number (item) and quantity that will be shipped by the revised or promise-to-ship ship date. PO102 contains the SKU quantity from the purchase order. In PO107, the item number for Liquidation [Catalog Outlet] is sent in the following format: AAAABBBBCCCCC where AAAA = lot, BBBB = line and CCCCC = size description. The size description *ONLY denotes assorted sizes, no size, or prepacks.


Note: Please do not use an asterisk (*) as your segment terminator, data element separator or delimiter. This character is sent and received by JCPenney as data. ITEM STATUS REPORT (ISR) The purpose of the ISR segment is to identify the order/item status codes. Status codes processed at the item level can be found in the ISR segment at the detail level. A date in ISR02 is required if the status code indicated in ISR01 is BP, CC, CP, ED, or RD. A status code of CC [Shipment Complete On] advises when a shipment was shipped complete. An ASN should have already been sent for this shipment. The 870 does not replace the 856 [ASN] for reporting shipments. QUANTITY (QTY) The purpose of this segment is to specify the number of units of the selected item to be shipped by the revised or expected to ship by date. The Quantity qualifier (QTY01) is always 01 (Discrete Quantity). QTY02 is the number of units to be shipped by the revised or expected to ship by date.


Liquidation Status Code Requirements for Transactions 856 and 870 Purpose: To provide an explanation of JCPenney’s Liquidation [Outlet Stores] usage of the Order/Item Status Codes in EDI Transactions 856 (TD506) and 870 (ISR).

ORDER LEVEL

Status Code 856 – Ship Notice/Manifest [TD506]

870 – Order Status Report [ISR01

BP [Shipment Partial, Back Order to

Ship On]

Status code BP is used to identify a partial shipment of the order. The open balance(s) of the order will be shipped later.

If BP is sent on the 856, then the 870 is sent with a status of BP with the ‘Back Order to Ship On’ date in ISR02.

CC [Shipment Complete On]

Status code CC is used to identify a complete shipment.

If CC is sent on the 856, then the 870 is not required.

CP [Partial Shipment on (Date), Considered No Backorder]

Status code CP is used to identify a partial shipment. The open balance(s) of the order will be canceled.

If CP is sent on the 856, the 870 is also sent with a status code of CP and the shipment date in ISR02.

DE [Deleted Order]

Status code DE is used to identify the cancellation of an entire order.

If DE is sent on the 856, the 870 is also sent with a status code of DE.

ED [Expect to Ship By Date]

Not used on the 856 Status code ED is used if merchandise on the entire order is not shipping on time. The 870 must be sent prior to Cancel Date of the order. The Expect to Ship by Date must be sent in ISR02.

RD [Revised Expect to Ship By Date

Not used on the 856 Status code RD is used if merchandise on the entire order is not shipping on time. The 870 must be sent prior to Cancel Date or Expect to Ship by Date of the order. The Revised Expect to Ship by Date must be sent in ISR02.


ITEM LEVEL

Status Code 856 – Ship Notice/Manifest [TD506]

870 – Order Status Report [ISR01

BP [Shipment Partial, Back Order to

Ship On]

Status code BP is used to identify a partial shipment of selected items on an order. The open balance(s) of the item(s) will be shipped later.

If BP is sent on the 856, then the 870 is sent with a status of BP with the ‘Back Order to Ship On’ date in ISR02.

CC [Shipment Complete On]

Status code CC is used to identify a complete shipment of an item.

If CC is sent on the 856, then the 870 is not required for the selected item(s) indicated on the 856.

CP [Partial Shipment on (Date), Considered No Backorder]

Status code CP is used to identify a partial shipment of an item(s). The open balance(s) of item(s) will be canceled.

If CP is sent on the 856, the 870 is also sent with a status code of CP and the shipment date of the shipped item(s) in ISR02.

ED [Expect to Ship By Date]

Not used on the 856 Status code ED is used if an item(s) on order is not shipping on time. The 870 must be sent prior to Cancel Date of the order. The Expect to Ship by Date must be sent in ISR02.

IC [Item Cancel]

Status code IC is used to identify the cancellation of an entire item.

If IC is sent on the 856, the 870 is also sent with a status code of IC. A date is not required in ISR02.

RD [Revised Expect to Ship By Date

Not used on the 856 Status code RD is used if a selected item(s) on order is not shipping on time. The 870 must be sent prior to Cancel Date or Expect to Ship by Date of the order. The Revised Expect to Ship by Date must be sent in ISR02.


870 - ORDER STATUS REPORT - Liquidation [Outlet Stores]

Business Example: Unsolicited Report (Selected Order-All Items)

Scenario: The following is an example of an unsolicited 870 - Order Status Report. JCPenney Supplier ACME SHIRT CO (JCPenney assigned supplier number 234567) received purchase order 93412345 on 11/9/04 with an at once ship date of 11/9/04 and a cancel date of 11/26/04. Due to an unforeseen circumstance, the trading partner is unable to ship the merchandise prior to the cancel date. ACME transmitted an unsolicited 870 on 11/17/2004, providing JCPenney an 'expected to ship' by date of 12/01/04.


ST 870 300000004 870: Transaction Set ID. 300000004: Transaction Set Control Number.

BSR 3 PA 00000001 20041117 3: Status Report Code [Unsolicited]. PA: Order/Item Code [Selected Order-All Items]. 00000001: Reference Identification. 20041117: Date of report (11/17/04).


Supplier Number). 234567: Reference Identification [JCPenney's assigned supplier number].

LOOP: N1 N1 Z7 92 30122 Z7: Entity Identifier Code [Mark-For Party]. 92:

Identification Code Qualifier [Assigned by Buyer]. 30122: Identification Code [Store number].


Code (Order). PRF 93412345 20041108 93412345: JCPenney Catalog purchase order

number. 20041108: Purchase order date (11/8/04).LOOP: HL/ISR ISR ED 20041201 ED: Shipment/Order Status Code [Expect to Ship

By]. 20041201: Date (12/01/2004) LOOP: HL/REF REF DP 531 DP: Reference Identification Qualifier (Department

Number) 531: Reference Identification [Subdivision Number].

REF VN 9341234501 VN: Reference Identification Qualifier (Vendor Order Number) 9341234501: Reference Identification [Supplier's order number].



segments including ST and SE]. 300000004: Transaction Set Control Number (same as ST02).



Business Example: Quantity Decreased [Selected Order-Selected Item]

Scenario: The following example is an 870 [PP - Selected Order-Selected Item]. JCPenney supplier ACME SHIRT CO [JCPenney assigned supplier number 234567] sent an 870 on 12/2/2004 for selected purchase order number 94312345, item number 89012376*ONLY, Subdivision 531. The order was created on 11/8/04 with an ‘at once’ ship date of 11/09/2004 and cancel date of 11/26/04 for 350 pieces.

Due to a shortage in inventory, the trading partner decreased the number units to be shipped by 30 pieces, from 350 to 320 pieces.

Here's the 870:



BSR 3 PP 00000001 20041202 3: Status Report Code [Unsolicited]. PP: Order/Item Code [Selected Order - Selected Items]. 00000001: Reference Identification. 20041202: Date (12/02/2004).



LOOP: N1 N1 Z7 92 30122 Z7: Entity Identifier Code. 92: Identification Code

Qualifier. 30122: Identification Code. ORDER



Date [11/08/2004] LOOP: HL/REF REF DP 531 DP: Reference Identification Qualifier [Department

Number] 531: Reference Identification [Subdivision].REF VN 9341234501 VN: Reference Identification Qualifier [Vendor Order

Number] 9341234501: Reference Identification [Supplier's Order number].


number. I: Hierarchical Level Code [Item]. LOOP: HL/PO1 PO1 350 EA IN 89012376*ONLY 350: Quantity Ordered. EA: Unit of Measurement

Code. IN: Product/Service ID Qualifier [Buyer's Item


Number]. 89012376*ONLY: Product/Service ID [JCP item number].

LOOP: HL/PO1/ISR ISR SC SC: Shipment/Order Status Code [Shipment

Quantity Decrease]. QTY 01 30 EA 01: Quantity Qualifier [Discrete quantity]. 30:

Quantity [Decreased quantity]. EA: Unit of measurement.



segments including ST and SE]. 300000005: Transaction Set Control number (same as ST02).



Business Example: Cancelled Order

Scenario: The following example is an 870 [PP - Selected Order-Selected Item]. JCPenney supplier ACME SHIRT CO [JCPenney assigned supplier number 234567] sent an 870 on 12/2/2004 to cancel selected purchase order number 94312345, Subdivision 531. The order was created on 11/8/04 with an ‘at once’ ship date of 11/09/2004 and cancel date of 11/26/04 for 350 pieces.

Here's the 870:



BSR 3 PA 00000001 20041202 3: Status Report Code [Unsolicited]. PP: Order/Item Code [Selected Order - Selected Items]. 00000001: Reference Identification. 20041202: Date (12/02/2004).



LOOP: N1 N1 Z7 92 30122 Z7: Entity Identifier Code. 92: Identification Code

Qualifier. 30122: Identification Code. ORDER



Date [11/08/2004] LOOP: HL/ISR ISR DE DE: Shipment/Order Status Code [Deleted Order]



segments including ST and SE]. 300000006: Transaction Set Control number (same as ST02).

870 Order Status Report - iconnect-corp.com · 870 Order Status Report ... Status Codes:...

Documents

Transcript of 870 Order Status Report - iconnect-corp.com · 870 Order Status Report ... Status Codes:...