753 request for routing instructions

753 Request for RoutingInstructions

VICS EDI/V4030/753: 753 Request for Routing Instructions

Modified: 07/17/2006

Notes: __________________________________________________________________J. C. Penney Co Proprietary and Confidential

J. C. Penney Co Proprietary and Confidential . i

V4030 Request for Routing Instructions - 753

Table of Contents Request for Routing Instructions Overview...................………………………………………………… 1

+++++

ISA - Interchange Control Header……………………………………………………………………..……. 2 GS - Functional Group Header…………………………………………………………………………...….. 5 ST - Transaction Set Header…………………………………………………………………………………. 7 BGN - Beginning Segment…………………………………………………………………………………. 8 PER - Administrative Communications Contact……………………………………………………….. 9 N1 - Name………………………………………………………………………………….…………………… 11 N3 - Address Information..................................................................................................................... 12 N4 - Geographic Location………………………………………………………………………………...….. 13 LX - Assigned Number……………………………………………………………………..…………………. 14 N1 - Name………………………………………………………………………………………………………… 15 L11 - Business Instructions and Reference Number…………………………………...……………… 16 G62 - Date/Time………………………………………………………………………………………….……… 17 OID - Order Identification Detail…………………………………………………….……………………….. 18 CMC - Commodity Classification…………………………………………………………...……………….. 20 SE - Transaction Set Trailer…………………………………………………………………………...……… 21 GE - Functional Group Trailer…………………………………………………..……………………………. 22 IEA - Interchange Control Trailer………………………………………………………..…………………… 23

+++++

TMS Dynamic Routing Business Rules……………………………………………………………………. 24 TMS Dynamic Routing Business Example………………………………………………………………… 26 TMS-Lite Routing Authorization Business Rules…..……………………………………………………. 31 TMS-Lite Routing Authorization Business Example…………………………………………………….. 33


J.C. Penney Co. Proprietary and Confidential 1

753 Request for Routing InstructionsFunctional Group=RF

This Draft Standard for Trial Use contains the format and establishes the data contents of the Request for RoutingInstructions Transaction Set (753) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to request routing instructions and provide general information about merchandisethat is ready to be shipped.

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 BGN Beginning Segment M 1 0300 PER Administrative Communications Contact O 1

LOOP ID - 0100 1 LOOP ID - 0100 1

0400 N1 Name M 1 0600 N3 Address Information O 2 0700 N4 Geographic Location O 1

Detail:Pos Id Segment Name Req Max Use Repeat Notes0100 LX Assigned Number M 1

LOOP ID - 0200 9999 LOOP ID - 0200 9999

0200 N1 Name M 1 0600 L11 Business Instructions and Reference Number O 5 0700 G62 Date/Time O 2

LOOP ID - 0210 >1 LOOP ID - 0210 >1

0900 OID Order Identification Detail M 1 1000 CMC Commodity Classification O 1 1100 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 ID: 6111355027 (Logistics).User Note 1: JCPenney receiver ID: 6111355027 (Logistics).

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 thisinterchange envelope is test, production or information

M ID 1/1



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 NameRF Request for Routing Instructions (753)

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 Name753 Request for Routing Instructions

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



BGN Beginning Segment Pos: 0200 Max: 1Heading - Mandatory


To indicate the beginning of a transaction set

Element Summary: Ref Id Element Name Req Type Min/MaxBGN01 353 Transaction Set Purpose Code

Description: Code identifying purpose of transaction set

M ID 2/2

Code Name00 Original

BGN02 127 Reference Identification

Description: Reference information as defined for a particularTransaction Set or as specified by the Reference IdentificationQualifierUser Note 1: A unique control number assigned by the sender.User Note 1: A unique control number assigned by the sender.

M AN 1/50

BGN03 373 Date

Description: Date expressed as CCYYMMDD where CCrepresents the first two digits of the calendar yearUser Note 1: Date transaction was generated.User Note 1: Date transaction was generated.

M DT 8/8

BGN04 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)User Note 1: Local time transaction was generated.User Note 1: Local time transaction was generated.

X TM 4/8

Semantics: 1. BGN02 is the transaction set reference number.2. BGN03 is the transaction set date.3. BGN04 is the transaction set time.



PER AdministrativeCommunications Contact

Pos: 0300 Max: 1Heading - Optional


To identify a person or office to whom administrative communications should be directed

Element Summary: Ref Id Element Name Req Type Min/MaxPER01 366 Contact Function Code

Description: Code identifying the major duty or responsibility ofthe person or group named

M ID 2/2

Code NameIC Information Contact

PER02 93 Name

Description: Free-form name

O AN 1/60

PER03 365 Communication Number Qualifier

