754 routing instructions - iconnect · 2008-01-29 · loop id - 0210loop id - 0210 2525 0700 qty...

754 Routing InstructionsVICS EDI/V4030/754: 754 Routing Instructions

Modified: 08/24/2006

Notes: _________________________________________________________________J. C. Penney Co Proprietary and Confidential

V4030 Routing Instructions - 754

i J.C. Penney Co.

Table of Contents

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 L11 - Business Instructions and Reference Number…………………………………………………… 15 BLR - Transportation Carrier Identification………………………………………………………………. 16 OID - Order Identification Detail……………………………………………………………………………... 17 G62 - Date/Time………………………………………………………………………………………………. 18 MSI - Multi-stop Shipment Information…………………………………………………………………… 19 QTY - Quantity…………………………………………………………………………………………………. 20 N1 - Name……………………………………………………………………………………………………….. 21 SE - Transaction Set Trailer………………………………………………………………………………….. 22 GE - Functional Group Trailer………………………………………………………………………………… 23 IEA - Interchange Control Trailer…………………………………………………………………………….. 24

+++++

TMS Dynamic Routing Business Rules………………..…………………………………………………… 25 TMS Dynamic Routing Business Example………………………………………………………………… 27 TMS-Lite Routing Authorization Business Rules…………..……………………………………………. 33 TMS-Lite Routing Authorization Business Example......………………………………………………... 35


J.C. Penney Co. Proprietary and Confidential 1

754 Routing InstructionsFunctional Group=RG

This Draft Standard for Trial Use contains the format and establishes the data contents of the Routing InstructionsTransaction Set (754) for use within the context of an Electronic Data Interchange (EDI) environment. Thistransaction set is used to communicate routing instructions to a supplier for a specific shipment. It can be used alsoto respond to a Request for Routing Instructions Transaction Set (753).

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 5

LOOP ID - 0100 5 LOOP ID - 0100 5

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

Detail:Pos Id Segment Name Req Max Use Repeat Notes

LOOP ID - 0200 9999 LOOP ID - 0200 9999

0100 LX Assigned Number M 1 0200 L11 Business Instructions and Reference Number O 5 0300 BLR Transportation Carrier Identification O 1 0400 OID Order Identification Detail O >1 0500 G62 Date/Time O 2 0600 MSI Multi-stop Shipment Information O 1

LOOP ID - 0210 25 LOOP ID - 0210 25

0700 QTY Quantity O 1

LOOP ID - 0220 1 LOOP ID - 0220 1

0900 N1 Name O 1 1300 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

Notes: 1/0400 One iteration of the N1 segment must be used to identify the ship-from location.



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 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 ID: 6111350027 (Logistics).User Note 1: JCPenney sender ID: 6111350027 (Logistics).

M AN 15/15

ISA07 I05 Interchange ID Qualifier

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

M ID 2/2


Ref Id Element Name Req Type Min/Max


being qualified

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

M ID 1/1

Code NameP Production Data


Code Name


T 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 NameRG Routing Instructions (754)

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

BGN07 640 Transaction Type Code

Description: Code specifying the type of transaction

O ID 2/2

Code NameRJ Response to Request for Routing Instructions

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: 5Heading - 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 here.User Note 1: Only one e-mail address can be entered here.

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.

User Note 1:User Note 1:One occurrence of the N1 segment is required to identify the ship-from location by using code SF in N101. Onlyone ship-from location may be specified in a single 754 transaction set.One occurrence of the N1 segment is required to identify the ship-from location by using code SF in N101. Onlyone ship-from location may be specified in a single 754 transaction set.



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.User Note 1: Maximum length is nineteen characters.

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.User Note 1: Nine digit postal code.

O ID 3/15

N404 26 Country Code

Description: Code identifying the countryUser Note 1: Country code required if not USA.User Note 1: Country code required if 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



L11 Business Instructions andReference Number

Pos: 0200 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 NamePUA Pick Up Appointment NumberRRC Routing Request Control Number

L1103 352 Description

Description: A free-form description to clarify the related dataelements and their contentUser Note 1: Transportation service level requirements.User Note 1: Transportation service level requirements.User Note 2: Data element only used when L1102 = RRCUser Note 2: Data element only used when L1102 = RRC

