869 order status inquiryj.c. penney co. proprietary and confidential 1 869 order status inquiry...

869 Order Status InquiryVICS EDI/V4030/869: 869 Order Status Inquiry

Modified: 10/11/2006

Notes:

_____________________________________________________________________________________________________

J. C. Penney Co Proprietary and Confidential

V4030 Order Status Inquiry - 869

J. C. Penney Co Proprietary and Confidential i

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

+++++ ISA - Interchange Control Header………………………………………………………………………….. 3 GS - Functional Group Header……………………………………………………………………………… 6 ST - Transaction Set Header………………………………………………………………………………… 8 BSI - Beginning Segment for Order Status Inquiry……………………………………………………… 9 HL - Hierarchical Level……………………………………………………………………………………….. 10 PRF - Purchase Order Reference…………………………………………………………………………... 11 DTM - Date/Time Reference…………………………………………………………………………………. 12 REF - Reference Identification………………………………………………………………………………. 13 N1 - Name………………………………………………………………………………………………………. 14 HL - Hierarchical Level……………………………………………………………………………………….. 15 LIN - Item Identification………………………………………………………………………………………. 16 CTT - Transaction Totals…………………………………………………………………………………….. 18 SE - Transaction Set Trailer…………………………………………………………………………………. 19 GE - Functional Group Trailer……………………………………………………………………………….. 20 IEA - Interchange Control Trailer…………………………………………………………………………… 21

+++++ Business Rules: Catalog………………………………………………………………………………………. 22 Business Example: Catalog (Item Level)…………………………………………………………………… 24 Business Example: Catalog (Order Level)…………………………………………………………………. 27 Business Rules: Catalog Factory Ship……………………………………………………………………… 29 Business Example: Catalog Factory Ship………………………………………………………………….. 30


J.C. Penney Co. Proprietary and Confidential 1

869 Order Status InquiryFunctional Group=RS

This Draft Standard for Trial Use contains the format and establishes the data contents of the Order Status InquiryTransaction Set (869) for use within the context of an Electronic Data Interchange (EDI) environment. Thetransaction set can be used to request all pertinent information relative to an entire purchase order, selected lineitems on a purchase order, or selected products/services on a purchase order. Inquiry can also be made for all or aselected portion of the customer's ordered items, all or a selected portion of the customer's unshipped items, or all ora selected portion of the customer's shipped items.

Not Defined:Pos Id Segment Name Req Max Use Repeat Notes0100 ISA Interchange Control Header M 1 0200 GS Functional Group Header M 1

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

Detail:Pos Id Segment Name Req Max Use Repeat Notes

LOOP ID - HL >1 LOOP ID - HL >1

0200 HL Hierarchical Level M 1 0300 PRF Purchase Order Reference O 1 0400 DTM Date/Time Reference O 10

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

1200 REF Reference Identification M 1

LOOP ID - N1 >1 LOOP ID - N1 >1

1500 N1 Name O 1

LOOP ID - HL >1 LOOP ID - HL >1

2800 HL Hierarchical Level M 1 3100 LIN Item Identification O >1

Summary:Pos Id Segment Name Req Max Use Repeat Notes0100 CTT Transaction Totals O 1 N3/01000200 SE Transaction Set Trailer M 1

Not Defined:Pos Id Segment Name Req Max Use Repeat Notes0100 GE Functional Group Trailer M 1 0200 IEA Interchange Control Trailer M 1

Notes:



3/0100 CTT01 is the number of HL segments.



ISA Interchange Control Header Pos: 0100 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 positionsUser 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 positionsUser 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 Name08 UCC EDI Communications ID (Comm ID)

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 elementUser Note 1: JCPenney Sender IDs by business entities:6111350019 - Retail6111350010 - Catalog6111350028 - Catalog Factory Ship

User Note 1: JCPenney Sender IDs by business entities:6111350019 - Retail6111350010 - Catalog6111350028 - Catalog Factory Ship

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

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 them

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

Description: Code indicating whether data enclosed by this

M ID 1/1




