Ryder
/
Response to a Load Tender
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Ryder. Contact Ryder for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Ryder logo

X12 990 Response to a Load Tender

X12 Release 4010

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • 990 Sample Data
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/ryder/response-to-a-load-tender/01GMR419HQZSQGECB5XFMAKXEK
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
B1
020
Beginning Segment for Booking or Pick-up/Delivery
Max use 1
Required
N9
030
Reference Identification
Max use 1
Optional
N7
036
Equipment Details
Max use 1
Optional
K1
060
Remarks
Max use 10
Optional
0100 Loop
SE
070
Transaction Set Trailer
Max use 1
Required
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required

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
ISA-12
I11
Interchange Control Version Number
Required

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
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required

Code identifying a group of application related transaction sets

GF
Response to a Load Tender (990)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

GS-04
373
Date
Required
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
Required
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version / Release / Industry Identifier Code
Required

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

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required

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
ST-02
329
Transaction Set Control Number
Required
String (AN)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

B1
020
Heading > B1

Beginning Segment for Booking or Pick-up/Delivery

RequiredMax use 1

To transmit identifying numbers, dates, and other basic data relating to the transaction set

Usage notes

If there is no response Ryder reserves the right to cancel the load tendered and re-tender the shipment to another carrier.

Example
B1-01
140
Standard Carrier Alpha Code
Required
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

  • B101 is the Standard Carrier Alpha Code (SCAC) of the carrier sending the EDI transmission.
B1-02
145
Shipment Identification Number
Required
String (AN)
Min 1Max 30

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)

Usage notes

Ryder Load Number. Sent in the B2 04 on the Ryder EDI Load Tender.

B1-03
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

  • B103 is the booking date accepted by the carrier.
B1-04
558
Reservation Action Code
Required

Code identifying action on reservation or offering

A
Reservation Accepted
D
Reservation Cancelled
N9
030
Heading > N9

Reference Identification

OptionalMax use 1

To transmit identifying information as specified by the Reference Identification Qualifier

Usage notes

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).

Example
If Reference Identification Qualifier (N9-01) is present, then Reference Identification (N9-02) is required
N9-01
128
Reference Identification Qualifier
Required

Code qualifying the Reference Identification

15
Vertical Coordinate
CN
Carrier's Reference Number (PRO/Invoice)
N9-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

Carrier Pro Number Assigned To The Load

N7
036
Heading > N7

Equipment Details

OptionalMax use 1

To identify the equipment

Example
N7-01
206
Equipment Initial
Optional
String (AN)
Min 1Max 4

Prefix or alphabetic part of an equipment unit's identifying number

  • N701 is mandatory for rail transactions.
N7-02
207
Equipment Number
Required
String (AN)
Min 1Max 10

Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)

Usage notes

Trailer Number

K1
060
Heading > K1

Remarks

OptionalMax use 10

To transmit information in a free-form format for comment or special instruction

Example
K1-01
61
Free-Form Message
Required
String (AN)
Min 1Max 30

Free-form information

K1-02
61
Free-Form Message
Optional
String (AN)
Min 1Max 30

Free-form information

0100 Loop
OptionalMax 1
S5
065
Heading > 0100 Loop > S5

Stop Off Details

RequiredMax use 1

To specify stop-off detail reference numbers and stop reason

Example
S5-01
165
Stop Sequence Number
Required
Numeric (N0)
Min 1Max 3

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.

S5-02
163
Stop Reason Code
Required

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
N9
066
Heading > 0100 Loop > N9

Reference Identification

OptionalMax use 10

To transmit identifying information as specified by the Reference Identification Qualifier

Example
If Reference Identification Qualifier (N9-01) is present, then Reference Identification (N9-02) is required
N9-01
128
Reference Identification Qualifier
Required

Code qualifying the Reference Identification

15
Vertical Coordinate
N9-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier.

Usage notes

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.

0100 Loop end
SE
070
Heading > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
String (AN)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Heading end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

990 Sample Data

ISA*00* *00* *02*CARRIERID *14*006922827TMO204*050909*0652*U*00400*000001504*0*P*>~
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.