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
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
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)
Tender ID - AVRT PRO #
Set Purpose
To allow for positive identification of transaction set purpose
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.
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.
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.
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
- IC
- Information Contact
Code identifying the type of communication number
- G6103 qualifies G6104.
- TE
- Telephone
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.
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
- IC
- Information Contact
Code identifying the type of communication number
- G6103 qualifies G6104.
- TE
- Telephone
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.
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.
Detail
Stop Off Details
To specify stop-off detail reference numbers and stop reason
Date/Time 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.
Date/Time Ship Not Before Date
To specify pertinent dates and times
- Use G62 segment either in loop 0300 or loop 0350, but not both.
Bill of Lading Handling Requirements
To identify Bill of Lading handling and service requirements
Code specifying special transportation handling instructions
- NC
- Notify Consignee Before Delivery
Code identifying the special service
- CD
- COD Request
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
Shipment Weight, Packaging and Quantity Data
To specify shipment details in terms of weight, and quantity of handling units
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
Code defining the type of weight
- G
- Gross Weight
- N
- Actual Net Weight
Number of units (pieces) of the lading commodity
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 1
GS*SM*SENDERGS*RECEIVERGS*20240723*191907*000000001*X*004010~
ST*204*000000001~
B2**SCAC**1234567890**PP~
B2A*00*BL~
L11*1234567890*CN~
L11*82214875*BM~
G62*86*20170630~
N1*SH*BETTERAIR~
N3*620·KOOLAIR·DR*SALES Dept~
N4*PADUCAH*KY*42003~
N1*CN*JASON·DOE~
N3*1625·GROUNDHOG·RD~
N4*ATHENS*GA*30601~
G61*IC*JASON·DOE*TE*123-456-7899~
N1*SF*AVRT~
S5*1*CL~
G62*10*20170706~
L5*1*AIR·CONDITIONERS,·AIR·COOLERS·OR~
AT8*N*L*310*2~
L5*2*LIFTGATE·DELIVERY~
L5*3*RESIDENTIAL·DLVY~
L5*4*FUEL·SURCHARGE~
L3*310*G*********2*L~
SE*23*000000001~
GE*1*000000001~
IEA*1*000000001~
Sample 2
GS*SM*SENDERGS*RECEIVERGS*20240723*192418*000000001*X*004010~
ST*204*000000001~
B2**SCAC**0171234567**PP~
B2A*00*BL~
L11*SHP2501495*PO~
L11*0171234567*CN~
G62*86*20170705~
N1*SH*SIGNATURE·HARDWARE~
N3*5·FRED HILL·DR~
N4*ERLANGER*KY*41018~
N1*CN*JANE DOE~
N3*3258·BROWNIE·WAY~
N4*DULUTH*GA*30097~
G61*IC*JANE DOE*TE*404-123-8484~
N1*SF*AVRT~
S5*1*CL~
G62*10*20170706~
AT5*NC*CD*2500~
L5*1*TUB~
AT8*N*L*438*1~
L5*2*RESIDENTIAL·DLVY~
L5*3*FUEL·SURCHARGE~
L5*4*·COMPANY·CHECK·ACCEPTABLE~
L5*5*LIFTGATE·DELIVERY~
L5*6*ARRIVAL·NOTIFY~
L3*438*G*********1*L~
SE*26*000000001~
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.