1. Security Guide
  2. Securing Oracle Banking Payments
  3. Oracle Banking Payments Controls
  4. Access Enforcement

Access Enforcement

Access management in Oracle Banking Payments can be done in four steps:
  1. Branch level — in such a case the user cannot view even the menu list of the FCUBS when he tries to login into the restricted branch. Thus, no transactions could be performed.
  2. Roles wise — as described above basing on the user-roles mapping, the user can access different modules in FCUBS. For an example, a bank clerk will have access to customer creation, account opening, term-deposits opening and liquidation screens, but he will not have access to SMDUSRDF UI, which is for user creation.
  3. Function-ID wise — here, the user can be restricted to launch even the UI on clicking on the menu list.
  4. Product/ Account class wise — here, the user can be prevented access to certain account classes or products. This will disable him from creating any accounts or transactions using those prevented account class and product respectively.

Parent topic: Oracle Banking Payments Controls