Configuring HRIS synchronization during implementation

Employee Central is the core HR system and contains relevant information to manage the employee lifecycle. Employee Profile serves as the platform for talent management activities, and it requires a mini-master of core employee data for the talent processes to launch and run successfully.

Employee Central stores employees’ Personal and Employment Information. For example, Job Information includes fields such as an employee’s Department, Company, or Location. Employee Central data is robust and connected to the supporting Foundation Object record data in the system, making it more valuable and accurate than the standard element data used by the User Data Tables.

When configuring HRIS Sync fields, you connect the Employee Central data fields to Standard Elements in Succession Data Model with an HRIS Synchronization Mapping. When there is a change in Employee Central information, it flows to Employee Profile fields and is consumed by talent solutions that cannot directly leverage Employee Central data.

For customers WITHOUT Employee Central, their talent process relies solely on imported data using the User Data File (UDF), which is displayed in Employee Profile blocks in People Profile. These fields allow the standard Org Chart to populate correctly, provide filter criteria for dashboards and reports, create the route maps used for Performance Management and Compensation, and more.

For customers WITH Employee Central, some talent modules continue to refer to User Data File to run the talent processes in the system because they can't leverage person and employment information directly from Employee Central. However, with HRIS Sync, customers do not need to upload this information manually.

Some fields are critical to keeping the sync between Employee Central and the UDF. If using Employee Central, you should not be making user data changes by importing the User Data File (UDF) either from the UI or through a scheduled job. Doing so can overwrite data coming from Employee Central and cause data inconsistencies.

You can schedule HRIS Sync Jobs in Provisioning. You can monitor the HRIS Sync Job using the Scheduled Job Manager in the Admin Center.

Use the interaction below to know how HRIS Sync is triggered.

Certain mappings are hard-coded into the system, meaning you MUST NOT configure these in the Succession Data Model. Configuring an HRIS-sync mapping in the data model for these fields can cause undesired results.

The system prevents anyone from adding duplicate sync mappings to the sync-mappings section of the Succession Data Model. Duplicate sync mappings lead to data not syncing to Employee Profile correctly. Manage Business Configuration (BCUI) has a validation that prevents creating an HRIS sync mapping for hard-coded fields.

These are some of the HRIS fields that are hard-coded to standard elements:

Note

Please refer to Implementing Employee Central Core guide in the Help Portal for the complete list and other sync logic.

You can create custom sync mapping by adding additional XML into your Succession Data Model or through BCUI. The separate section in your XML document uses the tag <hris-sync-mappings>.

The attribute entity-type is mandatory for HRIS-sync mapping of address, email, phone, and global info. Entity type specifies the type of information. For example, emailInfo can either be business or personal. The picklist center can verify the external code used for each type.

The following steps describe the custom mapping process in Succession Data Model.

1. Identify the Employee Central block, using hris-element-ref refid="jobInfo"
2. Identify the Employee Central field, usinghris-field-ref refid="business-unit".
3. Identify the Employee Profile field (standard-element), using standard-element-ref refid="custom01".
4. Update the XML in your Succession Data Model.
5. Upload to Provisioning.

The code in the Succession Data Model is as follows:

<hris-sync-mappings>
<hris-element-ref refid="jobInfo">
<hris-mapping>
<hris-field-ref refid="business-unit"/>
<standard-element-ref refid="custom01"/>
</hris-mapping>
</hris-element-ref>
</hris-sync-mappings>

Note

You can define multiple sets of hris-mapping within the hris-element-ref tag and multiple sets of hris-element-ref inside the hris-sync-mappings tag.

Alternatively, you can configure the mapping in Manage Business Configuration (BCUI) with these steps:

1. Go toManage Business Configuration → HRIS Sync Mappings
2. Select Plus (+)
3. Select the appropriate HRIS Element ID from the drop-down menu
4. Select the Field ID
5. Select the Target Field Type
6. Select the Target Field ID
7. Select Entity Type when applicable
8. Save.

You can view all your HRIS sync mappings on a single screen by selecting HRIS Sync Mappings in BCUI. Fields mapped using the HRIS Sync Mappings will also reflect in the details of the Field Element in the individual hris-elements.