In this post we’ll talk about Oracle Fusion Roles Assignment. We all know that in Oracle EBS, we give anyone access through responsibility, and within responsibility, we give them access to Reports and Oracle Forms, such as which Oracle Module Forms they can access, and we also set Data Groups to provide security based on Application. However, in Fusion, this concept is completely absent. Responsibility, Request Groups, Functions, and Data Groups are all part of R12, but Oracle has introduced a new concept of roles in Fusion. Oracle has given us Roles in place of responsibilities. We have access to Oracle Fusion Pages and Reports through our roles.
Oracle Fusion Roles vs EBS Responsibility
| Fusion | EBS |
| Job Roles | Menu |
| Duty Role | Submenu/Functions |
| Data Role | Job Role + Primary Ledger(responsibility) |
| Abstract Role | Employee |
In Oracle Fusion
- For example, if we want to grant access to Finance Manager in Fusion, we’ll create an Account Manager Job role in Fusion and assign it to the Finance Manager user.
- We have Duty Roles in Job Roles, which are the roles that a person needs to perform his or her job or job role. As a result, we assign roles based on their responsibilities.
- With the Data Security Role, we can also limit the amount of data that can be stored in roles.
- We don’t set BU access in Roles in Fusion. We set BU access in the Application User so that we can control which users have access to which BUs from the User.
- In Oracle Fusion, we can also create Custom Roles based on our business needs.
In Oracle EBS
- we uses profiles to set access t specific business unit(BU) for that responsibility.
- In EBS, we usually grant access to Reports to Request groups so that they can be assigned responsibilities. However, we are unable to create Request groups in Fusion. For that, we create privileges, which we then assign to roles.