Fusion HCM: Best Practices for Synchronize Person Records Process
(Doc ID 2921437.1)
Last updated on OCTOBER 30, 2024
Applies to:
Oracle Fusion Global Human Resources Cloud Service - Version 11.13.22.04.0 and laterOracle Fusion Global Payroll Cloud Service - Version 11.13.24.07.0 to 11.13.24.07.0 [Release 1.0]
Information in this document applies to any platform.
Goal
Synchronize Person Records ESS process performs the following actions:
- publishes ChangedPersonDetails event for employee and contingent workers to create party records corresponding to the workers' person records
- synchronizes future dated workers as they become active as of the current system date
- for additional details, refer to Doc ID 1593212.1 and Implementing Global Human Resources Guide - How You Communicate Person and Assignment Changes to Consumer Applications
This process should not be scheduled to run multiple times a day. Scheduling it multiple times raises event for same persons multiple times and causes unnecessary load on SOA servers to process them. This could result in delays in processing approval transactions.
Also, this process should not be scheduled with hard-coded values for From Date and To Date parameters. This will raise events for same persons over and over again resulting in unnecessary and duplicate events.
In case you have scheduled it incorrectly, follow the solution described below to resolve it.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |