Search Results pqh_rules




Overview
Explore in AI Chat

Overview

PQH_RULES is a table in the HR schema of Oracle E-Business Suite, owned by the Public Sector HR (PQH) product. It stores configurable business rules that govern the behavior of Public Sector HR processes, most notably position management, budget and position control, and related administrative workflows. Each row represents a single rule definition that is grouped under a rule set, allowing administrators to package and apply rules as a logical unit rather than individually. The table is central to the rule-driven validation and defaulting logic used throughout the PQH module, where rule outcomes determine whether a transaction is permitted, rejected, or modified at runtime.

From a data-modeling perspective, the ETRM metadata classifies PQH_RULES as satellite-leaning based on its foreign key structure. In Data Vault terms, this suggests the table behaves primarily as a descriptive satellite whose rows record attribute detail tied to a parent business key, joined through PQH_RULE_SETS, rather than as an independent hub or link. The single documented foreign key, RULE_SET_ID referencing PQH_RULES.RULE_SET_ID, reinforces this parent-child relationship and confirms that rules cannot exist outside a rule set.

Key Information Stored

The table contains 12 documented columns. The most significant are:

  • RULE_ID — the surrogate primary key, defined by the PQH_RULES_PK constraint. Along with ZD_EDITION_NAME, it forms the unique index, so it is also a business-key candidate.
  • RULE_SET_ID — foreign key to PQH_RULE_SETS, identifying the rule set to which the rule belongs. This column drives the table's primary grouping behavior.
  • APPLICATION_ID — the application context under which the rule applies.
  • LANGUAGE_CODE — language of the rule definition, supporting multilingual deployments.
  • MESSAGE_NAME — identifies the message or text associated with the rule, typically used for validation feedback or rule descriptions.
  • ZD_EDITION_NAME — edition name supporting edition-based redefinition, enabling online patching and versioning of the rule definition.
  • Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — which track who created and last modified each rule and provide optimistic locking for concurrent updates.

The distinction between the surrogate key (RULE_ID) and the business-key candidate (RULE_ID plus ZD_EDITION_NAME) is important for edition-aware queries, since the same logical rule may exist under multiple editions.

Common Use Cases and Queries

Typical operational and reporting scenarios include retrieving all rules for a given rule set, identifying rules associated with a particular application, and auditing rule changes. A representative query joining to the parent rule set is:

  • SELECT r.RULE_ID, r.MESSAGE_NAME, r.LANGUAGE_CODE FROM HR.PQH_RULES r, HR.PQH_RULE_SETS s WHERE r.RULE_SET_ID = s.RULE_SET_ID AND r.RULE_SET_ID = :p_rule_set_id;
  • SELECT RULE_ID, RULE_SET_ID, MESSAGE_NAME FROM HR.PQH_RULES WHERE APPLICATION_ID = :p_app_id AND LANGUAGE_CODE = :p_lang;
  • SELECT r.* FROM HR.PQH_RULES r WHERE r.RULE_ID = :p_rule_id AND r.ZD_EDITION_NAME = :p_edition;

Reporting use cases include listing active rule definitions for documentation, comparing rule sets across editions, and tracing rule messages for troubleshooting validation errors raised during position or budget transactions.

Related Objects

The most significant related objects are:

  • PQH_RULE_SETS — the parent table; PQH_RULES.RULE_SET_ID references PQH_RULE_SETS, joining rules to their sets.
  • PQH_RULES_PK — the primary key constraint on RULE_ID, also serving as the unique index with ZD_EDITION_NAME.
  • Associated PQH rule engine and validation APIs that consume rule definitions at runtime.
  • Other PQH configuration tables referenced by the same rule sets, used in conjunction to resolve complete rule behavior.

Because the documented relationship data is limited, the primary join path of interest remains PQH_RULES.RULE_SET_ID to PQH_RULE_SETS. Administrators extending this model should treat the rule set as the governing business key and preserve edition awareness in all queries.