Results for “pa_rbs_element_names_tl”

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

Overview

PA_RBS_ELEMENT_NAMES_TL is the translation table (the _TL suffix denotes "translated") for resource breakdown structure (RBS) element names within the Oracle Projects (PA) module. It stores the language-specific, translatable text associated with elements of an RBS that are not resource types. In Oracle EBS, an RBS organizes the resources assigned to project work—people, organizations, and non-labor resources—into a hierarchical structure. The translatable display name for each of these elements is held separately from the base (language-independent) definition so that the same element can present a localized name to users operating in different languages.

The object resides in the PA schema and is classified as VALID in the ETRM 12.2.2 repository. The base, language-independent attributes of an RBS element name reside in the companion table PA_RBS_ELEMENT_NAMES_B, while this _TL table supplies the per-language RESOURCE_NAME. Because it hangs off a base table via a foreign key and carries descriptive (translatable) attributes rather than business relationships between entities, the heuristic Data Vault classification ("link") should be treated cautiously; a satellite classification is more consistent with translation-table semantics, since it stores descriptive text keyed to a parent entity and a language. Consumers designing a Data Vault model should weigh the "link" suggestion against this satellite interpretation.

Key Information Stored

The documented physical schema exposes nine columns. The most significant are:

• RBS_ELEMENT_NAME_ID — The surrogate identifier that ties each translated row back to its base definition in PA_RBS_ELEMENT_NAMES_B. It is the leading column of the unique index and of the foreign key to the base table.
• RESOURCE_NAME — The translatable resource name for the RBS element in the given language. This is the primary payload of the table and the value rendered to end users.
• LANGUAGE — The language in which RESOURCE_NAME is expressed, drawn from FND_LANGUAGES. Together with RBS_ELEMENT_NAME_ID it forms the business-key candidate.
• SOURCE_LANG — The language from which the translation was derived; populated when a translation is seeded from an existing language and validated against FND_LANGUAGES.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO audit columns recording creation and last-modified context.

The surrogate primary key is RBS_ELEMENT_NAME_ID combined with LANGUAGE. The unique index PA_RBS_ELEMENT_NAMES_TL_U1 (RBS_ELEMENT_NAME_ID, LANGUAGE) is the documented business-key candidate and enforces one translated name per element per language.

Common Use Cases and Queries

The table is consulted whenever RBS element names must be displayed in a user's session language. A common pattern resolves a name for a given element and language, falling back to the base table when no translation exists:

• Retrieve the localized resource name for a specific element: SELECT RESOURCE_NAME FROM PA_RBS_ELEMENT_NAMES_TL WHERE RBS_ELEMENT_NAME_ID = :id AND LANGUAGE = USERENV('LANG');
• List available translations for an element: SELECT LANGUAGE, RESOURCE_NAME FROM PA_RBS_ELEMENT_NAMES_TL WHERE RBS_ELEMENT_NAME_ID = :id;
• Reporting extract joining base and translation for multi-language listings, filtered on LANGUAGE to render a chosen locale.
• Data-quality checks identifying elements lacking a translation in a target language, or translations whose SOURCE_LANG equals LANGUAGE unexpectedly.
• Migration and interface loads that seed translated names across languages, audited via the WHO columns.

Related Objects

• PA_RBS_ELEMENT_NAMES_B — The base (language-independent) table; joined on PA_RBS_ELEMENT_NAMES_TL.RBS_ELEMENT_NAME_ID = PA_RBS_ELEMENT_NAMES_B.RBS_ELEMENT_NAME_ID. This is the primary parent object.
• FND_LANGUAGES — Referenced twice, via LANGUAGE and SOURCE_LANG, to validate language codes and support language-installation validation.
• PA_RBS_ELEMENTS and PA_RBS_ELEMENT_NAMES (and the broader RBS hierarchy objects such as PA_RBS_STRUCTURES) — Depend on element-name definitions and therefore consume the translated name indirectly through the base table.
• PA project resource and assignment query objects — Reporting views and concurrent programs that present RBS resource names resolve translations through this table.

Because translations are joined against the base table and FND_LANGUAGES, any query needing a fully localized RBS element name should combine these objects rather than reading PA_RBS_ELEMENT_NAMES_TL in isolation.