Objective:

In this article we will understand the concept of various Roles in Oracle Fusion Applications security.

Roles in Oracle Fusion Applications:

In Fusion security we will encounter following Roles:

• Duty Role
• Job Role
• Abstract Role
• Data Role
• Data Access Set

Let us understand the above roles one by one in practical terms.

Duty Roles: Data Role is also known as Application Role. Let’s say a manager has a duty of creating invoices, approving invoices or creating journals. The duty of creating /approving invoices /journals are called Duty Roles.

Job Roles: Job roles are also known as External Role. These roles are created in Authorization Policy Manager (APM). Examples of these roles are Payable Accounts Manager, Chief Financial Manager, Finance Controller, etc. Various duties will be assigned to a Job role. In other words a Job role must have duty role. For instance Payable Accounts Manager will have duty of creating invoices, approving invoices, running payment batch, etc.

Abstract Roles: When an employee is hired by a company, by default he should get a role-Employee and in case of Contractor he should get a role- Contingent worker. The functions which are assigned to them are known as Abstract Role.

Data Roles: As per business need if we don’t want UK ledger to be accessed by the user in US organisation, we take the help of data role which needs to be assigned selectively. When we create ledger or business unit, system will automatically create job role with having access to data role. When a job role when attached with a data role, the job role created is confined to that particular ledger or business unit. Once it is done the job role gets the access to data, it can perform required function related to data.

Data Access Set: Data access set is mainly related to ledger data. Let’s say within a ledger we have multiple balancing segments. On business interest we don’t want to give the access of Company 01 to the user having access to Company 02. In order to do so we have to create few data access policies. This in turn will create a data role. In other words when we create a ledger, by default it creates a role which has an access to the entire ledger. However with data access set we can restrict the access to a particular balancing segment.

Below is the pictorial representation of various roles discussed above-

Anjan Mukerji

Add comment