Oracle® Fusion
Applications Coexistence for HCM Implementation Guide 11g Release 1 (11.1.3) Part Number E20378-01 |
Contents |
Previous |
Next |
This chapter contains the following:
Implementation Users for HCM Coexistence: Explained
Creating a Data Role for an Implementation User: Worked Example
You perform the following Oracle Fusion Functional Setup Manager (FSM) tasks to create implementation users who can complete the setup of HCM coexistence:
Create Implementation Users
Create Data Role for Implementation Users
Provision Roles to Implementation Users
To perform these tasks, you must have the IT security manager role. Depending on how you are implementing HCM coexistence, a local security administrator or your service provider (for example, Oracle On Demand) may perform these tasks.
The implementation user is a user name and password for the person or people who will be performing the Oracle Fusion FSM tasks for the HCM coexistence offering. Implementation users do not need to be associated with HCM person records.
You perform the Oracle Fusion FSM task Create Data Role for Implementation Users to create an HCM data role for the application implementation consultant job role.
This data role must have view-all access to all HCM data resources that are relevant to the application implementation consultant job role. When creating the data role, you provide this access by selecting an appropriate predefined security profile for the HCM object type. For example, to provide access to all organizations, you select the predefined security profile View All Organizations.
Implementation users cannot perform the Oracle Fusion FSM tasks for HCM coexistence until relevant data roles are provisioned to them.
You provision the following roles to implementation users:
IT security manager job role
The data role created for the application implementation consultant job role
Important
When the implementation of HCM coexistence is complete, you are strongly recommended to revoke these roles from implementation users. The level of access that they provide to HCM data is generally unnecessary outside the implementation phase and may constitute a security exposure.
This example shows how to create an HCM data role for an HCM coexistence implementation user.
The following table summarizes key decisions for this scenario.
Decisions to Consider |
In This Example |
---|---|
What is the name of the HCM data role? |
HCM Coexistence Application Implementation Consultant |
Which job role will the HCM data role include? |
Application Implementation Consultant |
Which person records do implementation users need to access? |
All |
Which public person records do implementation users need to access? |
All |
Which organizations do implementation users need to access? |
All |
Which positions do implementation users need to access? |
All |
Which countries do implementation users need to access? |
All |
Which legislative data groups do implementation users need to access? |
All |
Which document types do implementation users need to access? |
All |
Which payrolls do implementation users need to access? |
All |
Which payroll flows do implementation users need to access? |
All |
Create the HCM data role by:
Naming the HCM data role and selecting the associated job role
Selecting the appropriate predefined security profile for each HCM object type
Reviewing and submitting the new HCM data role
Field |
Value |
---|---|
Data Role |
HCM Coexistence Application Implementation Consultant |
Job Role |
Application Implementation Consultant |