Results for “rrs_site_group_nodes_tl”

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

Overview

RRS_SITE_GROUP_NODES_TL is the translation (language) table for site group nodes within the RRS - Site Management module of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. Its documented purpose is to store the translatable attributes of nodes — specifically the user-facing name and description text — while the language-independent attributes reside in the companion base table. The "_TL" suffix follows the standard Oracle EBS multilingual convention: one row exists per node per installed language, keyed by the pair of SITE_GROUP_NODE_ID and LANGUAGE.

In Data Vault terms, the metadata's heuristic classification is satellite-leaning. That is a modeling suggestion rather than a statement of physical design: the table behaves as a descriptive satellite attached to the base entity, holding context (translated text) rather than introducing new business entities or relationships. The true hub or link role belongs to the companion base table, which owns the identifying key.

Key Information Stored

The table is documented with ten columns. The most significant are:

• SITE_GROUP_NODE_ID — surrogate identifier of the site group node; part of the composite primary key and the join column back to the base table.
• LANGUAGE — the NLS language code for the row's translation; the second half of the composite primary key.
• SOURCE_LANG — the language in which the source text was originally authored, used by the translation framework to detect whether a row has been translated or is merely copied from the base language.
• NAME — the translated display name of the site group node.
• DESCRIPTION — the translated descriptive text of the node.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns providing audit and concurrency tracking.

The surrogate primary key is RRS_SITE_GROUP_NODES_TL_PK on (SITE_GROUP_NODE_ID, LANGUAGE). The unique index RRS_SITE_GROUP_NODES_TL_U1 covers the same column pair, meaning the composite key functions simultaneously as the uniqueness constraint for the business key candidate. There is no separate single-column business key; identity is entirely inherited from the base table.

Common Use Cases and Queries

Reporting against this table is almost always language-filtered, since unfiltered queries return one row per installed language and inflate result sets. A typical pattern joins the translation table to the base table and restricts to the session or reporting language:

• Multilingual name lookup: SELECT tl.name FROM rrs_site_group_nodes_tl tl WHERE tl.site_group_node_id = :id AND tl.language = USERENV('LANG');
• Translation completeness audit: compare source_lang against language to find rows that have not yet been translated.
• Node hierarchy reporting: join to RRS_SITE_GROUP_NODES_B to obtain structural attributes and render localized labels.
• Change tracking: use last_update_date and last_updated_by to audit recent translation edits.

Related Objects

The FK metadata documents a dependency on the base table, and the translation pattern implies the standard EBS companions:

• RRS_SITE_GROUP_NODES_B — the base table holding language-independent node attributes; joined on SITE_GROUP_NODE_ID.
• RRS_SITE_GROUP_NODES_TL_PK / _U1 — the primary key constraint and unique index enforcing node-plus-language uniqueness.
• RRS_SITE_GROUP_NODES_VL — the typical MLS view unioning base and translation rows for application queries.
• Site group and node hierarchy tables in the RRS schema that reference node identifiers for structure and ordering.
• FND_LANGUAGES — the language reference table used to validate LANGUAGE values.

Because RRS is a site management module, consumers should expect these objects to be referenced by site-level configuration and reporting logic rather than by core transaction processing.