I am seeing some odd behavior, but I am not able to replicate the behavior in Pilot testing. It happens occasionally in Live, but does not seem consistent.
Here is what our change log looks like:
We have a buyer whose limit is $1. When we generate the purchase order from New PO Suggestions, according to the change log, the PO gets created and then the approval status moves to Approved:
However, at the exact same second the status is moved to Approved, the price goes from $0 to something (but our buyer is not changing the price and is only Generating Purchase Orders from the Actions menu on New Po Suggestions):
The desired behavior is for the PO to go into the Pending state (as this PO exceeds the buyer limit). About 1/3 of the Purchase Orders generated for this buyer show this behavior (having a PODetail change log entry showing the buyer changing the price and then the PO starting in the Approved state). The 2/3 of the Purchase Orders that start in the Pending state for this buyer, do not have ANY PODetail entry on the change log (but the buyer is following the same exact steps from New PO Suggestions).
The issue seems to be that the “Buyer Limit” verification occurs before the price shows up on the PODetail. It seems like the methods are getting packed too close together and start to happen simultaneously. I think this is an Epicor issue, but if I cannot force this to occur consistently, Epicor has been reluctant to help me resolve this issue.
What things would you recommend that I try or test to resolve this issue?