X12 204 Stores 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.
Ross Stores requires this data element. This element is required for the B101 element of the 990 and the B1003 element of the 214.
Identification number assigned to the shipment by the shipper that uniquely identifies the shipment from origin to ultimate destination and is not subject to modification; (Does not contain blanks or special characters)
Ross Stores requires this data element. This value must be returned in the B102 element of the 990 and the B1002 element of the 214.
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.
G62 segment with G6201 = ‘64’ provides the latest date/time for the carrier to acceptance or reject the tender offer by transmitting the corresponding EDI 990. Load will be tendered to another carrier
after this date and time. The time is presented as local time for stop 1.
This segment is always sent when B2A is different than ‘01’ for cancellation.
This Segment is only used for Inbound shipments
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
- Z
- Mutually Defined
Bill of Lading Handling Requirements
To identify Bill of Lading handling and service requirements
This segment is optional. Information will be sent if there is a need to communicate specific handling requirements. One or more AT5 segments can be sent.
Pallet Information
To specify pallet information including quantity, exchange, and weight
This segment is optional. Information will be sent if there is a need to communicate pallet count for the shipment.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
When NTE01 = “SPH”, NTE02 will provide details on the special handling service requested for transportation like below examples:
• DIR (Dray movements only)
• CON (Dray movements only)
• SOLO (TL)
• TEAM (TL)
• STANDARD (IMDL)
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)
Ross Stores sends Trailer number or Container number in this field when available if trailer number is not available, the value ‘0’ is sent
Code identifying type of equipment used for shipment
- CN
- Container
- CZ
- Refrigerated Container
- TF
- Trailer, Dry Freight
- TW
- Trailer, Refrigerated
Standard Carrier Alpha Code
- N712 is the owner of the equipment.
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)
2000 : 20 FOOT TRAILER
4000 : 40 FOOT TRAILER
4500 : 45 FOOT TRAILER
4800 : 48 FOOT TRAILER
5300 : 53 FOOT TRAILER
Measurements
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights
(See Figures Appendix for example of use of C001)
Code identifying the broad category to which a measurement applies
- GL
- Guidelines
Code identifying a specific product or process characteristic to which a measurement applies
This data element is sent only when MAE04 = ‘DH’
- DT
- Distance From Base Point
Seal Numbers
To record seal numbers used and the organization that applied the seals
This Segment is only used for Outbound shipments
Detail
Stop Off Details
To specify stop-off detail reference numbers and stop reason
The description element S509 is used to provide information about the distance between two consecutive stops in Miles. S509 is not sent for Stop 1.
Identifying number for the specific stop and the sequence in which the stop is to be performed
Code specifying the reason for the stop
- LD
- Load
- UL
- Unload
Date/Time
To specify pertinent dates and times
- Use G62 segment either in loop 0300 or loop 0350, but not both.
Qualifiers EP and LP will be sent for both pickup and delivery stops to communicate earliest and latest pickup/arrival.
G6203, G6204, & G6205 will be sent with Outbound shipments only*
Code specifying type of date
- EP
- Earliest Pickup Date
- LP
- Latest Pickup Date
Code specifying the reported time
- U
- Scheduled Pick Up Time
- X
- Scheduled Delivery Time
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
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
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. Should weight, quantity, and volume also be sent in segment AT8 in loop 0320 and tied to commodity detail, then the accumulated amounts of weight, quantity, and volume in the AT8 segment in loop 0320 should equal the amounts in the single AT8 occurrence in loop 0300.
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 data element is used for Total number of units (Pieces)
Lading Detail
To transmit detailed lading data pertinent to a pickup or delivery
- Use LAD segment either in loop 0300 or loop 0350, but not both.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- EL
- Established Location
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
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
- IC
- Information Contact
Code identifying the type of communication number
- G6103 qualifies G6104.
- EM
- Electronic Mail
- TE
- Telephone
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 only used for Inbound shipments
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.
This data element is used for Ross Stores Purchase Order Number
Identifying number for Purchase Order assigned by the orderer/purchaser
This data element is used for Ross Stores Purchase Order Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- OID03 is the number assigned by the consignee to further define the purchase order number.
This data element is for Vendor Name
Lading Detail
To transmit detailed lading data pertinent to a pickup or delivery
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.
This data element includes the Shipping Order Number entered by the Vendor (Vendor pickup number)
Code describing a commodity or group of commodities
This data element includes D for Domestic, V for POE, I for International, X for Outbound
Code identifying the commodity coding system used for Commodity Code
- Z
- Mutually defined
- ZZ
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
This data element includes the Tracer Number / TMS Ready to Ship Number
Code specifying the application or source of Marks and Numbers (87)
- ZZ
- Mutually Defined
Code identifying the commodity coding system used for Commodity Code
- Z
- Mutually defined
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.
This field is used for Total number of units (Pieces)
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
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.
Incidental charges occurring during transportation which are not generally considered to be freight charges (examples - stop charges, diversion and reconsignment, icing) expressed in the standard monetary denomination for the currency specified
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 from Ross Stores
GS~SM~ ROSSSTORESTEST~CARRIER1~20160322~104400~1~X~004010
ST~204~0001
B2~~ABCD~~CS00000300~~CC
B2A~00
G62~64~20160625~1~1450
MS3~ABCD~Z~~LT
AT5~MRF
NTE~OTH~OUR FREIGHT TERMS ARE SHIPPER LOAD AND COUNT.
NTE~OTH~- IF THIS SHIPMENT IS AN LTL THE VENDOR MUST SHIP ON PALLETS.
NTE~OTH~- OUR CARRIER WILL CONTACT VENDOR TO ARRANGE ACTUAL PICKUP DATE/TIME
NTE~OTH~- Please make certain the delivery address on your BOL matches the delivery
NTE~OTH~ address outlined below under "PLEASE NOTE DELIVERY ADDRESS."
NTE~OTH~- The Bill of Lading must be marked as "Ross" or "dd's" freight.
NTE~OTH~- Please include the Ross/dd’s BILL OF LADING number on your Bill of Lading.
NTE~OTH~- Please provide the driver with 2 copies of the Bill of Lading.
S5~1~LD
G62~EP~20160629
G62~LP~20160630
AT8~G~L~1710.78~1764~~E~282.51
LAD~CTN~814
LAD~PLT~50
N1~EL~vendor name~ZZ~facility id
N3~address line
N4~city~CA~90670
G61~IC~contact name~TE~1-888-444-5555
OID~6082081~6082081~vendor name
LAD~CTN~814
LAD~PLT~50
L5~1~1233456~I~ZZ~159599861~ZZ
AT8~G~L~1710.78~1764~~E~282.51
S5~2~UL~~~~~~~150
G62~EP~20160629
G62~LP~20160630
AT8~G~L~1710.78~1764~~E~282.51
LAD~CTN~814
LAD~PLT~50
N1~EL~TRIANGLE CONSOL~ZZ~GLTN
N3~12818 SHOEMAKER AVE
N4~SANTA FE SPRINGS~CA~90670
G61~IC~ John Smith~TE~1-333-444-5555
OID~6082081~6082081~vendor name
L3~1710.78~G~~~195000~~~~282.51~E~1764~L
SE~42~0001
GE~1~00001
IEA~1~000000001
Sample from Ross Stores - 2
GS~SM~ ROSSSTORESTEST~CARRIER1~20160322~104400~1~X~004010
ST~204~0001
B2~~ABCD~~CS00000237~~CC
B2A~00
L11~MOLU15455013547~MB
L11~OOCL LUXEMBOURG~VA
L11~037E~V3
L11~TRANSPAC CONT SVS (WIL 136/139)~TT
L11~Steamshipline~SS
L11~20160120~ZZ
G62~64~20160625~1~1450
MS3~ABCD~Z~~ZZ
AT5~PYS
NTE~OTH~OUR FREIGHT TERMS ARE SHIPPER LOAD AND COUNT.
NTE~OTH~- IF THIS SHIPMENT IS AN LTL THE VENDOR MUST SHIP ON PALLETS.
NTE~OTH~- OUR CARRIER WILL CONTACT VENDOR TO ARRANGE ACTUAL PICKUP DATE/TIME
NTE~OTH~- Please make certain the delivery address on your BOL matches the delivery
NTE~OTH~ address outlined below under "PLEASE NOTE DELIVERY ADDRESS."
NTE~OTH~- The Bill of Lading must be marked as "Ross" or "dd's" freight.
NTE~OTH~- Please include the Ross/dd’s BILL OF LADING number on your Bill of Lading.
NTE~OTH~- Please provide the driver with 2 copies of the Bill of Lading.
N7~ABCD~0709902~~~~~~~~~CN~4000
MEA~GL~DT~1520~DH
S5~1~LD
G62~EP~20160629
G62~LP~20160630
AT8~G~L~1950.00~5400~~E~2577.97
LAD~CTN~525
N1~EL~Los Angeles~ZZ~LAS
N3~LA Port
N4~San Pedro~CA~90733
G61~IC~John Smith~TE~1-333-444-5555
OID~6063207~6063207~6063207
LAD~CTN~525
L5~1~1233456~I~ZZ~159599861~ZZ~ZZ
AT8~G~L~1950.00~5400~~E~2577.97
S5~2~UL~~~~~~~150
G62~EP~20160629
G62~LP~20160630
AT8~G~L~1950.00~5400~~E~2577.97
LAD~CTN~525
N1~EL~South West DC~ZZ~SWDC
N3~3404 Indian Avenue
N4~Perris~CA~92572
G61~IC~ John Smith~TE~1-333-444-5555
OID~6063207~6063207~vendor name
L3~11962.26~G~~~195000~~~~2577.97~E~5400~L
SE~47~0001
GE~1~00001
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.