Search Results per_ri_configurations_tl




Overview
Explore in AI Chat

Overview

PER_RI_CONFIGURATIONS_TL is the translation table for PER_RI_CONFIGURATIONS, the base table that stores configuration definitions used by the Oracle Human Resources "Responsibility Information" (RI) framework. In Oracle E-Business Suite 12.1.1 and 12.2.2, this object resides in the HR schema and carries a VALID status within the PER – Human Resources product family. Its sole architectural purpose is to hold language-specific versions of the translatable descriptive attributes of a configuration, so that end users see configuration names and descriptions rendered in their session language rather than in the language in which the configuration was originally defined.

The table is the classic companion translation pattern found throughout EBS: a base (non-translated) entity table holds the language-independent key, while the "_TL" table holds one row per installed language for each base row. Under a Data Vault heuristic derived from its foreign key structure, PER_RI_CONFIGURATIONS_TL is satellite-leaning: it depends entirely on PER_RI_CONFIGURATIONS and cannot exist without it, and it appends descriptive, change-tracked attributes (name and description) to that parent key rather than establishing new relationships or acting as a hub.

Key Information Stored

The physical schema documented for 12.2.2 contains 11 columns. The most significant are:

  • CONFIGURATION_CODE – The language-independent identifier of the configuration. This is the foreign key to PER_RI_CONFIGURATIONS and forms part of every unique key on this table.
  • LANGUAGE – The NLS language code (for example, "US" or "AR") in which the row's translated text is expressed. Combined with CONFIGURATION_CODE, it identifies the translated instance of a configuration.
  • CONFIGURATION_NAME – The translated (display) name of the configuration as shown to users in the corresponding language.
  • CONFIGURATION_DESCRIPTION – The translated descriptive text for the configuration.
  • SOURCE_LANG – The language in which the source text was originally entered, used by the Multi-Language Support (MLS) translation process to determine whether a row is the installed base or a translated derivative.
  • ZD_EDITION_NAME – The editioning column introduced by the 12.2 online patching architecture; it appears in the documented unique index PER_RI_CONFIGURATIONS_TL_PK.
  • Audit columns – LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE record who created and last touched each translation row, supporting the standard WHO-column audit model.

The primary key is PER_RI_CONFIGURATIONS_TL_PK. The documented unique index PER_RI_CONFIGURATIONS_TL_PK (CONFIGURATION_CODE, LANGUAGE, ZD_EDITION_NAME) is the closest business-key candidate, since it uniquely identifies a configuration's translation per language per edition. The parent reference is PER_RI_CONFIGURATIONS_TL.CONFIGURATION_CODE → PER_RI_CONFIGURATIONS, which is the enforcing foreign key and the join path for all base-to-translation queries.

Common Use Cases and Queries

The dominant use case is joining base configuration rows to their translated text while filtering on the session or reporting language. A typical reporting query constrains the translation result to a single language so that duplicate code rows are not returned:

  • Display configurations in a fixed language: SELECT b.configuration_code, t.configuration_name, t.configuration_description FROM per_ri_configurations b, per_ri_configurations_tl t WHERE b.configuration_code = t.configuration_code AND t.language = 'US'.
  • Audit translation coverage: group by LANGUAGE on the translation table to identify configurations that lack a translation for an installed language (a row-count mismatch against PER_RI_CONFIGURATIONS).
  • Detect untranslated text: compare SOURCE_LANG to LANGUAGE; rows where the two are equal are typically the original installed-language definitions rather than derived translations.
  • Administrative verification: query LAST_UPDATED_BY and LAST_UPDATE_DATE to determine when a given configuration name or description was last changed and by which user.
  • In 12.2 environments, add a ZD_EDITION_NAME predicate consistent with the current runtime edition to ensure queries resolve against the correct edition of the data.

Related Objects

  • PER_RI_CONFIGURATIONS – The base table; joined on CONFIGURATION_CODE and the authoritative parent of this translation satellite.
  • PER_RI_CONFIGURATIONS_TL_PK – The unique index (CONFIGURATION_CODE, LANGUAGE, ZD_EDITION_NAME) that enforces translation uniqueness and drives efficient lookups.
  • PER_RI_CONFIGURATIONS_VL – The MLS view layered over the base and translation tables, providing a single logical row per configuration resolved to the current language.
  • PER_RI_CONFIGURATION_PARAMS and related parameter objects – Child entities of PER_RI_CONFIGURATIONS that inherit the configuration identified by CONFIGURATION_CODE.
  • PER_RI_CONFIGURATION_LEVELS and assignment objects – Dependent definitions that reference the same configuration code and rely on the translation for user-facing labels.
  • FND_LANGUAGES – The language reference table validating the LANGUAGE and SOURCE_LANG values stored here.
  • FND_APPLICATION and the configuration setup forms/APIs – Runtime consumers that read the translated names and descriptions through the "_VL" view rather than the translation table directly.