Search Results pqh_rules_fk1

Overview

HR.PQH_RULES is a configurable business rules table within the Oracle E-Business Suite HR schema, part of the Oracle Public Sector Human Resources (PQH) application family. It stores rule definitions that drive configurable business logic used throughout HR and related public-sector processes during Oracle EBS 12.1.1 and 12.2.2 deployments. The table resides in the APPS_TS_TX_DATA tablespace and is registered in FND Design Data as PQH.PQH_RULES.

The object carries a Data Vault classification heuristic of satellite-leaning. This modeling suggestion reflects the fact that the table holds descriptive, attribute-level rows governed by a single parent key, with few outbound referential dependencies. In practice, PQH_RULES behaves as a dependent detail table: each row is a rule instance that hangs off a rule set, and its usefulness derives from the parent context rather than from independent identity. Designers modeling this structure should treat it as a satellite anchored to PQH_RULE_SETS as the surrounding hub/link context.

Key Information Stored

RULE_ID is the surrogate primary key, enforced by the unique index PQH_RULES_PK on the RULE_ID column. In the documented 12.2.2 physical schema the unique index is recorded as spanning RULE_ID together with ZD_EDITION_NAME, which serves as the business-key candidate when edition-aware lookups are required. Beyond the key, the most significant columns include:

• RULE_SET_ID — the parent rule set to which the rule belongs; a mandatory foreign key to PQH_RULE_SETS and the basis for the PQH_RULES_FK1 non-unique index.
• APPLICATION_ID — identifies the owning application context for the rule.
• LANGUAGE_CODE — the language of the rule definition, supporting multilingual deployments.
• MESSAGE_NAME — the message or rule name (VARCHAR2(30)) associated with the rule.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle framework to detect concurrent updates.
• Standard Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture audit and accountability metadata.
• ZD_EDITION_NAME — editioning column supporting Edition-Based Redefinition for online patching.

Common Use Cases and Queries

Typical usage revolves around retrieving rule definitions for a given rule set, auditing rule configuration, and diagnosing rule-driven behavior. Because PQH_RULES is unlikely to be queried in isolation, joins to PQH_RULE_SETS are standard. A representative query pattern mirrors the documented Query Text:

• Rule lookup by set: SELECT r.RULE_ID, r.MESSAGE_NAME FROM HR.PQH_RULES r WHERE r.RULE_SET_ID = :p_rule_set_id
• Join to parent for descriptive context: SELECT r.RULE_ID, rs.RULE_SET_NAME, r.MESSAGE_NAME FROM HR.PQH_RULES r, HR.PQH_RULE_SETS rs WHERE r.RULE_SET_ID = rs.RULE_SET_ID
• Audit reporting on recent changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Concurrent-change diagnostics using OBJECT_VERSION_NUMBER.

Reporting teams frequently use this table to validate that every rule set has at least one configured rule, and to detect orphaned or language-specific duplication.

Related Objects

HR.PQH_RULES maintains a single documented foreign key to PQH_RULE_SETS via RULE_SET_ID, making that table the principal related object. Downstream dependencies and companion synonyms include:

• HR.PQH_RULE_SETS — parent table linked on RULE_SET_ID; provides rule set identity and descriptive attributes.
• APPS.PQH_RULES — application synonym exposing the table to the APPS schema.
• APPS.PQH_RULES_WHO — Who-column companion view for standard audit access.
• PUBLIC.PQH_RULES — public synonym enabling general access.

No outbound references beyond PQH_RULE_SETS are documented, confirming the table's satellite-leaning character within the PQH rule configuration model.