X AN 1/80

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:Two consecutive L11 segments will be generated for each of the Reference Identification Qualifiers in L1102.

Routing Request Control Number (RRC). It will be used to identify the control number issued by the vendor onthe Request for Routing (753).

Pick Up Appointment Number (PUA). For TMS Dynamic Routing, this number will identify the individual loadbeing routed out of JCPenney's optimization program. For TMS Routing Authorization, this will be the JCPenneyRouting Authorization number.

Two consecutive L11 segments will be generated for each of the Reference Identification Qualifiers in L1102.

Routing Request Control Number (RRC). It will be used to identify the control number issued by the vendor onthe Request for Routing (753).

Pick Up Appointment Number (PUA). For TMS Dynamic Routing, this number will identify the individual loadbeing routed out of JCPenney's optimization program. For TMS Routing Authorization, this will be the JCPenneyRouting Authorization number.



BLR Transportation CarrierIdentification



To transmit the identifying SCAC code and effective date and time for the data in the transaction set

Element Summary: Ref Id Element Name Req Type Min/MaxBLR01 140 Standard Carrier Alpha Code

Description: Standard Carrier Alpha Code

M ID 2/4



OID Order Identification Detail Pos: 0400 Max: >1Detail - Optional


To specify order identification detail

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

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

X AN 1/22

OID10 647 Application Error Condition Code

Description: Code indicating application error condition

O ID 1/3

Code NameW Outside Ship WindowMA Missing or Invalid Store NumberMB Missing or Invalid Purchase Order NumberIQT Invalid Quantity



G62 Date/Time Pos: 0500 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 Name69 Scheduled Pick-Up Date

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 NameU Scheduled Pick Up Time

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.



MSI Multi-stop ShipmentInformation



To specify multi-stop shipment information

Element Summary: Ref Id Element Name Req Type Min/MaxMSI01 1073 Yes/No Condition or Response Code

Description: Code indicating a Yes or No condition or response

M ID 1/1

Code NameY Yes

MSI02 165 Stop Sequence Number

Description: Identifying number for the specific stop and thesequence in which the stop is to be performed

O N0 1/3

Semantics: 1. MSI01 identifies whether the shipment is a multi-stop shipment. A "Y" indicates the shipment is a multi-stop

shipment; an "N" indicates the shipment is not a multi-stop shipment.

Comments: 1. When MSI01 contains code Y, MSI02 will contain the stop sequence number.



QTY Quantity Pos: 0700 Max: 1Detail - Optional


To specify quantity information

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

Description: Code specifying the type of quantity

M ID 2/2

Code NameYU Trailers

QTY02 380 Quantity

Description: Numeric value of quantityUser Note 1: Maximum of one decimal place.User Note 1: Maximum of one decimal place.

X R 1/15

User Note 1:User Note 1:Used to indicate the number of trailers a single purchase order shipment will require.Used to indicate the number of trailers a single purchase order shipment will require.



N1 Name Pos: 0900 Max: 1Detail - Optional


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.



SE Transaction Set Trailer Pos: 1300 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.



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 25

754 ROUTING INSTRUCTIONS - BUSINESS RULES FOR TMS DYNAMIC ROUTING The purpose of this document is to provide and explanation of JCPenney's use of some of the major sections of the 754 Routing Instructions document when used for TMS Dynamic Routing. 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 in 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 [BGN01] of 'Original' [00], the reference identification [BGN02], date and time [BGN03 and BGN04] of the transaction and the type of transaction [BGN07]. The reference identification [BGN02] is the sender's (JCPenney) internal number used to identify the transaction set within the sender's application system. DETAIL LEVEL BUSINESS INSTRUCTIONS AND REFERENCE NUMBER [L11] This segment is used to identify the control number issued by the vendor on the Request for Routing (753) document and to provide the transportation service level requirements. L1101 will contain the reference identification number from the request. The reference identification qualifier [L1102] is RRC [Routing Request Control Number] and in section L1103 the vendor will find the transportation service level requirements. The second L11 segment (L1101) is used to provide the JCPenney Load ID number. This number will identify the individual load being routed out of our optimization program. The code value in L1102 is PUA (Pick-Up Appointment Number). A single TL, regardless of the number of pickups or delivery stops, will be issued a single JCPenney Load ID. This Load ID will be passed to the Supplier on the 754 as well as to our T/L 3PL provider on the EDI 204. This is the reference number that must be used by the supplier to communicate and coordinate shipments with our T/L 3PL provider. Each individual LTL, Small Package, or Air shipment will be assigned its own unique Load ID.

