Apps To Fusion

Security in Oracle HRMS controls the list of Employees that are visible to a given user from “Employee/Person Screen”.

Why do we need security?
In oracle HRMS, most of the data must be secured under data protection act. Your date of birth is one such example. Plus also, it is not nice for a system to make salary information etc visible to everyone [just because they have access to responsibility]


In this article, I will discuss the Standard HRMS security model and at the end of this article, I will explain the alternate Security Model in Oracle HRMS.
The alternate Security Model is required to overcome the limitation of standard[basic]security model design..


From a Responsibility, I wish to show people that work in just IT department: How do I do it?
Firstly you must have an Organization Hierarchy in place, let's say that will have structure similar to below:-
"XX Passi-Corp Hierarchy"   --Lets say this is the name of the Org Hierarchy.

XX Passi-Corp   --Top level organization
  ---XX Finance
        --XX Credit control
        --XX debt manager
        --XX customer relationship
  --XX IT
      --XX IT Technical
           --XX IT Technical Support
           --XX IT Development
    --XX IT Functional Support
    --XX IT Business analysts

Now lets assume you have an IT Head(overall), and also "IT Technical Head of Department".
You want to create a Responsibility from which only those people that work in following Departments can be queried.
XX IT Technical
    XX IT Technical Support
    XX IT Development


We will do the below steps to accomplish this business requirement:-
1. Define a Organization Hierarchy
2. Define a security Profile that is attached to node “XX IT Technical” of the Hierarchy
3. Attach this security profile as a profile option to our responsibility named “XX HRMS IT Technical Resp”
4. Run the concurrent program “Security List Maintenance”.



Now, I am going to explain the above steps by means of screenshots[don't I love them] :-

Step 1. Define a Organization Hierarchy



Step 2. Define a security Profile that is attached to node “XX IT Technical” of the Hierarchy





Step 3. Attach this security profile as a profile option to our responsibility named “XX HRMS IT Technical Resp”


Step 4. Run the concurrent program “Security List Maintenance”.
No screenshot needed here.

 
Now some notes :-
1. This article discussed the "Standard Security Model" in Oracle HRMS. In this security model, you will need to create One Responsibility per Security Profile. This is the limitation of this Security Model.
2. You can also create a Security Profile that uses a Custom Security via "SQL Statements". Alternately create a security model on Positions, Payroll etc [see screenshot for details]
3. The difference between PER_PEOPLE_F and PER_ALL_PEOPLE_F is that former is a view that filters on Security Profile [on the basis of logged in user/ responsibility ]
Whereas PER_ALL_PEOPLE_F is a table[no security filtration on table].
4. If you do not wish to use “Standard Security Model”, then you can use “Security Groups” feature.
For this you can set Profile Option “Enable Security Groups” to Yes.
Next, you can assign different Security Profiles to specific users [though for same Responsibility].
Hence you will be able to reuse the responsibility, and hence overcoming the limitation discussed as above.
See the screenshot below.

< Prev		Next >