Search Results pay_backpay_sets_pkg

Overview

PAY_BACKPAY_SETS_PKG is a payroll-setup PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Its documented purpose is to support the definition and validation of backpay sets — named groupings of backpay elements and related rules that Oracle Payroll uses when calculating retroactive (backpay) adjustments for employees.

In Oracle Payroll, backpay processing recalculates prior periods when an element entry, rate, or eligibility change is made with a retroactive effective date. Backpay sets let an administrator control which elements participate in that recalculation and how they are grouped, rather than applying the recalculation universally. PAY_BACKPAY_SETS_PKG exists to enforce the integrity of those set definitions — most notably by guaranteeing that each backpay set is uniquely named within its business group.

The package is classified in the ETRM metadata as an OTHER API. This classification is significant: unlike PUBLIC APIs, which are certified as stable integration points and carry Oracle's compatibility guarantees, an OTHER package is an internal implementation object. It is exposed in the data dictionary but is not part of Oracle's published interface contract, and its signature may change between releases.

Key Procedures and Functions

The package declares a single documented procedure:

• CHECK_NAME_UNIQUENESS — As the name states, this procedure verifies that a proposed backpay set name is not already in use within a given business group. It is a validation routine, intended to be called before a new set is created or an existing set is renamed, so that duplicate set names are rejected at the point of entry rather than surfacing as ambiguous data later. The ETRM metadata lists three parameters (p_bus_grp_id, p_set_name, and p_set_id) mapping to business group, set name, and set identifier. The inclusion of p_set_id allows the check to distinguish an update to the current record from a genuine collision with a different set.

The package contains no documented functions and no other documented procedures. The package body is not part of the published metadata; no additional public entry points should be assumed.

Tables Accessed

The ETRM metadata records exactly one referenced table, accessed through its APPS synonym:

• PAY_BACKPAY_SETS — the base table storing backpay set definitions. CHECK_NAME_UNIQUENESS queries this table to detect an existing row matching the supplied business group and set name. The procedure is a read-only validation routine; it does not insert, update, or delete rows. Population and maintenance of PAY_BACKPAY_SETS is handled by the forms and DML layer that call this package, not by the package itself.

No other tables are documented as referenced by this package.

Usage Notes

PAY_BACKPAY_SETS_PKG is an internal helper invoked by the Oracle Payroll setup forms — specifically the Backpay Set definition window under the Payroll configuration responsibility — when a user saves or renames a backpay set. In that flow, the form calls CHECK_NAME_UNIQUENESS to validate the entered name before committing the record, and raises a validation error if the name is already in use in the business group.

Because the package is classified as OTHER and the metadata in this release records no other packages depending on it, it should be treated as private implementation. Custom code and integrations should not call it directly; the supported path for creating backpay sets is through the standard setup forms or, where available, certified Payroll APIs. Direct invocation by custom code risks breakage on upgrade, since internal signatures are not preserved across releases.

Note that the ETRM excerpt carries a header date from 1999 and a version marker of 115.0. This indicates the object has been stable, and effectively untouched, for many release cycles across both EBS 12.1.1 and 12.2.2. Its documented scope — a single uniqueness check against one table — is correspondingly narrow, and it should not be expected to perform backpay calculation, element processing, or any other payroll business logic.