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
- 1
- Interchange 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
- 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
- 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
Beginning Segment for Shipment Information Transaction
To transmit basic data relating to shipment information
This segment is used to identify the carrier and the shipment ID assigned by the 3PL to the shipment. The shipment ID should be a unique identifier produced by the sender to identify the shipment. This number will also be used in any subsequent 214's to identify the shipment. (This is not the shipment ID on the ASN.)
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.
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)
Set Purpose
To allow for positive identification of transaction set purpose
Non AU/NZ partners: If a shipment is changed after the original 204 (code 00) is sent, a cancelling 204 (code 01) should be sent, then a new original 204 (code 00) can be sent.
AU/NZ partners: if a shipment is changed after the original 204 (code 00) is sent, a replacement 204 (code 05) should be sent rather than following the process above.
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
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.
This segment should contain the date the carrier accepted the load. The Time Code should represent local time of the carrier accepting the load.
Code specifying the reported time
- 4
- Pickup Requested Scheduled Time
- 5
- Delivery Requested Scheduled 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)
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
Interline Information
To identify the interline carrier and relevant data
Standard Carrier Alpha Code
- MS301 is the Standard Carrier Alpha Code (SCAC) of the interline carrier.
Code describing the relationship of a carrier to a specific shipment movement
- B
- Origin/Delivery Carrier (Any Mode)
Name
To identify a party by type of organization, name, and code
- Loop 0100 is used to convey name and address detail relative to bill-to, party controlling freight, or other shipment level name and address information. It is not used to convey ship from or ship to detail which should be handled within loop 0300 in table 2.
This segment should identify the 3PL administering the shipment.
Contact
To identify a person or office to whom communications should be directed
This segment should identify a contact at the 3PL to handle inquiries about this shipment
Code identifying the major duty or responsibility of the person or group named
- CN
- General Contact
Code identifying the type of communication number
- G6103 qualifies G6104.
- EM
- Electronic Mail
- TE
- Telephone
Equipment Details
To identify the equipment
This is an optional segment used to identify the trailer number and weight, if known.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Code defining the type of weight
- G
- Gross Weight
- N
- Actual Net Weight
Seal Numbers
To record seal numbers used and the organization that applied the seals
Detail
Stop Off Details
To specify stop-off detail reference numbers and stop reason
This segment identifies the sequence of stops for this shipment. It identifies the weight and quantity for the stop.
Identifying number for the specific stop and the sequence in which the stop is to be performed
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
If used the L11 'PU' segment should identify the Bill of Lading used for the orders on this stop on a previous shipment.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Requested Ship Date/Pick-up Date
To specify pertinent dates and times
- Use G62 segment either in loop 0300 or loop 0350, but not both.
This segment identifies the requested timeframe for the stop. A '10' or '68' identifies the requested pickup or delivery time. A '38' or '54' identifies the latest pickup or delivery time. These times should be in the local time relative to the address of the stop
Code specifying type of date
- 10
- Requested Ship Date/Pick-up Date
Code specifying the reported time
- 4
- Pickup Requested Scheduled 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)
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
Ship Not Later Than Date
To specify pertinent dates and times
- Use G62 segment either in loop 0300 or loop 0350, but not both.
This segment identifies the requested timeframe for the stop. A '10' or '68' identifies the requested pickup or delivery time. A '38' or '54' identifies the latest pickup or delivery time. These times should be in the local time relative to the address of the stop
Code specifying type of date
- 38
- Ship Not Later Than Date
Code specifying the reported time
- 4
- Pickup Requested Scheduled 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)
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
Name
To identify a party by type of organization, name, and code
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
- ZZ
- Mutually Defined
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.
"Transportation System Entity ID
This code will be required on inbound EDI 214 files"
Address Information
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 (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
This optional segment is used to identify a contact at the stop location
Code identifying the major duty or responsibility of the person or group named
- CN
- General Contact
Code identifying the type of communication number
- G6103 qualifies G6104.
- EM
- Electronic Mail
- TE
- Telephone
Description, Marks and Numbers
To specify the line item in terms of description, quantity, packaging, and marks and numbers
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
Code identifying the commodity coding system used for Commodity Code
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
Marks and numbers used to identify a shipment or parts of a shipment
Code specifying the application or source of Marks and Numbers (87)
Shipment Weight, Packaging and Quantity Data
To specify shipment details in terms of weight, and quantity of handling units
Number of units (pieces) of the lading commodity
- AT804 is the quantity of handling units that are not unitized (for example a carton). When added to the quantity in AT805, it is the total quantity of handling units in the shipment.
Number of units (pieces) of the lading commodity
- AT805 is the quantity of handling units that are unitized (for example on a pallet or slip sheet). When added to the quantity in AT804 it is the total quantity of handling units for the shipment.
Order Identification Detail
To specify order identification detail
- Use loop 0350 for conveying seller's order/invoice level detail or buyer's purchase order level detail. If not using order level detail, this loop should not be used.
This segment contains the key Deere reference number to all Deere to associate the shipment ID from the 3PL with the reference number used by Deere to identify the load.
Examples include: COMAR order number, PDC Parcel ID, and a 3PL confirmation number that is sent on an ASN.
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.
Lading Detail
To transmit detailed lading data pertinent to a pickup or delivery
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Description, Marks and Numbers
To specify the line item in terms of description, quantity, packaging, and marks and numbers
- If sending order level detail within the 0350 loop, then use L5 and AT8 segments in loop 0360 to relay commodity detail. Otherwise, use L5 and AT8 segments within the 0320 loop to relay commodity detail. Use either loop 0320 or loop 0360, but not both.
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
Code identifying the commodity coding system used for Commodity Code
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
Marks and numbers used to identify a shipment or parts of a shipment
Code specifying the application or source of Marks and Numbers (87)
Shipment Weight, Packaging and Quantity Data
To specify shipment details in terms of weight, and quantity of handling units
- Accumulated weights, quantities, and volumes sent in the AT8 segment in loop 0360 should total to the weight, quantity, and volume in the OID segment in loop 0350. Accumulated weights and quantities in the LAD segment in loop 0350 should total to the weight and quantity in the OID segment in loop 0350.
Number of units (pieces) of the lading commodity
- AT804 is the quantity of handling units that are not unitized (for example a carton). When added to the quantity in AT805, it is the total quantity of handling units in the shipment.
Number of units (pieces) of the lading commodity
- AT805 is the quantity of handling units that are unitized (for example on a pallet or slip sheet). When added to the quantity in AT804 it is the total quantity of handling units for the shipment.
Stop Off Details
To specify stop-off detail reference numbers and stop reason
This segment identifies the sequence of stops for this shipment. It identifies the weight and quantity for the stop.
Identifying number for the specific stop and the sequence in which the stop is to be performed
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
If used the L11 'PU' segment should identify the Bill of Lading used for the orders on this stop on a previous shipment.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Deliver No Later Than Date
To specify pertinent dates and times
- Use G62 segment either in loop 0300 or loop 0350, but not both.
This segment identifies the requested timeframe for the stop. A '10' or '68' identifies the requested pickup or delivery time. A '38' or '54' identifies the latest pickup or delivery time. These times should be in the local time relative to the address of the stop
Code specifying type of date
- 54
- Deliver No Later Than Date
Code specifying the reported time
- 5
- Delivery Requested Scheduled 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)
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
Requested Delivery Date
To specify pertinent dates and times
- Use G62 segment either in loop 0300 or loop 0350, but not both.
This segment identifies the requested timeframe for the stop. A '10' or '68' identifies the requested pickup or delivery time. A '38' or '54' identifies the latest pickup or delivery time. These times should be in the local time relative to the address of the stop
Code specifying type of date
- 68
- Requested Delivery Date
Code specifying the reported time
- 5
- Delivery Requested Scheduled 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)
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
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)
- 1
- D-U-N-S Number, Dun & Bradstreet
- ZZ
- Mutually Defined
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.
"Transportation System Entity ID
This code will be required on inbound EDI 214 files"
Address Information
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 (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
This optional segment is used to identify a contact at the stop location
Code identifying the major duty or responsibility of the person or group named
- CN
- General Contact
Code identifying the type of communication number
- G6103 qualifies G6104.
- EM
- Electronic Mail
- TE
- Telephone
Description, Marks and Numbers
To specify the line item in terms of description, quantity, packaging, and marks and numbers
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
Code identifying the commodity coding system used for Commodity Code
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
Marks and numbers used to identify a shipment or parts of a shipment
Code specifying the application or source of Marks and Numbers (87)
Shipment Weight, Packaging and Quantity Data
To specify shipment details in terms of weight, and quantity of handling units
Number of units (pieces) of the lading commodity
- AT804 is the quantity of handling units that are not unitized (for example a carton). When added to the quantity in AT805, it is the total quantity of handling units in the shipment.
Number of units (pieces) of the lading commodity
- AT805 is the quantity of handling units that are unitized (for example on a pallet or slip sheet). When added to the quantity in AT804 it is the total quantity of handling units for the shipment.
Order Identification Detail
To specify order identification detail
- Use loop 0350 for conveying seller's order/invoice level detail or buyer's purchase order level detail. If not using order level detail, this loop should not be used.
This segment contains the key Deere reference number to all Deere to associate the shipment ID from the 3PL with the reference number used by Deere to identify the load.
Examples include: COMAR order number, PDC Parcel ID, and a 3PL confirmation number that is sent on an ASN.
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.
Lading Detail
To transmit detailed lading data pertinent to a pickup or delivery
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Description, Marks and Numbers
To specify the line item in terms of description, quantity, packaging, and marks and numbers
- If sending order level detail within the 0350 loop, then use L5 and AT8 segments in loop 0360 to relay commodity detail. Otherwise, use L5 and AT8 segments within the 0320 loop to relay commodity detail. Use either loop 0320 or loop 0360, but not both.
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
Code identifying the commodity coding system used for Commodity Code
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
Marks and numbers used to identify a shipment or parts of a shipment
Code specifying the application or source of Marks and Numbers (87)
Shipment Weight, Packaging and Quantity Data
To specify shipment details in terms of weight, and quantity of handling units
- Accumulated weights, quantities, and volumes sent in the AT8 segment in loop 0360 should total to the weight, quantity, and volume in the OID segment in loop 0350. Accumulated weights and quantities in the LAD segment in loop 0350 should total to the weight and quantity in the OID segment in loop 0350.
Number of units (pieces) of the lading commodity
- AT804 is the quantity of handling units that are not unitized (for example a carton). When added to the quantity in AT805, it is the total quantity of handling units in the shipment.
Number of units (pieces) of the lading commodity
- AT805 is the quantity of handling units that are unitized (for example on a pallet or slip sheet). When added to the quantity in AT804 it is the total quantity of handling units for the shipment.
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
This segment identifies the total weight and quantity for the shipment
Code defining the type of weight
- G
- Gross Weight
- N
- Actual Net Weight
Code qualifying how to extend charges or interpret value
For a line item: freight or special charge; for the total invoice: the total charges -- expressed in the standard monetary denomination for the currency specified
- L305 is the total charges.
Code identifying type of special charge or allowance
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
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.