X12 417 Rail Carrier Waybill Interchange
This X12 Transaction Set contains the format and establishes the data contents of the Rail Carrier Waybill Interchange Transaction Set (417) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the rail carrier with detailed movement instructions pertinent to a rail carrier shipment and is used by all Class I rail carriers in the United States and Canada.
- ~ 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
- 00703
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2014
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Interchange Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested (TA1)
- 2
- Interchange Acknowledgment Requested only when Interchange is "Rejected Because Of Errors"
- 3
- Interchange Acknowledgment Requested only when Interchange is "Rejected Because Of Errors" or "Accepted but Errors are Noted"
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
- WB
- Rail Carrier Waybill Interchange (417)
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
- 007030
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2015
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code 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).
- 417
- Rail Carrier Waybill Interchange
General Shipment Information
To transmit identification numbers and other basic shipment data
- BX05 contains the Standard Carrier Alpha Code (SCAC) of the original roadhaul carrier receiving the shipment.
Example: BX00RPP**CNL*B
Code identifying purpose of transaction set
- 00
- Original
Code specifying the method or type of transportation for the shipment
- R
- Rail
Code identifying payment terms for transportation charges
- CC
- Collect
- PP
- Prepaid (by Seller)
Code identifying the Standard Carrier Alpha Code
- CN
- CN Rail
Rail Shipment Information
To transmit rail-specific shipment data
Example: BNX*R**S
Bill of Lading Number
To transmit identifying information as specified by the Reference Identification Qualifier
Allows Reference Numbers to be sent to CN. At least one N9 containing a Bill of Lading number must be included. This number will be included on all other documents such as Freight Invoice and Remittance/Payment.
Example: N9BM1257*201807101336
Code identifying the Reference Identification
- BM
- Bill of Lading Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
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)
Purchase Order Number
To transmit identifying information as specified by the Reference Identification Qualifier
Allows Reference Numbers to be sent to CN. At least one N9 containing a Bill of Lading number must be included. This number will be included on all other documents such as Freight Invoice and Remittance/Payment.
Code identifying the Reference Identification
- PO
- Purchase Order Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
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)
Weight Agreement Number
To transmit identifying information as specified by the Reference Identification Qualifier
Allows Reference Numbers to be sent to CN. At least one N9 containing a Bill of Lading number must be included. This number will be included on all other documents such as Freight Invoice and Remittance/Payment.
Code identifying the Reference Identification
- WM
- Weight Agreement Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
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)
Equipment Details
To identify the equipment
Example: N7CN123456213360N*******RR
Prefix or alphabetic part of an equipment unit's identifying number
- N701 is mandatory for rail transactions.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Code specifying the type of weight
- E
- Estimated Net Weight
- N
- Actual Net Weight
Origin Station
To identify the rail origin of the shipment
Indicates the origin of the shipment, the point from which it is shipped. The spelling should be in accordance with that listed in the Standard Point Location Code (SPLC) standard available from the National Motor Freight Tariff Association (USA) or the National Transportation Agency (Canada). CN can provide spellings for your stations.
Example: F9*WATSONSK
Destination Station
To identify the rail destination of the shipment
Indicates the destination of the shipment, the point at which it will be unloaded or where the transportation responsibility reverts to the consignee. The spelling should be in accordance with that listed in the
Standard Point Location Code (SPLC) standard available from the National Motor Freight Tariff Association (USA) or the National Transportation Agency (Canada). CN can provide spellings for your stations.
Example: D9*VANCOUVERBC
Associated to the N3 and N4 segments below. N1, N3 and N4 segments are repeated for the Consignee and any other Additional Parties to the shipment.
Example:
N1SHGENERIC CARLOAD INC
N3123 ROAD
N4WATSONSKS0K 4V0
N1CNGENERIC CONSIGNEE CO
N312 SMITH STREET
N4VANCOUVERBCV5K 1P7
N1PFGENERIC CARLOAD INC
N3123 ROAD
N4WATSONSKS0K 4V0
Party Identification
To identify a party by type of organization, name, and code
Party Location
To specify the location of the named 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 specifying the Standard State/Province as defined by appropriate government agency
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
- N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Example: PERICCONTACT NAMETE123-123-1234
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
Route Information
To specify carrier and routing sequences and details
One R2 segment for each railroad in the route. CN can provide route information for your shipments (ie: Railroad SCAC's and junctions).
Example: R2CNS****R
Code identifying the Standard Carrier Alpha Code
- CN
- CN Rail
Code specifying the relationship of a carrier to a specific shipment movement
- S
- Origin Carrier, Shipper's Routing (Rail)
Transaction Set Line Number
To reference a line number in a transaction set
Example: LX*1
Description, Marks and Numbers
To specify the line item in terms of description, quantity, packaging, and marks and numbers
CN can provide Standard Transportation Commodity Codes (STCC) for your commodities. The commodity code is required only on the first L5 segment. Additional L5 segments can be used to provide additional description of lading.
Example: L51WALLBOARD3275440T
Sequential line number for a lading item
Description of an item as required for rating and billing purposes
- L502 may be used to send quantity information as part of the product description.
Code describing a commodity or group of commodities
7 digit Standard Transportation Commodity Code (STCC).
Example: WALLBOARD = 3275440
Line Item - Quantity and Weight
To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data
Example: L01213360N1*CLD
Sequential line number for a lading item
Code specifying the type of weight
- E
- Estimated Net Weight
- N
- Actual Net Weight
Number of units (pieces) of the lading commodity
- L008 is the number of handling units of the line item tendered to the carrier.
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
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
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample
GS*WB*SENDERGS*RECEIVERGS*20231101*014318*000000001*X*007030
ST*417*988260001
BX*00*R*PP**CN*L*B
BNX*R**S
N9*BM*1257**20180710*1336
N7*CN*123456*213360*N*******RR
F9**WATSON*SK
D9**VANCOUVER*BC
N1*SH*GENERIC CARLOAD INC
N3*123 ROAD
N4*WATSON*SK*S0K 4V0
PER*IC*CONTACT NAME*TE*123-123-1234
N1*CN*GENERIC CONSIGNEE CO
N3*12 SMITH STREET
N4*VANCOUVER*BC*V5K 1P7
N1*PF*GENERIC CARLOAD INC
N3*123 ROAD
N4*WATSON*SK*S0K 4V0
R2*CN*S****R
LX*1
L5*1*WALLBOARD*3275440*T
L0*1***213360*N***1*CLD
SE*27*988260001
GE*1*000000001
IEA*1*000000001
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.