Search Results hri_bpl_conc_admin




Overview
Explore in AI Chat

Overview

HRI_BPL_CONC_ADMIN is an Oracle Applications (APPS) PL/SQL package body that provides administrative and configuration support logic for Oracle HR Intelligence (HRMS Intelligence / Daily Business Intelligence for HRMS) concurrent processing. It sits within the HRI_BPL (Business Process Library) family of packages, which coordinate the data collection, refresh, and request-set orchestration performed by HR Intelligence concurrent programs. The package centralizes the runtime decisions required to determine whether full refreshes must be performed, how event-based incremental refreshes should be scheduled, and how the underlying request sets that drive the collections should be resolved. Because it reads Oracle HR Intelligence collection tables (HRI_CS_SUPH, HRI_CL_WKR_SUP_STATUS_CT, HRI_MB_ASGN_EVENTS_CT) together with standard concurrent manager and profile infrastructure, it functions as the bridge between business collection programs and the concurrent manager. The object is documented as VALID in the APPS schema in EBS 12.1.1 and 12.2.2, and its API classification is OTHER, indicating it is an internal utility rather than a public, supported integration API.

Key Procedures and Functions

  • GET_FULL_REFRESH_FLAG — Returns a flag indicating whether a full refresh of the relevant HR Intelligence collection is required. This is typically consulted before launching a collection program so that incremental and full runs can be distinguished.
  • GET_FULL_REFRESH_CODE — Returns the coded value associated with the full refresh decision, complementing the boolean-style flag with a lookup or profile-driven code used by the calling process.
  • GET_EVENTS_FULL_REFRESH_FLAG — Returns the full refresh indicator specifically for event-based collections, allowing the caller to force or suppress a complete rebuild of event data rather than processing only deltas.
  • GET_HRI_GLOBAL_START_DATE — Returns the global start date that bounds the data window used by HR Intelligence collection programs. This date anchors the earliest point from which data is collected or refreshed.
  • GET_REQUEST_SET_DETAILS — Returns the details of the request set (objects and options) that must be submitted to the concurrent manager, resolving the request set definition to its constituent concurrent programs.

Tables Accessed

  • BIS_REQUEST_SET_OBJECTS and BIS_REQUEST_SET_OPTIONS — Provide the object and option definitions of the BIS/HR Intelligence request sets used by GET_REQUEST_SET_DETAILS.
  • FND_REQUEST_SETS_VL — Supplies the user-facing request set name and description resolved against the request set identifier.
  • FND_CONCURRENT_REQUESTS — Used to inspect prior or in-flight concurrent request state, supporting refresh-decision logic.
  • FND_LOOKUP_VALUES — Provides lookup-driven codes and meanings, particularly for the full refresh code returned by GET_FULL_REFRESH_CODE.
  • FND_PROFILE and FND_GLOBAL — Supply the current session context and profile option values (for example, responsibility, user, and HR Intelligence configuration settings) that parameterize the package's decisions.
  • HRI_CS_SUPH, HRI_CL_WKR_SUP_STATUS_CT, and HRI_MB_ASGN_EVENTS_CT — HR Intelligence collection and supervisor/assignment event tables consulted to determine collection scope and event-driven refresh behavior.

Usage Notes

HRI_BPL_CONC_ADMIN is invoked internally by Oracle HR Intelligence concurrent programs and by related HR Intelligence packages that orchestrate collection schedules. It is not referenced by any database object outside its own dependency set, confirming that it is a leaf-level utility consumed by the HR Intelligence collection framework rather than a general-purpose API. The ETRM metadata records three other packages referencing it, so custom code should call its functions only when replicating or extending HR Intelligence concurrent submission logic. Because its return values depend on profile options and session context (FND_PROFILE, FND_GLOBAL), results can vary by responsibility and user; callers must initialize the FND global context before invoking it. Parameter lists are intentionally not published here, as the documented metadata does not expose them; developers extending HR Intelligence should inspect the package specification in the APPS schema for exact signatures before use.