How to Create Responsibility in Oracle Apps

A responsibility lets you control what (forms / reports) a user can access when logged into it. A responsibility will have one main menu. Under that main menu you can have other sub menus or functions.

It is basically a predefined set of data, menus, and forms that define your particular level of authority while using the system.

Each Responsibility provides you access to an application, menus and a set of functions through online screens.

The Oracle Application menus present only the functions for which your Responsibility is given permission.

Each user has at least one responsibility and several users can share the same responsibility.

Choose your initial responsibility from your Home Page. Within the Oracle Applications window, you can change your responsibility by clicking the Switch Responsibilities button or select

File > Switch Responsibility from the menu bar.

When you login to System Administrator responsibility, First of all, you will see a lot of menus.

For Example a particular user has only limited access it may be only two forms – Users form and Responsibility form.

For this, you need to create a Custom menu that has only two forms – Users and Responsibility.
1. Create a Custom Menu

For this you can review article How to Create Menu in Oracle Apps.

After this you know that a custom menu MY_ACCESS Menu has been created.

2. Creating a New Responsibility

To create a new responsibility navigate to

System Administrator > Security > Responsibility > Define

Responsibilities form will open enter the below details:
Responsibility Name:

If you have multiple responsibilities, a pop-up window includes this name after you sign on. Set meaningful name for the new responsibility. Users will see this name in the responsibilities list.

Application:

This application name does not prevent the user of this responsibility from accessing other applications’ forms and functions if you define the menu to access other applications. Since this is a custom responsibility, give in the custom application name.
Responsibility Key:

This is a unique name for a responsibility that is used by loader programs. It is a short name for this responsibility for internal use.
Description:

It’s a meaningful description that expresses the need for this responsibility.

Available From:

From what Oracle Application system, this responsibility can be accessed from. A responsibility may be associated with only one applications system. Select from three.

Menu:

The menu you want to see under this responsibility and it must already be defined with Oracle Applications. As, we already defined MY_ACCESS Menu

Web Host Name

If your Web Server resides on a different machine from your database, you must designate the host name (URL) here. Otherwise, the Web Host Name defaults to the current database host server.

Web Agent Name

Enter the PL/SQL Agent Name for the database used by this responsibility. If you do not specify an Agent Name, the responsibility defaults to the agent name current at log-on.

Effective Dates:

It is the date range during which the user can access this responsibility. You can enter the start/end dates on which the responsibility becomes Active/Inactive.

The default value for the start date is the current date, and if you do not enter an end date, the responsibility is valid indefinitely.

Note: You cannot delete a responsibility because its information helps to provide an audit trail. You can deactivate a responsibility at any time by setting the end date to the current date. If you wish to reactivate the responsibility, change the end date to a date after the current date, or clear the end date.

Request Group:

It is used to set what reports or concurrent requests the user can run from this responsibility. If you do not assign a request security group to this responsibility, a user with this responsibility cannot run requests, request sets, or concurrent programs from the Submit Requests window, except for request sets owned by the user
Data Group:

The data group defines the pairing of application and ORACLE username. Select the application whose ORACLE username forms connect to when you choose this responsibility to access the underneath database tables.

Menu Exclusions Block: Define function and menu exclusion rules to limit the application functionality available to a responsibility.

• Type: Select either Function or Menu as the type of exclusion rule to apply against this responsibility.

• Name: Select the name of the function or menu you wish to exclude from this responsibility. The function or menu you specify must already be defined in Oracle Applications.

Securing Attributes:

Use the List of Values to select valid attributes. You may assign any number of securing attributes to the responsibility.

Excluded Attributes

Use the List of Values to select valid attributes. You can assign any number of Excluded Attributes to a responsibility.

In Menu field, you will add the menu that you created above in Step-1

Your new responsibility with own Menu has been created.

Now, you can assign this custom Responsibility to any User for access. To Review how to assign a Responsibility to a user: How can create a User in Oracle Apps R12

Menu Exclusion
Suppose, if you want to exclude Users and Responsibilities form from your custom responsibility which you created above, you can do it very easily. Open same Responsibilities form,

Navigation: System Administrator > Security > Responsibility > Define
Find your custom responsibility “Oraclegeeks Access Resp”

In Menu Exclusions tab, enter that form details which you want to exclude like below.

Type:

• If you want to exclude a menu then you will choose Menu.
• If you want to exclude a form then choose Function.

Name: Type in the Menu name / function name which you want to exclude.Save your work. That Menu/Form will be excluded from the responsibility.