Again I appreciate your visit. Hope to see you again and again! Your email address will not be published. Yes, add me to your mailing list. Notify me of follow-up comments by email. Notify me of new posts by email. This site uses Akismet to reduce spam. Learn how your comment data is processed.
Skip to content. Fill in the required information Explanation of all fields An application name and a responsibility name uniquely identify a responsibility. Responsibility Name Give the name of the responsibility.
It should be unique. Application An application that owns the responsibility. Responsibility Key The internal key for the responsibility that is used by loader programs, concurrent programs that load messages, user profiles, user profile values, and other information into Oracle E-Business Suite tables.
The responsibility key is unique per application. Below characters should not be added in the responsibility keys:! Description: Meaningful description that conveys the need for this responsibility.
Effective Dates: The date range during which the user can access this responsibility. Available From: From what Oracle Application system, this responsibility can be accessed from.
Menu: The menu you want to see under the responsibility. Request Group: What reports or concurrent requests the user can run from this responsibility. Select the application whose ORACLE username forms connect to when you choose this responsibility to access the underneath database tables.
Log in as the above user and get into the responsibility erpSchools Access Resp. You will see only two forms under the custom responsibility — Users and Responsibility. Under Menu Exclusions tab, give in the form details and save. Cookie and Privacy Settings. How we use cookies. Essential Website Cookies. Check to enable permanent hiding of message bar and refuse all cookies if you do not opt in.
We need 2 cookies to store this setting. Otherwise you will be prompted again when opening a new browser window or new a tab. Google Analytics Cookies. Other external services. Other cookies. Privacy Policy. You can read about our cookies and privacy settings in detail on our Privacy Policy Page. Accept settings Hide notification only.
Responsibilities and Access Control A responsibility corresponds to a set of views. Note: Modifying visibility or responsibility settings for an application can in some cases require that the associated Application Object Manager AOM be restarted in order for these new settings to take effect for users of the Siebel Web Client. If you have only modified responsibilities, then you can clear cached responsibilities instead, without restarting the Application Object Manager.
For more information, see "Clearing Cached Responsibilities". About Associating a Responsibility with Organizations You can associate a responsibility with one or more organizations. Note: Associate each responsibility with at least one organization if you include views that use either position or organization access control in the responsibility.
A view with All access control can cause unpredictable and possibly undesirable results for a mobile user. Related Topic "Responsibilities and Access Control". To assign a responsibility to a Person Log into a Siebel employee application as an administrator. Navigate to the Administration - User screen, then the Persons view. The Persons list appears. Select a Person record. In the form, click the select button on the Responsibility field.
A list of the responsibilities assigned to this Person appears. In the Responsibilities list, click New. A list of responsibilities available for assigning appears. Select one or more responsibilities, and then click OK. The selected responsibilities appear in the list of responsibilities for this Person. Click OK.
0コメント