interchange 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: 0200 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 as ISA06.User Note 1: Same ID as 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 as ISA08.User Note 1: Same ID as 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 Name869 Order Status Inquiry

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



BSI Beginning Segment for OrderStatus Inquiry

Pos: 0200 Max: 1Heading - Mandatory


To indicate the beginning of an order status inquiry and provide the type of customer status inquiry

Element Summary: Ref Id Element Name Req Type Min/MaxBSI01 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 systemUser Note 1: Number assigned by the sender to identify therequest within their application systemUser Note 2: Contains the date and time that the transactionwas generated. It is forward left justified in the format:AABBBCCDDEE, where AA=Julian Year, BBB=Julian Day,CC=Hour, DD=Minute, EE=Seconds.

User Note 2: Contains the date and time that the transactionwas generated. It is forward left justified in the format:AABBBCCDDEE, where AA=Julian Year, BBB=Julian Day,CC=Hour, DD=Minute, EE=Seconds.

M AN 1/50

BSI02 373 Date


M DT 8/8

BSI03 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

Semantics: 1. BSI01 is a status inquiry reference number.2. BSI02 is date of the inquiry.

User Note 1:User Note 1:When BSI03 is "PA", no item level data will be sent.When BSI03 is "PA", no item level data will be sent.



HL Hierarchical Level Pos: 0200 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 structure

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.

User Note 1:User Note 1: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: 0300 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 numberUser Note 1: Retailer's original purchase order number

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 date

M DT 8/8

PRF06 367 Contract Number

Description: Contract number

O AN 1/30

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



DTM Date/Time Reference Pos: 0400 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



REF Reference Identification Pos: 1200 Max: 1Detail - 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 NameDP Department NumberIA Internal Vendor 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

User Note 1:User Note 1:Up to three consecutive REF loops can be generated at this position for each of the Reference IdentificationQualifiers listed in REF01: Department Number (DP) is required, specifyfing the three digit subdivision number. Vendor Number (IA) is required, specifying the JCPenney assigned six digit supplier number. Vendor Order Number (VN) is only sent for Catalog orders if you have previously forwarded to us an 870 OrderStatus Report for this purchase order. The 870 is the only means for us to know the order number a supplierassigns to a retailer's purchase order. If the order number you send is more than 15 positions, we will return theright most 15 positions to you. For example, your order number is 12345678901234567, we will return345678901234567on the 869.

Up to three consecutive REF loops can be generated at this position for each of the Reference IdentificationQualifiers listed in REF01: Department Number (DP) is required, specifyfing the three digit subdivision number. Vendor Number (IA) is required, specifying the JCPenney assigned six digit supplier number. Vendor Order Number (VN) is only sent for Catalog orders if you have previously forwarded to us an 870 OrderStatus Report for this purchase order. The 870 is the only means for us to know the order number a supplierassigns to a retailer's purchase order. If the order number you send is more than 15 positions, we will return theright most 15 positions to you. For example, your order number is 12345678901234567, we will return345678901234567on the 869.



N1 Name Pos: 1500 Max: 1Detail - 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.

User Note 1:User Note 1:Segment is only sent for Retail and DFW orders.Segment is only sent for Retail and DFW orders.



HL Hierarchical Level Pos: 2800 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

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

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HLsegment.

User Note 1:User Note 1: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.



LIN Item Identification Pos: 3100 Max: >1Detail - Optional


To specify basic item identification data

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

Description: Alphanumeric characters assigned fordifferentiation within a transaction setUser Note 1: Only used by Catalog Factory Ship.User Note 1: Only used by Catalog Factory Ship.

O AN 1/20

LIN02 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

LIN03 234 Product/Service ID

Description: Identifying number for a product or serviceUser Note 1: If inquiry is for Retail merchandise, JCPenney willsend lot/line/size description in the following format:AAAABBBBCCCCC where AAAA= lot number, BBBB = linenumber, CCCCC = size description. For Catalog and CatalogFactory Ship merchandise, JCPenney will send lot/sku in thefollowing format: AAAAAAABBBB where AAAAAAA = lotnumber, BBBB = sku number.

