Search Results pqh_rule_sets_tl_pk




Overview

HR.PQH_RULE_SETS_TL is the translation (TL) table for the Rule Set definition in the Oracle E-Business Suite HR schema, part of the Public Sector/HR (PQH) module used for position management, rules configuration, and HR budget/workforce rule processing. Where the base table HR.PQH_RULE_SETS_B stores language-independent rule set attributes, this TL table holds the language-dependent, translated text — specifically the translated rule set name and description. It is registered under FND Design Data as PQH.PQH_RULE_SETS_TL with owner HR and status VALID across EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. In practice it is best understood as a satellite: it carries descriptive, non-key context (name, description, language attributes) attached to a rule set hub key (RULE_SET_ID). Because it references no database object itself and is only referenced by APPS synonyms and triggers, there is no hub-to-hub link relationship, reinforcing its satellite-like role rather than a hub or link.

Key Information Stored

The table's primary key is PQH_RULE_SETS_TL_PK, defined over (RULE_SET_ID, LANGUAGE). In the 12.2.2 physical schema a third column, ZD_EDITION_NAME, is also documented as part of the unique index, reflecting the multi-tenant/editioning model introduced in later releases. This composite key is a genuine business-key candidate because it enforces one translated row per rule set per language.

  • RULE_SET_ID (NUMBER(10), mandatory) — surrogate foreign key linking the translated row to its rule set in the base table; part of the primary key.
  • LANGUAGE (VARCHAR2) — the language in effect for this translated row; part of the primary key and the discriminator enabling multi-language storage.
  • RULE_SET_NAME (VARCHAR2(100)) — the translated rule set name shown to end users.
  • DESCRIPTION (VARCHAR2(240)) — the translated description of the rule set.
  • SOURCE_LANG (VARCHAR2) — the source language from which the translation was derived; supports the standard MLS translation workflow.
  • Standard Who columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit metadata tracking creation and modification.
  • ZD_EDITION_NAME — editioning column present in the 12.2.2 schema, supporting Edition-Based Redefinition.

Common Use Cases and Queries

The chief use case is retrieving the correct translated rule set name and description for a user's session language, then joining to the base table and rule set entities for reporting. A typical pattern filters on LANGUAGE and RULE_SET_ID:

  • Listing all rule sets with their localized names for a given language: SELECT rule_set_id, rule_set_name FROM hr.pqh_rule_sets_tl WHERE language = USERENV('LANG');
  • Joining to the base table on RULE_SET_ID to combine translated text with language-independent attributes.
  • Verifying that every base rule set has a translation in the required language, using an outer join and checking for NULL RULE_SET_NAME.
  • Audit reporting on which rule sets were translated, by whom, and when, using the Who columns.

Related Objects

The dependency metadata shows HR.PQH_RULE_SETS_TL references no database object but is referenced by the APPS synonym PQH_RULE_SETS_TL and the trigger PQH_RULE_SETS_TL041339_WHO (the standard Who-column maintenance trigger), also exposed as a PUBLIC synonym. The most significant related objects are:

  • HR.PQH_RULE_SETS_B — base table joined on RULE_SET_ID.
  • HR.PQH_RULE_SETS_VL / _TL views — MLS views exposing translated content.
  • APPS.PQH_RULE_SETS_TL — synonym for cross-schema access.
  • PQH_RULE_SETS_TL041339_WHO — trigger populating Who columns.
  • HR.PQH_RULE_SET_GROUPS / related PQH rule configuration tables — which consume rule sets keyed by RULE_SET_ID.

The translation table is therefore a supporting MLS satellite to the rule set base entity, essential for multilingual reporting but not a transactional hub in its own right.