Description: Code identifying the type of communicationnumber

X ID 2/2

Code NameTE Telephone

PER04 364 Communication Number

Description: Complete communications number includingcountry or area code when applicableUser Note 1: Telephone number format is AAABBBBBBB,where AAA = area code, BBBBBBB = telephone number.User Note 1: Telephone number format is AAABBBBBBB,where AAA = area code, BBBBBBB = telephone number.

X AN 1/256



X ID 2/2

Code NameEM Electronic Mail


Description: Complete communications number includingcountry or area code when applicableUser Note 1: Only one e-mail address can be entered. User Note 1: Only one e-mail address can be entered.

X AN 1/256



X ID 2/2

Code NameFX Facsimile


Description: Complete communications number including

X AN 1/256




country or area code when applicable

Syntax Rules: 1. P0304 - If either PER03 or PER04 is present, then the other is required.2. P0506 - If either PER05 or PER06 is present, then the other is required.3. P0708 - If either PER07 or PER08 is present, then the other is required.



N1 Name Pos: 0400 Max: 1Heading - Mandatory

Loop: 0100 Elements: 4

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 NameSF Ship From

N102 93 Name

Description: Free-form name

X AN 1/60

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: JCPenney assigned six digit supplier number.User Note 1: JCPenney assigned six digit supplier number.

X AN 2/80

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



N3 Address Information Pos: 0600 Max: 2Heading - Optional


To specify the location of the named party

Element Summary: Ref Id Element Name Req Type Min/MaxN301 166 Address Information

Description: Address information

M AN 1/55

N302 166 Address Information

Description: Address information

O AN 1/55



N4 Geographic Location Pos: 0700 Max: 1Heading - Optional


To specify the geographic place of the named party

Element Summary: Ref Id Element Name Req Type Min/MaxN401 19 City Name

Description: Free-form text for city nameUser Note 1: Maximum length is nineteen characters. Truncatecity name, if necessary.User Note 1: Maximum length is nineteen characters. Truncatecity name, if necessary.

O AN 2/30

N402 156 State or Province Code

Description: Code (Standard State/Province) as defined byappropriate government agency

O ID 2/2

N403 116 Postal Code

Description: Code defining international postal zone codeexcluding punctuation and blanks (zip code for United States)User Note 1: Nine digit postal code is required.User Note 1: Nine digit postal code is required.

O ID 3/15

N404 26 Country Code

Description: Code identifying the countryUser Note 1: Only send this data if country is not USA.User Note 1: Only send this data if country is not USA.

O ID 2/3

Comments: 1. N402 is required only if city name (N401) is in the U.S. or Canada.



LX Assigned Number Pos: 0100 Max: 1Detail - Mandatory


To reference a line number in a transaction set

Element Summary: Ref Id Element Name Req Type Min/MaxLX01 554 Assigned Number

Description: Number assigned for differentiation within atransaction setUser Note 1: This is a sequential number starting with one, andincremented by one, for every occurrence of the LX segment.User Note 1: This is a sequential number starting with one, andincremented by one, for every occurrence of the LX segment.

M N0 1/6



N1 Name Pos: 0200 Max: 1Detail - Mandatory


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 NameST Ship To

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 unit number.User Note 2: Five digit 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:At least one occurrence of the N1 segment must be used to identify the ship-to location by using code ST inN101.At least one occurrence of the N1 segment must be used to identify the ship-to location by using code ST inN101.



L11 Business Instructions andReference Number

Pos: 0600 Max: 5Detail - Optional


To specify instructions in this business relationship or a reference number

Element Summary: Ref Id Element Name Req Type Min/MaxL1101 127 Reference Identification

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

X AN 1/50

L1102 128 Reference Identification Qualifier

Description: Code qualifying the Reference Identification

X ID 2/3

Code NameRRC Routing Request Control Number

Syntax Rules: 1. R0103 - At least one of L1101 or L1103 is required.2. P0102 - If either L1101 or L1102 is present, then the other is required.

User Note 1:User Note 1:A unique routing request control number must be assigned for each ship-to location. This control numberprovides the means to assign a different routing to each ship-to location and must be conveyed in the Responseto a Routing Request.

A unique routing request control number must be assigned for each ship-to location. This control numberprovides the means to assign a different routing to each ship-to location and must be conveyed in the Responseto a Routing Request.

User Note 2:User Note 2:At least one occurrence of the L11 segment is required to specify the routing request control number by usingcode RRC in L1102.At least one occurrence of the L11 segment is required to specify the routing request control number by usingcode RRC in L1102.



G62 Date/Time Pos: 0700 Max: 2Detail - Optional


To specify pertinent dates and times

