Update Person Search Keywords ( Daily Twice ): 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.

Synchronize Person Records ( Daily Twice ):

Calculate Relationship Strength:

Refresh Manager Hierarchy ( Daily Once ): 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.

Send Pending LDAP Requests (Daily Ad Hoc): Bulk processing of user and role provisioning requests.
Sends bulk requests to OIM immediately to create (and also suspend or re-enable) user accounts, as
appropriate. When you load person records, the application automatically creates user-account
requests by default and provisions roles to users in accordance with role provisioning rules.

Auto provision Roles for All Users (Ad Hoc Rarely): Evaluates roles membership for all users, including
inactive. This process evaluates all users in the system against the role provisioning rules. This process
may have heavy performance impact on your environment if you run it regularly. You should run this
process occasionally, only when role-provisioning rules are added or updated. Should be run only when
role mapping rules have been added or changed, and these rules apply to the entire user population.

Send Personal Data for Multiple Users to LDAP(Ad Hoc Rarely): Reconciles personal information
changes in Oracle HCM Cloud with LDAP directory. 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.

Retrieve Latest LDAP Changes (Very rarely): Updates Oracle HCM Cloud person records with data
coming from LDAP directory. 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.

Synchronize Bell Notifications (Every 2 hours): Bell Notifications to synchronize with the BPM Worklist.
To move the already approved notifications from bell, there is an ESS job definition which can be
scheduled to run periodically.

Privilege Needed to Schedule/Execute this Job Definition is :

FND_MANAGE_SCHEDULED_JOB_DEFINITION_PRIV ( This privilege rolls up to all the Family Admin Job
Roles).
They will be marked as Read/moved from Pending Notifications to All Notifications immediately once
the user reads them as there are no pending actions on them. The Synchronize Bell Notifications should
be scheduled for every 2 hrs and is restricted by Development to update 500 records at a time.

Calculate Seniority Dates (Adhoc): To calculate the seniority dates for workers based on the seniority
rules configured in the application

Parameters: Person Number: Enter person number

Seniority Date Code List: ORA_ESD_P,ORA_LESD_W( This values may be different based on the customer
configurations– See the configuration setup data table for this information) (ORA_ESD_P, ORA_LESD_W,
ORA_POSITION_SD_A)

Exclude terminated Workers: Yes, Operation: Clean and Repopulate

Setup and Maintenance > Manage Common Lookups using the Lookup Type -
ORA_PER_SENIORITY_ITEMS

Synchronize Transaction Workflow Status (Daily once and Adhoc): This process ensures that the
workflow status is updated correctly in SOA and Oracle Fusion Applications

Import User and Role Application Security Data (Daily Once) : To set up and maintain the Security
Console copies users, roles, privileges, and data security policies from the LDAP directory, policy store,
and Applications Core Grants schema to Oracle Fusion Applications Security tables. IT Security Manager:
this role must to run this process.

Importing User Login History (Daily Once): This task runs a process that imports information about user
access to Oracle Fusion Applications to the Oracle Fusion Applications Security tables. This information is
required by the Inactive Users Report, which reports on users who have been inactive for a specified
period.

Optimize Person Search Keywords (Daily at times of low activity): Optimize Person Search Keywords
Index process to identify the fragmented indexes and help improve the overall search performance. The
Update Person Search Keywords process first and then the Optimize Person Search Keywords process.
We cannot schedule both processes simultaneously. If you schedule them at the same time, the second
process will wait for the first process to complete before it starts.

Process and Reassign Inactive User Accounts (Daily Once): Process identifies inactive user accounts and
removes them from their teams. It sends notifications to members reassigned as the new team leads.

To reflect the Flex Fields in OTBI then we need to run the below process in sequence:

Create Rules XML File for BI Extender Automation

Import Oracle Fusion Data Extension for Transactional Business Intelligence

Note: Should check the BI Enabled check box while creating segments and should deploy the Flex fields.

Generate Flexfield Database Items: (EFF / EIT only): We should run this process after creating the flex
fields and deploy successfully. Then only the Flex Fields DBI’s will available in Fast Formulas and HCM
Extracts.
Note: Navigator –> Payroll Checklist –> Tasks –> Submit a process or Report –> search Generate Flexfield
Database Items –> run this without selecting any LDG.

Run Reassign Pending Approvals for Terminations and Correct Invalid Supervisor Assignments Process
(Daily Once): 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. Reassign the line
reports manually to the transferring manager’s manager during the global transfer transaction or
terminated.

Populating Location Latitude and Longitude Information : Once geocoding is enabled, you can schedule
this feature to run at regular time intervals so that newly created or updated locations are picked up and
geocoded.

Geography Name Referencing: The Geography Name Referencing (GNR) process validates address
elements in location tables, such as HZ_LOCATIONS, against the master geography data.

Refresh Manager Hierarchy: The Refresh Manager Hierarchy process populates the denormalized
manager hierarchy table when person records are migrated from other applications.Whenever a change
is made to a person's manager hierarchy, the change is reflected automatically in the denormalized
manager hierarchy table.

Update Person Names: When you update a name format, you must run the process so that the
application updates the stored names according to the updated format type rules. You can run the
process for a specific name format and legislation combination.

Send User Name and Password E-Mail Notifications: You can run the process Send User Name and
Password E-Mail Notifications from the Scheduled Processes work area. For users for whom you haven't
so far requested an e-mail, this process resets passwords and sends out user names and passwords. The
e-mail goes to the primary work e-mail of the user or the user's line manager. You can send the user
name and password once only to any user.

Reassign Pending Approvals and Direct Reports: Run the Reassign Pending Approvals for Terminations
and Correct Invalid Supervisor Assignments process to reassign the direct reports and any pending
approval notifications of a manager who is either terminated or globally transferred. You can manually
run the process or schedule it to run automatically at a specific time in the Scheduled Processes work
area. The process reassigns the direct reports of a terminated manager to that person's line manager.
Similarly, it assigns any pending approval notifications to the line manager. You can either reassign
pending notifications or skip this step when you run the process. If you choose to reassign pending
notifications, then you must specify the number of days to be considered for reassigning the pending
approvals. For example, if you specify 30 days, the process reassigns pending approvals of workers or
managers terminated in the past 30 days.