Search Results okr_template_rgts_tl

Overview

OKR_TEMPLATE_RGTS_TL is a translation (TL) table belonging to the Oracle Contracts for Rights (OKR) product family. The OKR module historically supported rights and royalties contract management within Oracle E-Business Suite, and appears in the 12.1.1 and 12.2.2 codebase lineage as an obsolete or de-supported component. The "_TL" suffix identifies this as the language-dependent companion to the OKR_TEMPLATE_RGTS_B base table, holding descriptive text attributes that vary by installed language.

Per the ETRM metadata, the table is documented as "Not implemented in this database," meaning that in current environments the object may exist in the data dictionary but carry no active data, or may be absent entirely. Its primary key, OKR_TEMPLATE_RGTS_TL_PK, is composed of ID and LANGUAGE, confirming the standard Oracle multi-language pattern: rows are uniquely identified by the surrogate entity identifier combined with the language code.

From a Data Vault modeling perspective, the heuristic classification is standalone. The FK structure mined from the data dictionary returned no relational dependencies, so the object is best treated as neither a hub, link, nor satellite in a strict Data Vault sense. If modeled, it would most naturally be represented as a multi-active or language-qualified satellite attached to a template-rights hub, keyed on the entity ID.

Key Information Stored

Because the table is a translation companion, the column count is small. The following are the columns documented in the ETRM metadata:

• ID — Surrogate foreign key to OKR_TEMPLATE_RGTS_B, the base (language-independent) rights-template table. Part of the composite primary key.
• LANGUAGE — The Oracle language code indicating which installed language the translated text applies to. Part of the composite primary key.
• OKR_TEMPLATE_RGTS_TL_PK — The composite primary key constraint on (ID, LANGUAGE), which enforces one translation row per language for each rights template.

By Oracle convention for TL tables, additional columns such as NAME, DESCRIPTION, and SOURCE_LANG would typically be present, but these are not enumerated in the documented metadata and should be confirmed against the actual data dictionary. The composite primary key is the only documented unique identifier; no separate business-key unique index is reported.

Common Use Cases and Queries

The principal use case is language-sensitive lookup and reporting against the base rights-template table. Standard patterns include joining OKR_TEMPLATE_RGTS_B to the TL table on ID while filtering on LANGUAGE to return a description in the current session language.

• Deterministic translation lookup: SELECT b.id, t.name FROM okr_template_rgts_b b, okr_template_rgts_tl t WHERE b.id = t.id AND t.language = USERENV('LANG');
• Multi-language audit: group rows by ID to detect templates with missing translations across installed languages, useful before enabling a new language.
• Diagnostics: data-dictionary queries against ALL_TAB_COLUMNS and ALL_CONS_COLUMNS to verify whether the object is populated in a given environment, since the metadata records it as not implemented.

Reporting should never assume rows exist for every base record; outer joins from the base table are the safe pattern.

Related Objects

• OKR_TEMPLATE_RGTS_B — base table; join on B.ID = TL.ID, the master-detail relationship implied by the ID column.
• OKR_TEMPLATE_RGTS_TL_PK — composite primary key constraint on ID and LANGUAGE.
• FND_LANGUAGES — validation source for the LANGUAGE code, join on LANGUAGE_CODE = TL.LANGUAGE.
• OKR_TEMPLATE_RGTS_VL — conventional view merging base and translation rows, if defined for this object.
• FND_TERRITORIES / FND_LANGUAGE — supporting reference data for language-dependent display.

Because the ETRM metadata classifies this table as standalone, no additional FK-documented parents or children exist beyond the implicit base-table relationship.