It sometimes happens in Oracle E-Business Suite that changes you did, presented by the system in HTML or OA Framework pages, are not directly visible – also not when you logout and in.
For example when you assign a new responsibility to an user or when you re-enable an existing responsibility by removing the enddate it might happen that these changes are not directly reflected in the pages of the user – hence he’s not able to select his new responsibility.
Show invisible responsibilies (because they should be active)
When responsibilities are not visible to the end-user but they are active according to the user responsibility settings, eBS lost it a little. There are a number of options to fix this. If you have the privileges try option 4 first 8-D.
1) Run concurrent program Synchronize WF LOCAL tables from responsibility System Administrator with the below parameters.
2) Run concurrent program Workflow Directory Services User/Role Validation from responsibility System Administrator with the below parameters.
3) Put and end-date in the future on the missing responsibility – like 31-DEC-4712. This will trigger the system to synchronize.
4) Try to clear the OA Framework cache – in most cases this will fix your problem. Clearing OA Framework cache can be done from responsibility Functional Administrator. Follow the below steps to dump the cache.
a) Open up Functional Administrator and go to tab Core Services.
b) Open subtab Caching Framework.
c) Click on the number link after Total Cache Components.
d) Do a search on Name USER_INFO_CACHE.
e) Select USER_INFO_CACHE by ticking the checkbox and press Clear Cache. The User Info cache is cleared. The user should see all his active responsibilies now.
OA Framework personalizations not showing
When you’re doing some personalizations on OA Framework screens like changing labels, disabling rendering of tables, graphs etc or changing seeded views it might happen that those changes are not directly reflected in your pages due to caching. When this happens try the above option 4 to fix.
If the system did go mad completely and the above tricks were not succesfull – a bounce of Apache may work also.
