Search Results pay_customized_restriction_uk2




Overview
Explore in AI Chat

Overview

The PAY_CUSTOMIZED_RESTRICTIONS table is a core data object within the Oracle E-Business Suite Payroll module (PAY). It functions as the master repository for defining CustomForm restrictions for specific Oracle Forms. These restrictions are a key extensibility feature, allowing implementers and developers to control the visibility, accessibility, or behavior of fields and blocks within a form based on configurable business rules. The table stores the restriction definitions themselves, which are then associated with specific values or parameters through its child table. This mechanism is central to tailoring the payroll user interface and data entry validation to meet specific legislative or organizational requirements without direct modification of the base application code.

Key Information Stored

The table's structure is designed to uniquely identify a restriction within a specific context. The primary identifier is the system-generated CUSTOMIZED_RESTRICTION_ID. The key contextual columns are APPLICATION_ID (identifying the EBS product), FORM_NAME (the specific form being customized), and NAME (the unique name of the restriction rule). The table supports both multi-organization and legislative setups through BUSINESS_GROUP_ID and LEGISLATION_CODE, allowing restrictions to be scoped appropriately. The combination of APPLICATION_ID, FORM_NAME, NAME, BUSINESS_GROUP_ID, and LEGISLATION_CODE is protected by a unique key (PAY_CUSTOMIZED_RESTRICTION_UK2), ensuring rule definitions are not duplicated within the same scope.

Common Use Cases and Queries

A primary use case is auditing or documenting all CustomForm restrictions applied within a specific business group or for a particular legislation. For instance, a functional consultant may need to list all restrictions on the "Element Entry" form for a given business group. A common reporting query involves joining with PAY_RESTRICTION_VALUES to see the full definition, including the configured values. Sample SQL to find restrictions for a specific form might be:

  • SELECT name, legislation_code FROM pay_customized_restrictions WHERE form_name = 'PAYEEENT' AND business_group_id = 12345;

Another critical scenario is during data migrations or support, where identifying the source of a specific UI restriction requires tracing from the form behavior back to the record in this table via the restriction name logged by the application.

Related Objects

The PAY_CUSTOMIZED_RESTRICTIONS table has a direct parent-child relationship with the PAY_RESTRICTION_VALUES table. This is the primary documented foreign key relationship:

  • PAY_RESTRICTION_VALUES: This table holds the specific parameters or values for a restriction definition. It references PAY_CUSTOMIZED_RESTRICTIONS via the foreign key column PAY_RESTRICTION_VALUES.CUSTOMIZED_RESTRICTION_ID, which joins to PAY_CUSTOMIZED_RESTRICTIONS.CUSTOMIZED_RESTRICTION_ID. A single restriction defined in PAY_CUSTOMIZED_RESTRICTIONS can have multiple associated parameter rows in PAY_RESTRICTION_VALUES.