11 Define Data Mapping for Coexistence

This chapter contains the following:

Generating Mapping Identifiers for HCM Business Objects: Explained

Mapping PeopleSoft HRMS Data for HCM Coexistence: Explained

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

Generating Mapping Identifiers for HCM Business Objects: Explained

After you define all required business objects in Oracle Fusion, you must generate and export mapping identifiers for these objects. The mapping identifiers are an essential input to the data-mapping process.

To generate and export the business-object mapping identifiers, you run the Generate Mapping File for HCM Business Objects process from the Manage HCM Configuration for Coexistence page. This process creates .dat files containing Global Unique Identifiers (GUIDs) for each business object. The .dat files are packaged automatically in a zipped data file that is written to the FTP server. The system administrator for your source application retrieves the zipped data file so that you can create data mappings in the source application.

Note

Whenever you create additional records in Oracle Fusion for the mapped business objects, you must rerun the Generate Mapping File for HCM Business Objects process to generate additional GUIDs. The system administrator for your source application can then update the mappings with the new values.

For more information on creating the Domain Value Maps (DVMs) in PeopleSoft HRMS, see Implementing PeopleSoft HRMS 8.9 with Fusion Talent and Workforce Compensation, and Integrating PeopleSoft HRMS 8.9 with Fusion Talent and Workforce Compensation.

Mapping PeopleSoft HRMS Data for HCM Coexistence: Explained

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.

System Data Code	Meaning
PF	The DVM contains both PeopleSoft HRMS system data values and their corresponding Oracle Fusion values. No action is required unless you need to modify any of the delivered values.
P	The DVM contains PeopleSoft HRMS system data values only. You must: Verify the delivered values. Review the equivalent Oracle Fusion values in Oracle Fusion. Add PeopleSoft HRMS values that have no existing Oracle Fusion equivalents to the Oracle Fusion lookup type. For example, for the DVM PERSON_HIGHEST_EDU_LEVEL_CODE, review the PeopleSoft HRMS values in the DVM and compare them with the values in the Oracle Fusion lookup type HIGHEST_EDUCATION_LEVEL. You add PeopleSoft HRMS values that have no existing Oracle Fusion equivalents to the Oracle Fusion HIGHEST_EDUCATION_LEVEL lookup. To complete the mapping you add all of the Oracle Fusion values to the DVM, including any that you added to the lookup type, using the PeopleSoft HRMS Populate Domain Value Maps page.
M	The DVM contains neither PeopleSoft HRMS nor Oracle Fusion system data values. This system data code identifies values such as action and action reason codes that exist in Oracle Fusion only. To populate this DVM, you need to import the Oracle Fusion values. You: Review and manually modify the file of mapping identifiers (the .dat file) that was created by running the Oracle Fusion Generate Mapping File for HCM Business Objects process. Save the modified .dat file as a .csv file, and import the values into the DVM using the PeopleSoft HRMS Import Value Maps page.
N	The DVM contains neither PeopleSoft HRMS nor Oracle Fusion system data values. The PeopleSoft HRMS values exist, but not as system data values. To populate the DVM, you: Retrieve the PeopleSoft HRMS values using the SQL script supplied in the DVM. Compare the PeopleSoft HRMS values to those in the corresponding Oracle Fusion lookup. Add PeopleSoft HRMS values that have no existing Oracle Fusion equivalents to the Oracle Fusion lookup. For example, for the DVM PERSON_ETHNICITY_CODE, you retrieve the PeopleSoft HRMS values using the supplied SQL script and compare them to the values in the Oracle Fusion lookup type PER_ETHNICITY. You add PeopleSoft HRMS values that have no existing Oracle Fusion equivalents to the PER_ETHNICITY lookup. To complete the mapping, you add both sets of values to the DVM using the PeopleSoft Populate Domain Value Maps page.
X	The DVM contains neither PeopleSoft HRMS nor Oracle Fusion data. Steps for completing this DVM are identical to those for completing DVMs with the system data code M, except that you must add specific values to these DVMs.

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

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. This 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. You can find complete instructions 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.

Mapping Subtask	Description
Map business group defaults	For a specified business group, you select the name of a default reference data set and a default legal employer. You also enter the name of the business unit to be created for the business group, and optionally select an eligibility profile to filter person data. You perform this task for every business group identified for integration.
Map HR organizations to legal employers	For each HR organization in a specified business group, you can select the name of the legal employer in Oracle Fusion to which the HR organization maps. You perform this subtask only if you want to map HR organizations to legal employers.
Map key flexfield segments for job, position, grade, and competency flexfields	In E-Business Suite HRMS, key flexfields are used to hold job, position, grade, and competency definitions. In Oracle Fusion, the code and name attributes for job, position, grade, and competency are stored in the base tables rather than in key flexfields. Therefore, the data captured in segments for these entities in E-Business Suite HRMS must be mapped to the code and name values in Oracle Fusion.
Map user defined lookups	For each lookup type in E-Business Suite HRMS, the Oracle Fusion equivalent lookup type is preselected. For each lookup code, you enter the Oracle Fusion equivalent value.
Map EBS person types to Fusion person types	For each person type in a specified business group, you select an equivalent in Oracle Fusion.
Map actions and action reasons	For E-Business Suite HRMS entities such as employee leaving reasons and salary components, you select equivalent actions and action reasons in Oracle Fusion.
Map qualification type category to content type (for Oracle Fusion Talent Management)	For each qualification type category in E-Business Suite HRMS, you select a content type in Oracle Fusion from the imported list of values.
Map elements (for Oracle Fusion Workforce Compensation)	For each element and associated element input value in a specified business group, you select an equivalent in Oracle Fusion.

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.