Results for “pqh_rule_attributes”

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

Overview

PQH_RULE_ATTRIBUTES is a table in the HR schema owned by the Public Sector HR (PQH) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the detailed attribute definitions associated with a rules set, capturing which attributes a given rule is mapped to and the operation that should be evaluated against each attribute value. In the ETRM documentation this object is classified as VALID and is documented with eleven physical columns. Its heuristic Data Vault classification, mined from the foreign-key structure, is standalone; from a modeling perspective this suggests the table behaves as a reference or configuration structure rather than as a transaction hub or a dependent link. The table therefore serves a metadata role: it does not record business transactions themselves but rather the configuration metadata that drives how PQH rules are evaluated at runtime.

Key Information Stored

The primary key of the table is PQH_RULE_ATTRIBUTES_PK, which is enforced on the RULE_ATTRIBUTE_ID column. RULE_ATTRIBUTE_ID is a surrogate/system-generated identifier and is the only documented unique index, meaning no separate natural business-key constraint is recorded in the metadata.

• RULE_ATTRIBUTE_ID — surrogate primary key uniquely identifying each rule-attribute mapping row.
• RULE_SET_ID — identifies the rule set to which the attribute mapping belongs; this is the principal join column to the parent rule set definition.
• ATTRIBUTE_CODE — the code of the attribute being mapped, indicating which rule input the row governs.
• OPERATION_CODE — the comparison or operation applied to the attribute (for example, the operator used when evaluating the attribute value).
• ATTRIBUTE_VALUE — the value the rule compares against for the mapped attribute.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording the most recent change.
• CREATED_BY, CREATION_DATE — standard WHO columns recording row creation.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OA Framework to detect concurrent updates.

The complete row therefore expresses "for rule set X, attribute Y is evaluated with operation Z against value V", which is the fundamental unit of rule configuration in PQH.

Common Use Cases and Queries

Typical scenarios include auditing the rules configuration that drives Public Sector HR rule evaluation, extracting attribute mappings for migration or setup comparison across environments, and reporting on which operations and values are applied to a given attribute. A representative query joining attributes back to their rule set is:

• SELECT ra.rule_attribute_id, ra.rule_set_id, ra.attribute_code, ra.operation_code, ra.attribute_value FROM hr.pqh_rule_attributes ra WHERE ra.rule_set_id = :p_rule_set_id;
• Attribute usage analysis: SELECT attribute_code, COUNT(*) FROM hr.pqh_rule_attributes GROUP BY attribute_code;
• Change audit: SELECT rule_attribute_id, last_updated_by, last_update_date FROM hr.pqh_rule_attributes ORDER BY last_update_date DESC;

Because the table is configuration metadata, queries are usually read-only and are most useful when joined to the parent rule set entity rather than used in transaction reporting.

Related Objects

The metadata records no downstream foreign keys referencing this table, consistent with its standalone Data Vault classification. The most significant relationships are therefore upward to the rule set it belongs to and to the standard EBS infrastructure objects.

• Rule set definition table — joined via RULE_SET_ID, the parent configuration record to which each attribute row belongs.
• HR.PER_ALL_PEOPLE_F — standard WHO column resolution for CREATED_BY and LAST_UPDATED_BY.
• FND_USER — resolves user identifiers in the WHO columns.
• FND_APPLICATION / FND_APPLICATION_TL — identifies the owning application for the PQH configuration.
• OA Framework entities — the OBJECT_VERSION_NUMBER column indicates the table is maintained through OAF-based setup pages.

These joins support the practical administration and reporting scenarios described above.