Results for “pay_restriction_values”

50+ results




Overview
Explore in AI Chat

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

Overview

PAY_RESTRICTION_VALUES is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the discrete values that customize a form through the restriction framework. In EBS terminology, a "restriction" is a filtering or customization construct applied to a form or flexfield region so that only permitted values are presented to the user. PAY_RESTRICTION_VALUES holds those permitted (or excluded) values, each tied back to a parent restriction defined in PAY_CUSTOMIZED_RESTRICTIONS. The object is documented in ETRM as VALID with a physical structure of eleven columns.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this table as satellite-leaning. It carries a single foreign key to PAY_CUSTOMIZED_RESTRICTIONS and holds descriptive, attribute-like content rather than defining a new business hub or resolving many-to-many links. A modeler would therefore treat it as a satellite of the parent customized-restriction entity, with the parent key acting as the driving reference.

Key Information Stored

The table's most significant columns fall into three groups: the parent reference, the business keys, and the audit/legislative attributes.

  • CUSTOMIZED_RESTRICTION_ID — Foreign key to PAY_CUSTOMIZED_RESTRICTIONS.CUSTOMIZED_RESTRICTION_ID, identifying the parent restriction to which this value belongs. This is the primary join path and the leading column of the unique index.
  • RESTRICTION_CODE — The code identifying the restriction dimension being valued. Part of the business-key candidate set.
  • VALUE — The actual value supplied for the restriction (the permitted or excluded item). Part of the business-key candidate set.
  • INCLUDE_EXCLUDE_FLAG — Indicates whether the VALUE is included in or excluded from the restriction's result set, enabling both whitelist and blacklist customization.
  • REFERENCE_LEGISLATION_CODE — Legislative context under which the value applies, supporting country-specific payroll behavior.
  • ZD_EDITION_NAME — The edition/versioning column, part of the unique index and used for edition-based redefinition.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE capture standard EBS who/when metadata.

No standalone surrogate primary key is documented separately in the extracted metadata; the business-key candidate is the unique index PAY_RESTRICTION_VALUES_U50 on (CUSTOMIZED_RESTRICTION_ID, RESTRICTION_CODE, VALUE, ZD_EDITION_NAME), which defines the natural uniqueness of a value within a restriction.

Common Use Cases and Queries

The principal use case is resolving the effective value set for a payroll form restriction. A typical reporting query joins the values to their parent restriction to produce a complete restriction definition:

  • Listing all included values for a restriction: SELECT RESTRICTION_CODE, VALUE FROM HR.PAY_RESTRICTION_VALUES WHERE CUSTOMIZED_RESTRICTION_ID = :id AND INCLUDE_EXCLUDE_FLAG = 'I';
  • Finding where a specific value is referenced across restrictions: SELECT DISTINCT CUSTOMIZED_RESTRICTION_ID FROM HR.PAY_RESTRICTION_VALUES WHERE VALUE = :val;
  • Legislation-scoped reporting: filter on REFERENCE_LEGISLATION_CODE to compare restriction values between country setups.
  • Edition-aware queries in 12.2.2 should account for ZD_EDITION_NAME when resolving the active definition.

These patterns support setup validation, migration comparison between environments, and audit reporting on who customized which form restrictions.

Related Objects

  • PAY_CUSTOMIZED_RESTRICTIONS — The parent table; joined via CUSTOMIZED_RESTRICTION_ID. This is the only documented foreign-key relationship and the foundation for all value lookups.
  • PAY_RESTRICTION_VALUES_U50 — The unique index enforcing the business key.
  • HR schema objects generally — Restriction values are consumed indirectly by the Payroll form engine and related flexfield/validation components that apply restrictions at runtime.
  • DBA/ETRM metadata catalogs — Describe this object's structure and column semantics for 12.1.1 and 12.2.2.

Because the documented relationship data is limited to the single parent reference, related-object analysis beyond PAY_CUSTOMIZED_RESTRICTIONS relies on schema knowledge rather than explicit FK evidence, so joins should be validated against the target instance.