November 20, 2008

11i/R12: Not a valid responsibility for the current user

After attaching a responsibility to a user often used to receive,

"XXXX is not a valid responsibility for the current user. Please contact your System Administrator."

And the attached responsibility will not appear in the Home Page until you bounce the apache. It appears from 11i.FND.H to 12.0.4

We ran into many SR's while working with different customers at different patch levels.

According Note: 374309.1 Newly added responsibility is not displayed until Apache is bounced, after applying ATG RUP3 or ATG RUP4,

It is because of delayed processing of changes through the Apache Java Cache mechanism.

Normally when you are adding a responsbility to a user or end date a responsibility it fires considerable number of business events like,

  • oracle.apps.fnd.wf.ds.userRole.created
  • oracle.apps.fnd.user.role.insert
  • oracle.apps.fnd.wf.ds.userRole.updated, etc.,

If the Workflow Deferred Agent Listener and Workflow Java Deferred Agent Listener are not running, then these business events will not get processed.

Then we will face the above said error. Hence, It is necessary to ensure the below Workflow Service Components are up and running (OAM -> Workflow Manager -> Service Components) as one of the verification checks,

  • Workflow Deferred Agent Listener
  • Workflow Java Deferred Agent Listener

1 comment:

Anonymous said...

Hi,


Both the listeners are up and running but the still the same problem we have even after running create wf_roles ... request on R12 any idea ??

Regards

Balakrishna.