Search Results insert_salary_proposal_b




Overview
Explore in AI Chat

Overview

APPS.HR_MAINTAIN_PROPOSAL_BK1 is a generated PL/SQL package body belonging to the Oracle HRMS API Hook Pre-processor framework. Its header comment identifies the source file as hrpypapi.pkb (release 120.47, dated 2011/08/16) and records that the code was auto-generated on 2012/11/27. The package belongs to the APPS schema and is classified as an "OTHER" API object within the Oracle E-Business Suite 12.1.1 and 12.2.2 releases.

The business purpose of this package is to support the maintenance of salary proposals within Oracle HRMS. Salary proposals represent proposed changes to an employee's compensation, such as a new salary amount, a reason for the change, and associated review dates. The "_BK1" naming convention indicates a "Before Kernel" hook stub generated automatically by Oracle's API pre-processor. Such stubs provide an extensible, empty shell into which customers may insert custom business logic that executes before the corresponding "kernel" business logic. As shipped, the procedures contain no functional processing; they only bracket their own execution with calls to hr_utility.set_location to enable debugging and trace output.

Key Procedures and Functions

The package exposes two documented procedures:

  • INSERT_SALARY_PROPOSAL_A — The first before-kernel hook for the salary proposal creation flow. It encloses its logic between set_location trace calls ("Entering" and "Leaving") and otherwise performs no data manipulation in the delivered code. The parameter list is extensive, covering the pay proposal identifier, assignment, business group, change date, comments, next salary review date, proposal reason, proposed salary number, forced ranking, date to, performance review identifier, twenty descriptive flexfield attribute columns, object version number, multiple components flag, approved flag, element entry identifier, and several BOOLEAN warning flags relating to next salary date, proposed salary, approval, and payroll.
  • INSERT_SALARY_PROPOSAL_B — The companion before-kernel hook for the same insertion flow, carrying a partially documented parameter set including assignment identifier, business group, change date, comments, and next salary review date. Like procedure A, it functions as an extensibility placeholder within the generated API hook architecture.

Tables Accessed

The supplied ETRM documentation does not list any base tables referenced through APPS synonyms for this package body. This is consistent with its role as a generated hook stub: the delivered procedures perform no SELECT, INSERT, UPDATE, or DELETE against the underlying salary proposal tables (such as PER_PAY_PROPOSALS). Any table access occurs in the corresponding kernel package that the hook precedes. The extensive parameter list mirrors the column set of the salary proposal entity, allowing custom code added to the hook to receive and manipulate the same data the kernel will later persist.

Usage Notes

This package is not intended to be called directly by end users or standard application flows. It is invoked indirectly by the HRMS API framework whenever the salary proposal payroll API executes its insertion logic, so that any customer-defined before-kernel rules run first. Typical reasons to modify the package body include validating the proposed salary, deriving dependent flexfield attributes, enforcing approval conditions, or raising warnings before the kernel commits changes.

The ETRM metadata records that this package is referenced by one other package, confirming it is a dependent component within a larger API call chain rather than a top-level entry point. Because Oracle regenerates these hook stubs during upgrades and patches, customizations placed directly in the delivered source should be treated carefully; Oracle provides supported extension mechanisms for preserving such changes. The package is therefore best understood as an extension point within Oracle HRMS salary proposal processing rather than as business logic in its own right.