How To Fix Missing Responsibilities For A User
(Doc ID 429852.1)
Last updated on JUNE 28, 2019
Applies to:Oracle Application Object Library - Version 184.108.40.206 to 12.2 [Release 11.5 to 12.2]
Oracle Workflow - Version 220.127.116.11 to 12.2 [Release 11.5.10 to 12.2]
Oracle Bills of Material - Version 12.2.5 to 12.2.5 [Release 12.2]
Information in this document applies to any platform.
Reviewed for Relevance 29 Jul 18.
This is a consolidation of Top Documents to provide a Single Source for troubleshooting common problems with Missing Responsibilities for a user.
All information contained on this document includes both versions 11i and R12. When something is either 11i or R12 specific, it will be specified.
The symptoms experienced are:
- Missing responsibilities for a user in the navigator page during logon.
- After upgrading and patching, the System Administrator responsibility no longer appears in the Navigator.
- Some users cannot see/receive their open notifications due to missing responsibilities.
- Some users get notification e-mails even though their responsibilities are end-dated
- If a user is end-dated, a user's responsibility creates duplicate row
- Newly added responsibility is not displayed until Apache is bounced
- Intermitent issue: After resetting user passwords using the "Login Assistance " > "Forgot Password" link, users do not see their responsibilities in home page and get the following message:
- "There are no active responsibilities available for this user"
- "System Administrator" responsibility missing
Missing responsibilities for a user may occur if any of the following actions take place:
- User is end-dated.
- Username is changed.
- User is reactivated. Value of the end-date field is removed.
- Upgrade and patching.
- 11i: ATG RUP3 or ATG RUP4 Patches are applied.
- 11i: Responsibility with a colon (:) is assigned to a user after CU2 patch is applied
- The Effective From date for the user responsibility assigned is invalid. (For example 1951 - before Oracle Applications even existed)
SUMMARY / CHECKS
When a responsibility is assigned to a user in the Security / User / Define form, triggers are fired to send business events to the Workflow Deferred Agent Listeners. These events need to be processed before the base tables are updated with the changes. (The data used in the forms is derived from views based on certain workflow tables).
These business events are processed by the Workflow Deferred Agent Listener and Workflow Java Deferred Agent Listener.
Check the following:
1. Ensure both workflow services are running, the Workflow Deferred Agent Listener and Workflow Java Deferred Agent Listener.
Run the following code to get status of Listeners:
'WORKFLOW JAVA DEFERRED AGENT LISTENER');
Activate listeners if not running. See <Note 548918.1> "How to start the Workflow Deferred Agent Listener and Workflow Java Deferred Agent Listener?"
2. Ensure Deferred Workflow Events are being processed.
Run the following query to check for Deferred Workflow Events:
3, 'Exception', to_char(state)) State, count(*) COUNT from WF_DEFERRED where corrid like 'APPS:oracle.apps.fnd.wf.ds%' group by corrid, state ;
State of READY indicates they have NOT yet been processed.
If a backlog of processes exist, missing responsibilities may result from that. There can be a delay based on the load of the listeners as these are not the only business events that they process.
Use the script wfver.sql that is provided with Oracle Workflow 2.x to reflect the current health of workflow. For more information, see <Note 1011379.102> "How To Check The Version And Health Of Workflow Installed On The Server".
3. Ensure the Apache Java Cache Mechanism is working fine.
Do either of the two actions below to clear the cache.
3.1 Restart Apache
3.2 Manually clear Java Cache using the "Functional Administrator" responsibility. To do this, do the following:
- Login with 'Functional Administrator' responsibility
- Navigate to Core Service -> Caching Framework -> Global Configuration
- Click on 'Clear All Cache'
If responsibilities are not showing up, then you may be experiencing a Java Cache Mechanism issue. See <Note 374309.1> "Newly added responsibility is not displayed until Apache is bounced, after applying ATG RUP3 or ATG RUP4" to help fix this issue. Also sett Note 455194.1 to help you troubleshoot the health of your system in case you have this cache issue.
4. Ensure the Workflow Background Process request is scheduled to run daily.
See <Note 182936.1> on "How to Submit a Workflow Background Process Engine". A Workflow Background process should be scheduled to run with a frequency required by the volume of workflow processing. Some high volume instances run this once every 5 minutes. At a minimum, a workflow background process should be scheduled for deferred, stuck, and timeout processes.
5. 11i: Ensure Responsibility Assigned to User has no colon (:) in the name after CU2 patch is applied
If User Responsibility contains a colon please do the following:
2. Please apply any required pre-requisite patches and <Patch 4595862> in a Test environment.
This patch will install the following file:
FND: patch/115/sql AFSCURGB.pls 115.50
3. Please retest the issue.
4. If the issue is resolved, please migrate the solution as appropriate to other environments
6. Ensure new user responsibility assigned has a valid effective from date
You are assigning a predefined responsibility to new users. The responsibility does not show up in the menu when the user logs in. The responsibility shows in the Define User form (FNDSCAUS). However, the responsibility does not show in SSWA or Forms.
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
|SUMMARY / CHECKS|
|1. Ensure both workflow services are running, the Workflow Deferred Agent Listener and Workflow Java Deferred Agent Listener.|
|2. Ensure Deferred Workflow Events are being processed.|
|3. Ensure the Apache Java Cache Mechanism is working fine.|
|4. Ensure the Workflow Background Process request is scheduled to run daily.|
|5. 11i: Ensure Responsibility Assigned to User has no colon (:) in the name after CU2 patch is applied|
|6. Ensure new user responsibility assigned has a valid effective from date|
|Diagnostics & Utilities Community:|