JCPenny Vendor Requirements as a part of EDI program for vendors
The goal of this post is to provide JCPenny Vendor Requirements concerning mapping and translation process to partners. The objective of these JCPenny Vendor Requirements is to enhance the logistics processes through improved information flow and bar code technology.
JCPenny Vendor Requirements – Levels
Data JCPenny receives may be rejected at the interchange (ISA/IEA), functional group (GS/GE), or transaction set (ST/SE) level. Data will be rejected when the following conditions are detected:
Interchange Level
Data will be suspended at this level when:
- The ISA segment cannot be recognized by our translator.
- Your company EDI profile has not been set up on the JCPenny Partner File.
Functional Group Level
Data will be suspended at this level when:
- The GS segment cannot be recognized by JCPenny translator program.
- The functional group received is not a valid functional group.
- The version of the functional group received is not a valid version for JCPenny.
- The Trading Partner is not set up to process this transaction.
Transaction Level
Data will be suspended at this level when:
- The ST segment cannot be recognized by JCPenny translator program.
- The trading partner is not set up to process this transaction.
- Mandatory segments are missing or out of sequence.
JCPenny Vendor Requirements – Control Number Generation
JCPenny translator program will generate the following control numbers:
- Interchange Control Number (ISA13) – Number is assigned starting with ‘100000001’. The left most digit (highest order) will always be a 1 for interchange control numbers.
- Example: If the Interchange Control Number on the last ISA yesterday was ‘100000145’, the Interchange Control Number on the first ISA generated today would be ‘100000146’. The low order digits 145 will be incremented but the high order “1” will remain the same.
- Functional Group Control Number (GS06) – Number is assigned starting with 200000001′. The left most digit (highest order) will always be a 2 for Functional Group Control Numbers.
- Example: If the Group Control Number on the last GS yesterday was number ‘200000215’, the Group Control Number on the first GS today would be number ‘200000216’. The low order digits 215 will be incremented but the high order “2” will remain the same.
- Transaction Set Control Number (ST02) – Number is assigned starting with “300000001”. The left most digit (highest order) will always be a 3 for Transaction Set control numbers
- Example: If the Transaction Set Number on the last Transaction yesterday was number “300007651”, the Transaction Set Control Number on the first ST today would be number “300007652”. The low order digits 7651 will be incremented but the high order “3” will remain the same.
- The JCPenny translator maintains separate control files for inbound and outbound documents. To avoid duplication of control numbers for 997 Functional Acknowledgments two high order digits are generated on all outbound 997s. The first high order digit is 9, and it identifies the acknowledgment. The second high order digit is a 1, 2, or 3.
JCPenny Vendor Requirements – Reading EDI Specifications (ver. 004030 and above)
Each segment and data element will have one of the following requirement designators:
- M – Mandatory. The presence of a specified segment/data element is required by VICS.
- O – Optional. The presence of a specified segment/data element is at the option of the sending/receiving parties. Optional segments/elements used by JCPenny are included in the specifications. These segments/elements are required to be sent, unless stated otherwise in the user notes or business rules.
- X – Relational. The presence of a specified data element is dependent on the value or presence of other data elements in the segment. Relational data elements used by JCPenny and their dependencies are included in the specifications. These relational data elements are required to be sent, unless stated otherwise in the user notes or business rules.
User Notes – By default, JCPenny uses the VICS attributes. User notes are used to identify unique jcpenney requirements, exceptions, or clarification. For example, if a data element/segment is only required for specific business entities, then it will be stated in a user note.
Last Data Element – The last data element used by JCPenny is listed for that segment. This may or may not be the last data element in the VICS manual. Any trailing data elements in VICS not used by jcpenney are not included in the specifications.
Excluded Data Elements – Data elements not required or used by jcpenney are excluded from the specifications. The excluded data elements between the first and last data element, however, still need to be mapped to maintain the integrity of the segment.
Data Element Separator – JCPenny accepts characters recommended by VICS. JCPenny uses the data element separator character “Bel” (%) character. (Hex “2F” in EBCDIC or hex “07” in ASCII).
Note: Do not use an asterisk * (HEX 5C, DECIMAL 092) as a data element separator. This character is sent and received as data by JCPenny.
SubElement Separator Character – Trading partners can use characters recommended by VICS. The “>” character (Hex “6E” in EBCDIC or hex “3E” in ASCII) is used by JCPenny.
Segment Terminator Character – Trading partners can use characters recommended by VICS. The “New Line” character (Hex “15” in EBCDIC or Hex “7E” in ASCII) is used by JCPenny.