Thursday, July 3, 2014

Security Profiles

Defining which records and information users can access is fundamental to HRMS security.

As part of your implementation plan, you identify who will use Oracle HRMS, what information they require, and how they use it. You can control a user's access to database elements such as records, fields, forms, and functions, and you can also control a user's access to other user records and data.

All Oracle Applications users access the system through a responsibility that is linked to a security group and a security profile. The responsibility is the primary means of defining security. The security group determines which business group the user can access. The security profile determines which records (related to organizations, positions and payrolls) the user can access within the business group.  For example, you can restrict a manager's security permissions so that the manager can only access the person records for those employees and workers within a supervisor hierarchy. This restriction enables secure, reliable data access and ensures that only people with the correct permissions can access personal data.

In general, a user can only view the records for one business group at a time. However, depending on the value of the HR:Cross Business Group Profile option, you can view specific information across business groups.

Within a business group you can control: Who the user can access, using security profiles. You can restrict access by:

1)Organization Security
2)Position Security
3)Supervisor Security
4)Payroll Security

Steps to create security Profiles

Step1:

US HRMS Manager >> Security >> Profile


Step 2: Create one security profile with Organisation List




Step 3: Go to System profile by copying your security profile (Test_security)

System Administrator >> Profile >> System




Step 4:
Run the concurrent Program: Security List Maintenance

Select your responsibility >>View >> Request >> Submit a New Request >> OK>> select Security List Maintenance concurrent program



No comments:

Post a Comment