Control Batch Record E-signature Workflow Approval Action Is Failing With Error WF_INVALID_USER Invalid user name 'Username'
(Doc ID 1989469.1)
Last updated on AUGUST 16, 2018
Applies to:Oracle MES for Process Manufacturing - Version 12.1.3 and later
Oracle Process Manufacturing Process Execution - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Process Operations Electronic
Control Batch Record E-signature workflow approval action is failing when one of the approver's Oracle account is end dated after the WF was initiated.
The issue was captured in reference with OPM Control Batch Record e-signature approval process, but this could happen to any workflow approval process.
The approval notification will send to multiple users as the rule was defined with 'First Responder Wins' having multiple approvers.
In the multiple approvers, if an approver is inactivated after the approval workflow got initiated, then there is an error.
1. Data fix to close the workflow notifications which are still in open even after they are approved - This list is growing and adds lot of confusion, please request development to provide the data fix asap.
2. Then patch for a avoiding this issue from happening.
Workflow Error >
Item Type = EDRPSIGF
Item Key = 1918242-733121
User Key =
Error Name = WF_INVALID_USER
Error Message = 398: Invalid user name 'Username'
Error Stack =
Wf_Engine_Util.Function_Call(EDR_PSIG_PAGE_FLOW.UPDATE_NOTIF_RESPONSE, EDRPSIGF, 1918242-733121, 188558, RUN)
Activity Id = 188558
Activity Label = PSIG_OFFLINE_NOTIF_PROCESS:PSIG_ESIGN_APPR_OFFLINE_NOTF
Result Code = #EXCEPTION
Notification Id = 13094641
The issue can be reproduced at will with the following steps:
1. Responsibility: Production Supervisor
Navigation: Batch Details > Tools > Batch Progression
Click View control batch record button
Click send for approval button
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.|