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
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.
Carrier’s SCAC Code
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)
Bill of Lading Number (BOL). This identification number will be used for freight payment (sent to Kraft Heinz in the 210 segment).
This will be the SID – 10 digit Shipment number
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
Based on the Load Class within SMS
I = Load class I
B = Load Class T (no stops)
F = Load Class T (with stops)
- B
- Bill of Lading for Individual Shipment
Single
- F
- Stop-off Shipment
Shipment contains stop–off(s)
- I
- Intermodal
Intermodal
- L
- LTL (less than truckload)
Set Purpose
To allow for positive identification of transaction set purpose
Code identifying purpose of transaction set
- 00
- Original
Used when the load is tendered for the first time is used when the load is tendered again to the same carrier as the original tender. This can occur when the shipment is recalled and retendered for transmission problems.
- 01
- Cancellation
Used when the shipment is recalled or cancelled
- 04
- Change
Used when something on the order changes:
Ship/Delivery Dates
PO’s added or deleted
Stops added/deleted
CM created
Continuous Move Number
To specify instructions in this business relationship or a reference number
This segment will be used when the Tender is part of a continuous
move
The CM qualifier will be used to designate the continuous move
number.
This segment will be used when the shipment being tendered is part of a continuous movement.
The first leg of a continuous movement will be tendered as a ‘normal’ shipment. When the second leg is tendered, the first leg will be updated. A 204 update will be sent and there will be an L11 segment with a CM qualifier. The Continuous movement number will be sent in the L1101.
When the second (or subsequent) leg of the continuous movement is tendered, there will be two occurrences of this segment.
The first will contain the continuous movement number and the CM qualifier. The second occurrence will contain the shipment number (BOL) of the previous leg with the PSI qualifier.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
This will be the Continuous Move Reference Number assigned by Kraft Heinz
Code qualifying the Reference Identification
- CM
- Continuous Move Number
BOL of the previous leg of the Continuous Move
To specify instructions in this business relationship or a reference number
This segment will be used when the Tender is part of a continuous
move
The PSI qualifier will be used to designate the previous leg of the
continuous move.
This segment will be used when the shipment being tendered is part of a continuous movement.
The first leg of a continuous movement will be tendered as a ‘normal’ shipment. When the second leg is tendered, the first leg will be updated. A 204 update will be sent and there will be an L11 segment with a CM qualifier. The Continuous movement number will be sent in the L1101.
When the second (or subsequent) leg of the continuous movement is tendered, there will be two occurrences of this segment.
The first will contain the continuous movement number and the CM qualifier. The second occurrence will contain the shipment number (BOL) of the previous leg with the PSI qualifier.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
This will be the BOL of the previous leg of the continuous move.
Code qualifying the Reference Identification
- PSI
- BOL of the previous leg of the Continuous Move
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 is used to inform the carrier when they must respond to our offer. In other words, the 990 response is due back to LCC by the date and time provided in this segment. The Date & Time populated should be 2 hours after the tender time, and should be converted to local time for the carrier.
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)
Time expressed in 24-hour clock time as follows: HHMM
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
Bill of Lading Handling Requirements
To identify Bill of Lading handling and service requirements
The AT5 segment is used to inform carriers that the shipment tender is a part of a loop. The carrier will need to invoice Kraft Heinz using a loop rate.
Code specifying special transportation handling instructions
Blank
Code identifying the special service
Blank
Free-form additional description of special handling instructions to appear on printed bill if special handling code is not adequate
Route Leg ID – contains ‘Route Template’, ‘Route Instance’, and the ‘Route Leg’ information
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Up to 20 lines of additional data can be transmitted to the carriers. This data should include any comments that are sent to us via COD, or any standard comments that are associated with the stopoff. These could be directions to the facility or instructions about not using certain size equipment, etc.
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 will be populated with the information associated with the SHIPPER CODE on the shipment.
Ship-to Code and Ship-to Name. The internal customer number and qualifier will not be supplied when the shipment is a drop shipment.
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 the organization originating the transaction set
Code assigned by Kraft Heinz
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.
Kraft Heinz internal customer number associated with Shipper
Additional Name Information
To specify additional names or those longer than 35 characters in length
Address Information
To specify the location of the named party
This segment is populated with the address information in the ship-to record.
Geographic Location
To specify the geographic place of the named party
This segment contains the information relating to the ship-to record.
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
City of Shipper
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.
State or Province of Shipper
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Postal / Zip code of shipper
Code identifying the country
Country of Shipper (USA)
Contact
To identify a person or office to whom communications should be directed
This segment will contain information relating to the load planner that actually tendered the shipment. The contact name will be the load planner’s name (found in the shipment audit record, x-refed to the userid).
The Communication number could be hard-coded to the 1888LOADCTR number. If at all possible if would be great to be able to map an extension number on the end.
Code identifying the major duty or responsibility of the person or group named
- SH
- Shipper Contact
Code identifying the type of communication number
- G6103 qualifies G6104.
- TE
- Telephone
Complete communications number including country or area code when applicable
LCC Phone Number
Equipment Details
To identify the equipment
Information in this segment will come from the shipment record. Data element 40 – Equipment description code will be mapped as:
TF when equipment type starts with a VN
RT when equipment type starts with a RF
TI when equipment type starts with an IN
TA when equipment type starts with an HT
The equipment length field is from the last two digits of the equipment type at the shipment level.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Value Kraft Heinz will use 0 (zero)
Code identifying the volume unit
- E
- Cubic Feet
- M
- Cubic Meters (M3)
for Brazil only
Code identifying type of equipment used for shipment
- RT
- Controlled Temperature Trailer (Reefer)
- TA
- Trailer, Heated/Insulated/Ventilated
- TE
- Trailer Easter (Brazil only)
- TF
- Trailer, Dry Freight
- TI
- Trailer, Insulated
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)
Length of equipment requested
4800 – 48’ trailer
5300 – 53’ trailer
Detail
Stop Off Details
To specify stop-off detail reference numbers and stop reason
The S5 is the beginning of the stop-off loop. There will be at LEAST two occurrences of the S5 segment with each 204.
The weight, case count, and cube are populated from the stop off record. The stop reason code is straightforward and should be mapped accordingly. The stop sequence number will begin with 01 (for the original pickup) and 02 will designate the final unload.
Identifying number for the specific stop and the sequence in which the stop is to be performed
Specific stop sequence number
Code specifying the reason for the stop
- CL
- Complete
complete shipment
- CU
- Complete Unload
complete unload (final stop)
- LD
- Load
complete load (last pickup)
- PL
- Part Load
part load (used when there are multiple pickup stops)
- PU
- Part Unload
part unload (used when there are multiple delivery stops)
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Number of units (Cases) shipped
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CA
- Case
Code identifying the volume unit
- E
- Cubic Feet
- M
- Cubic Meters (M3)
for Brazil only
Shipment stop-off identifier
To specify instructions in this business relationship or a reference number
This will be the reference number returned in the 214
The occurrence will include the shipment stop-off number (SID + 01 + stop), with the SI qualifier. The pickup stop will only have this reference. The delivery stops will have this qualifier and another occurrence of the L11.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- SI
- Shipper's Identifying Number for Shipment (SID)
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
IL qualifier – for internal order number (Kraft Heinz replenishment #) OR a PO qualifier – for the customer’s PO number
If the IL qualifier is used, the reference number will be the replenishment number (ROCET). If the PO qualifier is used, the reference number will be the customer’s Purchase Order Number. There will be multiple occurrences of this segment when there are multiple PO’s on a stop-off.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- IL
- Internal Order Number
Used to identify Replenishment Orders
- PO
- Purchase Order Number
Purchase Order of Customer
Date/Time
To specify pertinent dates and times
- Use G62 segment either in loop 0300 or loop 0350, but not both.
The G62 segment is very dependent on the information passed to LCC on the order and to what stop it applies. There can be up to two occurrences of the G62 segment per stop-off. This is usually seen when a time range is provided to the carrier.
The pickup stop-offs (stop reason code LD or PL – see S502) will have the following:
G6201 will have a value of 10 or 69 (most times it will be 69, as Kraft Heinz is establishing the ship date.
The G6203 in the first occurrence of the G62 will contain an I. The second occurrence of the G62 will contain a K. The times entered in the G62 segments will relate to the dock hours if no specific time is specified.
If a specific time is specified (i.e. earliest & latest is the same), then the value of Y will be used and only one G62 will be sent.
Very rarely will pickup appointments be provided to the carriers.
If the order has a scheduled delivery appointment, it will be outlined in the standard comments.
Standard Comments are:
0002 _____A.M.-DEL. BEFORE - G6201 value = 70, G6203 value = L
0003 _____P.M.-DEL. BEFORE - G6201 value = 70, G6203 value = L
0004 _____A.M.-DEL. AFTER - G6201 value = 70, G6203 value = G
0005 _____P.M.-DEL. AFTER – G6201 value = 70, G6203 value = G
0006 _____A.M.-DEL TIME – G6201 value = 70, G6203 value = 3
0007 _____P.M.-DEL TIME – G6201 value = 70, G6203 value = 3
In many cases, the delivery date will be requested, with no assigned time. In this case, the G6201 value will be 69. The G6203 value will be:
Z if there is a specific time provided OR there will be two occurrences of the G62. The first G6203 will contain the value G and the second G6203 will contain the value L.
Code specifying type of date
- 10
- Requested Ship Date/Pick-up Date
Carrier MUST MAKE appointment
- 68
- Requested Delivery Date
Carrier MUST MAKE appointment
- 69
- Scheduled Pick-Up Date
Carrier MUST CONFIRM appointment
- 70
- Scheduled Delivery Date
Carrier MUST CONFIRM appointment
Code specifying the reported time
If pick up or delivery ‘windows’ are given:
G – Earliest Requested Delivery Time
I – Earliest Requested Pick up Time
K – Latest Requested Pick up Time
L – Latest Requested Delivery Time
- 2
- Pickup Appointment Scheduled Time
Carrier MUST CONFIRM appointment time
- 3
- Delivery Appointment Scheduled Time
Carrier MUST CONFIRM appointment time
- G
- Earliest Requested Deliver Time
- I
- Earliest Requested Pick Up Time
- K
- Latest Requested Pick Up Time
- L
- Latest Requested Delivery Time
- Y
- Requested Pick Up Time
Carrier MUST MAKE appointment
- Z
- Requested Delivery Time
Carrier MUST MAKE appointment
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)
Time expressed in 24-hour clock time as follows: HHMM
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
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Up to 20 lines of additional data can be transmitted to the carriers. This data should include any comments that are sent to us via COD, or any standard comments that are associated with the stop-off. These could be directions to the facility or instructions about not using certain size equipment, etc.
Code identifying the functional area or purpose for which the note applies
- ADD
- Additional Information
A free-form description to clarify the related data elements and their content
A free-form description to clarify the related data elements and their content
Name
To identify a party by type of organization, name, and code
This segment is used to identify the stop-off details. There will be one occurrence of this segment for each S5. If the shipment is going to a ‘drop ship’ address, the drop ship information will be sent to the carrier in these segments. For the original pickup (stop 01, stop reason code LD) the N101 value will be SF. For subsequent pickup (if there are any, stop reason code PL) the N101 value will be PW. For intermediate stops (if there are any, stop reason code PU) the N101 value will be DA. For the final delivery (stop 02, stop reason code CU) the N101 value will be ST. The N102 will contain the name of the stop-off customer. The N104 will contain the customer number on the stop-off.
Code identifying an organizational entity, a physical location, property or an individual
- CN
- Consignee
used by SMS only
- DA
- Delivery Address
used by both SMS and Manugistics
- PW
- Pick Up Address
- SF
- Ship From
- ST
- Ship To
used by Manugistics only
Code designating the system/method of code structure used for Identification Code (67)
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.
Additional Name Information
To specify additional names or those longer than 35 characters in length
In general, we don’t usually use this. If there were a second line in the name, the information would go here.
Address Information
To specify the location of the named party
Address information is shown here.
Geographic Location
To specify the geographic place of the named party
This segment contains the information relating to the city/state of the stop-off. The information maps from the stop off data.
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
City Name of 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.
State / Province of Location
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Postal or Zip Code of location
Code identifying the country
Code identifying the country of location
- CA
- Canada
- US
- United States of America (the)
Contact
To identify a person or office to whom communications should be directed
If there is a contact name & number associated with the stop off or customer number, it is sent in this segment. If the stop is a pickup stop the G6101 value will be SH, if the stop is a delivery stop the G6101 value is DC.
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.
- TE
- Telephone
Complete communications number including country or area code when applicable
Telephone Number of contact Person
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 is used to provide the carrier with the case count, weight and cube of each order. It is used by larger customers when the delivery appointments are made. There will be one occurrence of this segment for each Purchase Order on the stop. This segment is associated with customer delivery stops only. The value in the OID02 should match the data sent in the L11 segment with a PO qualifier.
Identifying number for Purchase Order assigned by the orderer/purchaser
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CA
- Case
Numeric value of quantity
Number of cases ordered on given Purchase Order
Numeric value of weight
Weight (in pounds) associated with the given Purchase Order
Code identifying the volume unit
- E
- Cubic Feet
- M
- Cubic Meters (M3)
for Brazil only
Value of volumetric measure
Volume (in cubic feet) associated with the given Purchase Order
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
Value of volumetric measure
Total Volume of the Shipment (in cubic feet)
Code identifying the volume unit
- E
- Cubic Feet
- M
- Cubic Meters (M3)
for Brazil only
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
Sample
B2**SCAC**2021601410*L*PP*B~
B2A*00~
G62*64*20160509*1*1247*LT~
N1*SH*Kraft Heinz Foods Company*93*569129~
N3*PO Box 982141~
N4*El Paso*TX*79998-2141*USA~
G61*SH*LOAD PLANNER*TE*Call Dispatch Office~
N7**0*300*G****51000*E**RT****5300~
S5*1*CL*30000*L*30000*CA*510*E~
L11*20216014100101*SI~
L11*3561004455*PO~
G62*10*20160516*I*0000*LT~
G62*10*20160516*K*2359*LT~
NTE*ADD*6~
N1*SF*GLANBIA FOODS INC*93*0002028601~
N3*236 WASHINGTON AVE S~
N4*TWIN FALLS*ID*83301*US~
G61*SH*LOAD PLANNER CONTACT*TE*Call Dispatch Office~
OID**3561004455**CA*30000*L*30000*E*510~
S5*2*CU*30000*L*30000*CA*510*E~
L11*20216014100102*SI~
L11*3561004455*PO~
G62*68*20160520*G*0000*LT~
G62*68*20160520*L*2359*LT~
NTE*ADD*6~
N1*ST*CEDAR GROVE*93*028787_0101~
N3*903 GROSSMAN STREET~
N4*SCHOFIELD*WI*54476-6103*US~
OID**3561004455**CA*30000*L*30000*E*510~
L3*30000*G*******51000*E~
SE*32*22450~
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.