Transportation Service Level Codes (L1103) U2ND - UPS 2nd Day Air UGND - UPS Next Day Air UGND - UPS Ground UNDS - UPS Next Day Saver LTL1 - Direct LTL to Retail LTL1 - PEPS LTL1 – Catcon LTL1 - Direct LTL to Catalog LTL1 - Pacer Dedicated (California)

ENDA - Emery Next Day Air E2ND - Emery 2nd Day Air INT1 - Intermodal DED - Ridgefield Dedicated BKHL - SSC Backhaul TL1 - Truckload LTIS - LTL for Canadian Origins and for Dart into 94417

J.C. Penney Co Proprietary and Confidential 26

TRANSPORTATION CARRIER IDENTIFICATION [BLR] The BLR01 section will contain the SCAC code of the specific carrier assigned to pick up the shipment. Refer to the Dynamic Routing Initiative [TMS] guidelines for a list of core carrier SCAC codes [see Frequently Asked Questions - Miscellaneous question #1]. DATE/TIME [G62] The purpose of this segment is to specify the scheduled pickup date/time for the shipment. The pickup date is the date that JCPenney is requiring the shipment to be tendered to the approved carrier. JCPenney will not be passing back a pick-up time. TL shipments must be available for pick-up by open of business on the ATS date. TL pick-up times must be jointly coordinated between the supplier and our T/L 3PL provider. LTL, Small Package and Air pickup times must be coordinated by the supplier with the approved carrier. MULTI-STOP SHIPMENT INFORMATION [MSI] This segment is used to indicate a multi-stop shipment. MSI01 (Yes/No Condition/Response Code) will have an indicator of Y (Yes). MS102 is the stop sequence number. It is the reverse of the actual load sequence. For example, if Dest A is the last delivery, Dest B is the next to last delivery and Dest C is the first delivery; Dest A would have stop off sequence 3 and would be loaded first. Dest B would have stop off sequence 2 and would be loaded second and Dest C would be loaded last and be assigned stop of sequence 1.

Destination Trailer Location Stop-off sequence number Dest A Nose 3 Dest B Middle 2 Dest C Tail 1

QUANTITY [QTY] Segment QTY is used to indicate the number of trailers (QTY01, "YU") a single purchase order shipment will require. This quantity is determined by the total shipment volume to a single destination on a single day’s shipment. In the event that the shipment exceeds the capacity of a single trailer, the value of QTY02 will include a decimal point (i.e. 1.5) which is the fraction of whatever is left over from the single trailer. The left over volume is loaded onto a second trailer. NAME [N1 - ST] This segment identifies the ship to location. This is the destination that should be listed on the Bill of Lading.

J. C. Penney Co. Proprietary and Confidential 27

754 ROUTING INSTRUCTION (TMS – DYNAMIC ROUTING) BUSINESS EXAMPLE Scenario: JCPenney Co. Inc. processes the 753: Request for Routing Instructions and creates optimized routings. As a result of optimization, the nine Routing Request Control Numbers [RRC#] were broken into eight [8] separate JCP Load IDs. The details are as follows:

READY TO SHIP STORE RRC# P.O.# CTNS PCS WGT

LBS. VOL. CFT. HAZ MAT SHIP

TO JCP LOAD ID

10/3 24588 12345624588200 01001000004 12345678 100 1,200 1,200 337.5 N “ “ “ 23456789 80 960 960 270 N “ 19836 12345619836200 01001000003 67890123 70 840 840 236.3 N “ 99481 12345699481200 01001000006 1234567K 700 8,400 8,400 2,363 N Total 950 11,400 11,400 3,206.8 90506 1111111111111111111111111111 10/3 99853 12345699853200 01001000009 3456789H 100 1,200 1,200 337.5 N 99853 2222222222222222222222222222 10/3 24596 12345624596200 01001000005 90123456 7 84 84 23.63 N 24596 3333333333333333333333333333 10/3 24596 12345624596200 01001000005 12345678 70 840 840 236.3 N 90506 4444444444444444444444444444 10/3 00166 12345600166200 01001000001 45678901 1,200 14,400 14,400 3400 Y 97766 5555555555555555555555555555 “ “ “ “ 600 7,200 7,200 1700 Y 90506 6666666666666666666666666666 Total 1,800 21,600 21,600 6,075 Y 10/3 15313 12345615313200 01001000002 12345678 5 60 60 16.88 N 15313 7777777777777777777777777777 10/3 99804 12345699804200 01001000008 6789012R 100 1,200 1,200 337.5 N “ 99788 12345699788200 01001000007 8901234C 70 840 840 236.3 N Total 170 2,040 2,040 573.8 N 90506 8888888888888888888888888888

JCPenney Co. Inc. sends a 754: Routing Instructions to ACME DRESS COMPANY 0n 10/2/00 at 9 AM. [See below.]

EDI TRANSMISSION DATA EXPLANATION HEADER ST 754 987654321 754: Trans. Set ID. 987654321: Trans. Set

Control Number. BGN 00 2000100213253515123456 20001002 09000000 RJ 00: Trans. Set Purpose for “Original”.

2000100213253515123456: Ref. ID. 20001002: Trans. Date. 09000000: Trans. Time. RJ: Trans. Type Code for “Response to Request for Routing Instructions”.

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. L11 1234562458820001001000004 RRC TL1 1234562458820001001000004: Routing

Request Number from the 753: Request for Routing Instructions. RRC: Ref. ID Qualifier for “Routing Request Control Number. TL1: Transportation service level requirement indicating TRUCKLOAD.

L11 1111111111111111111111111111 PUA 1111111111111111111111111111: JCP


Load ID. PUA: REF. ID Qualifier for “Pickup Appointment Number”.

BLR TPQL TPQL: SCAC for assigned pickup carrier. OID 12345678 12345678: JCP Purchase Order Number. OID 23456789 23456789: JCP Purchase Order Number. G62 69 20001003 69: Date Qualifier for “Scheduled Pick-

Up”. 20001003: Scheduled Pick-Up Date. MSI Y 001 Y: Response Code indicating Multi-Stop

Shipment. 001: Stop Sequence Number indicating first delivery stop. This should be loaded last.

N1 ST 92 90506 ST: Entity ID Code for “Ship To”. 92: ID Code Qualifier for “Assigned by Buyer”. 90506: JCP Unit Number for assigned Ship-To Location

LX 000002 000002: Assigned Number. L11 1234561983620001001000003 RRC• TL1 1234561983620001001000003: Routing


L11 1111111111111111111111111111 PUA 1111111111111111111111111111: JCP Load ID. PUA: REF. ID Qualifier for “Pickup Appointment Number”.

BLR TPQL TPQL: SCAC for assigned pickup carrier. OID 67890123 67890123: JCP Purchase Order Number. G62 69 20001003 69: Date Qualifier for “Scheduled Pick-


Shipment. 001: Stop Sequence Number indicating first delivery stop. This should be loaded last.

N1 ST 92 90506 ST: Entity ID Code for “Ship To”. 92: ID Code Qualifier for “Assigned by Buyer”. 90506: JCP Unit Number for assigned Ship-To Location.

LX 000003 000003: Assigned Number. L11 1234569948120001001000006 RRC TL1 1234569948120001001000006: Routing



BLR TPQL TPQL: SCAC for assigned pickup carrier. OID 1234567K 1234567K: JCP Purchase Order Number. G62 69 20001003 69: Date Qualifier for “Scheduled Pick-


Shipment. 002: Stop Sequence Number indicating second delivery stop. This should be loaded first.



LX 000004 000004: Assigned Number. L11 1234569985320001001000009 RRC LTL1 1234569985320001001000009: Routing

Request Number from the 753: Request for Routing Instructions. RRC: Ref. ID Qualifier for “Routing Request Control Number. LTL1: Transportation service level requirement for “Direct LTL to Catalog”.


BLR TINA TINA: SCAC for assigned pickup carrier. OID 3456789H 3456789H: JCP Purchase Order Number. G62 69 20001003 69: Date Qualifier for “Scheduled Pick-

Up”. 20001003: Scheduled Pick-Up Date. N1 ST 92 99853 ST: Entity ID Code for “Ship To”. 92: ID

Code Qualifier for “Assigned by Buyer”. 99853: JCP Unit Number for assigned Ship-To Location.


Request Number from the 753: Request for Routing Instructions. RRC: Ref. ID Qualifier for “Routing Request Control Number. LTL1: Transportation service level requirement for “Direct LTL to Retail”.


BLR JOES JOES: SCAC for assigned pickup carrier. OID 90123456 90123456: JCP Purchase Order Number. G62 69 20001003 69: Date Qualifier for “Scheduled Pick-




Request Number from the 753: Request for Routing Instructions. RRC: Ref. ID Qualifier for “Routing Request Control Number. LTL1: Transportation service level requirement for “PEPS”.


BLR IKES IKES: SCAC for assigned pickup carrier. OID 12345678 12345678: JCP Purchase Order Number. G62 69 20001003 69: Date Qualifier for “Scheduled Pick-

Up”. 20001003: Scheduled Pick-Up Date.




Request Number from the 753: Request for Routing Instructions. RRC: Ref. ID Qualifier for “Routing Request Control Number. TL1: Transportation service level requirement for TRUCKLOAD.



Up”. 20001003: Scheduled Pick-Up Date. QTY YU 1 YU: Quantity Qualifier for “Trailers”. 1:

Number of trailers required for this shipment (1.0). This indicates that this trailer should be 100% loaded with cartons from the Purchase Order in the OID segment. [This segment would only be used where a single purchase order requires more than one trailer.]



Request Number from the 753: Request for Routing Instructions. RRC: Ref. ID Qualifier for “Routing Request Control Number. TL1: Transportation service level requirement for TRUCKLOAD.



Up”. 20001003: Scheduled Pick-Up Date. QTY YU 0.5 YU: Quantity Qualifier for “Trailers”. 0.5:

Number of trailers required for this shipment (0.5). This indicates that this trailer should be approximately 50% loaded with cartons from the Purchase Order in the OID segment. [This segment would only be used where a single purchase order requires more than one trailer.]



LX 000009 000009: Assigned Number. L11 1234561531320001001000002 RRC U2ND 1234561531320001001000002: Routing

Request Number from the 753: Request for Routing Instructions. RRC: Ref. ID Qualifier for “Routing Request Control Number. U2ND: Transportation service level requirement for “UPS 2nd DAY AIR”.


BLR UPSN UPSN: SCAC for assigned pickup carrier. OID 12345678 12345678: JCP Purchase Order Number. G62 69 20001003 69: Date Qualifier for “Scheduled Pick-




Request Number from the 753: Request for Routing Instructions. RRC: Ref. ID Qualifier for “Routing Request Control Number. LTL1: Transportation service level requirement for “CATCON”.


BLR JOES JOES: SCAC for assigned pickup carrier. OID 6789012R 6789012R: JCP Purchase Order Number. G62 69 20001003 69: Date Qualifier for “Scheduled Pick-




Request Number from the 753: Request for Routing Instructions. RRC: Ref. ID Qualifier for “Routing Request Control Number. LTL1: Transportation service level requirement for “CATCON”.


BLR JOES JOES: SCAC for assigned pickup carrier. OID 8901234C 8901234C: JCP Purchase Order Number. G62 69 20001003 69: Date Qualifier for “Scheduled Pick-




SUMMARY SE 90 987654321 90: Number of Included Segments.

987654321: Trans. Set Control Number.

J. C. Penney Co Proprietary and Confidential 33

754 ROUTING INSTRUCTIONS – BUSINESS RULES FOR TMS ROUTING AUTHORIZATION (TMS-LITE) The purpose of this document is to provide and explanation of JCPenney's use of some of the major sections of the 754 Routing Instructions document when used for TMS Routing Authorization. TMS Routing Authorization is an intermediate step towards required 'full' TMS compliance. While suppliers work to become compliant on the full TMS Dynamic Routing 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 full 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 TMS Routing Authorization guidelines under the Logistics section of the supplier web site. GENERAL REQUIREMENTS JCPenney will send a 754 [TMS - Routing Authorization] authorizing shipment for each specific Purchase Order/Delivery Instruction after orders are validated. A supplier is not authorized to ship without receipt of a 754. Purchase Orders/Delivery Instructions that are not authorized for shipment will be communicated to the supplier via email. HEADER LEVEL BEGINNING SEGMENT [BGN] The purpose of this segment is to identify the transaction set purpose [BGN01] of 'Original' [00], the reference identification [BGN02], date and time [BGN03 and BGN04] of the transaction and the type of transaction [BGN07]. The reference identification [BGN02] is the sender's (JCPenney) internal number used to identify the transaction set within the sender's application system. DETAIL LEVEL BUSINESS INSTRUCTIONS AND REFERENCE NUMBER [L11] This segment is used to identify the control number issued by the vendor on the Request for Routing: TMS Routing Authorization (753) document. L1101 will contain the reference identification number from the request. The reference identification qualifier [L1102] is RRC [Routing Request Control Number]. The second L11 segment (L1101) is used to provide the JCPenney Routing Authorization number. The code value in L1102 is PUA (Pick-Up Appointment Number). TRANSPORTATION CARRIER IDENTIFICATION [BLR] This segment is not required for TMS Routing Authorization. However, the usage of the BLR segment is required for the 'full' TMS program. ORDER INFORMATION DETAIL [OID] This segment is used to identify the JCPenney Purchase Order or Delivery Instruction authorized for shipment. Data field OID02 will contain the 8 or 9 digit Purchase Order/Delivery Instruction number.


DATE/TIME [G62] The purpose of this segment is to specify the 'Ready to Ship' date. The 'ready to ship' date is when the supplier will ship the JCPenney Purchase Order/Delivery Instruction as indicated on the 753 - Request for Routing document.


754 ROUTING INSTRUCTION

Business Example: TMS - Routing Authorization

Scenario: On 5/5/2003 the ACME SHIRT COMPANY [JCPenney assigned supplier number 123456] submitted a ‘Request for Authorization’ for 5 JCPenney locations to be shipped on 5/7/03. On 5/6/03 at 3:00 am, JCPenney responded to the request with a 754 Routing Authorization. The details are as follows:

Mark For Store

Routing Request # PO# Sub Pieces JCP Load ID

00166 1234569445820030505000001 12345678 524 700 RA0101200112345615313 1234569447420030505000002 23456789 524 900 RA0101200112345624588 1234569446620030505000003 45678901 524 1000 RA0101200112345610876 1234569442520030505000004 56789012 524 1200 RA0101200112345600813 1234569444120030505000005 67890123 524 800 RA01012001123456

TRANSACTION EXPLANATION HEADER

ST 754 012345677 754: Transaction Set ID. 012345677: Transaction Set Control number.

BGN 00 200305063579 20030506 0300RJ

00: Transaction Set Purpose [Original]. 200305063579: Reference Identification. 20030506:Date transaction was generated [05/06/03]. 0300: Local time transaction was generated [3am]. RJ: Transaction Type Code [Response to Request for Routing Authorization]

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. L11 1234569445820030505000001 RRC 1234569445820030505000001: Reference

Identification RRC: Routing Request Control Number.

L11 RA01012001123456 PUA RA01012001123456: Reference Identification. PUA: Pick Up Appointment Number.


OID 12345678 12345678: JCP Purchase order number. G62 69 20030507 69: Date Qualifier [Scheduled Pickup Date].

20030507: Date [05/07/2003] LOOP: LX LX 000002 000002: Assigned number. L11 1234569447420030505000002 RRC 1234569447420030505000002: Reference
















20030507: Date [05/07/2003] TRAILER

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

754 routing instructions - iconnect · 2008-01-29 · loop id - 0210loop id - 0210 2525 0700 qty...

Documents