Logistics
Some example steps listed- 204 Motor Carrier Load Tender
- 990 Response To A Load Tender
- 214 Transportation Carrier Shipment Status Message
- 210 Motor Carrier Freight Details and Invoice not listed on Kimberly-Clark (via Blue Yonder)
Channel
Kimberly-Clark CorporationKimberly-Clark (via Blue Yonder)
Plan a reliable EDI exchange for Kimberly-Clark Corporation / Kimberly-Clark (via Blue Yonder). Explore 3 document references, map them to your business records and test the complete workflow before launch.
- Documents
- 3 transactions
- Standards
- X12
- Implementation
- Mapping and launch plan
Implementation guide
Kimberly-Clark Corporation / Kimberly-Clark (via Blue Yonder): EDI implementation plan
Build a reliable EDI workflow for Kimberly-Clark Corporation / Kimberly-Clark (via Blue Yonder). Use 3 document types to plan record mapping, prevent duplicate processing and reconcile results in your business systems.
The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| X12 204 Motor Carrier Load TenderListed for Kimberly-Clark (via Blue Yonder) | load tender load reference, pickup and delivery stop identifiers |
|
| X12 990 Response To A Load TenderListed for Kimberly-Clark (via Blue Yonder) | load-tender response original load reference, carrier and response |
|
| X12 214 Transportation Carrier Shipment Status MessageListed for Kimberly-Clark (via Blue Yonder) | shipment status event shipment reference, event code, event time and location |
|
Implementation steps
-
Choose the trading account and channel
Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for Kimberly-Clark (via Blue Yonder). Compare other Kimberly-Clark Corporation channels before reusing a mapping.
-
Map records and assign owners
Start with load tender, load-tender response, shipment status event. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.
-
Test a complete exchange
Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the Kimberly-Clark Corporation production handoff and save the results of each approved test.
-
Check results after launch
Match records between systems using load reference, pickup and delivery stop identifiers. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.
Go-live checklist
- The required X12 documents, versions and sample files are agreed.
- Sender and receiver IDs, test connections and production connections are agreed with the channel owner.
- Delivery receipts, document validation and business responses have monitoring and a named owner.
- Tests cover duplicates, partial processing and reconciliation with realistic business records.
Document catalog
EDI documents listed for Kimberly-Clark Corporation / Kimberly-Clark (via Blue Yonder)
3 EDI transactions listed in this catalog.
Document flow on this channel
Document relationships on Kimberly-Clark (via Blue Yonder)
This channel lists all 3 document types in the Kimberly-Clark Corporation directory. Example relationships are shown below; confirm the required sequence in the channel guide.
Network onboarding
Plan the Blue Yonder connection
The directory associates Blue Yonder with 15 partner entries across 17 channels. Confirm transport, network enrollment, commercial terms and testing with the channel owner before implementation.
Most frequently listed documents on Blue Yonder
- 204 14 ch
- 990 13 ch
- 214 12 ch
- 210 3 ch
- 810 1 ch
- 846 1 ch
Other partner entries associated with Blue Yonder
Kimberly-Clark (via Blue Yonder) questions
Which EDI documents are listed for Kimberly-Clark Corporation / Kimberly-Clark (via Blue Yonder)?
X12 204 Motor Carrier Load Tender; X12 990 Response To A Load Tender; X12 214 Transportation Carrier Shipment Status Message. Confirm which documents, directions and versions apply to your account.
How should I choose the Kimberly-Clark Corporation EDI channel?
Kimberly-Clark (via Blue Yonder) lists 3 distinct document types. Match the channel to your business unit, account and delivery arrangement; compare the other channel links before choosing a connection. Confirm access and enrollment with the channel owner.
Which identifiers should the Kimberly-Clark Corporation mapping preserve?
For X12 204 Motor Carrier Load Tender, plan around load reference, pickup and delivery stop identifiers. For X12 990 Response To A Load Tender, use original load reference, carrier and response. Use the partner guide to locate these values and check their allowed formats.
Does a successful EDI receipt mean Kimberly-Clark Corporation accepted the business document?
Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.
What should be tested before launching Kimberly-Clark Corporation / Kimberly-Clark (via Blue Yonder) EDI?
Send an amended pickup appointment and retain the previous tender decision. Test a multi-stop load whose stop sequence differs from address sorting. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.
Connect Kimberly-Clark Corporation 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.