User Note 1: If inquiry is for Retail merchandise, JCPenney willsend lot/line/size description in the following format:AAAABBBBCCCCC where AAAA= lot number, BBBB = linenumber, CCCCC = size description. For Catalog and CatalogFactory Ship merchandise, JCPenney will send lot/sku in thefollowing format: AAAAAAABBBB where AAAAAAA = lotnumber, BBBB = sku number.User Note 2: Minimum length and maximum lengths:Retail = 4/16Catalog and Factory Ship = 11/11

User Note 2: Minimum length and maximum lengths:Retail = 4/16Catalog and Factory Ship = 11/11

M 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



X ID 2/2

Code NameEN EAN/UCC - 13


X AN 1/48




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

Syntax Rules: 1. P0405 - If either LIN04 or LIN05 is present, then the other is required.2. P0607 - If either LIN06 or LIN07 is present, then the other is required.

Semantics: 1. LIN01 is the line item identification



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: 0100 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: 0200 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 22

869 ORDER STATUS INQUIRY BUSINESS RULES (CATALOG) The purpose of this document is to provide an understanding of JCPenney's use of some of the major sections in the 869 Order Status Inquiry in support of the JCPenney Catalog Division's business. The 869 Order Status Inquiry, for the JCPenney Catalog Division, is generated based upon exceptions. Exceptions are the problems the Catalog Purchase Order Follow-up (POF) system identifies as significant enough to require follow-up with the supplier. These exceptions are generally created by a need to fill backorders or to advise the JCPenney Catalog Buying team of a potential loss of sale (omissions) on open SKU quantities. It is the trading partner's responsibility to take immediate action upon receipt of the 869 inquiry by responding to the inquiry with either an 870 Order Status Report or an 856 Ship Notice/Manifest depending upon the status of the open SKU quantity. The 869 is automatically generated as often as exceptions occur. This can be daily for some trading partners. Since this is an automatic generation, the 869 may be released to the trading partner's mailbox (VAN) on the same day an 870 or 856 document is being picked up by JCPenney. These 869s may not require a response. Even though a response may not be required, the trading partner should never discard the 869 inquiry without (1) verifying receipt of the Functional Acknowledgment for the 870 or 856 document to JCPenney, (2) checking the inquiry against error notices sent to you from JCPenney EDI Support, and (3) comparing the original ordered quantities against what was shipped and what is left on balance in your system. HEADER LEVEL BEGINNING SEGMENT [BSI] The BSI segment purpose is to identify the type of Order Status Inquiry that is being transmitted to the trading partner. In BSI01 (Reference Identification), the 11-digit reference number is composed of the 2-digit Julian year, 3-digit Julian day, and the time (hour, minute and seconds) of when the transaction was generated. All Catalog Order Status Inquiries will either have a transaction type code of "PA" or "PP" in BSI03. JCPenney Catalog will issue an 869 with a "PA" code if half or more than half of the open skus (items that have not been shipped) on a purchase order have an exception (problem). A "PP" code is sent if there is a problem with less than half of the open skus on the order. This is determined by the total number of open skus in which an exception has been generated in the Purchase Order Follow-up system. ORDER LEVEL DATE/TIME REFERENCE [DTM] In DTM02, JCPenney Catalog will send the 'Requested ship date' from the original purchase order or the last 'promise to ship' date sent by the supplier on an 870. REFERENCE IDENTIFICATION [REF] [VN] JCPenney Catalog will send in the Reference Identification segment [REF02] zeroes as the Suppliers Order Number [REF 'VN'] on the 869 prior to receiving an 870 (Order Status Report). Once an 870 is transmitted against the selected order, the subsequent 869 will reflect the Suppliers Order Number from the 870 transmission.


ITEM LEVEL No item level information will be sent when BSI03 contains code "PA" (Selected order - All items). Only when the BSI03 is "PP" will you receive both order and item level details.


869 ORDER STATUS INQUIRY

Business Example: Catalog, Selected Order-Selected Items

