How do I enable Oracle Search for HCM?

To enable Oracle Search for HCM, you need to configure profile options and run the initial data ingestion process to set up Oracle Search index, which is the foundation of Oracle Search based Global Search.

These are the broad steps to enable Oracle Search:

  1. Set Oracle Search profile options.
  2. Run initial data ingestion.
  3. Refresh indexes after upgrade.
  4. Refresh indexes after P2T.

Set Oracle Search Profile Options

  1. Navigate to Home > Setup and Maintenance > Manage Administrator Profile Values.
  2. Search for and review the following profile options. Set the values with the corresponding level if not set already.
    Profile Option Code Profile Display Name Application Module Profile Level Profile Value
    ORA_FND_SEARCH_EXT_ENABLED Enable/Disable Search Ext Framework Oracle Middleware Extensions for Applications Oracle Middleware Extensions for Applications Site Yes
    HRC_ELASTIC_SEARCH_ENABLED HRC: Enable Elastic Search HCM Common Architecture

    Search Framework

    Site Y
    PER_SEARCH_LOGIN_EVENT_PUB PER: User Login Event Publication for Search Global Human Resources Security Site ATOM

Run Initial Data Ingestion

  1. Navigate to Tools > Scheduled Processes.
  2. Submit this process to run only once:
    1. HCM Access Control List Initial Ingestion.
  3. Schedule these processes to run at regular intervals:
    1. Compute Users ACL by Event - Schedule for every 15-60 mins.
    2. Compute Users ACL - For User Population as Logged in users - Schedule for every 30-120 minutes.
    3. Compute Users with Large ACL – For Action: Compute and User Population: All Users with Large ACL – Schedule to run once every day.
Note: If you need to set up the index for a feature, select the relevant parameter value. For example, fa-hcm-person for person search or fa-hcm-position for positions search. If you’re setting up multiple indexes, then you need to run multiple processes with different index name parameters.
Job Name Parameter Name Parameter Value
Scheduled job to create index definition and perform initial ingest to OSCS Index Name to Reingest <index_name> For example: fa-hcm-person

This process is secured with FND_MANAGE_SCHEDULED_JOB_DEFINITION_PRIV function privilege. The privilege is available in the ORA_FND_APPLICATION_ADMINISTRATOR_JOB or ORA_FND_APPLICATION_DEVELOPER_JOB job roles.

Refresh Indexes after Upgrade

Oracle Search indexes are automatically reingested with release upgrades. You must not reingest the existing Oracle Search indexes manually. The automated reingestion will only reingest if new attributes are added to an index. Automated ingestion process is nondestructive and runs in the background while existing indexes are available.

Refresh Indexes after P2T

You must run the initial data ingestion process for every created index after P2T (production-to-test) process.