Support Request System
View Patch #60.101.103
Modify PayApprover To = PR RequestedBy if it is a valid PayApprover
Previously, when creating a PO from a PR, the PayApprover defaulted to the PR RequestedBy person, whether or not the RequestedBy person was a valid PayApprover. This was a bug since it would cause "Not a valid PayApprover" errors in various places, which several customers complained about. If the RequestedBy person happened to be on the PayApproverList, no problems would be raised. The bug was fixed by having the PayApprover default to blank or the first person from the PayApproverList, depending on the existing VOBLKPAYAPP setting. This is the same way the default is determined when creating a manual PO(not from a PR). One customer would like the PayApprover to default to the PR RequestedBy person. Since the PR RequestedBy person is not necessarily a valid PayApprover this may again cause "Not a valid PayApprover" errors for other customers.
In order to satisfy all customer requirements while at the same time not allowing the PO to be created with an invalid PayApprover, the creation of a PO from a PR has been changed to default the PayApprover to the PR RequestedBy person **IF** the RequestedBy person is a valid PayApprover, otherwise it will use the VOBLKPAYAPP setting to set the PayApprover to blank or the first person in the PayApproverList.
Find a Patch
Return to Request System Menu