EDI 860 Change Order Exception Report

  • 19 April 2022
  • 3 replies

Userlevel 1

2021R2 version.  We receive an EDI 850 from our customer.  Through True Commerce APIs, we create a sales order in Acumatica.  Later, we receive an EDI 860 change order from our customer.  Our business does not want this change order to be automatically applied to the existing sales order in Acumatica.

Instead, our business wants us to generate an exception report that lists the content of the 860 (e.g. header info, line item data) and generate exception messages where the 860 change order is different than the sales order on Acumatica.  For example, provide exception message that the line item quantity changed, or that a new line item was being added to the sales order.  This exception report would go to the customer service rep., who would review the changes and manually enter them on the Acumatica sales order if accepted.  

Has anyone already built functionality that creates custom change order tables (header, lines, notes), and then matches this to the sales order already existing on Acumatica?  




Best answer by timpollard36 25 April 2022, 15:17

View original

3 replies

Userlevel 5
Badge +3

We use an in-house EDI solution and have grappled with the idea, but never implemented the 860.

Your process for managing the exception is similar to how we handle exceptions during our 850 sales order creation process. One example: Sales order lines are typically added at PO price and then we have a GI/Business Event check for discrepancies. The GI compares the PO price against the calculated Acumatica sales price, the business event will then flag the order by updating a custom field, and finally another business event will email a report to customer service and they can choose how to act on the information and manually update the order if needed.

We have several business events that use GIs to identify and act on certain scenarios, especially for automating tasks on EDI orders.

If the 860 data is in available in a DAC, a similar process could be implemented by using a GI to join the sales order info to the 860 data and trigger a business event.

Userlevel 1

Thanks for the feedback.  We will be pursuing putting the 860 data into custom tables, then will join this together with the standard order tables to identify discrepancies and differences.  Thanks.

Userlevel 4
Badge +1


My comment may be out of place for this thread; I thought it might be helpful.

Acumatica on a sales order will flag a line item to "Manuel Price" if the price given is not any of the pricing connected to the customer account, regardless of what pricing function used. For customers who order from thought platforms like True Commerce, we use approvals to manage pricing discrepancies. If Manuel Price is TURE, it gets flagged for approval.

We had issues where EDI 850 was not getting flagged for Manuel Price. Working with True Commerce, they changed the app pool and we turned on the price verification feature in foundry for it to work.


About Acumatica ERP system
Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.
© 2008 — 2024  Acumatica, Inc. All rights reserved