To start and identify an interchange of zero or more functional groups and interchange-related control segments
Procter & Gamble X12 990 Response to a Load Tender
Plan X12 990 Response to a Load Tender for Procter & Gamble (via Blue Yonder (formerly JDA)) (990 only). Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 6
- Loops
- 0
- X12 990
- Partner references ↗
Implementation guide
Procter & Gamble (via Blue Yonder (formerly JDA)) (990 only): 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 Procter & Gamble (via Blue Yonder (formerly JDA)) (990 only). 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 6 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
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 Procter & Gamble 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 Procter & Gamble (via Blue Yonder (formerly JDA)) (990 only)
- Procter & Gamble channels
- 1 of 3
1 of Procter & Gamble's 3 channels list 990
- Trading partners
- 168
partner references list 990
- Channels
- 240
channel entries list 990
Frequently listed alongside 990
The directory associates Blue Yonder and 990 with 13 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 — 6 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 specify instructions in this business relationship or a reference number
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Procter & Gamble (via Blue Yonder (formerly JDA)) (990 only) EDI 990 questions
Common questions about 990 Response to a Load Tender on the Procter & Gamble (via Blue Yonder (formerly JDA)) (990 only) 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 Procter & Gamble (via Blue Yonder (formerly JDA)) (990 only)?
990 is listed for Procter & Gamble (via Blue Yonder (formerly JDA)) (990 only). 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?
Keep 990 business processing separate from transport receipt and technical validation. Agree which preceding record, response or reconciliation completes the load-tender response workflow; confirm any required companion messages with your partner.
Connect Procter & Gamble 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.
