To start and identify an interchange of zero or more functional groups and interchange-related control segments
E2open, LLC X12 990 Response to a Load Tender
Plan X12 990 Response to a Load Tender for E2open, LLC / HB Fuller (via E2open) . Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 7
- Loops
- 0
- X12 990
- Partner references ↗
Implementation guide
E2open, LLC / HB Fuller (via E2open) : 990 mapping and validation
X12 990 Response to a Load Tender is used when a carrier responds to a tender. Preserve original load reference, carrier and response so the load-tender response in your business system stays connected to the original document.
This document is listed for E2open, LLC / HB Fuller (via E2open) . Confirm the version, required fields and responses that apply to your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | load-tender response original load reference, carrier and response |
|
| Update the receiving system | Processing the load-tender response ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the load-tender response Original document reference and matching response |
|
The document reference includes 7 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 204 Motor Carrier Load Tender
load tender: a shipper offers a load to a carrier.
- X12 214 Transportation Carrier Shipment Status Message
shipment status event: the carrier reports a transport milestone or exception.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a carrier responds to a tender. Name the operational owner of the load-tender response and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map original load reference, carrier and response. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and E2open, LLC guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic load-tender response data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful load-tender response processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 990 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic load-tender response data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out load-tender response without processing it twice.
Transaction context
Where 990 Response to a Load Tender fits on HB Fuller (via E2open)
On HB Fuller (via E2open) , the X12 990 Response to a Load Tender can follow the 204 Motor Carrier Load Tender and can precede the 214 Transportation Carrier Shipment Status Message in an example Logistics cycle. Confirm the required sequence for your trading agreement.
- E2open, LLC channels
- 37 of 37
37 of E2open, LLC's 37 channels list 990
- Trading partners
- 168
partner references list 990
- Channels
- 240
channel entries list 990
Frequently listed alongside 990
The directory associates E2open and 990 with 41 channels.
Document structure
X12 990 Response to a Load Tender at the element level
The X12 990 reference contains 16 segment entries and 108 data elements; 38 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 16
- Data elements
- 108
- Mandatory elements
- 38
| Segment | Elements | Mandatory |
|---|---|---|
| B1 | 4 | 1 |
| N9 | 3 | 1 |
| N7 | 24 | 1 |
| L9 | 2 | 2 |
| V9 | 20 | 1 |
| K1 | 2 | 1 |
| S5 | 11 | 2 |
Key identifiers in 990
- Shipment Identification Number
- Reference Identification Qualifier
- Equipment Number
- Special Charge or Allowance Code
- Monetary Amount
- Event Code
- Free-Form Message
- Stop Sequence Number
Segment reference — 7 segments 0 loops · X12 990 Response to a Load Tender
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To transmit identifying numbers, dates, and other basic data relating to the transaction set
To transmit identifying information as specified by the Reference Identification Qualifier
To transmit information in a free-form format for comment or special instruction
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Related references
990 Response to a Load Tender on other E2open, LLC channels
Compare the listed channel references and confirm their current implementation guides.
Nouryon (via E2open) X12 990 Ruiz Foods (via E2open) X12 990 Ball Corporation (via E2open) X12 990 America's Logistics (Amer Serv Lines) (via E2open) X12 990 JBS Swift (via E2open) X12 990 Rise Baking via E2Open X12 990 Blujay Solutions TM Shippers X12 990 Chiquita (via E2open) (1425470) X12 990 Schwan's (via E2open) X12 990 Arkema (via E2open) X12 990 AWG (via E2open) X12 990 Butterball Lean (via E2open) X12 990 Winona Foods LLG (via E2open) X12 990 Bar-S Foods (via E2open) X12 990 Truco (UTZ Brands) (via E2open) X12 990 Reyes Holdings (via E2open) X12 990 CHEP (via E2open) X12 990 Barilla (via E2open) X12 990 Lakeview Farms (via E2open) X12 990 Sargento (via E2open) X12 990 Malt (via E2open) X12 990 Chiquita (via E2open) (001425470) X12 990 E2open (Generic Templates) X12 990 Simmons (via E2open) X12 990 RTP (via E2open) X12 990 Exide Technologies (via E2open) X12 990 Old Hickory (via E2open) X12 990 Chemours (via E2open) X12 990 Lindt (via E2open) X12 990 Dawn Foods (via E2open) X12 990 Martin Brower (via E2open) X12 990 Lineage (via E2open) X12 990 SiteOne (via E2open) X12 990 Leprino (via E2open) X12 990 Smuckers (via E2open) X12 990 Blujay (formerly Kewill Transport) (via E2open) X12 990
No references match your search.
Showing 21 of 36 references
Browse the full directoryRelated references
Other transactions in HB Fuller (via E2open)
Other EDI documents listed on this channel.
E2open, LLC / HB Fuller (via E2open) EDI 990 questions
Common questions about 990 Response to a Load Tender on the HB Fuller (via E2open) channel.
What is X12 990 Response to a Load Tender used for?
990 is used when a carrier responds to a tender. It carries information for the load-tender response. Match it to your business system using original load reference, carrier and response.
Is 990 required for E2open, LLC / HB Fuller (via E2open) ?
990 is listed for E2open, LLC / HB Fuller (via E2open) . Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 990?
Start with original load reference, carrier and response and the target load-tender response. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 990 error handling?
Associate acceptance with the correct version of the load tender. Test a declined tender and ensure it returns to dispatch for reassignment. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 990 relate to other EDI messages?
X12 204 Motor Carrier Load Tender; X12 214 Transportation Carrier Shipment Status Message are related documents also listed on HB Fuller (via E2open) . Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 990 and 204?
990 is used when a carrier responds to a tender. 204 is used when a shipper offers a load to a carrier. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
Connect E2open, LLC EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
