Functional

Mapping Oracle E-Business Suite HRMS Data for HCM Coexistence:

You use Web Applications Desktop Integrator (Web ADI) spreadsheets to map Oracle E-Business Suite Human Resources Management Systems (HRMS) objects to Oracle Fusion objects. Only when this mapping is complete can you import E-Business Suite HRMS data into Oracle Fusion. You can find complete instruThis topic provides a summary of the Web ADI spreadsheet review and completion tasks, for which you use the E-Business Suite HRMS responsibility HCM Coexistence Manager. Functions in the documents Integrating Oracle HRMS 12.1 with Oracle Fusion Talent Management and Workforce Compensation and Integrating Oracle HRMS Release 11i with Oracle Fusion Talent Management and Workforce Compensation.

Identifying Business Groups for Integration

You perform the task Identify Business Groups for Integration. In the Web ADI spreadsheet invoked by this task, you indicate, for each business group in the E-Business Suite HRMS instance, whether its data is to be integrated with Oracle Fusion.
Once this task is complete, you can import cross-reference data from Oracle Fusion and complete the mapping task.

Mapping E-Business Suite HRMS Data to Oracle Fusion

You perform the Define Mapping task (Release 12.1) or the Setup: Mapping function (Release 11i).
The purpose of the mapping task is to ensure that:  
Every E-Business Suite HRMS data value has a corresponding Oracle Fusion data value.  Every Oracle Fusion data value is accounted for in the mapping.
The mapping activity comprises several mapping subtasks, for each of which you complete a Web ADI spreadsheet. The following table summarizes the mapping substasks .

Once the mapping subtasks are complete, you perform the task Process and Validate to ensure that the mapping selections made for specific subtasks are valid.

Once the mapping is successfully validated, you can extract E-Business Suite HRMS data for delivery to Oracle Fusion. For this task, you use the E-Business Suite HRMS responsibility HCM Coexistence Integrator.      

Mapping PeopleSoft HRMS Data for HCM Coexistence:  

You use Domain Value Maps (DVMs) to map Oracle PeopleSoft HRMS objects to Oracle Fusion objects. Only when this mapping is complete can you import PeopleSoft HRMS data into Oracle Fusion. This topic provides a summary of the DVM review and completion tasks. You can find complete instructions in the PeopleSoft HRMS document Integrating PeopleSoft HRMS 8.9 with Fusion Talent and Workforce Compensation.

Understanding System Data Codes in DVMs

PeopleSoft HRMS supplies multiple DVMs. Each of the supplied DVMs has a system data code that identifies whether the DVM contains system data values (equivalent to predefined values in Oracle Fusion). The system data code also specifies how to complete the DVM definition such that:  
Every PeopleSoft HRMS data value has a corresponding Oracle Fusion data value.  
Every Oracle Fusion data value is accounted for in the mapping.
Unless you review and complete the DVMs, data cannot be imported successfully to Oracle Fusion.
Completing the DVM Definitions
For this activity you work in both PeopleSoft HRMS and Oracle Fusion. You also need the .dat files from the Generate Mapping File for HCM Business Objects process in Oracle Fusion.
The following table summarizes how to complete the DVM for each system data code.

Synchronization of User and Role Information with Oracle Identity Management: How It Is Processed?

Oracle Identity Management (OIM) maintains Lightweight Directory Access Protocol (LDAP) user accounts for users of Oracle Fusion Applications. OIM also stores the definitions of abstract, job, and data roles, and holds information about roles provisioned to users.
Most changes to user and role information are shared automatically and instantly by Oracle Fusion Human Capital Management (HCM) and OIM. In addition, two scheduled processes, Send Pending LDAP Requests and Retrieve Latest LDAP Changes, manage information exchange between Oracle Fusion HCM and OIM in some circumstances.   
Send Pending LDAP Requests sends to OIM bulk requests and future-dated requests that are now active.  
Retrieve Latest LDAP Changes requests from OIM changes that may not have arrived because of a failure or error, for example.

<-->


Settings That Affect Synchronization of User and Role Information

You are recommended to run the Send Pending LDAP Requests process at least daily to ensure that future-dated changes are identified and processed as soon as they take effect. Retrieve Latest LDAP Changes can also run daily, or less frequently if you prefer. For example, if you know that a failure has occurred between OIM and Oracle Fusion HCM, then you can run Retrieve Latest LDAP Changes to ensure that user and role information is synchronized.
When processing bulk requests, the batch size that you specify for the Send Pending LDAP Requests process is the number of requests to be processed in a single batch. For example, if you specify a batch size of 25, 16 batches of requests will be created and processed in parallel if there are 400 requests to be processed.

How Synchronization of User and Role Information Is Managed  

