Search Results rrs_sites_ext_tl




Overview
Explore in AI Chat

Overview

RRS_SITES_EXT_TL is the translation table belonging to the RRS (Site Management) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the language-specific values of user defined attributes (UDAs) associated with sites. In the RRS data model, a site is any physical or logical location tracked by the application — a store, warehouse, depot, service point, or trading partner location — and RRS_SITES_EXT holds the base (non-translated) extension attribute values for those sites. RRS_SITES_EXT_TL carries the multilingual counterparts of those attribute values, so that the same site can present its descriptive attributes in each installed language independent of the language in which the record was originally entered.

The table follows the standard EBS "_TL" convention: it is keyed by the owning entity identifier plus LANGUAGE, and it participates in the Oracle Translation (TPL) mechanism whereby a base table and its translation table are maintained in parallel, typically through the Translation API or a Forms-based translation screen. Its Data Vault classification, derived heuristically from the foreign key structure, is standalone; no FK links to parent or child entities were mined. From a modeling perspective, this is best read as a satellite of the site extension hub (RRS_SITES_EXT), carrying descriptive, time-variant-optional attribute text rather than relationships between hubs.

Key Information Stored

The table contains 52 documented columns in the RRS schema. The most operationally significant are:

  • EXTENSION_ID — the identifier linking the translation row to its parent extension record; the leading column of the primary key.
  • LANGUAGE — the NLS language code for the translated row; the second column of the primary key and the discriminator that makes each row language-specific.
  • SOURCE_LANG — the language in which the base attribute values were originally entered, used by the translation framework to determine whether a re-translation is required.
  • DATA_LEVEL_ID — identifies the attribute group/level context to which the translated values apply.
  • SITE_ID — the site to which the extension record belongs; a denormalized but heavily queried reference.
  • SITE_USE_TYPE_CODE — the site use (for example bill-to, ship-to, or internal) that scopes the UDA values.
  • ATTR_GROUP_ID — the user defined attribute group definition from which the attribute layout is derived.
  • TL_EXT_ATTR1 through TL_EXT_ATTR40 — forty translated attribute value columns holding the actual localized UDA text.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS WHO columns used for auditing and for incremental extraction.

The surrogate primary key is RRS_SITES_EXT_TL_PK on (EXTENSION_ID, LANGUAGE). The unique index RRS_SITES_EXT_TL_U1 covers the same column pair and is therefore the business-key candidate — it enforces that exactly one translation row exists per extension per language.

Common Use Cases and Queries

Reporting and integration scenarios typically resolve a site's localized description by joining the translation table to its base table on EXTENSION_ID and filtering on LANGUAGE. A representative pattern is:

  • Localized site UDA report: SELECT s.site_id, t.tl_ext_attr1, t.tl_ext_attr2 FROM rrs_sites_ext s, rrs_sites_ext_tl t WHERE s.extension_id = t.extension_id AND t.language = USERENV('LANG').
  • Missing-translation audit: compare base rows against translations with an outer join, flagging records where no row exists for a required LANGUAGE or where SOURCE_LANG differs from the current base language.
  • Incremental interface extraction: extract rows where LAST_UPDATE_DATE exceeds the prior run timestamp, keyed by (EXTENSION_ID, LANGUAGE), to push translated UDA text to downstream systems.
  • Attribute-group validation: group by ATTR_GROUP_ID and SITE_USE_TYPE_CODE to confirm that each site use carries the expected set of translated attributes.

Because the table is standalone in the FK graph, queries must supply the join to RRS_SITES_EXT or RRS_SITES explicitly; the translation table alone cannot resolve a site identity beyond SITE_ID.

Related Objects

  • RRS_SITES_EXT — the base extension table; join on EXTENSION_ID. It supplies non-translated attribute values and the site linkage.
  • RRS_SITES — the site master; join through SITE_ID to obtain site name, address, and status.
  • RRS_SITE_USES / site use tables — resolve SITE_USE_TYPE_CODE into meaningful site-use descriptions.
  • RRS_ATTR_GROUPS (or equivalent UDA definition table) — defines the attribute group referenced by ATTR_GROUP_ID and the labels for TL_EXT_ATTR1..40.
  • FND_LANGUAGES — validates the LANGUAGE and SOURCE_LANG codes against installed languages.
  • Translation API / Forms translation screen — the maintenance path through which RRS_SITES_EXT_TL rows are created and updated, rather than direct DML.