In PO Entry, on the releases tab, when we click on the G/L Account’s Get Default button, two methods are triggered, the Update and the GetDefaultGLAccount. The issue is that the Update happens first and then the GetDefaultGLAccount according to the trace log. I’m trying to make the GL Account a mandatory field but the Update trigger happening first is causing issues. If the GL Account field is blank and you want to pull in the GL Account using the Get Default, it will trigger the hard stop on the Update but shouldn’t since the Get Default is the process that actually pulls in the GL Account correctly. I haven’t seen this where two BO’s are triggered at the same time especially with the update happening first and then the GetDefaultsGLAccount.
We added all of our GL account logic to the PO Approval step so a PO can be entered and changed with invalid accounts but it cannot be approved until everything is correct.
Is that a manual process to review valid accounts? When reviewing valid accounts, does it include blank values? We ran into an issue where a GL account was blank and processed through causing issues.
We have our default expense account on the company GL Control set to a suspense account, so when POs are marked approved, a method directive BPM on PO.OnChangeApproved checks all releases for a non-suspense GL account and kicks the PO back if any release is coded to suspense.
We only do this for PUR-UKN (Other) PO Releases - Job Material, Subcontract, and Stock POs are assumed to be good since all parts have a Part Class assigned with a GL account.
I’m still trying to see of a way to handle the two methods called simultaneously where the Update happens first and then the GetDefaultGLAccount. For some reason, the system allows you to manually delete the GL account and then update it leaving it as blank.