Search Results pqh_rule_sets_tl




Overview
Explore in AI Chat

Overview

PQH_RULE_SETS_TL is the translation (language-dependent) table for Rule Set definitions within the Oracle E-Business Suite Public Sector HR (PQH) module. A rule set is a named container that groups one or more business rules used by the Rules Engine, most notably by the Position Management and position budgeting/control functionality. The base (language-independent) attributes of a rule set reside in the companion table PQH_RULE_SETS_B, while PQH_RULE_SETS_TL stores the translatable text — principally the rule set name and description — one row per installed language. The row identified by SOURCE_LANG holds the master language text, and additional rows hold translated variants.

The table is owned by the HR schema. The documented physical schema in ETRM 12.2.2 lists 11 columns, and the primary key is PQH_RULE_SETS_TL_PK on (RULE_SET_ID, LANGUAGE). Oracle’s documented unique index includes an edition column, PQH_RULE_SETS_TL_PK (RULE_SET_ID, LANGUAGE, ZD_EDITION_NAME), reflecting the editioning support introduced for this object. From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. A practical modeling suggestion is to treat it as a satellite hanging off a rule-set hub (keyed by RULE_SET_ID), with LANGUAGE acting as a multi-active or descriptive discriminator rather than a separate business entity.

Key Information Stored

The columns below are the most significant of the 11 documented columns. They fall into three groups: the key, the translatable text, and the standard who-columns.

  • RULE_SET_ID — Surrogate identifier of the rule set. It is the foreign reference to the base table PQH_RULE_SETS_B and part of the primary key.
  • LANGUAGE — The language code of the row. It completes the primary key (RULE_SET_ID, LANGUAGE) and determines which translation is returned for a given session language.
  • SOURCE_LANG — The language of the source (master) text for the row, used by the translation framework to identify the original.
  • RULE_SET_NAME — The translatable display name of the rule set, shown in the Rules Engine and position management setup forms.
  • DESCRIPTION — The translatable description of the rule set’s purpose.
  • ZD_EDITION_NAME — The edition discriminator documented in the unique index, supporting edition-based redefinition.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit (who) columns recording creation and last modification context.

The surrogate primary key is RULE_SET_ID plus LANGUAGE, while the business-key candidate is the unique index including ZD_EDITION_NAME. In practice, consumers join to the base table on RULE_SET_ID to combine translatable text with language-independent attributes.

Common Use Cases and Queries

Typical scenarios include reporting the rule set name and description in the user’s session language, validating that all required translations exist, and extracting rule set metadata for list-of-values definitions. A representative query joins the translation table to its base table:

  • SELECT b.rule_set_id, t.rule_set_name, t.description FROM pqh_rule_sets_b b, pqh_rule_sets_tl t WHERE b.rule_set_id = t.rule_set_id AND t.language = USERENV('LANG');
  • Reporting missing translations by comparing installed languages against rows present per RULE_SET_ID.
  • Building LOV queries that display RULE_SET_NAME filtered by LANGUAGE and the current edition.
  • Auditing changes via LAST_UPDATED_BY and LAST_UPDATE_DATE for setup governance.

Related Objects

  • PQH_RULE_SETS_B — The base, language-independent table; joined on RULE_SET_ID.
  • PQH_RULE_SET_RULES — Associates rules to a rule set; joined on RULE_SET_ID.
  • PQH_RULES_B / PQH_RULES_TL — The rule definitions grouped by a rule set.
  • PQH_RULE_SET_GROUPS — Groups rule sets, referencing RULE_SET_ID.
  • FND_LANGUAGES — Source of valid LANGUAGE and SOURCE_LANG values.
  • FND_LANGUAGE_TL — Provides language display names for translation reports.