Element Summary: Ref Id Element Name Req Type Min/MaxG6201 432 Date Qualifier

Description: Code specifying type of date

X ID 2/2

Code NameRS Ready to Ship

G6202 373 Date

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

X DT 8/8

G6203 176 Time Qualifier

Description: Code specifying the reported time

X ID 1/2

Code NameRS Ready to Ship

G6204 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)User Note 1: Local timeUser Note 1: Local time

X TM 4/8

Syntax Rules: 1. P0102 - If either G6201 or G6202 is present, then the other is required.2. P0304 - If either G6203 or G6204 is present, then the other is required.



OID Order Identification Detail Pos: 0900 Max: 1Detail - Mandatory


To specify order identification detail

Element Summary: Ref Id Element Name Req Type Min/MaxOID01 127 Reference Identification

Description: Reference information as defined for a particularTransaction Set or as specified by the Reference IdentificationQualifierUser Note 1: Requestor’s order identification number.User Note 1: Requestor’s order identification number.

X AN 1/50

OID02 324 Purchase Order Number

Description: Identifying number for Purchase Order assignedby the orderer/purchaserUser Note 1: Retailer’s purchase order number.User Note 1: Retailer’s purchase order number.

X AN 1/22

OID03 127 Reference Identification

Description: Reference information as defined for a particularTransaction Set or as specified by the Reference IdentificationQualifierUser Note 1: Retailer’s subdivision number.User Note 1: Retailer’s subdivision number.

X AN 1/50

OID04 211 Packaging Form Code

Description: Code for packaging form of the lading quantity

X ID 3/3

Code NameCTN CartonPCS Pieces

OID05 380 Quantity

Description: Numeric value of quantity

X R 1/15

OID06 188 Weight Unit Code

Description: Code specifying the weight unitUser Note 1: Only required to be sent by suppliers participatingin the TMS Dynamic Routing - Request for Routing Instructionsprogram.

User Note 1: Only required to be sent by suppliers participatingin the TMS Dynamic Routing - Request for Routing Instructionsprogram.

X ID 1/1

Code NameL Pounds

OID07 81 Weight

Description: Numeric value of weightUser Note 1: Only required to be sent by suppliers participatingin the TMS Dynamic Routing - Request for Routing Instructionsprogram.


X R 1/10

OID08 184 Volume Unit Qualifier

X ID 1/1




Description: Code identifying the volume unitUser Note 1: Only required to be sent by suppliers participatingin the TMS Dynamic Routing - Request for Routing Instructionsprogram.


Code NameE Cubic Feet

OID09 183 Volume

Description: Value of volumetric measureUser Note 1: Only required to be sent by suppliers participatingin the TMS Dynamic Routing - Request for Routing Instructionsprogram.


X R 1/8

Syntax Rules: 1. C0302 - If OID03 is present, then OID02 is required.2. P0405 - If either OID04 or OID05 is present, then the other is required.3. P0607 - If either OID06 or OID07 is present, then the other is required.4. P0809 - If either OID08 or OID09 is present, then the other is required.

Semantics: 1. OID01 is the seller's order identification number.2. OID03 is the number assigned by the consignee to further define the purchase order number.

User Note 1:User Note 1:This loop is used to specify the quantities ready to ship for each purchase order.This loop is used to specify the quantities ready to ship for each purchase order.

User Note 2:User Note 2:For TMS Lite - Request for Routing Authorization, only one OID loop is required to be sent for each purchaseorder. The OID loop will specify the number of items shipped (OID04 = PCS). For TMS Dynamic Routing - Request for Routing Instructions, two consecutive OID loops are required to be sentfor each purchase order. One OID loop will specify the number of cartons shipped (OID04 = CTN). The otherOID loop will specify the total number of items shipped (OID04 = PCS).

For TMS Lite - Request for Routing Authorization, only one OID loop is required to be sent for each purchaseorder. The OID loop will specify the number of items shipped (OID04 = PCS). For TMS Dynamic Routing - Request for Routing Instructions, two consecutive OID loops are required to be sentfor each purchase order. One OID loop will specify the number of cartons shipped (OID04 = CTN). The otherOID loop will specify the total number of items shipped (OID04 = PCS).



CMC Commodity Classification Pos: 1000 Max: 1Detail - Optional


To specify freight commodity code and freight classification

Element Summary: Ref Id Element Name Req Type Min/MaxCMC01 22 Commodity Code

Description: Code describing a commodity or group ofcommoditiesAll valid standard codes are used.

O AN 1/30

Semantics: 1. CMC01 is the National Motor Freight Classification Commodity Code.

User Note 1:User Note 1:Only used for hazardous materials.Only used for hazardous materials.



