Results for “pay_customized_restrictions”

50+ results




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

Overview

PAY_CUSTOMIZED_RESTRICTIONS is an HR-schema table within the Oracle E-Business Suite Payroll (PAY) module. It stores CustomForm restrictions that apply to specific Oracle Forms, allowing implementers and administrators to control when and how particular form elements, titles, or navigation paths are presented to users. The table is primarily associated with legislative and business-group scoping, which enables a single EBS instance to apply different form behaviors across legislation codes and business groups.

In Oracle EBS 12.1.1 and 12.2.2, the object is documented as a VALID table owner HR, and it plays a configuration and metadata role rather than a transaction-capture role. Under the heuristic Data Vault classification derived from its foreign-key structure, the table is hub-leaning. In Data Vault modeling terms, this suggests treating CUSTOMIZED_RESTRICTION_ID as a durable business key hub, with dependent descriptive attributes (form titles, enabled flags, comments) as satellite data, and the references from PAY_RESTRICTION_VALUES and HR_NAVIGATION_NODES as link-style relationships. This is a modeling suggestion, not a native Oracle classification.

Key Information Stored

The table contains 17 documented columns. The most operationally significant are summarized below.

The business-key candidate is captured by PAY_CUSTOMIZED_RESTRICTION_UK2, which combines APPLICATION_ID, FORM_NAME, NAME, BUSINESS_GROUP_ID, LEGISLATION_CODE, and ZD_EDITION_NAME. This composite uniquely identifies a restriction beyond the surrogate primary key.

Common Use Cases and Queries

Typical uses include diagnosing why a form behaves differently across legislations, auditing active restrictions before and after patching, and reporting which forms are customized for a given business group. A standard query retrieves active restrictions for a form:

  • SELECT customized_restriction_id, application_id, form_name, name, legislation_code, enabled_flag FROM pay_customized_restrictions WHERE form_name = :form_name AND enabled_flag = 'Y';
  • Join to PAY_RESTRICTION_VALUES on CUSTOMIZED_RESTRICTION_ID to list the permissible values associated with each restriction.
  • Join to HR_NAVIGATION_NODES on CUSTOMIZED_RESTRICTION_ID to identify navigation entries governed by the restriction.

These queries support troubleshooting, migration validation between 12.1.1 and 12.2.2, and compliance reporting on form-level configuration.

Related Objects

The following objects reference or depend on PAY_CUSTOMIZED_RESTRICTIONS through documented relationships.

  • PAY_RESTRICTION_VALUES — references CUSTOMIZED_RESTRICTION_ID and holds the restriction's permitted values.
  • HR_NAVIGATION_NODES — references CUSTOMIZED_RESTRICTION_ID and links restrictions to navigable form nodes.
  • PAY_CUSTOMIZED_RESTRICTION_PK / PAY_CUSTOMIZED_RESTRICTION_UK2 — unique indexes enforcing the surrogate and business keys.
  • FND_APPLICATION — conceptually joined via APPLICATION_ID to resolve the owning application.
  • HR_ALL_ORGANIZATION_UNITS — conceptually joined via BUSINESS_GROUP_ID to resolve the business group name.