Responsibility Ownership

The Responsibility Ownership function enables you (as an administrator or implementor) to view a list of owned responsibilities. You can expand the list of responsibilities to display the menus and functions attached to each responsibility. From the list of responsibilities, you can see the number of people with access to each responsibility both within the organization (in other words, within your HR security access environment) and outside of the organization (outside of your HR security access environment). By clicking on the number of people, you can display the user ID and other information for each user with access to the responsibility and if required, you can revoke access directly in the self-service page. If you choose to revoke access to a responsibility, the affected user receives notification of the change.

Additional Information: When the application generates the notification, it also triggers a business event. You can subscribe to this business event and call Application Programmatic Interfaces (APIs) to end date the responsibility access.

See: Event Subscriptions

You can use the Responsibility Ownership functionality as an extra security measure to review and restrict the number of people outside of your organization with access to particular responsibilities. You can also monitor the number of people with access to each responsibility for auditing purposes.

Menu and Function Names

You access this module can be accessed from the following menus and functions:

User Menu Name Function Name
Responsibility Ownership Responsibility Ownership

Workflow

The workflow details for this module are listed below:

Workflow Process Display Name:

Not applicable

Configurable Workflow Attributes:

Not applicable

Configurable Profile Options

Not applicable

Additional Configuration Steps

  1. Before you can use the Responsibility Ownership function, you must create data security grants to link responsibilities to your users.

    See: Creating Data Grants for Responsibility Ownership

    See: Create Data Grant (Oracle Applications System Administrator's Guide)

  2. You should create code to subscribe to the following business event:

    This code should trigger the fnd_user_resp_groups_api.update_assignment API to end date the responsibility assignment.

    See: Sample Code for Subscribing to Business Event (Responsibility Ownership)