Troubleshooting: Responsibility not Visible by User After unendate

Feb

27

Troubleshooting: Responsibility not Visible by User After unendate

It can happen that after unendating a responsibility assignment, the user cannot see that responsibility. To solve this problem there are 2 procedures that can help:

1. Run the request ‘Sync responsibility role data into the WF table’.
2. Run the request “Synchronize WF LOCAL tables”.
3. Run the request “Workflow Directory Services User/Role Validation” (with parameters 10000, yes,
yes, yes).
4. Have the user log off and back on and verify that the responsibility appears.

If after that the problem is not solved yet, then it’s possible to use the System Administrator responsibility: Workflow -> Oracle Applications Manager -> Workflow Manager

troubleshooting responsibility not visible by user after unendate 01 Troubleshooting: Responsibility not Visible by User After unendate
space Troubleshooting: Responsibility not Visible by User After unendate

Selecting ‘Service Components’ and starting the following listeners:
- Workflow Deferred Notification Agent Listener
- Workflow Error Agent Listener
- Workflow Java Deferred Agent Listener
- Workflow Java Error Agent Listener

troubleshooting responsibility not visible by user after unendate 02 Troubleshooting: Responsibility not Visible by User After unendate
space Troubleshooting: Responsibility not Visible by User After unendate

The user should then be able to use the unendate responsibility.
If you have found this post useful, don’t forget to share your comments! :D

Comments

This entry was posted on Friday, February 27th, 2009 at 6:00 am and is filed under Oracle EBS. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

3 Comments so far

Kalyan on July 20, 2011 3:01 pm
Thanks…Works like a charm.
Boyzen on February 4, 2012 12:22 am
Perform the flowloing steps to enable a user to be an Administrator:1. Put a line in the SQLNET.ORA file as follows (by default is in there):SQLNET.AUTHENTICATION_SERVICES = (NTS)2. Create a local windows group “ORA_DBA” OR “ORA_sid_DBA” (‘SID’ is your DB service identifier and is uppercase)3. Create a local user in Windows, typically called “ORACLE”.4. Add the local user created to be a part of the “ORA_DBA” or the “ORA_sid_DBA” created group in step 2.5. Start the Registry Editor (“regedit” on the command prompt and search for a variable called “LOCAL” in the Oracle Home: Unset it.
Adarsh Reddy on April 5, 2012 3:13 pm
Thank you! I faced the issue I solved it.