SE Transaction Set Trailer Pos: 1100 Max: 1Detail - 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.

https://supplier.jcpenney.com/supplier/general/edi/E-Commerce/Dynamic_Routing/TMS_Business_Glossary.htm

https://supplier.jcpenney.com/supplier/general/edi/E-Commerce/Dynamic_Routing/Introduction.htm

https://supplier.jcpenney.com/supplier/general/edi/E-Commerce/Dynamic_Routing/Introduction.htm

https://supplier.jcpenney.com/supplier/Logistics_Distribution/default.asp

https://supplier.jcpenney.com/



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 24

753 REQUEST FOR ROUTING INSTRUCTIONS BUSINESS RULES FOR TMS – DYNAMIC ROUTING (revised 09/17/04) The purpose of this document is to provide an explanation of JCPenney's use of some of the major sections of the 753 Request for Routing Instructions used by suppliers participating in the TMS Dynamic Routing Initiative program. GENERAL REQUIREMENTS This transaction is integral to the TMS - Dynamic Routing Initiative program. For a complete explanation of the requirements of the program, refer to the Business Rules and Glossary of the TMS Dynamic Routing Initiative guidelines under the Logistics section of the supplier web site. HEADER LEVEL BEGINNING SEGMENT [BGN] The purpose of this segment is to identify the transaction set purpose, reference identification, date and time of the transaction. The transaction set purpose [BGN01] is 'Original' (00). The sender's [vendor] internal number is used as the reference identification number [BGN02] to identify the transaction set within the vendor's application system. ADMINISTRATIVE COMMUNICATION CONTACT [PER] This segment is used to specify the Supplier's contact information. In section PER02, the supplier will provide the contact person's name. The contact's telephone number is sent in the PER04 field. The telephone number must consist of a 3-digit area code and a 7-digit phone number. The supplier must also send an email address [PER06]. JCPenney will reject the 753 request if the email address in PER06 is missing or incomplete. DETAIL LEVEL BUSINESS INSTRUCTIONS AND REFERENCE NUMBER [L11] The reference identification in L1101 is the vendor assigned control number for a specific shipment. L1102 is the reference identification qualifier 'RRC'[Routing Request Control Number]. The Routing Request Control Number [RRC] must be formatted to include the 6-digit JCPenney supplier number, with leading zeroes and inclusive of the check digit, the 5-digit JCPenney unit number for the ordering stores, Store Support Center [SSC] or Catalog Logistics Center [CLC] with leading zeroes and inclusive of the check digits, the current date in the YYYYMMDD format and a 6-digit sequential number. For example, vendor #012345, shipping to store 00166, and sending the 753 on 6/25/02 would have an RRC number of "0123450016620020625000001". The 6-digit sequential portion of the RRC would be incremented by 1 for each subsequent RRC. ORDER INFORMATION DETAIL [OID] This segment is used to identify the JCPenney purchase order information which includes the purchase order number [OID02], subdivision number [OID03], quantity (number of cartons and pieces) [OID05], weight in pounds [OID07] and volume in cubit feet. Both number of cartons and selling units are required. This is accomplished by sending two OID loops for each purchase order, one for cartons and a second for selling units [pieces]. The first OID, representing the number of cartons, will contain a packaging form code of CTN in data field OID04 and in data field OID05 the value will be the number of cartons shipped against the purchase order number listed in OID02. The second OID will contain information related to the number of


selling units [pieces] in those cartons. In data field OID04 the packaging form code is PCS [pieces], OID05 is the number of pieces [selling units] contained in each carton.

J.C. Penney Co Proprietary and Confidential 26

753- Request for Routing Instructions (TMS Dynamic Routing) – Business Example

