Search Results process_request

Overview

The APPS.HRI_BPL_PYUGEN_WRAPPER package is a wrapper API belonging to the Oracle Human Resources Intelligence (HRI) product family. Its name derives from "BPL" (Business Process Library) and "PYUGEN" (a Payroll Update Generation process), indicating that it encapsulates a payroll-related data collection or generation sub-process invoked through the HRI business process layer. The package is declared AUTHID CURRENT_USER, meaning that it executes with the privileges of the invoking user rather than the defining user, a design choice typical of wrapper APIs that expect to be called from within the APPS schema or from concurrent processing contexts where invoker's rights semantics are required.

The source header ($Header: hribpgw.pkh 115.0 2004/04/28) and the noship label confirm that this is an internal, non-shipped object — it is part of the supporting infrastructure used by Oracle's own collection and payroll generation flows rather than a publicly documented extension point. Its principal role is to expose one or more sub-processes to a controlling driver, translating wrapper-level exceptions (sub_process_not_found, sub_process_failed) into outcomes the caller can interpret.

Key Procedures and Functions

The package exposes two overloads of a single documented procedure, PROCESS_REQUEST:

• PROCESS_REQUEST (standard PL/SQL form) — Accepts the collection name, business group identifier, collection date range, full refresh flag, and two generic attribute parameters. This form is intended for direct programmatic invocation, where errors are surfaced through PL/SQL exceptions (sub_process_failed, sub_process_not_found) rather than through an outcome buffer.
• PROCESS_REQUEST (concurrent-program form) — Adds the standard errbuf OUT NOCOPY and retcode OUT NOCOPY parameters required by Oracle concurrent manager entry points. The remaining parameters mirror the first overload. This form allows the procedure to be registered directly as a concurrent program executable argument and to report completion status back to the concurrent manager.

Both overloads share the same driver contract: they receive the collection context (name, business group, date window, refresh mode, and two reserved attribute slots) and coordinate the underlying payroll update generation sub-process. The two user-defined exceptions signal the two failure modes the wrapper anticipates — the requested sub-process cannot be located, or it ran but reported a failure.

Tables Accessed

According to the ETRM metadata, the package references one table via an APPS synonym: FND_CONCURRENT_PROGRAMS. This access is consistent with the package's concurrent-program orientation — the wrapper likely queries the concurrent program definition to resolve the sub-process to be executed, confirm its registration, or validate that the requested concurrent program exists before launching it. No application data tables (for example, payroll or collection staging tables) are documented as directly referenced, which reinforces the wrapper's role as a routing and validation layer rather than a business-logic owner. Actual payroll generation work is delegated to the sub-process the wrapper locates and invokes.

Usage Notes

Because HRI_BPL_PYUGEN_WRAPPER is not referenced by any other documented package, it is not a shared library utility. It is intended to be invoked either (a) directly from custom PL/SQL code that needs to trigger the payroll update generation sub-process within an existing session, using the non-concurrent overload and handling the declared exceptions, or (b) as a concurrent program entry point, using the errbuf/retcode overload so the concurrent manager can record success or failure. In Oracle EBS 12.1.1 and 12.2.2 environments, the typical invocation path is through the concurrent manager or through HRI collection programs that manage business group and date-range context. Developers integrating with this package should treat it as an internal Oracle object: its signature is stable within the release but is not a supported public API, and the two reserved p_attribute parameters should be passed as NULL unless the underlying collection flow explicitly requires values. Exception handling should distinguish sub_process_not_found (configuration or registration problem) from sub_process_failed (runtime failure of the invoked process).