X12 204 Motor Carrier Load Tender
This Standard 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 motor carrier including detailed scheduling, equipment requirements, commodities, and shipping instructions pertinent to a load tender.
This document identifies all data elements Groupe Robert Inc (GRI) will provide to our transportation vendors when sending electronic load tenders (204s). Please note that the examples provided are representative of the data elements we will send.
Please contact Groupe Robert Inc’s EDI Coordinator if you have any questions.
- ~ 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
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;
NOTE: This Shipment ID MUST be returned to GRI on EDI transactions 210, 214 and 990s exactly as sent by GRI
Set Purpose
To allow for positive identification of transaction set purpose.
Loads may be sent to carrier up to 72 hours in advance of expected ship date.
Examples:
Original Load Tender - B2A00LT
- GRI’s system will automatically generate an Original (Initial) Load Tender; this 204 is a load tender offer. The carrier is encouraged to respond with a 990 (Accept or Decline). No 990 is considered as an Acceptance of the Load Tender.
Change to Load Tender - B2A04LT - If carrier agrees to accept the Load Tender changes no response other than
the 997 functional acknowledgement is required. But a 990 is accepted - If carrier does not accept the Load Tender changes carrier must call the
originator of the EDI message. Cancellation of Load Tender - B2A01LT - Indicates shipment is canceled.
- No response other than the 997 functional acknowledgment is required.
Code identifying purpose of transaction set
Examples:
Original Load Tender - B2A00LT
- GRI’s system will automatically generate an Original (Initial) Load Tender; this 204 is a load tender offer. The carrier is encouraged to respond with a 990 (Accept or Decline). No 990 is considered as an Acceptance of the Load Tender.
Change to Load Tender - B2A04LT - If carrier agrees to accept the Load Tender changes no response other than
the 997 functional acknowledgement is required. But a 990 is accepted - If carrier does not accept the Load Tender changes carrier must call the
originator of the EDI message. Cancellation of Load Tender - B2A01LT - Indicates shipment is canceled.
- No response other than the 997 functional acknowledgment is required.
- 00
- Original
- 01
- Cancellation
- 04
- Change
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
Code qualifying the Reference Identification
- 2I
- Tracking Number
- RU
- Route Number
Date/Time
To specify pertinent dates and times
NOTE: Segment G62 in header is used to convey the must-respond-by date and time when responding to a 204 transaction.
Date Qualifier 64 will only be used on B2A01 0f 16 (Proposal). All other B2A01 values will have an LC as Planned Loading Complete until loading is complete at which time a CL will be sent.
Code specifying the reported time
- I
- Earliest Requested Pick Up 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
- LT
- Local Time
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)
Bill of Lading Handling Requirements
To identify Bill of Lading handling and service requirements
NOTE: TOF represents an intermodal move by the carrier
Code specifying special transportation handling instructions
TOF represents an intermodal move by the carrier.
- GSS
- Greater Security Service
- TOF
- Trailer on Flat Car
Code identifying the special service
Free-form additional description of special handling instructions to appear on printed bill if special handling code is not adequate
- 28 FT 140 IN TRAILER HIGH CUBE
- 28 FT FLATBED SETS
- 40 FT CONTAINER
- 48 FT FLATBED TRAILER
- 53 FT 102 IN TRAILER
- CURTAIN SIDE
- HEAVY HAUL
- HIGH CUBE
- ROLL DOOR
- ROLLER BED
- TRAILER SET
Pallet Information
To specify pallet information including quantity, exchange, and weight
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
NOTE: Loop 0100 is used to convey name and address detail relative to the bill-to party controlling the freight or other shipment level name and/or address information to include Vessel Name, Shipper, Steamship Company when applicable. It is not to convey ship from or ship to detail which should be handled within loop 0300.
Name
To identify a party by type of organization, name, and code
NOTE: Loop 0100 is used to convey name and address detail relative to the bill-to party controlling the freight or other shipment level name and/or address information to include Vessel Name, Shipper, Steamship Company when applicable. It is not to convey ship from or ship to detail which should be handled within loop 0300.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- FS
- Final Destination
Code designating the system/method of code structure used for Identification Code (67)
- 93
- Code assigned by Robert
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.
NOTE: Only used for N101 of SH and FS
Geographic Location
To specify the geographic place of the named party
NOTES:
- Only used for N101 of SH and FS
- N404 is required if country is NOT USA
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
- BJ
- Operations
- IC
- Information Contact
Code identifying the type of communication number
- G6103 qualifies G6104.
- EM
- Electronic Mail
- FX
- Facsimile
- TE
- Telephone
NOTE: Loop 0100 is used to convey name and address detail relative to the bill-to party controlling the freight or other shipment level name and/or address information to include Vessel Name, Shipper, Steamship Company when applicable. It is not to convey ship from or ship to detail which should be handled within loop 0300.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- SH
- Shipper
Code designating the system/method of code structure used for Identification Code (67)
- 93
- Code assigned by Robert
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.
NOTE: Only used for N101 of SH and FS
Geographic Location
To specify the geographic place of the named party
NOTES:
- Only used for N101 of SH and FS
- N404 is required if country is NOT USA
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
- BJ
- Operations
- IC
- Information Contact
Code identifying the type of communication number
- G6103 qualifies G6104.
- EM
- Electronic Mail
- FX
- Facsimile
- TE
- Telephone
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 identifying type of equipment used for shipment
- 2B
- 20 ft. IL Container (Closed Top)
- 4B
- 40 ft. IL Container (Closed Top)
- AC
- Closed Container
- AT
- Closed Container (Controlled Temperature)
- DT
- Drop Back Trailer
- FT
- Flat Bed Trailer
- HV
- High Cube Van
- RT
- Controlled Temperature Trailer (Reefer)
- TA
- Trailer, Heated/Insulated/Ventilated
- TF
- Trailer, Dry Freight
- TV
- Truck, Van
- TW
- Trailer, Refrigerated
Degree in Celsius or Fahrenheit of the temperature that the trailer must be maintained.
Temperature of Trailer
Example:
57 F
14 C
Detail
NOTE: Segment G62 will be used in loop 0300, not 0350.
Stop Off Details
To specify stop-off detail reference numbers and stop reason,
GRI's scheme is 1, 2, 3, etc. to 999 where the initial pickup stop is always 1.
Identifying number for the specific stop and the sequence in which the stop is to be performed
NOTE: GRI's scheme is 1, 2, 3, etc. to 999 where the initial pickup stop is always 1.
Code specifying the reason for the stop
- CL
- Complete Load
- CU
- Complete Unload
- PL
- Part Load
- PU
- Part Unload
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
NOTES:
- Must provide G-Ps internal Delivery Number(s) (Order).
- Must provide Customer PO Number(s).
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
Notes:
- PO is the customer's purchase order number
- VN is GRI's internal delivery number and is used on all 204's
- BM
- Bill of Lading Number
- PO
- Purchase Order Number
- QN
- Stop Sequence Number
- SI
- Shipment Id (SID)
- VN
- Vendor Order Number
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
- 53
- Deliver Not Before Date
- 54
- Deliver No Later Than Date
- 77
- Pickup Appointment Scheduled Date
- 78
- Delivery Appointment Scheduled Date
- 79
- Pickup Requested Scheduled Date
- 80
- Delivery Requested Scheduled Date
- EP
- Earliest Pickup Date
- LP
- Latest Pickup Date
Code specifying the reported time
- 2
- Pickup Appointment Scheduled Time
- 3
- Delivery Appointment Scheduled 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
- LT
- Local Time
Shipment Weight, Packaging and Quantity Data
To specify shipment details in terms of weight, and quantity of handling units
- Segment AT8 in loop 0300 is intended for the transmitting of total weight, quantity, and volume relative to the specific stop-off.
Code defining the type of weight
- G
- Gross Weight
- T
- Tare Weight
Numeric value of weight
NOTE: Total Weight at stop off.
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.
- This is the number of non-unitized shipping units (e.g. cartons).
Pallet Information
To specify pallet information including quantity, exchange, and weight
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
NOTE: Loop 0310 is used to convey name and address detail relative to the Ship-From and Ship-To as they pertain to the particular stop.
Name
To identify a party by type of organization, name, and code
Notes:
- Ship-From identifies the Pickup point.
- Ship-To identifies the Delivery point.
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)
Notes: The ID code qualifier will be defined only if this location is assigned a GRI location code.
- 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.
GRI location code.
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
Code identifying the major duty or responsibility of the person or group named
- BJ
- Operations
- IC
- Information Contact
Code identifying the type of communication number
- G6103 qualifies G6104.
- EM
- Electronic Mail (email)
- FX
- Facsimile
- TE
- Telephone
NOTE: Loop 0310 is used to convey name and address detail relative to the Ship-From and Ship-To as they pertain to the particular stop.
Name
To identify a party by type of organization, name, and code
Notes:
- Ship-From identifies the Pickup point.
- Ship-To identifies the Delivery point.
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)
Notes: The ID code qualifier will be defined only if this location is assigned a GRI location code.
- 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.
GRI location code.
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
Code identifying the major duty or responsibility of the person or group named
- BJ
- Operations
- IC
- Information Contact
Code identifying the type of communication number
- G6103 qualifies G6104.
- EM
- Electronic Mail (email)
- FX
- Facsimile
- TE
- Telephone
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
Numeric value of weight
Notes: Total Weight for Shipment.
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
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.