X12 transaction code
X12 860 Purchase Order Change Request
X12 860 Purchase Order Change Request: explore its business purpose, mapping identifiers, validation tests and 1 partner references across 1 listed channels.
- Standard
- X12
- Code
- 860
- Partner references
- 1
Implementation guide
X12 860 mapping and validation
X12 860 Purchase Order Change Request is used when a buyer changes a previously issued order. Preserve original purchase order, change revision and affected line so the buyer order-change request in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | buyer order-change request original purchase order, change revision and affected line |
|
| Update the receiving system | Processing the buyer order-change request ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the buyer order-change request Original document reference and matching response |
|
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 850 Purchase Order
purchase order or sales order: a buyer places an order.
- X12 865 Purchase Order Change Acknowledgment Request Seller Initiated
seller order-change response or request: a seller acknowledges or proposes an order change.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a buyer changes a previously issued order. Name the operational owner of the buyer order-change request and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map original purchase order, change revision and affected line. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic buyer order-change request 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 buyer order-change request processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 860 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic buyer order-change request 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 buyer order-change request without processing it twice.
Document structure
X12 860 Purchase Order Change Request at the element level
The X12 860 reference contains 55 segment entries and 162 data elements; 62 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 55
- Data elements
- 162
- Mandatory elements
- 62
| Segment | Elements | Mandatory |
|---|---|---|
| BCH | 4 | 4 |
| CUR | 2 | 2 |
| REF | 3 | 1 |
| PER | 2 | 1 |
| FOB | 5 | 1 |
| N9 | 2 | 1 |
| N1 | 4 | 1 |
| N2 | 1 | 1 |
| N3 | 2 | 1 |
| POC | 13 | 1 |
- Transaction Set Purpose Code
- Purchase Order Type Code
- Purchase Order Number
- Date
- Entity Identifier Code
- Currency Code
- Reference Identification Qualifier
- Contact Function Code
Find your trading partner for X12 860
1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 860 Purchase Order Change Request appears in this catalog
The largest groups of classified 860 catalog entries are in automotive.
By industry
- automotive 1 channel
FAQ
X12 860 questions
What is X12 860 Purchase Order Change Request used for?
860 is used when a buyer changes a previously issued order. It carries information for the buyer order-change request. Match it to your business system using original purchase order, change revision and affected line.
Which partners list X12 860?
The directory on this page links 1 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
What should I map for X12 860?
Start with original purchase order, change revision and affected line and the target buyer order-change request. 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 860 error handling?
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 a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 860 relate to other EDI messages?
X12 850 Purchase Order; X12 865 Purchase Order Change Acknowledgment Request Seller Initiated are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 860 and 850?
860 is used when a buyer changes a previously issued order. 850 is used when a buyer places an order. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
Connect 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.
