Cannot Assign Responsibility ORA-20002 WF_NO_ROLE and 'Custom Responsibility internal name ... has been detected in FND_USER_RESP_GROUPS_API.INSERT_ASSIGNMENT'
Last updated on JUNE 04, 2018
Applies to:Oracle Workflow - Version 126.96.36.199 to 188.8.131.52 [Release 11.5.10]
Information in this document applies to any platform.
Checked for relevance on June 4th, 2018
When assigning a responsibility to a user using the form (security user define), the following error gets displayed:
NAME=FND_RESP|EPGL|the custom responsibility internal name|STANDARD ORIG_SYSTEM=FND_RESP ORIG_SYSTEM_ID=nnnnn has been detected in FND_USER_RESP_GROUPS_API.INSERT_ASSIGNMENT
As a result, one is unable to assign a custom responsibility to anyone, but there are users using this custom responsibility who were assigned to it in 2007.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms