ttOrderRel has more than one record

Hi all,

I have taken over looking after Epicor, and I have inherited an issue that users are experiencing - when they convert a quote to an order, or when they amend details on an order, say ship by or need by dates, they are getting the below error:


From looking at similar issues that have been posted here, it seems this has something to do with BPMs potentially but I’m a total novice with these. We currently have 4 BPMs for this:
1 standard, which is to email when a customer line release is updated,
3 in-transaction: Unconfirm release (checks for added rows to OrderRel table and "Set the ttOrderRel.FirmRelease field of the changed row to the false… expression); SetOrderRelPlant (checks for <There is at least one added row in the ttOrderRel table and Number of rows in the MyQuery query is more or equal to 1>, then “Set the ttOrderRel.Plant field of the changed row to the callContextClient.CurrentPlant expression”); ChangeLog (if there is at least one updated row in the ttOrderRel table then “Log changes to the selected fields of ttOrderRel table”).

Any ideas on whether any of these BPMs might be the culprits and why? Thank you in advance!

Dana,

I am not an expert by any means but I think the first step (at least that I would take) would be to isolate the error. In the directives screen there is an Enabled checkbox that you can uncheck. Checking this for all the BPMs will let you see how Epicor handles the change without the BPMs firing.

If I were you I’d duplicate the error in a test environment and then disable all the directives and see if the error goes away. Assuming the error does go away, I’d then enable the directives one at a time until the error re-surfaces. From there you know exactly which BPM is the culprit and can take a deeper dive into the “code”.

-Max