Search Results pqh_rule_sets_vl




Overview
Explore in AI Chat

Overview

PQH_RULE_SETS_VL is a multilingual (VL) view owned by the APPS schema within the Public Sector HR (PQH) product family of Oracle E-Business Suite. It presents rules set definitions — the configuration objects that govern how business rules are grouped, evaluated, and applied across an organization hierarchy — in the language of the current session. Rules sets are central to the ETRM (Enterprise Transaction Rules Management) framework used by Oracle Public Sector applications and related modules to determine rule applicability, rule level, and rule category for transactions such as budgeting, position management, and workforce administration.

Because it is a VL view, PQH_RULE_SETS_VL resolves the translatable descriptive attributes (rule set name and description) against the translation table using the session language, while exposing the non-translatable attributes from the base table. This makes it the standard reporting and integration interface for rule set data, since it returns one row per rule set in a single language rather than the multiple rows a raw join to the translation table would produce.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms in the APPS schema:

  • PQH_RULE_SETS — the base (non-translatable) table holding the rule set identifier, organizational context, rule metadata, and who-columns.
  • PQH_RULE_SETS_TL — the translation table holding language-specific RULE_SET_NAME and DESCRIPTION values, keyed by RULE_SET_ID and LANGUAGE.

The defining query joins the two tables on RULE_SET_ID and filters RTL.LANGUAGE = USERENV('LANG'), which restricts output to the current session language. In Oracle EBS 12.1.1 and 12.2.2 the underlying objects are exposed to APPS as synonyms; the view itself carries the PUBLIC synonym convention typical of EBS and is granted to standard reporting responsibilities. Note that the ETRM metadata documents the join as selecting from PQH_RULE_SETS_TL aliased RTL and PQH_RULE_SETS aliased RST, with ROW_ID derived from RST.ROWID.

Key Columns

Common Use Cases and Queries

Typical uses include: listing available rule sets for a business group, identifying seeded versus custom rule sets, tracing rule set hierarchies via REFERENCED_RULE_SET_ID, and feeding rule set metadata into integrations or extracts. Because the view is language-restricted, queries always return names in the session language.

Example 1 — list rule sets for a business group:

  • SELECT rule_set_id, rule_set_name, short_name, rule_level_cd, rule_category FROM pqh_rule_sets_vl WHERE business_group_id = :p_business_group_id ORDER BY rule_set_name;

Example 2 — identify Oracle-seeded rule sets:

  • SELECT rule_set_id, rule_set_name, rule_category, seeded_rule_flag FROM pqh_rule_sets_vl WHERE seeded_rule_flag = 'Y';

Example 3 — resolve referenced rule sets within a hierarchy:

  • SELECT a.rule_set_name parent_rule_set, b.rule_set_name referenced_rule_set FROM pqh_rule_sets_vl a, pqh_rule_sets_vl b WHERE a.referenced_rule_set_id = b.rule_set_id AND a.business_group_id = :p_business_group_id;

Because RULE_SET_NAME and DESCRIPTION are resolved from the translation table, applications needing all installed languages must query PQH_RULE_SETS_TL directly rather than this view.