PAWFCISC Gives 3120: ACTIVITY 'PAWFCISC/815457' HAS NO PERFORMER (Doc ID 2189907.1)

Last updated on NOVEMBER 16, 2022

Applies to:

Symptoms

In an instance where patch 22687240 (delta 7) has been applied, when restarting a failed request or processing a new change request, the following error is given:

3205: 'APPR_PAWFCISC297222245678635064' is not a valid role or user name.

The item is no longer viewable from the front end but can be viewed from the back end.

wfstatus shows:

Enter value for 1: PAWFCISC
Enter value for 2: 297222
**** WorkFlow Item

**** Errored Activities

Activity Result Error Name
  
--------------------------------------------- ---------------
------------------------------
Error Message
  
------------------------------------------------------------------------------
------------------------------------------------------
Error Stack
  
------------------------------------------------------------------------------
------------------------------------------------------
Approval Request #EXCEPTION WFNTF_ROLE
  
3205: 'APPR_PAWFCISC297222245678635064' is not a valid role or user name.
  
  
  
Wf_Notification.Send(APPR_PAWFCISC297222245678635064, PAWFCISC, APPROVAL
REQUEST, WF_ENGINE.CB)
Wf_Engine_Util.Notification_Send(PAWFCISC, 297222, 236453, PAWFCISC:APPROVAL
REQUEST)
Wf_Engine_Util.Notification(PAWFCISC, 297222, 236453, RUN)
  
  
  ACTION_RESULT
  
CI_APPROVER APPR_PAWFCISC297222245678635064
  
CI_APPROVER_NAME JOHN.DOE

~~~~~~~~~~~~~

Customer notes:

Noticed some changes as part of patch 22687240 that might have caused the issue:

1. set ci approver return 'F' and (2) approval request Exception as no role found.
Please review the Pseudo code for Set_ci_approver.
1.set l_approval_role as 'APPR_'||p_item_type||p_item_key||
to_char(sysdate,'Jsssss');

2. loop through approvers cursor for manager user info
Get Display name for the manager user name(l_proj_mgr_full_name) by using
wf_directory.getroleinfo

3.If l_proj_mgr_full_name is NULL then create adhoc user :
  WF_DIRECTORY.CreateAdHocUser( name => v_approvers.user_name
 , display_name => v_approvers.party_name
 --, notification_preference => 'MAILTEXT'
 , EMAIL_ADDRESS =>v_approvers.email_address)
  -- bug#21253438

  l_role_users := l_role_users || v_approvers.user_name;

Note : In most case - display name is not NULL so, adhoc role not created and l_role_users is NULL.  This is Bug fix for patch 22687240 causing the issue.

4. Create adhoc role :
  WF_DIRECTORY.CreateAdHocRole( role_name => l_approval_role
  ,
role_display_name => l_proj_mgr_full_name
  , expiration_date => sysdate+15
  -- Set expiration_date
for bug#5962401--Changed expiration_date for bug#10269493

Note : This role created above will be valid only for 15days.

5. If (l_role_users is NOT NULL) then
  WF_DIRECTORY.AddUsersToAdHocRole( l_approval_role,
l_role_users) and return `T'
  Else returns `F'

Note : In our case l_role_users is null (in step3) so it returns `F'

~~~~~~~~

When this code is commented out, the workflow completes successfully.

Customer's issue started as Bug 21253438: ERROR WF_DUP_ROLE RAISED IN PAWFCISC WHEN RESUBMITTING A WORKFLOW. After applying delta 7, this new issue appeared.

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.