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
Beginning Segment for Booking or Pick-up/Delivery
To transmit identifying numbers, dates, and other basic data relating to the transaction set
This segment will be used to determine if the carrier has accepted or rejected the shipment. If the value A is sent in the reservation code, the acceptance should process. If the value D is sent, the rejection should process. If the value U is sent, the carrier is only acknowledging they have received the updated 204.
Standard Carrier Alpha Code
- B101 is the Standard Carrier Alpha Code (SCAC) of the carrier sending the EDI transmission.
SCAC code of carrier responding to the 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; (Does not contain blanks or special characters)
Unique identifier – Kraft Heinz will use the BOL number transmitted to the carrier in the B204.
Date expressed as CCYYMMDD
- B103 is the booking date accepted by the carrier.
Date the response is being sent
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- TD
- Reason for Change
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Tender Decline Reason Code
- CDA
- Driver Availability
- CEA
- Carrier Equipment Availability
- CMC
- Over Tender or Capacity Met
- CTA
- Trailer Availability
- DAR
- Delays at Receiver
- DAS
- Delays at Shipper
- ETT
- Extended Transit
- IMS
- Multi-Stop
- ITT
- Insufficient Transit Time
- MTS
- Multi-Temp
- NAL
- Not an Awarded Lane
- NIF
- No Inbound Freight into Area
- NTA
- No Team Available
- RAA
- Receiver Appointment Availability
- SAA
- Shipper Appointment Availability
- SLT
- Short Lead Time
- UCS
- Undesirable Customer
- URS
- Undesirable Region
- WND
- Weather or Natural Disaster
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
ACCEPTANCE
GS*GF*SENDERGS*RECEIVERGS*20231117*004951*000000001*X*004010~
ST*990*935030002~
B1*SCAC*2016722790*20150622*A~
N9*TD*URS~
SE*4*935030002~
GE*1*000000001~
IEA*1*000000001~
DECLINE
GS*GF*SENDERGS*RECEIVERGS*20231117*005011*000000001*X*004010~
ST*990*935030002~
B1*SCAC*2016722790*20150622*D~
N9*TD*URS~
SE*4*935030002~
GE*1*000000001~
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.