X12 990 Response to a Load Tender
This Draft Standard for Trial Use contains the format and establishes the data contents of the Response to a Load Tender Transaction Set (990) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide general information relative to a specific shipment. The Response to a Load Tender is used as the response to a Motor Carrier Shipment Information Transaction Set (204) which has been used as a load tender.
- ~ 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
- GF
- Response to a Load Tender (990)
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).
- 990
- Response To a 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 Booking or Pick-up/Delivery
To transmit identifying numbers, dates, and other basic data relating to the transaction set
If there is no response Ryder reserves the right to cancel the load tendered and re-tender the shipment to another carrier.
Standard Carrier Alpha Code
- B101 is the Standard Carrier Alpha Code (SCAC) of the carrier sending the EDI transmission.
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)
Ryder Load Number. Sent in the B2 04 on the Ryder EDI Load Tender.
Date expressed as CCYYMMDD
- B103 is the booking date accepted by the carrier.
Code identifying action on reservation or offering
- A
- Reservation Accepted
- D
- Reservation Cancelled
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
The carrier must provide their pro number if they will not be able to send back Ryder's load number on all transactions returning to Ryder (EDI 990, EDI 214, EDI 210).
LTL Carriers- Provide your pro number in this segment.
TL Carriers- If it is a point-to-point shipment with a single invoice assigned to the shipment then you may provide your invoice number in this segment. If the shipment has multiple stops then use the Loop ID - 0100 Stop Detail to provide your invoice number(s).
Code qualifying the Reference Identification
- 15
- Vertical Coordinate
- CN
- Carrier's Reference Number (PRO/Invoice)
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Carrier Pro Number Assigned To The Load
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)
Trailer Number
Remarks
To transmit information in a free-form format for comment or special instruction
Stop Off Details
To specify stop-off detail reference numbers and stop reason
Identifying number for the specific stop and the sequence in which the stop is to be performed
0 is the pick up (origin) location with each stop incrementing by 1. 99 may be used for the final consignee stop.
Code specifying the reason for the stop
- CL
- Complete
- CN
- Consolidate
- CU
- Complete Unload
- DT
- Drop Trailer
- LD
- Load
- PL
- Part Load
- PU
- Part Unload
- UL
- Unload
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- 15
- Vertical Coordinate
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier.
For Truck Load carriers. If you create a suffix pro/invoice number per stop, or a separate pro/invoice number per stop, include the pro/invoice number for a given stop in this element.
If you do not have a separate pro number per stop then provide your pro/invoice number for the shipment in the N9 segment in the header of this transaction.
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
990 Sample Data
GS*GF*CARRIERID*006922827TMO204*20050909*0652*1504*X*004010~
ST*990*15040001~
B1*SCAC*2144832*20050909*D~
K1*PROBLEMS SCHEDULING~
SE*4*15040001~
GE*1*1504~
IEA*1*000001504~
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.