Results for “uniqueness_check”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PAY_CUST_RESTRICT_PKG is a small, self-contained PL/SQL package body that supports Oracle HRMS and Payroll configuration of customized restrictions. Customized restrictions are the user-defined rules stored in the PAY_CUSTOMIZED_RESTRICTIONS table that control which business group, legislation, or organizational context a given restriction applies to. The package encapsulates the validation and identity-assignment logic required when an end user defines or modifies such a restriction through a form-based maintenance flow.

The body contains two procedures: UNIQUENESS_CHECK, which enforces name uniqueness and generates a synthetic primary key for new records, and POST_QUERY, which resolves a technical form name into its user-facing display name for display in the form. The package is owned by APPS, is classified as OTHER, and is not referenced by any other package, meaning it is invoked directly rather than as part of a larger dependency chain. The source header indicates it was originally delivered as file pecrs01t.pkb version 115.1, last touched during a porting shipment, which is consistent with the long-standing Oracle Payroll "customized restrictions" feature set.

Key Procedures and Functions

• UNIQUENESS_CHECK — Determines whether the supplied restriction name already exists for the same business group and legislation code, and, when unique, assigns the next value from the PAY_CUSTOMIZED_RESTRICTIONS_S sequence to the in/out restriction identifier parameter. The check is performed by a single-row cursor that compares uppercased names and applies NVL-normalized comparisons on business group and legislation, with a ROWID comparison (or a NULL ROWID) used to exclude the record currently being edited. When a duplicate is found, the procedure raises the Oracle error message associated with HR_6030_CUST_UNIQUE_NAME through HR_UTILITY.SET_MESSAGE and HR_UTILITY.RAISE_ERROR, halting the transaction. If no duplicate exists and the procedure was not called from the WVI (Web Validation Infrastructure) flow, it fetches the sequence into the caller's identifier parameter. When invoked from WVI, the procedure returns without consuming a sequence value, leaving key generation to the caller.
• POST_QUERY — A lightweight post-query display helper that returns the user form name for a given form name and application identifier by querying FND_FORM_VL. It populates the in/out display form name parameter so that the form can present a friendly label rather than the internal form name.

Tables Accessed

• PAY_CUSTOMIZED_RESTRICTIONS — Read (via the C_C1 cursor) to detect an existing record with the same name, business group, and legislation. The cursor selects a constant 1 and filters using NVL-normalized comparisons so that NULL business group or legislation values are treated consistently.
• PAY_CUSTOMIZED_RESTRICTIONS_S — Read (via the C_NEXTVAL cursor on SYS.DUAL) to obtain the next sequence value used as the new customized restriction identifier.
• FND_FORM_VL — Read by POST_QUERY to resolve the user form name and application identifier into a display name.

Usage Notes

This package is typically invoked from the Oracle Forms-based maintenance screens for customized restrictions, where UNIQUENESS_CHECK is called on save or on field validation, and POST_QUERY is called after a query to populate display fields. The WVI branch indicates that the same logic is reachable from the Web Validation Infrastructure used by newer self-service and web-based payroll flows, in which case the caller manages the sequence value itself. Because there are no dependent packages, customizations and extensions that call these procedures are not exposed to ripple effects from other code, but any custom code that raises or handles duplicate-name errors should be prepared for the HR_6030_CUST_UNIQUE_NAME message raised through HR_UTILITY. The package behaves identically on EBS 12.1.1 and 12.2.2, as the PAY_CUSTOMIZED_RESTRICTIONS schema has not changed across those releases.