Apps To Fusion

In this article we will learn the usage of RBAC [Role Based Access Control] in AME. To illustrate RBAC in AME, we will create a brand new user in eBusiness Suite and will allocate the AME Roles one by one to explain the purpose behind those roles. After going through this article you will learn that RBAC not only controls the menus that are visible in AME Responsibilities, but RBAC also controls the data that is visible to the AME User.

Two responsibilities must be added to the user, in order for them to be able to configure AME approval processes.
    Approvals Management Administrator
    Approvals Management Business Analyst

You will note that, even though the responsibilities have been attached, the user does not have access any menu within AME responsibilities.
Therefore some roles must be allocated to the user, so that they can access the menu items required for AME.
These steps for are illustrated using the video link as shown below
Click here to see this video
After see the above video, you will learn that
    -- AME Menu's and Functions are now available to the user AME_USER [used in this example]
    -- Even though the screens are available, but user AME_USER is unable to view any of the AME data.


As seen in video above, we are using responsibility named "User Management" to allocate the desired roles to the user. However you can also use Functional Administrator to attach the roles.
Another very important thing you will notice from the above video is that, the user AME_USER has access to AME menus after the roles were granted via RBAC, however they still do not see anything "AME Transaction Types". In order for AME Transaction Types to be visible, some additional grant must be created. These steps are detailed in video link below.
Click here to see this video

After following the steps in both these videos you will be able to create an AME User with desired access to AME Functionality.

In the above video you learnt
    --How the data is being secured in AME using RBAC
    --Steps for implementing the RBAC Transaction Type for AME
    --In the above example we have assigned all the transaction types. You may decide to selectively grant specific transaction types to a role.