How To Fix Missing Responsibilities For A User
(Doc ID 429852.1)
Last updated on MARCH 08, 2023
Applies to:Oracle Bills of Material - Version 12.2.5 to 12.2.5 [Release 12.2]
Oracle Application Object Library - Version 126.96.36.199 to 12.2 [Release 11.5 to 12.2]
Oracle Workflow - Version 188.8.131.52 to 12.2 [Release 11.5.10 to 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:
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.
7. Run the WFDS Data Collection Script found in Doc ID 742062.1 to validate the values in the base tables.
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|
|7. Run the WFDS Data Collection Script found in Doc ID 742062.1 to validate the values in the base tables.|
|Diagnostics & Utilities Community:|