To start and identify an interchange of zero or more functional groups and interchange-related control segments
Shoe Sensation Inc X12 860 Purchase Order Change Request - Buyer Initiated
Plan X12 860 Purchase Order Change Request - Buyer Initiated for Shoe Sensation Inc / SHOESENSATION. Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 23
- Loops
- 7
- X12 860
- Partner references ↗
Implementation guide
Shoe Sensation Inc / SHOESENSATION: 860 mapping and validation
X12 860 Purchase Order Change Request - Buyer Initiated 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.
This document is listed for Shoe Sensation Inc / SHOESENSATION. 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 | 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 |
|
The document reference includes 23 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 850 Purchase Order
purchase order or sales order: a buyer places an order.
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 Shoe Sensation Inc 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.
Transaction context
Where 860 Purchase Order Change Request - Buyer Initiated fits on SHOESENSATION
- Shoe Sensation Inc channels
- 1 of 1
1 of Shoe Sensation Inc's 1 channel list 860
- Trading partners
- 140
partner references list 860
- Channels
- 171
channel entries list 860
Frequently listed alongside 860
Document structure
X12 860 Purchase Order Change Request - Buyer Initiated 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 |
Key identifiers in 860
- Transaction Set Purpose Code
- Purchase Order Type Code
- Purchase Order Number
- Date
- Entity Identifier Code
- Currency Code
- Reference Identification Qualifier
- Contact Function Code
Segment reference — 23 segments 7 loops · X12 860 Purchase Order Change Request - Buyer Initiated
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 indicate the beginning of the Purchase Order Change Transaction Set and transmit identifying numbers and dates
To specify identifying information
To identify a person or office to whom administrative communications should be directed
SAC Loop Repeat: 25
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
To specify terms of sale
To specify pertinent dates and times
To specify the carrier and sequence of routing and provide transit time information
To specify tax information
N9 Loop Repeat: 1,000
To transmit identifying information as specified by the Reference Identification Qualifier
To specify textual data
N1 Loop Repeat: 200
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
POC Loop Repeat: 1,000
To specify changes to a line item
PID Loop Repeat: 1,000
To describe a product or process in coded or free-form format
To specify destination and quantity detail
SLN Loop Repeat: 1,000
CTT Loop Repeat: 1
To transmit a hash total for a specific element in the transaction set
To indicate the total monetary amount
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To specify product subline detail item data
Related references
Other transactions in SHOESENSATION
Other EDI documents listed on this channel.
Shoe Sensation Inc / SHOESENSATION EDI 860 questions
Common questions about 860 Purchase Order Change Request - Buyer Initiated on the SHOESENSATION channel.
What is X12 860 Purchase Order Change Request - Buyer Initiated 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.
Is 860 required for Shoe Sensation Inc / SHOESENSATION?
860 is listed for Shoe Sensation Inc / SHOESENSATION. Confirm the required version and direction for your business unit and account with the partner.
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 is a related document also listed on SHOESENSATION. 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 Shoe Sensation Inc 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.
