Search Results create_solution_a

Overview

PER_SOLUTION_BK1 is a generated PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It belongs to the Oracle Human Resources (HRMS) family of "BK" (Business Knowledge / API Hook) packages and was produced automatically by the Oracle HRMS API Hook Pre-processor, as indicated by the header comment "Code generated by the Oracle HRMS API Hook Pre-processor" and the source revision string "pesolapi.pkb 115.2," dated 2003/01/04. The file itself was regenerated on 2007/01/03.

Functionally, PER_SOLUTION_BK1 provides the pre-processor hook stubs that correspond to the public "Solution" API for Oracle Learning Management (OLM) and related HRMS functionality. A "solution" is an HRMS concept representing a publication, knowledge item, or informational solution entry that can be associated with solution types, legislation, verticals, and descriptive text. This package body does not contain substantive business logic; instead, it exposes hook entry points where customer or partner extensions can be attached to the standard solution creation flow. In ETRM terms, the API is classified as OTHER, meaning it is not one of the primary entity-maintenance APIs but a supporting hook layer.

Key Procedures and Functions

The package body exposes two documented procedures, both acting as pre-processor hooks for the CREATE_SOLUTION operation:

• CREATE_SOLUTION_A — The "A" variant hook invoked during solution creation. Its signature accepts a broad set of solution attributes, including an effective date, solution name, solution type name, description, link-to-full-description flag, vertical, legislation code, user identifier, and additionally a solution ID and object version number. The presence of the ID and object version parameters indicates this variant participates in the versioned, persisted side of the create flow.
• CREATE_SOLUTION_B — The "B" variant hook. Its parameter set mirrors CREATE_SOLUTION_A except that it omits the solution ID and object version number parameters, reflecting an earlier or logical (pre-persistence) stage of the same creation process.

Both procedures are generated stubs: each opens with an hr_utility.set_location call at line-step 10 bearing the message "Entering: PER_SOLUTION_BK1.<procedure>," immediately followed by a matching set_location at step 20 with the message "Leaving," and then terminates. No committed DML or conditional logic exists in the body as shipped. This design intentionally leaves the hook points empty so that users may implement custom code without modifying Oracle-owned objects.

Tables Accessed

The ETRM metadata records no direct table references from this package body. In their shipped form, neither CREATE_SOLUTION_A nor CREATE_SOLUTION_B performs any SQL — there are no INSERT, UPDATE, SELECT, or DELETE statements, and no references to APPS synonyms are documented. Any table interaction associated with solution creation is handled by the parent API that invokes these hooks, not by the hook package itself. Should a customer extend either hook, it is the extension code that would introduce table access.

Usage Notes

PER_SOLUTION_BK1 is a hook package and is not intended to be called directly by end users, forms, or concurrent programs. It is instead invoked indirectly by the core Oracle HRMS solution API whenever a solution record is created. The "BK1" suffix denotes one member of a numbered series of hook packages, each corresponding to a specific API operation or stage. The two variants, A and B, give implementers the choice of attaching custom logic at different moments within the create process — B before the identifier is assigned, A after.

Practical usage typically involves copying an Oracle-provided hook template into a customer-owned package and registering it against the standard API, rather than editing PER_SOLUTION_BK1 itself, which remains Oracle-maintained. Because the package header does not expose return values, custom logic must communicate through side effects such as writing to a staging table or invoking another program. In both EBS 12.1.1 and 12.2.2, the package is location-agnostic (it carries no editioning or online-patching annotations) and is typically compiled as part of the standard HRMS patch application. The package is referenced by one other package in the ETRM inventory, confirming its role as a supporting rather than a top-level API component.