Search Results hri_bpl_pyugen_wrapper




Overview
Explore in AI Chat

Overview

The concurrent program HRI_OPL_WMV_WRPR_INCR belongs to the HRI – Human Resources Intelligence product family, which carries the designation Obsolete in Oracle E-Business Suite documentation. Its user-facing name is Update Workforce Measurement Value Base Metric (OLTP, with shared HR support), and its documented purpose is to update the Workforce Measurement Value History base metric. The program therefore operates on the fact and history structures that support workforce measurement reporting within the HR Intelligence data model, refreshing the base metric values that feed higher-level workforce analytics.

The internal short name reflects the wrapper architecture used by the HR Intelligence stack: the request is initiated through the executable that incrementally reloads generic hierarchy versions, while the program itself targets workforce measurement value increments. This dual naming is a common characteristic of HRI programs, where the same executable wrapper (HRI_BPL_PYUGEN_WRAPPER) services multiple logical concurrent requests distinguished by their argument sets.

Execution Details

The documented execution metadata for this program is as follows:

  • Product: HRI – Human Resources Intelligence (Obsolete)
  • Enabled: Yes
  • Execution Method: PL/SQL Stored Procedure
  • Argument Method: Standard
  • Executable: HRI_BPL_PYUGEN_WRAPPER
  • Execution Filename: HRI_BPL_PYUGEN_WRAPPER.process_request
  • Executable User Name: HRI_BPL_PYUGEN_WRAPPER
  • Executable Description: HRI Load All Generic Hierarchy Versions

The executable description ("Load All Generic Hierarchy Versions") indicates that the underlying PL/SQL package is responsible for populating or refreshing generic hierarchy version data used across HR Intelligence subject areas. The process_request routine exposed as the execution filename is the entry point invoked by the Concurrent Manager when the request is submitted.

How to Run

Because the Argument Method is Standard, the program is submitted through the standard Concurrent Programs form or the Schedule Requests interface in the System Administrator or HRMS Manager responsibility. In EBS 12.1.1 and 12.2.2, administrators navigate to Requests → Run, select the request name Update Workforce Measurement Value Base Metric (OLTP, with shared HR support), and supply the standard HRI parameters. Typical HRI concurrent programs of this class accept parameters controlling the business group, effective date, hierarchy version, and processing mode (incremental versus full load). The "incremental" behavior implied by the program short name suggests that a narrowly scoped parameter set is used to refresh only new or changed workforce measurement values rather than rebuilding the entire history.

Given its obsolete status, customers on 12.1.1 or 12.2.2 should confirm whether the program is still scheduled as part of existing HR Intelligence extracts before relying on it. Where it remains active, it is normally run in sequence with the broader HRI hierarchy load programs and is commonly scheduled after source HRMS data has been staged.

Related Objects

The program is architecturally tied to the following objects and components within the HR Intelligence stack:

  • Executable package: HRI_BPL_PYUGEN_WRAPPER and its process_request procedure, shared across multiple HRI concurrent programs.
  • Workforce Measurement Value History structures: the base metric tables updated by this program, which feed derived workforce measurement metrics.
  • Generic hierarchy version tables: populated by the parent "Load All Generic Hierarchy Versions" executable logic.
  • Sibling HRI concurrent programs: the related full-load and incremental load requests that share the same wrapper executable.

Because the product is marked obsolete, Oracle no longer enhances these objects; support is limited to existing behavior. Implementers should treat any reference to HRI_BPL_PYUGEN_WRAPPER as a shared wrapper invoked by several HRI requests, and should inspect the concurrent program definition in the target instance to determine the exact parameter list and any instance-specific customizations.