Synchronization of most user and role information between Oracle Fusion HCM and OIM occurs automatically. However, when you run Send Pending LDAP Requests to process future-dated or bulk requests, it sends to OIM:   
Requests to create, suspend, and re-enable user accounts.
When a person record is created in Oracle Fusion HCM, OIM creates a user account automatically. When all of a person's work relationships are terminated and the person has no roles, the person's user account is suspended automatically. If the person is subsequently rehired, the suspended account is automatically re-enabled.  
Role provisioning and role deprovisioning changes for individual users.  
Changes to relevant person attributes for individual users.  
New and updated information about HCM data roles, which are created in Oracle Fusion HCM.
The process Retrieve Latest LDAP Changes sends to Oracle Fusion HCM:  
Names of new user accounts .
When a person record is created in Oracle Fusion HCM, OIM creates a user account automatically and returns:
o The user account name and password. If the user's primary work e-mail address was entered when the person record was created, then the user account name and password are returned to the user; otherwise, this information is returned to the primary work e-mail address of the user's line manager. (No notification is sent if the user has no line manager or the line manager has no primary work e-mail address.)
o The globally unique identifier (GUID) associated with the LDAP directory user account, which is added automatically to the person record.  
Latest information about abstract, job, and data roles.
OIM stores latest information about all abstract, job, and data roles, including HCM data roles. Oracle Fusion HCM maintains a local copy of all role names and types so that lists of roles presented in role mappings and elsewhere are up to date.
Note
New HCM data roles are available only when OIM has returned information about those roles to Oracle Fusion HCM.  
Work e-mail addresses, if OIM owns the work e-mail address.
The values of the following person attributes are sent to OIM automatically whenever a person record is created and whenever any of these attributes is subsequently updated.  
Person number  
System person type from the person's primary assignment  
Latest start date of the current period of service  
The GUIDs of all of the person's managers  
Work e-mail address, if Oracle Fusion HCM owns the work e-mail address  
Work mobile phone number  
Work phone number  
Work FAX number  
Both the display name and the following name components in all languages in which they have been created in the person record:
o First name
o Middle name
o Last name
o Name suffix  
Both the formatted work-location address and the following components of the work-location address from the person's primary assignment:
o Address line 1
o City
o State
o Postal code
o Country code
No personally identifiable information (PII) is sent from Oracle Fusion HCM to OIM. 

User and Role Synchronization: Explained

Oracle Identity Management (OIM) maintains Lightweight Directory Access Protocol (LDAP) user accounts for users of Oracle Fusion applications. OIM also stores the definitions of abstract,   job, and data roles and holds information about roles provisioned to users. During implementation, any existing information about users, roles, and roles provisioned to users must be copied from the LDAP directory to the Oracle Fusion Applications tables. Once the Oracle Fusion Applications tables are initialized with this information, it is maintained automatically. To perform the initialization, you run the process Retrieve Latest LDAP Changes.
Note
For security and audit best practice, implementation users have person records and appropriate role-based security access. So that appropriate roles can be assigned to implementation users, you must run the process Retrieve Latest LDAP Changes before you create implementation users.
During initial implementation, the installation super user performs the task Run User and Role Synchronization Process to run the Retrieve Latest LDAP Changes process.
Tip
The user name and password of the installation super user are created during installation provisioning of Oracle Fusion Applications. For details of the user name and password, contact your system administrator or the person who installed Oracle Fusion Applications.

Creating Users and Provisioning Roles for HCM Coexistence: Explained

A user is created automatically for each worker record that you load into Oracle Fusion from your source application. User accounts are created and maintained in a Lightweight Directory Access Protocol (LDAP) directory local to Oracle Fusion by Oracle Identity Management (OIM). You must work with your service provider to configure items such as identity policy and password policy in OIM. Users have a user name and password that are specific to their use of Oracle Fusion applications. 

The process for creating users and provisioning roles to them varies according to whether you are performing an initial or incremental data load.

Creating Users and Provisioning Roles for an Initial Data Load

To create users and provision roles to them during the initial data load, you: 

1. Create the role provisioning rules required by your enterprise.
User access to functions and data is determined entirely by the roles that users have, and roles must be provisioned to users. To manage both automatic and manual provisioning of roles to users, you create role mappings. For example, you create role mappings to provision abstract roles, such as employee and line manager, automatically to all employees and line managers. If you create data roles for particular job roles, you must create role mappings to manage the provisioning of those roles to eligible users. A typical user has multiple roles. To create role mappings, you perform the Manage HCM Role Provisioning Rules task.
Note
If your initial data load includes large volumes of person and employment data, you are recommended to perform step 1 (this step) after step 3.
2. Load person and employment data. For the initial data load, you perform the Oracle Fusion Functional Setup Manager task Load HCM Data for Coexistence.
3. Run the Send Pending LDAP Requests process.
This process sends bulk requests to OIM to create, suspend, and re-enable user accounts, as appropriate.
4. Apply autoprovisioning , using the Manage Role Mappings task, to assign all roles with the Autoprovision option selected to eligible workers.
5. Manually assign roles, as appropriate.
Roles identified in your role provisioning rules as Requestable can be assigned to other workers by managers and human resource specialists who satisfy the role mapping conditions. Workers who satisfy the role mapping conditions can request for themselves roles identified in your role provisioning rules as Self-requestable.

Creating Users and Provisioning Roles for an Incremental Data Load

When you load person and employment data after the initial data load, the process for managing users and role provisioning is as follows:
1. Update role provisioning rules, if necessary.
The role mappings that you created for the initial data load may be sufficient; however, you are recommended to validate the existing mappings and make any changes before you perform an incremental data load.
2. Load person and employment data using the Load HCM Data task in the Data Exchange work area.
3. Run the Send Pending LDAP Requests process. You can schedule this process to run automatically. For example, you could schedule this process to run daily.  
4. Manually assign requestable roles, as appropriate.

Ashish Harbhajanka

Add comment