X12 204 Motor Carrier Load Tender
This Draft Standard for Trial Use contains the format and establishes the data contents of the Motor Carrier Load Tender Transaction Set (204) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow shippers or other interested parties to offer (tender) a shipment to a full load (truckload) motor carrier including detailed scheduling, equipment requirements, commodities, and shipping instructions pertinent to a load tender. It is not to be used to provide a motor carrier with data relative to a Less-than-Truckload bill of lading, pick-up notification, or manifest.
- ~ Segment
- * Element
- > Component
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify 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 to identify 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)
Qualifier to designate 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
Qualifier to designate 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
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
Code to indicate 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
- SM
- Motor Carrier Load Tender (204)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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 used in conjunction with Data Element 480 to identify the issuer of the standard
- 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
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
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) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 204
- Motor Carrier Load Tender
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Shipment Information Transaction
To transmit basic data relating to shipment information
Standard Carrier Alpha Code
- B202 contains the Standard Carrier Alpha Code (SCAC) of the carrier that will receive the bill of lading.
- B202 is mandatory for transaction set 204.
This field must match the B10-03 field of the 214.
Identification number assigned to the shipment by the shipper that uniquely identifies the shipment from origin to ultimate destination and is not subject to modification; (Does not contain blanks or special characters)
This field will contain the Master BOL. This field must match the B10-02 field of the 214.
Code identifying payment terms for transportation charges
- CC
- Collect
- PP
- Prepaid (by Seller)
Code defining relationship of this shipment with respect to other shipments given to the carrier at the same time
This field will contain an “I” if the shipment is intermodal. It will not be included if it is not.
Set Purpose
To allow for positive identification of transaction set purpose
Code identifying purpose of transaction set
- 00
- Original
- 01
- Cancellation
- 04
- Change
Code identifying an application
- LT
- Load Tender - Truckload (TL) Carrier Only
- PC
- Partial Load Tender, Carrier Consolidate
Business Instructions and 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
Usage: Load ID will appear in this field. This field must match the L1101 field of the 214.
Code qualifying the Reference Identification
Date/Time
To specify pertinent dates and times
- Segment G62 in header is used to convey the must-respond-by date and time when responding to a 204 transaction.
IMPORTANT: The date and time that will be sent in this segment will always be in MT. Coors needs the 990 response back to us by this time. We expect you to respond within two hours of when we send the 204. Please remember that VAN interconnects can slow your response to us. Therefore, please allow time for this.
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)
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
- MT
- Mountain Time
Length (in feet and inches) of equipment ordered or used to transport shipment (The format is FFFII where FFF is feet and II is inches; the range for II is 00 through 11)
Additional Equipment Details
To identify additional equipment details
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- N7B06 is the Department of Transportation or the Interstate Commerce Commission Motor Carrier Cargo Tank Specification.
- N7B06 may include but are not limited to MC300 through MC307, MC310 through MC312, MC330, MC331, MC338, DOT 406, DOT 407, and DOT 412.
This field should be passed on in the 210. This will contain a character equipment type up to ten characters in length.
Detail
Stop Off Details
To specify stop-off detail reference numbers and stop reason
Identifying number for the specific stop and the sequence in which the stop is to be performed
Usage: This field must match the LX-01 field of the 214.
Code specifying the reason for the stop
- CL
- Complete
- CU
- Complete Unload
- PL
- Part Load
- PU
- Part Unload
Date/Time
To specify pertinent dates and times
- Use G62 segment either in loop 0300 or loop 0350, but not both.
Code specifying type of date
- 37
- Ship Not Before Date
- 38
- Ship Not Later Than Date
- 53
- Deliver Not Before Date
- 54
- Deliver No Later Than Date
Code specifying the reported time
- G
- Earliest Requested Deliver Time
- I
- Earliest Requested Pick Up Time
- K
- Latest Requested Pick Up Time
- L
- Latest Requested Delivery Time
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)
Name
To identify a party by type of organization, name, and code
This segment needs to be returned on the 214. The N1 segment that indicates the ship from location should be returned on the 214 in the 0100 loop. This is in the header of the 214. The N1 segment that indicates the ship to location should be returned on the 214 in the 0231 loop. This is in the detail of the 214.
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 93
- Code assigned by the organization originating the transaction set
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
If the N1-03 contains a 93 and is therefore Coors’ location number in the N1-04, the N3 and N4 are not required on the 214.
Geographic Location
To specify the geographic place of the named party
If the N1-03 contains a 93 and is therefore Coors’ location number in the N1-04, the N3 and N4 are not required on the 214.
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)
Contact
To identify a person or office to whom communications should be directed
Code identifying the major duty or responsibility of the person or group named
- DC
- Delivery Contact
- SH
- Shipper Contact
Code identifying the type of communication number
- G6103 qualifies G6104.
- FX
- Facsimile
- TE
- Telephone
Complete communications number including country or area code when applicable
Summary
Total Weight and Charges
To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items
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.