753 Specs06272013
753 Specs06272013
Instructions
VICS EDI/V4030/753: 753 Request for Routing Instructions
Table of Contents
753 Request for Routing Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . . 1
ISA Interchange Control Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . . 2
GS Functional Group Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . . 5
ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . . 7
BGN Beginning Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . . 8
PER Administrative Communications Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . . 9
N1 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 11
N3 Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 12
N4 Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 13
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 Notes
0100 ST Transaction Set Header M 1
0200 BGN Beginning Segment M 1
0300 PER Administrative Communications Contact O 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 Notes
0100 LX Assigned Number M 1
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
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
Pos: Max: 1
ISA Interchange Control Header Not Defined - Mandatory
Loop: N/A Elements: 16
Purpose: 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/Max
ISA01 I01 Authorization Information Qualifier M ID 2/2
Code Name
0 No Acknowledgment Requested
Pos: Max: 1
GS Functional Group Header Not Defined - Mandatory
Loop: N/A Elements: 8
Purpose: To indicate the beginning of a functional group and to provide control information
Element Summary:
Ref Id Element Name Req Type Min/Max
GS01 479 Functional Identifier Code M ID 2/2
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.
Purpose: To indicate the start of a transaction set and to assign a control number
Element Summary:
Ref Id Element Name Req Type Min/Max
ST01 143 Transaction Set Identifier Code M ID 3/3
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).
Element Summary:
Ref Id Element Name Req Type Min/Max
BGN01 353 Transaction Set Purpose Code M ID 2/2
Semantics:
1. BGN02 is the transaction set reference number.
2. BGN03 is the transaction set date.
3. BGN04 is the transaction set time.
Element Summary:
Ref Id Element Name Req Type Min/Max
PER01 366 Contact Function Code M ID 2/2
Code Name
FX Facsimile
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.
Element Summary:
Ref Id Element Name Req Type Min/Max
N101 98 Entity Identifier Code M ID 2/3
Syntax Rules:
1. P0304 - If either N103 or N104 is present, then the other is required.
Element Summary:
Ref Id Element Name Req Type Min/Max
N301 166 Address Information M AN 1/55
Element Summary:
Ref Id Element Name Req Type Min/Max
N401 19 City Name O AN 2/30
Comments:
1. N402 is required only if city name (N401) is in the U.S. or Canada.
Element Summary:
Ref Id Element Name Req Type Min/Max
LX01 554 Assigned Number M N0 1/6
User Note 1:
At least one occurrence of the N1 segment must be used to identify the ship-to location by using code ST in
N101.
Element Summary:
Ref Id Element Name Req Type Min/Max
N101 98 Entity Identifier Code M ID 2/3
Syntax Rules:
1. P0304 - If either N103 or N104 is present, then the other is required.
User Note 1:
This segment is MANDATORY by JCPenney business requirements.
User Note 2:
A unique routing request control number must be assigned for each ship-to location. This control number
provides the means to assign a different routing to each ship-to location and must be conveyed in the Response
to a Routing Request.
User Note 3:
At least one occurrence of the L11 segment is required to specify the routing request control number by using
code RRC in L1102.
Element Summary:
Ref Id Element Name Req Type Min/Max
L1101 127 Reference Identification X AN 1/50
Element Summary:
Ref Id Element Name Req Type Min/Max
G6201 432 Date Qualifier X ID 2/2
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.
User Note 1:
This loop is used to specify the quantities ready to ship for each purchase order.
Element Summary:
Ref Id Element Name Req Type Min/Max
OID01 127 Reference Identification X AN 1/50
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:
Only used for hazardous materials.
Element Summary:
Ref Id Element Name Req Type Min/Max
CMC01 22 Commodity Code O AN 1/30
Semantics:
1. CMC01 is the National Motor Freight Classification Commodity Code.
Purpose: 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/Max
SE01 96 Number of Included Segments M N0 1/10
Comments:
1. SE is the last segment of each transaction set.
Pos: Max: 1
GE Functional Group Trailer Not Defined - Mandatory
Loop: N/A Elements: 2
Purpose: To indicate the end of a functional group and to provide control information
Element Summary:
Ref Id Element Name Req Type Min/Max
GE01 97 Number of Transaction Sets Included M N0 1/6
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 the
corresponding header.
Pos: Max: 1
IEA Interchange Control Trailer Not Defined - Mandatory
Loop: N/A Elements: 2
Purpose: 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/Max
IEA01 I16 Number of Included Functional Groups M N0 1/5
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 Transportation Management System (TMS) Dynamic Routing and Routing
Authorization (TMS Lite). For a complete explanation, refer to the Business Rules and Glossary under the
Transportation Management System section of the Supplier website.
GENERAL REQUIREMENTS
TMS DYNAMIC ROUTING:
The TMS Dynamic Routing program provides benefits of real-time network optimization, including destination and
mode selection. This transaction is integral to the TMS – Dynamic Routing Initiative program.
ROUTING AUTHORIZATION:
TMS Routing Authorization (TMS Lite) is an exception to the Dynamic Routing process that requires approval from
the JCPenney Supply Chain Manager or JCPenney Load Management on a case by case basis. TMS Routing
Authorization (TMS Lite) will validate the PO/DI (Purchase Order/Delivery Instruction) included in the request, but will
not provide routing information. Routing must be done manually and the approver will provide to the supplier
information on how to route the shipment. A supplier is not authorized to ship without receipt of a 754 for each
specific Purchase Order/Delivery Instruction.
***Note: The reference to Purchase Order (PO) in the above statement is not the POM PO (contract order). The POM
PO number is not included in the 753 Request for Routing document.
HEADER LEVEL
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.
DETAIL LEVEL
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 from the 850 N1 Z7 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/12 would have an RRC number of
"0123450016620120625000001". The 6-digit sequential portion of the RRC would be incremented by 1 for each
subsequent RRC.
Note: The purchase order number used in the OID02 is found in the EDI 850 where BEG02 is ‘SA’ or ‘RE’ and
BEG03 is the 8 digit purchase order/delivery instruction number.