Order-to-cash
Some example steps listed- 850 Purchase Order
- 855 Purchase Order Acknowledgment
- 856 Ship Notice Manifest
- 810 Invoice not listed on Target Direct Vendor Ship
Channel
Plan a reliable EDI exchange for Target Direct Vendor Ship. Explore 8 document references, map them to your business records and test the complete workflow before launch.
Implementation guide
Build a reliable EDI workflow for Target Direct Vendor Ship. Use 8 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 860 Purchase Order Change Request Buyer InitiatedListed for Target Direct Vendor Ship | buyer order-change request original purchase order, change revision and affected line |
|
| X12 214 Transportation Carrier Shipment Status MessageListed for Target Direct Vendor Ship | shipment status event shipment reference, event code, event time and location |
|
| X12 850 Purchase OrderListed for Target Direct Vendor Ship | purchase order or sales order buyer purchase order, order line and trading-party identifiers |
|
| X12 864 Text MessageListed for Target Direct Vendor Ship | business message message reference, subject and related business document |
|
| X12 856 Ship Notice ManifestListed for Target Direct Vendor Ship | shipment notice (ASN) shipment, order, package and item references |
|
| X12 855 Purchase Order AcknowledgmentListed for Target Direct Vendor Ship | purchase-order response original purchase order, response revision and order line |
|
| X12 846 Inventory Inquiry AdviceListed for Target Direct Vendor Ship | inventory availability record item, location, quantity type and snapshot time |
|
| X12 865 Purchase Order Change Acknowledgment Request Seller InitiatedListed for Target Direct Vendor Ship | seller order-change response or request original purchase order, change reference and affected line |
|
Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for Target Direct Vendor Ship. Compare other Target channels before reusing a mapping.
Start with buyer order-change request, shipment status event, purchase order or sales order. 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.
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 Target production handoff and save the results of each approved test.
Match records between systems using original purchase order, change revision and affected line. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.
Document catalog
8 EDI transactions listed in this catalog.
Document flow on this channel
This channel lists 8 of the 14Target document types; other entries appear on Target channels (listed below). Example relationships are shown below; confirm the required sequence in the channel guide.
X12 860 Purchase Order Change Request Buyer Initiated; X12 214 Transportation Carrier Shipment Status Message; X12 850 Purchase Order; X12 864 Text Message; X12 856 Ship Notice Manifest; X12 855 Purchase Order Acknowledgment; X12 846 Inventory Inquiry Advice; additional documents are shown in the mapping plan. Confirm which documents, directions and versions apply to your account.
Target Direct Vendor Ship lists 8 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.
For X12 860 Purchase Order Change Request Buyer Initiated, plan around original purchase order, change revision and affected line. For X12 214 Transportation Carrier Shipment Status Message, use shipment reference, event code, event time and location. Use the partner guide to locate these values and check their allowed formats.
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.
Apply a quantity reduction to the existing order instead of creating another order. Test a cancellation arriving after allocation or shipment and route it to an exception owner. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.
Related references
Compare the document lists for other Target channels.
Showing 3 of 3 references
Browse the full directorySee 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.