R12: AP: Unable to Approve Invoice After Escalation Notification Is Sent - ORA-20001 (Doc ID 1061869.1)

Last updated on APRIL 04, 2025

Applies to:

Symptoms

• Unable to approve an invoice after the approval process escalates
  
  
• Invoice remains in Initiated Status after attempting to approve
  
  
• Further notifications are sent to approver
  
  
• Error:

Item Type = APINVAPR
Item Key = XXXX_1
User Key =

Error Name = -20001
Error Message = ORA-20001: The approver identified by the following parameter is invalid:
wf_roles name 50 .
Please delete or replace this approver wherever they occur in AME data, including approval groups, list-modification conditions, and substitution actions.

Error Stack =
APINVAPR.process_doc_approval(APINVAPR, XXXX_1, YYYY, RUN)
Wf_Engine_Util.Function_Call(AP_WORKFLOW_PKG.PROCESS_DOC_APPROVAL, APINVAPR, XXXX_1, YYYY, RUN)

Activity ID = YYYY
Activity Label = APPROVAL_INVOICE:PROCESS_DOC_APPROVAL
Result Code = #EXCEPTION
Notification ID =
Assigned User =

• WFSTAT.sql output shows:

PROCESS_DOC_APPROVAL #EXCEPTION -20001
ORA-20001: The 'name' parameter in the approver record is null. The 'name' parameter should have a not-null value for an approver record.

-- Steps to Reproduce
Enter an invoice in the AP workbench.
Initiate approval routing.
Invoice is routed to first approver.
Workflow times out on first approver and reminder is sent
Reminder Notification Timeout and it gets escalated up to their supervisor via standard functionality.
Escalated approver receives notification and attempts to approve

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.