An ANSI X12 EDI 860 is a purchase order change message used to update, amend, or cancel a previously sent EDI 850 purchase order.
Key takeaways
- An EDI 860 is used after an EDI 850 purchase order when the buyer needs to change or cancel order information.
- EDI 860 messages follow the ANSI X12 standard and contain buyer, seller, order, item, change, and delivery details.
- Reliable EDI 860 processing depends on accurate master data, accepted specifications, and connected ERP and EDI systems.
When is an ANSI X12 EDI 860 used?
A buying organization first sends an EDI 850 purchase order to place the initial request with a supplier. If the order needs to change, the buyer can send an ANSI X12 EDI 860 to change or cancel one or more goods or items from that previous order. The message can also relate to one or more delivery schedules and can provide order-specific details that were not yet known, including customs, transport, and delivery information.
The supplier can respond with an ANSI X12 EDI 855 purchase order acknowledgement. In the source process, this acknowledgement can confirm receipt of the EDI 860 or indicate that the supplier is requesting changes.
The EDI 860 message is used in consumer packaged goods and retail. For grocery retail and fresh-food scenarios, a separate buyer-triggered purchase order change message, EDI 876, may be used.
What does an ANSI X12 EDI 860 message contain?
Purchase order change messages follow the segment and element structure of the ANSI X12 standard. A buyer's ERP system creates the order change information, which can then be translated into the EDI 860 format by the EDI solution in place.
Typical EDI 860 content includes:
- buyer and seller information
- previous purchase order details
- ordered material details with required quantities and dates
- information showing whether material details should be added, removed, or changed
- delivery details, including timing and location
ISA*00* *00* *ZZ*SENDER *01*RECEIVER *231014*1719*U*00401*000000001*0*P*:~
GS*PC*APP SENDER*APP RECEIVER*20231014*1719*0001*X*004010~
ST*860*0001~
BCH*00*CA*36579**9*20231014~
REF*CT*00049~
DTM*002*20231017*0000~
DTM*118*20231016*0000~
N9*ZZ**SPECIAL INSTRUCTIONS~
N1*SU*SUPLIER NAME*ZZ*11222333~
N3*203 STREET NAME~
N4**ATLANTA*GA*30309~
N1*ST*SEEBURGER AG*ZZ*00000085~
N3*EDISONSTRASSE 1~
N4*BRETTEN**75015*DE~
POC*001*RZ*27*27*EA***IN*001234560*UP*123456789012*VN*123~
PID*F****DESCRIPTION~
CTT*1~
SE*16*0001~
GE*1*0001~
IEA*1*000000001~
How is an ANSI X12 EDI 860 processed?
After the supplier receives an EDI 860 message, the supplier's EDI solution checks the content against the EDI 860 specification. If the message follows the specification, the supplier's ERP system can update the previously stored order details using the purchase order number supplied.
A functional acknowledgement, such as an EDI 997, may be sent back to confirm that the message has arrived and has been accepted.
Common EDI 860 errors
- Goods requested may not be available in the supplier's ERP system or may use a different code.
- Specific location codes, such as gate, warehouse, or dock codes, may be unknown to the supplier.
What are the equivalents of ANSI X12 EDI 860 in other EDI standards?
UN/EDIFACT uses ORDCHG for purchase order change types. TRADACOMS, often seen in the UK consumer packaged goods retail industry, uses ORDHDR for the initial order and, when needed, subsequent order changes.
What are the benefits of using ANSI X12 EDI 860?
Using EDI to update purchase order details can help speed up time-critical ordering and adjustment processes, reduce manual workload, reduce the risk of errors, and support paperless message flows.
Benefits for suppliers
Benefits for customers
How does SEEBURGER support purchase orders and purchase order changes?
EDI processes need to be flexible, stable, and cost-effective to automate purchasing. The SEEBURGER BIS Platform supports EDI processes as a fully managed EDI Cloud Service in the SEEBURGER Cloud, in a public cloud environment, or as an on-premises software solution.
SEEBURGER Fully Managed EDI Clouds provide EDI technology and operating expertise for managing EDI solutions, helping organizations handle EDI errors and chargebacks.
Frequently asked questions about ANSI X12 EDI 860
An EDI 860 references the previous purchase order number so the supplier can apply changes to the correct order.
The buying organization sends the EDI 860 after it has already sent an EDI 850 purchase order and needs to change or cancel order information.
An EDI 860 can change or cancel goods or items, relate to delivery schedules, and provide order details such as customs, transport, and delivery information.
A supplier can respond with an ANSI X12 EDI 855 purchase order acknowledgement. A functional acknowledgement such as EDI 997 may also confirm message arrival and acceptance.
The source article identifies EDI 860 as widely used in consumer packaged goods and retail.
The EDIFACT equivalent is ORDCHG, which covers purchase order change types.
Related topics
Do you work in a sector with its own specific needs?
Take a look at the SEEBURGER range of industry-specific solutions