Search Results per_solution_bk3

Overview

APPS.PER_SOLUTION_BK3 is a generated PL/SQL hook package that forms part of the Oracle HRMS API Hook Pre-processor framework. Its source header (pesolapi.pkb, version 115.2) and the generation timestamp of 2007/01/03 identify it as an auto-generated companion to the PER_SOLUTION_API business logic. The package provides the "BK3" (Before-Kernel, third variant) stub layer through which the Oracle Human Resources solution entity processing routes control before the corresponding business logic in the solution API executes. In Oracle E-Business Suite 12.1.1 and 12.2.2 this construct is used to allow extensions and customisations to intercept standard API execution at well-defined points without modifying Oracle's seeded code.

Key Procedures and Functions

The package exposes two documented procedures, both of which are empty stubs that only exercise the debug instrumentation calls to hr_utility.set_location:

• DELETE_SOLUTION_A — The hook procedure invoked at the enter point of the solution deletion process. It is called before the core delete logic and then again at the leave point, as reflected by the "Entering" and "Leaving" location markers set at lines 10 and 20.
• DELETE_SOLUTION_B — The companion hook procedure for the second deletion phase, again with only the entering and leaving debug markers replacing any actual logic.

Neither procedure contains business logic in the seeded delivery. They are placeholders intended to be replaced or supplemented by customer-specific code when an extension of the delete flow is required.

Tables Accessed

The ETRM metadata records no directly referenced tables for this package. Because the procedures are stub bodies with no executable SQL or PL/SQL DML statements, no base table reads or writes occur. The underlying PER_SOLUTION_API, which this hook augments, operates against the HR solution tables (PER_SOLUTIONS) and its related child entities; however, these accesses are not attributed to PER_SOLUTION_BK3 itself. Any table activity would only arise if a customer customises the hook bodies.

Usage Notes

PER_SOLUTION_BK3 is not invoked directly by end users or concurrent programs. It is called indirectly by the Oracle HRMS API hook dispatch mechanism, which wraps the standard PER_SOLUTION_API routines. The package is referenced by one other package in the documented dependency graph, confirming that it is a dependent module rather than a top-level entry point.

Typical invocation paths include:

• Oracle Forms-based HRMS maintenance screens that perform solution deletion, where the form triggers the solution API and the API in turn calls the BK3 hook.
• Concurrent programs or batch processes that call PER_SOLUTION_API.DELETE_SOLUTION, resulting in the hook being executed as part of the API pre-processing.
• Custom PL/SQL integrations that invoke the solution API and therefore inherit the hook call chain.

Consultants extending solution deletion behaviour should implement custom logic inside the hook bodies rather than altering the seeded PER_SOLUTION_API. Because the generated code is marked "generated noship" and carries an Oracle Proprietary and Confidential designation, modifications belong in a separate custom package registered through the HRMS hook framework to preserve upgrade safety across 12.1.1 and 12.2.2.