Hi Russell, my question is regarding the possibility of creating a query-only responsibility in Oracle Apps. I understand that there is a way to create a read-only DB account and tie that Oracle ID to the data group that eventually would use the query-only responsibility. My question is: What's the type of privileges or DB roles that particular DB account should have associated with it, in order for my query-only responsibility to work properly?
My suggestion would be to use CUSTOM.PLL to fire a WHEN-NEW-FORM-INSTANCE trigger. If the responsibility is one you want to be Query Only, then set the standard form level parameter: QUERY_ONLY = YES. I would suggest a Flex value set to store the responsibility name and ID. That way you can add or remove them without having to hard-code values in CUSTOM.PLL.
I am not up to speed on 11.5.10 forms personalization enough to say if it can be used instead of CUSTOM.PLL. I don't know if you would have to make changes to all the forms in the menu of the responsibility (which could be a lot of work). With CUSTOM.PLL, all forms use it.
Hope this helps,
Dig Deeper on Oracle E-Business Suite
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.