Fusion HCM: What to Do If Send Personal Data for Multiple Users to LDAP Job Has Been Scheduled
(Doc ID 2852944.1)
Last updated on JULY 26, 2022
Applies to:Oracle Fusion Global Human Resources Cloud Service - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Send Personal Data for Multiple Users to LDAP process updates the Identity Store information to match information held by HCM Cloud.
This process should not be scheduled to be run at regular intervals at all. We recommend to submit this process only as needed. For example:
- Run manually with parameter 'Changed users only' parameter after changing personal data of the workers in bulk using HCM Data Loader (HDL). The job will synchronize personal data to LDAP only for the changed users.
- Run manually with 'All users' parameter only as one-time synchronization of all user records to LDAP during initial implementation.
Each time the job is executed with 'All users' parameter, it creates an LDAP request for each user regardless of whether personal information was changed or not. If the job is scheduled with 'All users' parameter, it creates two issues:
- Creates unnecessary LDAP requests for all users in the system causing the LDAP requests table to grow in size
- Causes unnecessary processing overhead for Send Pending LDAP Requests job and can result in performance issues
In case you have scheduled it, then follow the solution described below to resolve any of the two potential issues you might be facing.
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