This is an example of an 869 Order Status Inquiry generated by the JCPenney Catalog Purchase Order Follow-up system to Acme Shirt Company (supplier #234567) on March 16, 2002 at 10:15:02 AM. The inquiry was for selected items on purchase order numbers 7654321H, 8765432R, and 9876543A. These purchase orders were created on 02/18/2002 with a ship by date of 03/08/2002. There has been a partial shipment against these orders but the SKUs listed below are still open. The cancel date has passed and JCPenney Catalog is in need of merchandise to fill backorders (customer orders).

Purchase Order Number Lot/Sku Numbers on Inquiry 7654-321H 531-1234 0059

531-1234 0125 8765-432R 531-1234 0059

531-1234 0125 9876-543A 531-1234 0059

531-1234 0125

EDI TRANSMISSION DATA EXPLANATION HEADER

ST 869 987654321 987654321: Transaction Set Control Number. BSI 02075101502 20020316 PP

02075101502: Reference number created by application. Format: (Julian year and day, hour, minute and seconds). 20020316: Date of inquiry - 03/16/2002. PP: Order code (Selected Order - Selected Items).

ORDER LOOP: HL HL 1 O 1: Hierarchical ID number. O: Hierarchical level

code for 'Order'. PRF 7654321H 20020218

7654321H: JCP Catalog purchase order number. 20020218: Original purchase order date (02/18/2002)

DTM 010 20020308 010: Requested Ship. 20020308: Ship by date (03/08/2002).

LOOP: HL/REF REF DP 531 DP: Department. 531: Subdivision number. REF IA 234567 IA: Internal Vendor number. 234567: JCPenney's

assigned supplier number. REF VN 000000000000000 VN: Vendor Order number. 0000000000000000:

Suppliers Order Number prior to receiving an 870. ITEM

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


Number. I: Level Code for "Item". LIN IN 53112340059 IN: Buyers Item Number. 53112340059: JCPenney

assigned lot/sku number. 2nd ITEM



assigned lot/sku number. ORDER

LOOP: HL HL 4 O 4: Hierarchical ID number O: Hierarchical level

code for 'Order'. PRF 8765432R 20020218

8765432R: JCP Catalog purchase order number. 20020218: Original purchase order date (02/18/2002)










assigned lot/sku number. ORDER

LOOP: HL HL 7 O 7: Hierarchical ID number. O: Hierarchical level

code for 'Order'. PRF 9876543A 20020218 9876543A: JCP Catalog purchase order number.

20020218: Original purchase order date (02/18/2002)


LOOP: HL/REF


REF DP 531 DP: Department. 531: Subdivision number. REF IA 234567 IA: Internal Vendor number. 234567: JCPenney's








assigned lot/sku number. TRAILER

CTT 9 9: Number of HL segments SE 34 987654321

34: Count of all segments including ST and SE. 987654321: Transaction Set Control Number [same as ST02].



Business Example: Catalog, Selected Order-All Items

This is an example of an 869 Order Status Inquiry generated by the JCPenney Catalog Purchase Order Follow-up system to Acme Shirt Company (supplier #234567) on March 16, 2002 at 10:15:02 am. The inquiry was for all items on purchase order numbers 1234567A, 2345678K, and 3456789C. These purchase orders were created on 02/18/2002 with a ship by date of 03/08/2002. An 870 was previously sent on purchase order 2345678K. The promise to ship date was 03/04/02 on Suppliers Order Number 293017. There has not been a shipment against these orders and the cancel date and the promise to ship date is now in the past.


ST 869 123456789 123456789: Transaction Set Control Number. BSI 02075101502 20020316 PA

02075101502: Reference number created by application. Format: (Julian year and day, hour, minute and seconds). 20020316: Date of inquiry - 03/16/2002. PA: Order code (Selected Order - All Items).

ORDER LOOP: HL HL 1 O 1: Hierarchical ID number. O: Hierarchical level

code for 'Order'. PRF 1234567A 20020218

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




Suppliers Order Number prior to receiving an 870.LOOP: HL HL 2 O 2: Hierarchical ID number O: Hierarchical level

code for 'Order'. PRF 2345678K 20020218

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

DTM 010 20020304 010: Requested Ship. 20020304: Promised to ship by date (03/04/2002).


assigned supplier number. REF VN 293017 VN: Vendor Order number. 293017: Supplier


Order number from a previous 870. LOOP: HL HL 3 O 3: Hierarchical ID number. O: Hierarchical level

code for 'Order'. PRF 3456789C 20020218

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




Suppliers Order number prior to receiving an 870.TRAILER

CTT 3 3: Number of HL segments SE 22 123456789



869 ORDER STATUS INQUIRY BUSINESS RULES (CATALOG FACTORY SHIP) The purpose of this document is to provide an understanding of JCPenney's use of some of the major sections in the 869 Order Status Inquiry in support of the JCPenney Catalog Factory Ship business. The 869 Order Status Inquiry, for the JCPenney Catalog Factory Ship, is generated based upon the original ship date of the purchase order. The 869 is automatically generated as often as exceptions occur. It is the trading partner's responsibility to take immediate action upon receipt of the 869 by responding to the inquiry with either an 870 Order Status Report or an 810 Invoice depending upon the status of the order. HEADER LEVEL BEGINNING SEGMENT [BSI] The BSI segment purpose is to identify the type of Order Status Inquiry that is being transmitted to the trading partner. In BSI01 [Reference Identification], the 11-digit reference number is composed of the 2-digit Julian year, 3-digit Julian day, and the time (hour, minute and seconds) of when the transaction was generated. Catalog Factory Ship Order Status Inquiries will send a code of "PP" in BSI03. ORDER LEVEL DATE/TIME REFERENCE [DTM] In DTM02, JCPenney Catalog Factory Ship will send the 'Requested ship date' from the original purchase order or the last revised or expected to ship by date sent from the supplier on the 870 Order Status Report. REFERENCE IDENTIFICATION [REF - VN] This segment is not used by Catalog Factory Ship. NAME [N1] This segment is not used by Catalog Factory Ship. ITEM LEVEL ITEM IDENTIFICATION [LIN] The purpose of this segment is to identify the SKU number in the inquiry. The Assigned Identification number in LIN01 is a 20-digit number id number found in the PO101 [Assigned ID] data field of the 850 document. JCPenney Catalog Factory Ship will send the lot/sku [LIN03] in the following format: AAAAAAABBBB where AAAAAAA = lot number, BBBB = SKU number.



Business Example: Factory Ship - Selected Order-Selected Items

Scenario: On 6/19/2003, JCPenney Catalog Factory Ship generated and sent an Order Status Inquiry [869] to Acme Appliance Company (supplier #234567]. The inquiry was for item 85712340000 on purchase order number 123445678 from subdivision 857.

The purchase order was created on 6/16/2003. The inquiry was created because JCPenney hasn't received a 'proof of delivery' from the Acme Appliance Company.


ST 869 987654320 987654320: Transaction Set Control Number. BSI 03170183503 20030619 PP

03170183503: Reference number created by application. Format: (Julian year and day, hour, minute and seconds). 20030619: Date of inquiry - 06/19/2003. PP: Order code (Selected Order - Selected Items).

ORDER LOOP: HL

HL 1 O 1: Hierarchical ID number. O: Hierarchical level code for 'Order'.

PRF 123445678 20030616

123445678: JCP Catalog purchase order number. 20030616: Original purchase order date (06/16/2003)


LOOP: HL/REF REF DP 857 DP: Department. 857: Subdivision number.

REF IA 234567 IA: Internal Vendor number. 234567: JCPenney's assigned supplier number.

ITEM LOOP: HL

HL 2 1 I 2: Hierarchical ID number. 1: Hierarchical Parent ID Number. I: Level Code for "Item".

LIN 00000000000000000456 IN 85712340000 00000000000000000456: Assigned ID. Only used by Catalog Factory Ship. IN: Buyers Item Number. 85712340000: JCPenney assigned lot/sku number.

TRAILER CTT 2 2: Number of HL segments SE 11 987654320


869 order status inquiryj.c. penney co. proprietary and confidential 1 869 order status inquiry...

Documents