转:https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=337817957843841&id=429852.1&_adf.ctrl-state=15w90pbihl_81
![](https://i-blog.csdnimg.cn/blog_migrate/200491d1ae6203cbdf7e02dca39a75b1.gif)
In this Document
APPLIES TO:Oracle Application Object Library - Version 11.5.10.2 to 12.1.3 [Release 11.5 to 12.1]Oracle Workflow - Version 11.5.10.2 to 11.5.10.2 [Release 11.5.10] Information in this document applies to any platform. GOALThis is a consolidation of Top Documents to provide a Single Source for troubleshooting common problems with Missing Responsibilities for a user.
NOTE: Please first review the troubleshooting steps below to apply one that best meets current needs. Not ALL are required for resolving missing responsibility issues.
The symptoms experienced are:
Missing responsibilities for a user may occur if any of the following actions take place:
SUMMARY / CHECKSWhen 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). 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:
SELECT c.component_name, c.component_status from fnd_svc_components c where upper (c.component_name) in ('WORKFLOW DEFERRED AGENT LISTENER',
'WORKFLOW JAVA DEFERRED AGENT LISTENER');
2. Ensure Deferred Workflow Events are being processed.Run the following query to check for Deferred Workflow Events:
select corrid, decode(state, 0, 'Ready', 1, 'Delayed', 2, 'Retained',
3, 'Exception', to_char(state)) State, count(*) COUNT from WF_DEFERRED where corrid like 'APPS:oracle.apps.fnd.wf.ds%' group by corrid, state ;
3. Ensure the Apache Java Cache Mechanism is working fine.Do either of the two actions below to clear the 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 appliedIf User Responsibility contains a colon please do the following:
1. Please download
Patch 4595862 FND_USER_RESP_GROUPS fixes for CU2 and review the readme and pre-requisites
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 dateYou 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.
SOLUTIONPlease review the Doc ID 943096.1 before going through all the steps of Doc ID 429852.1. Please first review the steps below to determine the one that best meets existing needs as not all are required. Please take a backup before making any of these changes and try this on a Test instance first as direct table updates from sqlplus are not supported. 1. 11i: Verify Pre/Post RUP5 code level is up-to-date
FND_USER_RESP_GROUPS_API.sync_roles_one_resp_secgrp is not setting the status to ACTIVE
when calling WF_LOCAL_SYNCH.Propagate_Role() for the old role name format. FND_USER_RESP_GROUPS_API.sync_roles_one_resp_secgrp() does not pass WFSYNC_OVERWRITE when calling WF_LOCAL_SYNCH.Propagate_Role() This happens for all versions of file AFSCURGB.pls <= 115.54. If a user/role relationship refers to a user or a role that does not exist in WF_LOCAL_ROLES, it should remove the relationship. If a user/role relationship is duplicated with users and roles that do exist then it should select one of the records based on priority of 'FND_USR', registered originating system, non-registered originating system and log the decision using WF_LOG and correct the assignments so that these records would not appear in the result sets for the corrective measures down the line. This issue is described in unpublished Bug:4719658: MISSING RESPONSIBILITIES PATCH VERSION 2
1. Please download
Patch 4719658
ONE OFF PATCH FOR MISSING RESPONSIBILITIES and review the readme and pre-requisites 2. Please apply any required pre-requisite patches and Patch 4719658 in a Test environment. This patch will install the following file: FND: patch/115/sql AFSCURGB.pls 115.55 3. After the patch is installed, run the Workflow Directory Services User/Role Validation concurrent program with parameters 10000, Yes, Yes. 4. Please retest the issue. 5. If the issue is resolved, please migrate the solution as appropriate to other environments.
Patch 5121512 fixes many bugs regarding the user/responsibilities and so run some sql statements via concurrent requests which solve issues regarding the end date on users and end date on assignment of responsibilities.
Note: This patch was originally replaced by < >. The most recent replacement for this patch is Patch 6241631 (Applications Technology 11i.ATG_PF.H.delta.7). To apply this patch, please execute the following steps: 1. Please download Patch 5121512 AOL USER RESPONSIBILITY SECURITY FIXES VERSION 1 and review the readme and pre-requisites 2. Please apply any required pre-requisite patches and Patch 5121512 in a Test environment. This patch will install the following file: FND: patch/115/sql AFSCURGB.pls 115.61 3. After the patch is installed, run the Workflow Directory Services User/Role Validation concurrent program with parameters 10000, Yes, Yes. 4. Please retest the issue. 5. If the issue is resolved, please migrate the solution as appropriate to other environments.
This issue is described in
Bug:6008417
AOL USER RESPONSIBILITY SECURITY FIXES 2b
1. Please download
Patch 6008417
AOL USER RESPONSIBILITY SECURITY FIXES 2b and review the readme and pre-requisites 2. Please apply any required pre-requisite patches and Patch 6008417 in a Test environment. This patch will install the following file: FND: patch/115/sql affxdesc.sql 115.5 3. After the patch is installed, run the Workflow Directory Services User/Role Validation concurrent program with parameters 10000, Yes, Yes. 4. Please retest the issue. 5. If the issue is resolved, please migrate the solution as appropriate to other environments. 2. 11i: Verify the status of the subscription AP_WEB_PROXY_ASSIGN_PKG.proxy_assignments The problem can ALSO be caused by the subscription of AP_WEB_PROXY_ASSIGN_PKG.proxy_assignments on the event 'oracle.apps.fnd.wf.ds.userRole.updated', which is failing and set to rollback the transaction, which makes the whole update not make any effect.
select subscription_rule_function from wf_active_subscriptions_v
where event_name in ( 'oracle.apps.fnd.wf.ds.userRole.created', 'oracle.apps.fnd.wf.ds.userRole.updated');
It may happen that when a user or user-responsibilities are modified, business events may fail to update tables related to role and user information. User data can be found in tables FND_USER, FND_RESPONSIBILITY, WF_LOCAL_USER_ROLES, and WF_USER_ROLE_ASSIGNMENTS and these tables can become out of sync as some business events may fail.
3.2.2. Bounce Apache. During Upgrade and Patching a concurrent request may change the status of the role in the wf_local_user_roles table. In most cases where this occurs, an upgrade has recently been performed and during the upgrade some responsibilities were removed. This affected the dates of other responsibilities and usually coincided with the end date that appeared in the column. For example, it has been reported that after upgrading and patching, the System Administrator responsibility no longer appears in the Navigator.
select ura.user_name, ura.role_name
from wf_local_user_roles ur, wf_user_role_assignments ura where ur.user_name = ura.user_name and ur.role_name = ura.role_name and ura.relationship_id = -1 and ((ur.effective_start_date is null or ur.effective_start_date <> ura.effective_start_date) or (ur.effective_end_date is null or ur.effective_end_date <> ura.effective_end_date));
2. Set the role_end_date to null in the wf_local_user_roles.
update wf_local_user_roles
set role_end_date = null where user_name like 'SYSADMIN%' and role_name = 'FND_RESP|SYSADMIN|SYSTEM_ADMINISTRATOR|STANDARD';
update wf_user_role_assignments
set user_end_date=null, role_end_date=null, assigning_Role_end_Date=null, effective_end_Date=to_date('31-12-4712','dd-mm-yyyy') where user_name=upper('&username'); update wf_user_role_assignments set user_end_date=null, role_end_date=null, assigning_role_end_Date=null, effective_end_Date=to_date('31-12-4712','dd-mm-yyyy') where role_name=upper('&rolename'); update wf_local_user_Roles set user_end_date=null, role_end_date=null, effective_end_Date=to_date('31-12-4712','dd-mm-yyyy') where user_name=upper('&username'); update wf_local_user_Roles set user_end_date=null, role_end_date=null, effective_end_Date=to_date('31-12-4712','dd-mm-yyyy') where role_name=upper('&rolename');
NOTE:
&username = Applications Username &rolename = Responsibility name 4. R12: Apply latest UMX code levels. You may try this item solution when users reset their passwords using the "Login Assistance " > "Forgot Password" link, and do not see their responsibilities in home page and get the following message:
There are no active responsibilities available for this user
1. Please download Patch 7507301:R12.UMX.A - PASSWORD RESET VIA LOGIN ASSISTANCE EXPIRING USER - and review the readme and pre-requisites. This patch will bring the latest code level for UMX - User management.
5. A user cannot see any responsibilities after login: 1. Review the 'Applications Start Page' profile option.
6. The "System Administrator" Responsibility is missing: Please run the below concurrent programs in the order given, with the respective values of the parameters, and then retest the issue.
Diagnostics & Utilities Community:
REFERENCESNOTE:943096.1 - User is Unable to See a Responsibility In the Home Page |