APINV - Approving Via Email After Delegate/Vacation Rule Shows Incorrect Approval History
(Doc ID 871952.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Payables - Version: 126.96.36.199
This problem can occur on any platform.
When invoice approval is initiated and the approver has a vacation rule setup to delegate
approval, the notification is redirected to the new person as expected.
Once they approve this notification VIA EMAIL, the invoice is correctly updated to Approved and
notifcation in worklist is closed, BUT when the invoice is queried - the view invoice approval
history form shows incorrect approver details.
RFISHER Delegates to SFISHER
SFISHER approves via email
History shows 2 approval rows RFISHER and SYSADMIN
SYSADMIN shouldn't be there at all since SYSADMIN user did not approve, and the user that approved
the invoice was SFISHER not RFISHER.
wfstat correctly shows SFISHER approved and therefore history form should reflect same information.
-- Steps To Reproduce:
Approvals Management Business Analyst > Approvals
Transaction Type - Payables Invoice Approval
Setup AME rule to route to RFISHER
Create Vacation rule to delegate from RFISHER to SFISHER
Payables > Invoice > Entry > Invoices
Actions > Validate
Actions > Initiate Approval
Logon as SFISHER/Approver
Email notification is sent to SFISHER
Requery approved invoice - check approval history
It's showing incorrect information
This only happens when email approving.
-- Business Impact:
Upper level management are responsible for signing off on the invoices and these delegated
approvals show incorrect approver information. The fact that a sysadmin user is showing as an
approver has serious implications for their documented approval authority business process. This
is also an audit issue as the data on the form does not match that in the database so custom
reports will highlight these errors.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.|