Search Results update_solution_b

Overview

APPS.PER_SOLUTION_BK2 is a generated PL/SQL package body belonging to the Oracle HRMS (Human Resources Management System) API layer. Its name follows the Oracle HRMS naming convention in which the _BK suffix denotes a "backward compatibility" or pre-processor hook wrapper, and the trailing digit (2) indicates a variant in a sequence of related generated stubs. The package's documented purpose is to provide procedural entry points for updating a "Solution" entity within the Oracle HRMS/Advanced Benefits and Knowledge Base data model, where a solution represents a reusable record (such as a service or resolution description) associated with the PER schema.

The source header reveals the object's provenance: it was produced by the Oracle HRMS API Hook Pre-processor and generated on 2007/01/03, with an underlying RCS header originating from pesolapi.pkb version 115.2 dated 2003/01/04. This confirms the package is machine-generated rather than hand-authored, and that it exists to preserve callable interfaces for backward compatibility with earlier releases of the HRMS Solution API.

Key Procedures and Functions

The ETRM metadata for 12.2.2 documents two procedures, both classified under "OTHER," meaning neither is a formally published PL/SQL API in the public sense but rather an internal generated hook:

• UPDATE_SOLUTION_A — The first of two update hook entry points. Its body simply marks entry and exit points using hr_utility.set_location, indicating it serves as a pre-update hook or placeholder that delegates processing to surrounding generated logic. It is the "A" variant, typically invoked before or as the primary update call.
• UPDATE_SOLUTION_B — The second update hook entry point, structurally identical to UPDATE_SOLUTION_A in the documented excerpt. The "B" variant typically represents a secondary or post-processing hook or an alternate call path used by the API pre-processor to interleave custom logic.

Both procedures accept the same parameter signature — effective date, solution ID, object version number, solution name, solution type name, description, a link-to-full-description flag, vertical, legislation code, and user ID — but this signature should not be treated as a supported public interface, since the package is generated infrastructure.

Tables Accessed

The ETRM metadata records no tables referenced via APPS synonyms for PER_SOLUTION_BK2. This is consistent with its role as a hook stub: the procedures contain only location-tracking calls and perform no direct DML. The actual insert, update, and delete operations against the underlying solution tables (such as the PER solution base tables) are handled by the primary API package, with PER_SOLUTION_BK2 acting as an intercepted wrapper. The metadata further notes the package is referenced by one other package, confirming it participates in a generated call chain rather than standing alone.

Usage Notes

PER_SOLUTION_BK2 is not intended for direct invocation by developers, forms, or concurrent programs. It is invoked indirectly by the HRMS API Hook Pre-processor framework whenever the parent Solution API is called. In EBS 12.1.1 and 12.2.2, such generated _BK packages exist to allow Oracle or customer extensions to inject logic at defined hook points without modifying seeded API code. Because the procedures are regenerated, any customization placed directly inside them will be overwritten during patching; supported extension should instead leverage the corresponding CUSTOM hook packages. Use of this package should therefore be limited to diagnostic tracing, where the hr_utility.set_location markers help confirm the API path being executed during a Solution update.