In this article, we will be discussing several commonly used Oracle Cloud HCM processes that should be scheduled to run at regular intervals to ensure the smooth operation of your business. We recommend reviewing this list before your next implementation project. While not all processes may be relevant to your specific needs, it is worthwhile to familiarize yourself with the list. Please note that the frequencies mentioned in the table below are only guidelines, and you can adjust them based on your customers’ requirements.
Here is a list of Oracle Cloud HCM processes that should be considered for scheduling:
| S.NO | Job Name | Description | Frequency |
| 1 | Refresh Transaction Administrator Console Transaction Status | This process updates the status of a transaction in the Console | Every 1 Hour |
| 2 | Synchronize Bell Notifications | Bell Notifications to synchronize with the BPM Worklist | Every 2 Hours |
| 3 | Import Oracle Taleo Recruiting Cloud Service Data | Import candidates from taleo to Fusion | Daily |
| 4 | Send Pending LDAP Requests | Sends bulk requests to OIM immediately to create (and also suspend or re-enable) user accounts | Daily |
| 5 | Import User and Role Application Security Data | This task runs a process that imports information about user access to Oracle Fusion Applications to the Oracle Fusion Applications Security tables | Daily |
| 7 | Process and Reassign Inactive User Accounts | Process that identifies inactive user accounts and removes them from their teams. It also sends notifications to members reassigned as the new team leads. | Daily |
| 8 | Run Reassign Pending Approvals for Terminations and Correct Invalid Supervisor Assignments Process | This process automatically reassigns the direct line reports. All direct reports are reassigned to the transferring manager’s manger as of the date following the transfer. | Daily |
| 9 | Calculate Seniority Dates | To calculate the seniority dates for workers based on the seniority rules configured in the application | Daily |
| 10 | Refresh Manager Hierarchy | Populates the denormalized manager hierarchy tables with latest information after each data load. For performance reasons, the complete manager hierarchy for each person is extracted from live data tables and stored in a separate manager-hierarchy table, known as the denormalized manager hierarchy | Daily |
| 11 | Flatten HCM Position Hierarchy | Synchronize the HCM position hierarchy.Run this job in Serial mode. | Daily |
| 12 | Optimize Person Search Keywords | Optimize Person Search Keywords Index process to identify the fragmented indexes and help improve the overall search performance.
It has to be run/scheduled after “Update Person Search Keywords” job. If you schedule them at the same time, the second process will wait for the first process to complete before it starts. |
Daily — Off peak hours |
| 13 | Update Person Search Keywords | Copies attributes of person, employment, and profile records that are used as search keywords to the PER_KEYWORDS table, where they’re indexed to improve search performance. The process updates the entire PER_KEYWORDS table. | On Demand |
| 14 | Synchronize Person Records | Communicates changes to person and assignment records that have occurred since the last data load to consuming applications, such as Oracle Fusion Trading Community Model and Oracle Identity Management (OIM). | On Demand |
| 15 | Synchronize Person Assignments from Position | The Synchronize Person Assignment from Position process must be run to update impacted assignments when position synchronization is configured for the first time or changed.
It also must be run if position changes were uploaded using HCM Data Loader |
On Demand |
| 16 | Refresh Manager Hierarchy | Populates the denormalized manager hierarchy tables with latest information after each data load. For performance reasons, the complete manager hierarchy for each person is extracted from live data tables and stored in a separate manager-hierarchy table, known as the denormalized manager hierarchy | On Demand |
| 17 | Send Personal Data for Multiple Users to LDAP | This process synchronizes changes performed in bulk on Oracle HCM Cloud person records with the LDAP directory records. The following fields are synchronized: First Name, Last Name, Email, and Manager. You typically run this process after loading person data in bulk. You can also run this process to update the manager hierarchy in the LDAP directory | On Demand |
| 18 | Autoprovision Roles for All Users | Evaluates roles membership for all users, including inactive. | On Demand |
| 19 | Retrieve Latest LDAP Changes | This job updates the Oracle Cloud Applications Security tables with data coming from the LDAP directory.You should run this process once after the product update is completed. For example, after you upgrade from 18C to 19A | On Demand |
| 20 | Import User Login History | Imports information that the Inactive Users Report uses to identify inactive users. | On Demand |
We trust that this article has provided valuable information on the essential processes that need to be scheduled for Oracle Core HR module. You can refer to this article as a reference to ensure you schedule all the necessary processes for the smooth operation of your Core HR implementation project.
If you believe there are any other critical processes that should be included in this list, we encourage you to share them in the comment section below. By exchanging your experiences and insights we can build a valuable resource that benefits the entire Oracle Cloud HCM community.
We have shared the list of similar commonly used processes for Oracle Time and Labor (OTL) here » Essential Processes to Schedule for Oracle Time and Labor (OTL) Project