Scenario: On 10/1/2000 the ACME DRESS COMPANY [JCP Supplier #123456, shipping from 1234 MAIN STREET, PLEASANTON, NY 100201234] determines that it will have shipments for nine [9] JCPenney locations ready for pickup at 3 PM on 10/3/2000. Since the shipment will be for nine different locations, there will be nine unique Routing Request Control Numbers [RRC#]. The details are as follows: ACME sends a 753: Request for Routing Instructions to JCPenney at 4:30 PM on 10/1/2000. [See below.]

READY TO SHIP

STORE ROUTING REQUEST# P.O.# SUB CARTONS PIECES WEIGHT LBS. VOLUME CFT.

HAZMAT

10/3 00166 1234560016620001001000001 45678901 223 1,800 21,600 21,600 6075.00 Y “ 15313 1234561531320001001000002 12345678 223 5 60 60 16.88 N “ 19836 1234561983620001001000003 67890123 223 70 840 840 236.30 N “ 24588 1234562458820001001000004 12345678 223 100 1200 1200 337.50 N “ “ “ 23456789 644 80 960 960 270.00 N “ 24596 1234562459620001001000005 90123456 644 7 84 84 23.63 N “ “ “ 12345678 223 70 840 840 236.30 N “ 99481 1234569948120001001000006 1234567K 208 700 8400 8400 2363.00 N “ 99788 1234569978820001001000007 8901234C 208 70 840 840 236.30 N “ 99804 1234569980420001001000008 6789012R 208 100 1200 1200 337.50 N “ 99853 1234569985320001001000009 3456789H 208 100 1200 1200 337.50 N EDI TRANSMISSION DATA EXPLANATION

HEADER ST 753 123456789 753: Transaction Set ID. 123456789: T/S Control Number. BGN 00 ABC123 20001001 16300000 00: T/S Purpose Code for ‘Original”. ABC123: Ref. ID. 20001001: Transaction Date. 16300000: Transaction Time. PER IC EM [email protected] IC: Contact Function Code for ‘Information Contact’. EM: Comm. Number Qualifier for ‘Electronic Mail’. [email protected] : Comm. Number [Contact E-Mail ID]. N1 SF ACME DRESS COMPANY 92 123456 SF: Entity ID Code for ‘Ship From’. ACME DRESS

COMPANY: Vendor Name. 92: ID Code Qualifier for ‘Assigned by Buyer’. 123456: JCP-assigned vendor number. N3 1234 MAIN STREET 1234 MAIN STREET: Vendor’s ship point address. N4 PLEASANTON NY 100201234 PLEASANTON: Ship Point City. NY: Ship Point State. 100201234: Ship Point Zip.

DETAIL LX 000001 000001: Assigned Number. N1 ST 92 00166 ST: Entity ID Code for ‘Ship To’. 92: ID Code Qualifier for ‘Assigned by Buyer’. 00166: JCP Destination Unit Number. L11 1234560016620001001000001 RRC 1234560016620001001000001: Ref. ID. RRC: Ref. Id

Qualifier for ‘Routing Request Control Number’. G62 RS 20001003 RS 15000000 RS: Date Qualifier for ‘Ready to ship’. 20001003:

Ready-to-Ship Date. RS: Time Qualifier for ‘Ready to ship’. 15000000: Ready-to-Ship Time.

OID 45678901 223 CTN 1800 L 21600 E 6075

45678901: JCP Purchase Order Number. 223:


Subdivision number. CTN: Packaging Form Code for ‘Carton’. 1800: Quantity [cartons]. L: Weight Unit Code for ‘Pounds’. 21600: Weight [21,600 lbs.]. E:

Volume Unit Code for ‘Cubic Feet’. 6075: Volume [6075 cft.]. OID 45678901 223 PCS 21600 L 21600 E 6075 45678901: JCP Purchase Order Number. 223: Subdivision number. PCS: Packaging Form Code for ‘Pieces’. 21600: Quantity [pieces]. L: Weight Unit

Code for ‘Pounds’. 21600: Weight [21,600 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 6075: Volume

[6075 cu. ft.]. CMC ORMD ORMD: Commodity Code for ‘Other Regulated Materials, Class D’. N1 ST 92 15313 ST: Entity ID Code for ‘Ship To’. 92: ID Code Qualifier for ‘Assigned by Buyer’. 15313: JCP Destination Unit Number. L11 1234561531320001001000002 RRC 1234561531320001001000002: Ref. ID. RRC: Ref. Id

Qualifier for ‘Routing Request Control Number’. G62 RS 20001003 RS 15000000 RS: Date Qualifier for ‘Ready to ship’. 20001003: Ready-to-Ship Date. RS: Time Qualifier for ‘Ready to

ship’. 15000000: Ready-to Ship Time. OID 12345678 223 CTN 5 L 60 E 16.88 12345678: JCP Purchase Order Number. 223: Subdivision number. CTN: Packaging Form Code for ‘Carton’. 5: Quantity [cartons]. L: Weight Unit Code for ‘Pounds’. 60: Weight [60 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 16.88: Volume [16.88 cu. ft.]. OID 12345678 223 PCS 60 L 60 E 16.88 12345678: JCP Purchase Order Number. 223: Subdivision number. PCS: Packaging Form Code for ‘Pieces’. 60: Quantity [pieces]. L: Weight Unit Code for ‘Pounds’. 60: Weight [60 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 16.88: Volume [16.88 cu. ft.]. N1 ST 92 19836 ST: Entity ID Code for ‘Ship To’. 92: ID Code Qualifier for ‘Assigned by Buyer’. 19836: JCP Destination Unit Number. L11 1234561983620001001000003 RRC 1234561983620001001000003: Ref. ID. RRC: Ref. Id

Qualifier for ‘Routing Request Control Number’. G62 RS 20001003 RS 15000000 RS: Date Qualifier for ‘Ready to ship’. 20001003: Ready-to-Ship Date. RS: Time Qualifier for ‘Ready to ship’. 15000000: Ready-to-Ship Time. OID 67890123 223 CTN 70 L 840 E 236.3 67890123: JCP Purchase Order Number. 223: Subdivision number. CTN: Packaging Form Code for ‘Carton’. 70: Quantity [cartons]. L: Weight Unit Code

for ‘Pounds’. 840: Weight [840 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 236.3: Volume [236.3 cu. ft.].

OID 67890123 223 PCS 840 L 840 E 236.3 67890123: JCP Purchase Order Number. 223: Subdivision number. PCS: Packaging Form Code for

‘Pieces’. 840: Quantity [pieces]. L: Weight Unit Code for ‘Pounds’. 840: Weight [840 lbs.]. E: Volume Unit

Code for ‘Cubic Feet’. 236.3: Volume [236.3 cu. ft.]. N1 ST 92 24588 ST: Entity ID Code for ‘Ship To’. 92: ID Code Qualifier

for ‘Assigned by Buyer’. 24588: JCP Destination Unit Number.

L11 1234562458820001001000004 RRC 1234562458820001001000004: Ref. ID. RRC: Ref. Id Qualifier for ‘Routing Request Control Number’.

G62 RS 20001003 RS 15000000 RS: Date Qualifier for ‘Ready to ship’. 20001003: Ready-to-Ship Date. RS: Time Qualifier for ‘Ready to ship’. 15000000: Ready-to-Ship Time.


OID 12345678 223 CTN 100 L 1200 E 337.5 12345678: JCP Purchase Order Number. 223: Subdivision number. CTN: Packaging Form Code for

‘Carton’. 100: Quantity [cartons]. L: Weight Unit Code for ‘Pounds’. 1200: Weight [1200 lbs.]. E: Volume

Unit Code for ‘Cubic Feet’. 337.5: Volume [337.5 cu. ft.].

OID 12345678 223 PCS 1200 L 1200 E 337.5 12345678: JCP Purchase Order Number. 223: Subdivision number. PCS: Packaging Form Code for ‘Pieces’. 1200: Quantity [pieces]. L: Weight Unit Code for ‘Pounds’. 1200: Weight [1200 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 337.5: Volume [337.5 cu. ft.].

OID 23456789 644 CTN 80 L 960 E 270 23456789: JCP Purchase Order Number. 644: Subdivision number. CTN: Packaging Form Code for ‘Carton’. 80: Quantity [cartons]. L: Weight Unit Code for ‘Pounds’. 960: Weight [960 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 270: Volume [270 cu. ft.].

OID 23456789 644 PCS 960 L 960 E 270 23456789: JCP Purchase Order Number. 644: Subdivision number. PCS: Packaging Form Code for ‘Pieces’. 960: Quantity [pieces]. L: Weight Unit Code for ‘Pounds’. 960: Weight [960 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 270: Volume [270 cu. ft.].

N1 ST 92 24596 ST: Entity ID Code for ‘Ship To’. 92: ID Code Qualifier for ‘Assigned by Buyer’. 24596: JCP Destination Unit Number.



OID 90123456 644 CTN 7 L 84 E 23.63 90123456: JCP Purchase Order Number. 644: Subdivision number. CTN: Packaging Form Code for ‘Carton’. 7: Quantity [cartons]. L: Weight Unit Code for ‘Pounds’. 84: Weight [84 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 23.63: Volume [23.63 cu. ft.].


OID 12345678 223 CTN 70 L 84 0 E 236.3 12345678: JCP Purchase Order Number. 223: Subdivision number. CTN: Packaging Form Code for ‘Carton’. 70: Quantity [cartons]. L: Weight Unit Code for ‘Pounds’. 840: Weight [840 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 236.3: Volume [236.3 cu. ft.].






OID 1234567K 208 CTN 700 L 8400 E 2363 1234567K: JCP Purchase Order Number. 208: Subdivision number. CTN: Packaging Form Code for ‘Carton’. 700: Quantity [cartons]. L: Weight Unit Code for ‘Pounds’. 8400: Weight [8400 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 2363: Volume [2363 cu. ft.].

OID 1234567K 208 PCS 8400 L 8400 E 2363 1234567K: JCP Purchase Order Number. 208: Subdivision number. PCS: Packaging Form Code for ‘Pieces’. 8400: Quantity [pieces]. L: Weight Unit Code for ‘Pounds’. 8400: Weight [8400 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 2363: Volume [2363 cu. ft.].




OID 8901234C 208 CTN 70 L 840 E 236.3 8901234C: JCP Purchase Order Number. 208: Subdivision number. CTN: Packaging Form Code for ‘Carton’. 70: Quantity [cartons]. L: Weight Unit Code for ‘Pounds’. 840: Weight [840 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 236.3: Volume [236.3 cu. ft.].

OID 8901234C 208 PCS 840 L 840 E 236.3 8901234C: JCP Purchase Order Number. 208: Subdivision number. PCS: Packaging Form Code for ‘Pieces’. 840: Quantity [pieces]. L: Weight Unit Code for ‘Pounds’. 840: Weight [840 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 236.3: Volume [236.3 cu. ft.].


L11 1234569980420001001000008 RR C 1234569980420001001000008: Ref. ID. RRC: Ref. Id Qualifier for ‘Routing Request Control Number’.


OID 6789012R 208 CTN 100 L 1200 E 337.5 6789012R: JCP Purchase Order Number. 208: Subdivision number. CTN: Packaging Form Code for ‘Carton’. 100: Quantity [cartons]. L: Weight Unit Code for ‘Pounds’. 1200: Weight [1200 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 337.5: Volume [337.5 cu. ft.].

OID 6789012R 208 PCS 1200 L 1200 E 337. 5 6789012R: JCP Purchase Order Number. 208: Subdivision number. PCS: Packaging Form Code for ‘Pieces’. 1200: Quantity [pieces]. L: Weight Unit Code for ‘Pounds’. 1200: Weight [1200 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 337.5: Volume [337.5 cu. ft.].


L11 1234569985320001001000009 RR C 1234569985320001001000009: Ref. ID. RRC: Ref. Id Qualifier for ‘Routing Request Control Number’.



OID 3456789H 208 CTN 100 L 1200 E 337.5 3456789H: JCP Purchase Order Number. 208: Subdivision number. CTN: Packaging Form Code for ‘Carton’. 100: Quantity [cartons]. L: Weight Unit Code for ‘Pounds’. 1200: Weight [1200 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 337.5: Volume [337.5 cu. ft.].

OID 3456789H 208 PCS 1200 L 1200 E 337.5 3456789H: JCP Purchase Order Number. 208: Subdivision number. PCS: Packaging Form Code for ‘Pieces’. 1200: Quantity [pieces]. L: Weight Unit Code for ‘Pounds’. 1200: Weight [1200 lbs.]. E: Volume Unit Code for ‘Cubic Feet’. 337.5: Volume [337.5 cu. ft.].

TRAILER SE 58 123456789 58: Number of Included Segments. 123456789: T/S

Control Number.

https://supplier.jcpenney.com/supplier/general/edi/E-Commerce/Dynamic_Routing/TMS-Lite_Main.htm

https://supplier.jcpenney.com/supplier/general/edi/E-Commerce/Dynamic_Routing/TMS-Lite_Business_Glossary.htm

https://supplier.jcpenney.com/supplier/Logistics_Distribution/default.asp

https://supplier.jcpenney.com/


753 REQUEST FOR ROUTING INSTRUCTIONS BUSINESS RULES FOR TMS – ROUTING AUTHORIZATION (revised 09/17/04) The purpose of this document is to provide an explanation of JCPenney's use of some of the major sections of the 753 Request for Routing Instructions for suppliers participating in the TMS Routing Authorization program. TMS Routing Authorization is an intermediate step towards required 'full' TMS compliance. While suppliers work to become compliant on the full TMS Dynamic Routing Initiative program, TMS Routing Authorization (aka TMS - Lite) allows JCPenney to validate and authorize orders before shipment. TMS Routing Authorization continues to utilize the static routing guides and authorizes the supplier to ship, whereas the TMS Dynamic Routing program provides benefits of real-time network optimization, including destination and mode selection. For a complete explanation of the requirements of the TMS Routing Authorization program, refer to the Business Rules and Glossary of the TMS Routing Authorization guidelines under the Logistics section of the supplier web site. GENERAL REQUIREMENTS The 753 transaction for TMS - Routing Authorization may be sent the same day of the shipment, or up to and including two business days before shipment. A supplier is not authorized to ship without receipt of a 754 for each specific Purchase Order or Delivery Instruction. HEADER LEVEL BEGINNING SEGMENT [BGN] The purpose of this segment is to identify the transaction set purpose, reference identification, date and time of the transaction. The transaction set purpose [BGN01] is 'Original' (00). The sender's [vendor] internal number is used as the reference identification number [BGN02] to identify the transaction set within the vendor's application system. ADMINISTRATIVE COMMUNICATION CONTACT [PER] This segment is used to specify the Supplier's contact information. In section PER02, the supplier will provide the contact person's name. The contact's telephone number is sent in the PER04 field. The telephone number must consist of a 3-digit area code and a 7-digit phone number. The supplier must also send an email address [PER06]. JCPenney will reject the 753 request if the email address in PER06 is missing or incomplete. DETAIL LEVEL BUSINESS INSTRUCTIONS AND REFERENCE NUMBER [L11] The reference identification in L1101 is the vendor assigned control number for a specific shipment. L1102 is the reference identification qualifier 'RRC' [Routing Request Control Number]. The Routing Request Control Number [RRC] must be formatted to include the 6-digit JCPenney supplier number, with leading zeroes and inclusive of the check digit, the 5-digit JCPenney unit number for the ordering stores, Store Support Center [SSC] or Catalog Logistics Center [CLC] with leading zeroes and inclusive of the check digits, the current date in the YYYYMMDD format and a 6-digit sequential number. For example, vendor #012345, shipping to store 00166, and sending the 753 on 6/25/02 would have an RRC number of “0123450016620020625000001". The 6-digit sequential portion of the RRC would be incremented by 1 for each subsequent RRC.


The Routing Request Control Number [RRC] must be unique for each Request for Routing [753]. Duplicated RRC numbers will be rejected. ORDER INFORMATION DETAIL [OID] This segment is used to identify the JCPenney purchase order information which includes the purchase order number [OID02], subdivision number [OID03] and quantity [PCS - pieces]. For TMS - Routing Authorization, only the number of selling units is required [OID05]. OID05 is the total number of pieces [selling units] contained in the shipment. Note: Cartons [CTN], weight and volume [OID07 and OID09] are not required for TMS - Routing Authorization but these data fields are mandatory for the 'full' TMS program.

J. C. Penney Co. Proprietary and Confidential 33

753 – REQUEST FOR ROUTING INSTRUCTIONS

Business Example: TMS – Request for Routing Authorization

Scenario: On 5/5/2003 the ACME SHIRT COMPANY [JCPenney assigned supplier number 123456] submitted a ‘Request for Routing Authorization’ for 5 JCPenney locations to be shipped on 5/7/03. The details are as follows:

Mark For Store Routing Request # PO# Sub Pieces 00166 1234569445820030505000001 12345678 524 700 15313 1234569447420030505000002 23456789 524 900 24588 1234569446620030505000003 45678901 524 1000 10876 1234569442520030505000004 56789012 524 1200 00813 1234569444120030505000005 67890123 524 800

TRANSACTION EXPLANATION HEADER

ST 753 012345678 753: Transaction Set ID. 012345678: Transaction Set Control number.

BGN 00 13579 20030318 00: Transaction Set Purpose [Original]. 13579: Reference Identification. 20030505: Date of transmission [05/05/03]

PER IC EM [email protected] IC: Contact Function Code [Information Contact]. EM: Communication Number Qualifier [Electronic Mail]. [email protected]: Communication number [Contact E-Mail ID].

LOOP N1 N1 SF 92 123456 SF: Entity Identifier Code [Ship From]. 92: Identification

Code Qualifier [Assigned by Buyer]. 123456: Identification Code [JCPenney assigned supplier number].

N3 1234 MAIN STREET 1234 MAIN STREET: Vendor's ship point address. N4 PLEASANTON NY 100201234 PLEASANTON: Ship Point City name NY: Ship Point

State 100201234: Ship Point Postal [Zip] Code. DETAL

LOOP: LX LX 000001 000001: Assigned number. LOOP: N1 N1 ST 92 00166 ST: Entity Identifier Code [Ship To]. 92: Identification

Code Qualifier [Assigned by Buyer]. 00166: Identification Code [JCP Destination Unit number].

L11 1234569445820030505000001 RRC 1234569445820030505000001: Reference Identification. RRC: Routing Request Control Number.

G62 RS 20030507 RS: Date Qualifier [Ready to ship]. 20030507: Date [05/07/2003]

LOOP : N1/OID OID 12345678 524 PCS 700 12345678: JCP Purchase order number. 524: JCP

Subdivision number. PCS: Packaging Form Code


[Pieces]. 700: Quantity [pieces] LOOP: N1 N1 ST 92 15313 ST: Entity Identifier Code [Ship To]. 92: Identification





Subdivision number. PCS: Packaging Form Code [Pieces]. 900: Quantity [pieces]

LOOP: N1 N1 ST 92 24588 ST: Entity Identifier Code [Ship To]. 92: Identification


















TRAILER SE 28 012345678 28: Count of all segments including ST and SE.


012345678: Transaction Set Control Number [same as ST02].

753 request for routing instructions

Documents