Use the following setup steps if your enterprise wants to enable many business groups for one responsibility.
Note: You only need to perform steps 1 and 2 when you first implement Oracle HRMS security. You can perform the other steps at any time.
You can update your security model from Standard HRMS Security to Security Groups Enabled security by following these steps.
Attention: Once you have changed to Security Groups Enabled Security you cannot revert to the Standard Security model.
To set up users for Security Groups Enabled Security:
Set the Enable Security Groups Profile Option using the System Profile Values window.
Ensure the Enable Security Groups profile option is set to Yes at the application level for Oracle Human Resources.
Note: If this option is set to No then you are not using Security Groups Enabled security.
See: System Profile Values.
Run the Enable Multiple Security Group Process using the Submit Request window.
You must run the Enable Multiple Security Group process to set up Oracle HRMS to use security groups.
See: Submitting a Request
Warning: The creation of security groups is more complex with Oracle HRMS 11.5.10 and later releases. For this reason, the Enable Multiple Security Group process may appear slow, particularly if you have a large number of business groups.
The Enable Multiple Security Group process sets the Enable Security Groups profile option to Yes for all HRMS applications. We strongly recommend that you do not change the value of this profile option to another value.
Note: For each restricted security profile you create that references a reporting user, you must run the Generate Secure User (SECGEN) process. This is a one off process that is not required for view all security profiles.
Ensure that the functions or menus you require are set up.
This is required for the responsibility. For menu functions calling configured forms or task flows, you must enter a parameter in the Parameter field of the Form Functions window.
See: Set Up Menus.
See: Defining Menus.
Ensure that the request group you require is set up.
You can define the groups of standard reports and processes that a user can run from the Submit a New Request window. Every responsibility can have access to one request group.
Use the Request Group window.
See: Request Group window
Define a responsibility using the Responsibility window.
Set the HR User Profile Options for the new responsibility using the System Profile Values window. You must set up the HR: User Type option.
You can also set the HR:Cross Business Group Profile option. This enables you to view some information across all business groups within your enterprise. See HR:Cross Business Group Profile option for more information.
Note: For Security Groups Enabled security donot set up or amend the HR:Security Profile profile option or the HR: Business Group profile option using the System Profile Values window. To set up or change this profile option use the Assign Security Profile window.
You can set also set up other User Profile Options.
Create usernames and passwords using the User window.
Attention: Do not link responsibilities and security groups (business groups) to users in this window. Instead, use the Assign Security Profile window. If you do enter a responsibility and security group in this window, you still need to use the Assign Security Profile window, to link your user to a responsibility and security profile. If you do not use the Assign Security Profile window, the default view-all security profile is used and your user will be able to see all records in the business group.
See: Users Window
End-date unwanted user responsibilities linked to Standard security group
When you first enable security groups and run the Enable Multiple Security Groups concurrent process, the process creates two sets of records for existing user/responsibility pairs:
For each responsibility connected to a user it creates a record linking the user, the responsibility and the Standard security group.
For each HRMS responsibility connected to a user it creates a record linking the user, the responsibility, the security group associated with the business group, and the security profile.
If you are updating from Standard security, there may be many such records. For each existing user responsibility with a security group value of 'Standard', decide whether the user requires access to the responsibility. Users who may need to update global lookup codes need access to the Standard security group.
In most cases, users will not require access to the Standard security group. In this case, enter an end date to remove access to the responsibility. This reduces the number of responsibilities the user sees on logging in, and prevents users from accidentally entering data into the wrong business group.
Note: By default, the Standard security group is associated with the Setup business group.
Use the Users window.
See: Users Window
Associate a security profile with a user, responsibility and business group using the Assign Security Profile window.
Run system security process using the Submit Request window:
Security List Maintenance
Ensure this process is run every night.