1. Oracle Search Cloud Service
  2. Best Practices for Setting Up Additional HCM Module Implementations with Oracle Search

Best Practices for Setting Up Additional HCM Module Implementations with Oracle Search

Follow these best practices when setting up additional HCM module implementations with Oracle Search.

  • Run the initial data ingestion (ESS job to ingest) only for the new index that’s required by the new module.
  • Run the Compute Users ACL with parameter population = All users, only after all functional indices required by your implementation were ingested.
    • This job will not cause any downtime for users working with already implemented Oracle Searches.
  • Do not run the HCM Access Control List Initial Ingestion job. Running this job after you implemented some searches will cause users search downtime until it’s completed because it’s re-creating the ACL index from scratch.

Enable the module specific profile options if needed. Review your module documentation for details.