Search Results hri_opl_multi_thread




Overview
Explore in AI Chat

Overview

HRI_FULL_RFRSH_EVNT_CPTR is a concurrent program belonging to the HRI — Human Resources Intelligence product family. In Oracle EBS 12.1.1 and 12.2.2, the program carries the user-facing name HRI Full Refresh Event Capture Process and is documented as the "Event Capture Full Refresh Process." Its role is to perform a complete, full-cycle refresh of the event capture data used by the HRI (Human Resources Intelligence) reporting and analytics infrastructure.

Notably, the underlying executable is HRI_OPL_MULTI_THREAD, whose description is "Entry point for HRI Multi Threading Utility." This is the object most users encounter when searching for "hri_opl_multi_thread". The concurrent program is therefore a specialized wrapper that invokes the HRI multi-threading utility specifically to drive the full refresh of event capture records. The HRI product is flagged as Obsolete in the 12.2.2 metadata, meaning the program remains enabled but is part of a legacy module that Oracle no longer actively develops.

Execution Details

The documented execution details are as follows:

  • Execution Method: PL/SQL Stored Procedure
  • Argument Method: Standard
  • Executable: HRI_OPL_MULTI_THREAD
  • Execution File Name: HRI_OPL_MULTI_THREAD.PROCESS
  • Subroutine Name: (not specified)
  • Enabled: Yes

Because the execution method is a PL/SQL stored procedure, the program is submitted and executed entirely within the database tier. The executable HRI_OPL_MULTI_THREAD.PROCESS acts as the single entry point that dispatches work across multiple worker threads, which is the defining characteristic of the HRI Multi Threading Utility. This design allows the full refresh operation to parallelize its processing rather than performing the work serially.

How to Run

As with all standard concurrent programs in Oracle EBS, HRI_FULL_RFRSH_EVNT_CPTR is submitted through the Submit Request (SRS) window, accessible via the Requests form or the Concurrent Programs responsibility. Users select the program by its user-facing name, "HRI Full Refresh Event Capture Process," supply any required arguments in the standard parameter window, and submit the request for scheduling by the Concurrent Manager.

Because the program uses the Standard argument method, its parameters are defined in the ordinary EBS parameter framework rather than through a specialized argument set. Oracle does not publicly document the individual parameter list in the available ETRM excerpt; administrators should inspect the program definition in the Concurrent Programs form to identify the complete parameter set before submission. Full refresh operations of this type are typically run during maintenance windows, as they reprocess the entire event capture data set and can consume significant database resources and run time.

Related Objects

The program is closely tied to the HRI Multi Threading Utility and its executable, HRI_OPL_MULTI_THREAD, which serves as the shared entry point for multiple HRI concurrent processes. Related objects commonly associated with HRI event capture processing include the HRI event capture interface and staging tables that hold event data prior to processing, the HRI reporting and analytics tables that consume the refreshed data, and other concurrent programs that invoke the same HRI_OPL_MULTI_THREAD executable for incremental or targeted refresh tasks rather than full refresh. Administrators troubleshooting the program should review the concurrent manager log and the request log generated by HRI_OPL_MULTI_THREAD.PROCESS, since the multi-threaded design spawns worker activity that may be recorded separately from the parent request.