Ok, so you want to know for an user , what responsibility you should use in order to be able to perform the invocation?
Here is an example for Sysadmin user
Select usr.user_name,usr.user_id, resp.RESPONSIBILITY_NAME ,
resp.RESPONSIBILITY_KEY, grp.SECURITY_GROUP_KEY, grp.SECURITY_GROUP_ID,
From FND_USER_RESP_GROUPS furg, FND_USER usr, fnd_responsibility_vl
resp,FND_SECURITY_GROUPS grp,FND_APPLICATION APP
The query that you provided retrieves the entire set of responsibilities that a user has. But during the call to a login API, the user wont be having any responsibilities to specify in the header part of the soap request. In that case, should we be omitting the responsibility header during the login API call?
There should be the Header part and you should assign at least one valid responsibility.
The responsibility you are using to set the context and run the API from sqlplus , the same should be assign to the user when you invoke the API from WS
Thanks for the reply. I have one more doubt regarding the subject. Its about the user Login.
During login, user willnot or cannot have any responsibilities right? Also when logging in, we are logging in using default parameters as given below
function_id=1032925 resp_id=-1 resp_appl_id=-1 security_group_id=0
So when writing a login API, i was not able to find the responsibility with id = -1. Can you suggest how oracle is handling this scenario? In this case, what should be the header responsibility?