Oracle System Administrator

Role of Oracle System Administrator Module

Ø There is no specific person acting as an System Administrator In Oracle Application Product. This Module is highly used by the Apps DBA consultants to manage the User Logins and to Control the Concurrent Program Managers. Apart from this the Higher Senior Level Managers use this Module to provide rights to update the Profile Options, Creation of Custom Responsibilities, Monitor Audit Controls, Configuration of Printer Program, Registration of the Custom Programs, Forms and Reports

  

Define New Users

Ø The Login ID or User Name is must for the people accessing into Oracle Application either a Business Team or Consultants. The Login User Name is not suppose to be Shared

Ø The Login Name can be provided to the organization customers / Suppliers to access the Self Service Application like i-Receivables, i-Procurements, i-Supplier Portal

Ø Mostly all the Employees will be provided a separate login Name to access the i-Expense Module

Ø Each Login User Name will be assigned the respective Responsibility based on their nature of the designation and Roles.

Ø For ex., Finance Team will be accessing all the Financials Modules and SCM Team will be accessing all the SCM Modules, CFO can have responsibility related to General Ledger Module

Ø Once a User Name is created, we can’t able delete those Login ID, we can Inactive those ID if not in Use.

Ø The Login Name or User Name should be always associated with an Employee or Supplier or Customer Contact Person.

Ø Navigation: Security > User > Define

Ø User Name, Password, Description, Password Expiry, Employee Name is required at the Header Level

Ø Line Level we can assign the List of Responsibilities to be accessed by those Users

Responsibility

Ø A Responsibility is the Physical look and Feel of the Oracle Application Modules

Ø A Particular Module like Oracle Payables is separated by Responsibilities like Payables Manager, Payables Controller, Payables End Users based on the Business Team Activity

Ø There are so many predefined Responsibilities provided by default we can make use of those responsibilities if it’s satisfy our requirement

Ø We can also create a Custom Responsibility like ABC India Payables Manager, ABC India Payables Controller etc.,

Ø To Create a New Responsibility there components are required

Data Group – used to Connect to your Data Base (Mostly Standard)

Menu Group – The Menu or Function (Forms)

Request Group – The Concurrent Programs or Reports

Ø The Physical Feel of the 3-Tier Architecture can be highly visible through accessing the Responsibility

Ø Once the User Login into the System, the Personal Home Page (PHP) Screen list all the applicable Responsibility assigned to those users. So that Users Click on a Particular Responsibility, then system connects to the Application Tier and Data Base Tier by default.

Ø Exclusion Criteria – To Restrict a Particular Form or Menu or Sub Menu we can make use of the Exclusion Criteria. To Hide certain functionalities to the Users this option is highly used rather than customize a New Menu Group

Ø Exclude a Form (Functions)

Ø Exclude a Form Components (Like Posting Button)

Ø Exclude a Menu (Menu Name – Like Setup Menu)

Ø Exclude a Sub Menu (A Particular Sub Menu Functions)

Profile Options

Profile Option is one of the Important concepts in the entire Oracle Application to Control certain Objects.

Ø Profile Options set the Behavior of the Application or Module or Responsibilities.

Ø All the Profiles are grouped based on Modules and it is predefined by Default

Ø Each Profile Name is used for a certain activity

Ø You can Set the Profile Options in the following Manner

1.     Site Level – Lowest Level

2.     Application Level – For a Specific Module

3.     Responsibility Level – For a Specific Responsibility

4.     User level – For a Specific User Name

Ø The User Level is the Highest Priority which overrides the other 3 Levels.

Ø Mostly the Profile are configured at Site Level or Responsibility Level

Ex., GL: Ledger Name, MO: Operating Unit, HR: Business Group

Security Levels

1.     Functional Security – Restriction of Certain Functions / Menu / Sub Menu. This is done through the Exclusion Criteria concepts in the Responsibility Screen

2.     Data Security – The Data Security is at Table Level. This is highly used in the Self Service Application Module. For Ex.,

Ø A Responsibility like i-Supplier Portal is assigned to multiple Vendors through a separate login Name

Ø While a Vendor is accessing these Responsibility, only Data related to his transactions should be accessed by these Vendor. Overall all the Data of the vendor transactions is available in a Single Table. While accessing through a Login Name the data automatically gets filtered and display those transactions which is applicable for those Login Name.

Ø This can be configured through Security Attributes for Rows and Exclusive Attributes for Columns

3.     Role Based Security – The Role Based Access Control (RBAC) is used to provide certain functionalities based on the Roles of the business. For Ex., Buyer is a Role in Purchasing Module, where as a certain Employees can be assigned as a Buyer to Create the Purchase Order. Not anyone can create a Purchase Order, only those who assigned as a Buyer can only able to create the PO’s even though other have access to those Modules

Ex., In Project Accounting Module, One Employee can be assigned as Project Manager in One Projects, so that he has all the rights to update the resource list, budgets and the same employee can be assigned as Project Administrator in another Project with some limited controls.