We’re currently on 10.0.700 series where EDI is working for all customers.
Testing 10.1.500 all but one customer works fine. The EDI import that comes in clean. Verified that there are no errors in Demand Workbench, but when we try to Process it into an order, it throws the error “The transaction has aborted”.
Odd thing is, all other customers works, it just effects this one customer no matter the file imported. We’ve checked the Demand contract, customer setup, verified the parts in the POs are valid, and everything else we can think of.
It’s a pretty cryptic error and even the trace logs are no help.
Yes, all our EDI comes in via .app files and they are now all importing into Epicor 10.1 just fine. The error happens when we try to process the PO into an order.
We had some fun with UD fields early on in testing our 10.1 pilot. There is a thread here as well, but once we setup the DemandImport tables to the same fields as the Demand tables it worked. We recreated all the the E9 type UD fields, ShortChar01, etc.
They are all Firm imports and we use the standard Epicor EDI mapping. Thus the E9 type UD field names.
We found the issue. In Customer Maintenance, this customer has Capable To Promise setup and “Shipping” as the date type. However, their EDI file did not include the ship by date. This caused the error.
Once we entered a ship by date it’d process. But since this customer doesn’t send one, we changed to date to Need by which lets Epicor calculate the ship by when importing the file.