X12 754 Routing Instructions
This Draft Standard for Trial Use contains the format and establishes the data contents of the Routing Instructions Transaction Set (754) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to communicate routing instructions to a supplier for a specific shipment. It can be used also to respond to a Request for Routing Instructions Transaction Set (753).
- ~ Segment
- * Element
- > Component
- ^ Repetition
- None included
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
- RG
- Routing Instructions (754)
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).
- 754
- Routing Instructions
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment
To indicate the beginning of a transaction set
Code identifying purpose of transaction set
- 00
- Original
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BGN02 is the transaction set reference number.
Cabela Load ID
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BGN03 is the transaction set date.
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.
N1 CA Loop will always be sent. This represents the Carrier that will be picking up the shipment
N1 SF Loop (includes N3 and N4 segment) will be optional.
N1 ST loop will contain N103 and N104. Be aware that the Ship To may be the Cabela's Store or DC as you indicated in the 753 or may be a Consolidation Center with the final destination still remaining as the Store or DC. If the Consolidation Center address 900 is sent, this information needs to be on the Bill of Lading.
Code identifying an organizational entity, a physical location, property or an individual
- CA
- Carrier
- SF
- Ship From
- 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.
Address Information
To specify the location of the named party
Only used with N1 SF and ST Loop
Geographic Location
To specify the geographic place of the named party
Only used with N1 SF and ST Loop
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
Assigned Number
To reference a line number in a transaction set
Number assigned for differentiation within a transaction set
Business Instructions and Reference Number Carrier Reference Number
To specify instructions in this business relationship or a reference number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- CN
- Carrier's Reference Number (PRO/Invoice)
A free-form description to clarify the related data elements and their content
Service Level
Business Instructions and Reference Number Bill Of Lading
To specify instructions in this business relationship or a reference number
This number will be the value sent in the 753 in BGN02 so may not be the Bill Of Lading number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
Transportation Carrier Identification
To transmit the identifying SCAC code and effective date and time for the data in the transaction set
Order Identification Detail
To specify order identification detail
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.
Cabela Assigned Vendor Number to Supplier
Identifying number for Purchase Order assigned by the orderer/purchaser
Cabela's PO Number
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.
Code for packaging form of the lading quantity
- CTN
- Carton
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).
Customer Order number for Cabela Direct to Consumer orders
Date/Time
To specify pertinent dates and times
Multi-stop Shipment Information
To specify multi-stop shipment information
Code indicating a Yes or No condition or response
- 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.
- When MSI01 contains code Y, MSI02 will contain the stop sequence number.
- W
- Not Applicable
Identifying number for the specific stop and the sequence in which the stop is to be performed
Name
To identify a party by type of organization, name, and code
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.
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
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.