Hi,
This is the ‘story’.
We are preparing to use a third party supplier collaboration tool which sends Change suggestions from MRP to the supplier and need to come up with some way of stopping change suggestions going across to the 3rd Party database, if the combined impact of implementing all the change suggestions for a PO would blow the PO Approval of the buyer.
Without this functionality, we breach our PO limit auditing requirement, as a user could just go into the third party tool, accept the change suggestion, which then supplier accepts and the third party software updates Epicor via the API.
At this point the ‘Approved’ status in Epicor would change to pending, but this is too late.
My idea is to run a function after MRP has run that calculates the impact of all the change suggestions for a PO and then store this value against the change suggestion.
I can then create an updateable BAQ which will allow the relevant approver to approve the suggestion.
In terms of audit, I’ll keep all info in a UD table.
Only approved change suggestions will go across to the third party.
I thought it would be very straightforward and the code is something I coded before and constructed with widgets on other BO’s (i.e. GetByID, make the changes and then Update).
I found this post Logic works in BL Tester, but not BPM Code (Mass Shipment), but whilst the reported problem is similar, the scenario is different.
Cheers,
Andrew.