Search Results check_name_uniqueness

Overview

APPS.PAY_BACKPAY_SETS_PKG is a payroll-level PL/SQL package body in the Oracle E-Business Suite (available in both 12.1.1 and 12.2.2) that supports the Backpay Set setup entity used by Oracle Payroll. A backpay set groups one or more payroll elements for which retroactive (backpay) processing is to be performed, and it is defined within the scope of a business group. The package encapsulates the server-side validation logic required by the Backpay Set definition form, ensuring the integrity of the data that the form ultimately inserts into or updates in the underlying base table. The package is classified in the ETRM metadata as OTHER, meaning it is not registered as a public or open API; it is internal support code invoked by the Oracle Payroll forms layer rather than something intended to be called directly by customer extensions. The documented package body is small and purpose-built, containing a single procedure whose sole responsibility is enforcing name uniqueness during form-level data entry and maintenance.

Key Procedures and Functions

The documented metadata lists one procedure: CHECK_NAME_UNIQUENESS.

• CHECK_NAME_UNIQUENESS — Validates that the name of a backpay set is unique within its owning business group. The procedure accepts the business group identifier, the backpay set name, and the backpay set identifier as inputs and branches on whether the set identifier is null. When the identifier is null the operation is an insert, so the procedure tests whether any row in PAY_BACKPAY_SETS already carries the same name within the same business group. When the identifier is not null the operation is an update, so the same test is performed but the current row is excluded from the comparison via the inequality on the primary key. If an existing duplicate is found, an error condition is signaled by raising the predefined application message PAY_7883_USER_TABLE_UNIQUE through the FND_MESSAGE API, which surfaces the standard “the value entered is not unique” style error to the user.

No other procedures or functions are documented in the ETRM metadata for this package.

Tables Accessed

The package references a single table, PAY_BACKPAY_SETS, accessed through the APPS synonym.

• PAY_BACKPAY_SETS — The Payroll base table that stores backpay set definitions. The uniqueness check reads this table to determine whether the supplied set name already exists for the given business group. The query selects no business columns; it is a pure existence test, using an anti-join construct wrapped in a DUAL query. The business_group_id column is compared with a numeric coercion (business_group_id + 0), and the primary key column used for the update exclusion is backpay_set_id.

The procedure performs read-only access. It does not insert, update, or delete rows; the form itself performs the DML once validation has passed.

Usage Notes

CHECK_NAME_UNIQUENESS is invoked from the Oracle Payroll Backpay Sets window during both the insert and update phases of record processing, typically from the WHEN-VALIDATE-RECORD or pre-insert/pre-update trigger on the backpay set name item. It is an internal validation routine and is not listed as a public API, so it should not be called from custom code in place of a supported interface; customers extending the Backpay Set form should expect the standard Oracle-owned validation to run first.

Because the uniqueness rule is scoped to the business group, the same backpay set name may legitimately exist in two different business groups. The error emission uses the FND_MESSAGE/FND_MESSAGE.RAISE_ERROR pattern, so any calling context must be prepared for a raised Oracle Forms error rather than a returned status flag. The package is self-contained, is referenced by no other documented packages, and its behavior is unchanged between EBS 12.1.1 and 12.2.2 as far as the documented metadata indicates.