X12 753 Request for Routing Instructions
This Draft Standard for Trial Use contains the format and establishes the data contents of the Request for Routing Instructions 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 merchandise that is ready to be shipped.
- Segment
- * Element
- > Component
- ^ Repetition
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code identifying the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00403
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code indicating whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- RF
- Request for Routing Instructions (753)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission; codes agreed to by trading partners
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the 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 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004030
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- 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).
- 753
- Request for Routing Instructions
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Code identifying purpose of transaction set
- 00
- Original
- 01
- Cancellation
- 04
- Change
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BGN02 is the transaction set reference number.
Shipment Reference Number assigned by Shipper
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BGN03 is the transaction set date.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BGN06 is the transaction set reference number of a previously sent transaction affected by the current transaction.
This is the Load ID that was assigned to the order during the load optimization process.
If you are sending updates or you are wanting to cancel a previous Request for Routing prior to receiving a 754 (Routing Instructions) transaction, then this number is not required.
If you are sending updates or you are wanting to cancel a previous Request for Routing after receiving a 754 (Routing Instructions) transaction, then this number is required.
******** This number is sent in BGN02 of the 754 transaction *****
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- IC
- Information Contact
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Name
To identify a party by type of organization, name, and code
- One iteration of the N1 segment must be used to identify the ship-from location.
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
- 1
- D-U-N-S Number, Dun & Bradstreet
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Detail
Number assigned for differentiation within a transaction set
Name
To identify a party by type of organization, name, and code
- One iteration of the N1 segment must be used to identify the ship-to location.
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
This must be the same number that was sent in the N104 in the Ship To N1 loop on the 850.
For Drop Ship to Consumer 753’s, please include the location number of 899 in the N104 ST segment. This location number will NOT be in the N104 in the ST N1 loop on the 850.
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
Used to communicate Notes about this shipment to the carrier. Information such as Equipment requirement or to comment on types of materials being moved.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Used to communicate the carrier assigned to the shipment
Code qualifying the Reference Identification
- L1
- Letters or Notes
- SCA
- Standard Carrier Alpha Code (SCAC)
A free-form description to clarify the related data elements and their content
L1 qualifier in the L102 to be used for Customer Phone Number
Date/Time
To specify pertinent dates and times
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Date/Time
To specify pertinent dates and times
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Unitized Shipment Information
To specify the quantity, number of pallet spaces and stackability of unitized units
Code for packaging form of the lading quantity
- USI02 defines the quantity in USI01.
- PLT
- Pallet
Code indicating a Yes or No condition or response
- USI03 identifies whether the unitized handling units are stackable. A "Y" indicates the unitized handling units are stackable; an "N" indicates the unitized handling units are not stackable.
- N
- No
- Y
- Yes
Order Identification Detail
To specify order identification detail
- The 0210 loop is used to specify the quantities ready to ship for each purchase order.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- OID01 is the seller's order identification number.
This must be the Cabela Assigned Vendor number to your company. This was sent in REF02 with REF01 = IA on the 850. A Cabela Assigned Vendor Number is between 2-7 digits long.
Identifying number for Purchase Order assigned by the orderer/purchaser
Must be the same PO number from BEG03 on the 850
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- OID03 is the number assigned by the consignee to further define the purchase order number.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- OID11 specifies the sorting and/or segregating number for each receiving location (processing area).
If the 850 was a Direct To Consumer (BEG02 = DS), this number was sent in REF02 where REF01 = CO. This must be that number.
Commodity Classification
To specify freight commodity code and freight classification
If the National Motor Freight Classification (NMFC) and/or class are unknown, the vendor should contact their shipping department to get the information. If the shipping department does not know, the vendor should contact a qualified carrier to help classify the freight correctly. If that process is unsuccessful please contact Domesticship@cabelas.com for further assistance.
Code describing a commodity or group of commodities
- CMC01 is the National Motor Freight Classification Commodity Code.
Code indicating generalized classification that applies to one or more items in the shipment, i.e., class 70, 77.5, etc.
- CMC02 is the Freight Class Code published in the National Motor Freight Classification.
Commonly used Freight Class Codes for Cabela’s are –
50
55
60
65
70
77
77.5
85
92
92.5
100
110
125
150
175
200
250
300
400
500
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample from Cabelas 1
BGN*00*00004*20050606
N1*SF*Supplier name*1*111111111
N3*333 7TH AVE SO.
N4*MINNEAPOLIS*MN*55108*USA
LX*1
N1*ST*CABELA'S, INC*92*8095790000134
N3*501 CLIFF HAVEN ROAD
N4*PRARIE DU CHIEN*WI*53821*USA
G62*EP*20050501*EP*0850
G62*LP*20050502*LP*1650
USI*1*PLT*Y
OID*2777*921607**CTN*50*L*500*E*50
CMC*DFT*100
SE*16*00010001
Sample from Cabelas 2
BGN*04*00004*20050606
N1*SF*Supplier name*1*111111111
N3*333 7TH AVE SO.
N4*MINNEAPOLIS*MN*55108*USA
LX*1
N1*ST*CABELA'S, INC*92*8095790000134
N3*501 CLIFF HAVEN ROAD
N4*PRARIE DU CHIEN*WI*53821*USA
G62*EP*20050501*EP*0850
G62*LP*20050502*LP*1650
USI*1*PLT*Y
OID*2777*921607**CTN*50*L*500*E*50
CMC*DFT*100
SE*16*00010001
Sample from Cabelas 3
BGN*04*00004*20050606***00000001
N1*SF*Supplier name*1*111111111
N3*333 7TH AVE SO.
N4*MINNEAPOLIS*MN*55108*USA
LX*1
N1*ST*CABELA'S, INC*92*8095790000134
N3*501 CLIFF HAVEN ROAD
N4*PRARIE DU CHIEN*WI*53821*USA
G62*EP*20050501*EP*0850
G62*LP*20050502*LP*1650
USI*1*PLT*Y
OID*2777*921607**CTN*50*L*500*E*50
CMC*DFT*100
SE*15*00010001
Sample from Cabelas 4
BGN*01*00004*20050606
N1*SF*Supplier name*1*111111111
N3*333 7TH AVE SO.
N4*MINNEAPOLIS*MN*55108*USA
LX*1
N1*ST*CABELA'S, INC*92*8095790000134
N3*501 CLIFF HAVEN ROAD
N4*PRARIE DU CHIEN*WI*53821*USA
G62*EP*20050501*EP*0850
G62*LP*20050502*LP*1650
USI*1*PLT*Y
OID*2777*921607**CTN*50*L*500*E*50
CMC*DFT*100
SE*15*00010001
Sample from Cabelas 5
BGN*01*00004*20050606***00000001
N1*SF*Supplier name*1*111111111
N3*333 7TH AVE SO.
N4*MINNEAPOLIS*MN*55108*USA
LX*1
N1*ST*CABELA'S, INC*92*8095790000134
N3*501 CLIFF HAVEN ROAD
N4*PRARIE DU CHIEN*WI*53821*USA
G62*EP*20050501*EP*0850
G62*LP*20050502*LP*1650
USI*1*PLT*Y
OID*2777*921607**CTN*50*L*500*E*50
CMC*DFT*100
SE*15*00010001
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.