Results for “okc_roles_tl”

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

Overview

OKC_ROLES_TL is a translation (TL) table within the OKC schema, belonging to the Oracle Contracts Core module. In Oracle E-Business Suite Release 12.1.1 and 12.2.2, TL tables store language-specific, translated attributes for a corresponding base table. OKC_ROLES_TL holds translated role definitions — meaning and description text — for the roles used across the Contracts application, keyed by a language code so that the same underlying role identifier can be rendered in the session or installation language.

The documented metadata describes this table's stated purpose as "for future use," indicating it is a reserved or partially implemented structure rather than one actively driven by current Contracts functionality. Even so, its physical definition, primary key, unique index, and foreign key are fully materialized in the 12.2.2 schema, so it is visible to any data dictionary query or ETRM-style reverse-engineering exercise.

Under the Data Vault classification heuristic applied to its foreign-key structure, OKC_ROLES_TL is modelled as a standalone object. In Data Vault terms this suggests it is not a traditional hub or link: it carries no inbound or outbound relationships to other business entities beyond an optional security reference. It behaves most like a descriptive satellite attached to a role identity, holding the language-variant text attributes of that role rather than participating in cross-entity links.

Key Information Stored

The table contains 12 documented columns. The most significant are:

• LANGUAGE — the NLS language code identifying the translation locale; part of the composite primary key and of the unique index.
• CODE — the role code that identifies the role independently of language; the second component of the composite primary key and unique index.
• SOURCE_LANG — the language from which the translated text was derived, used by the translation framework to track origin.
• MEANING — the user-facing translated name of the role.
• DESCRIPTION — the longer translated description of the role.
• SFWT_FLAG — the "Seed/Flag and Translation" style indicator used by Oracle's translation utilities to control whether a row is a seed value and can be overwritten.
• CREATED_BY, CREATION_DATE — standard audit columns recording who created the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording the most recent change and the login that made it.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, partitioning the row for multi-org or security-group access control.

The surrogate primary key is OKC_ROLES_TL_PK over (LANGUAGE, CODE). The unique index OKC_ROLES_TL_U1 is also defined on (LANGUAGE, CODE), confirming that this pair is the business-key candidate: one translated row per language per role code.

Common Use Cases and Queries

Because the table stores the human-readable label and description of each Contracts role, reporting typically joins it to a base role table (or a lookup) on CODE, then filters by the required language. A representative pattern:

• Retrieve role labels for a locale: SELECT code, meaning, description FROM okc_roles_tl WHERE language = USERENV('LANG');
• List all translations for a role: SELECT language, meaning FROM okc_roles_tl WHERE code = :role_code ORDER BY language;
• Find untranslated or stale rows: compare SOURCE_LANG against LANGUAGE, or join to the base table and flag rows where no translation exists.
• Audit changes: use LAST_UPDATED_BY and LAST_UPDATE_DATE to report roles whose labels changed in a given period.

Reporting use cases include generating role glossaries, validating localization coverage before an upgrade, and including readable role names in custom Contracts extracts. Given the "for future use" designation, the safest assumption is that the table may hold few or no production rows, so queries should tolerate empty results.

Related Objects

• OKC_ROLES — the presumed base role table whose CODE is translated by OKC_ROLES_TL.
• FND_SECURITY_GROUPS — referenced by OKC_ROLES_TL.SECURITY_GROUP_ID; join on SECURITY_GROUP_ID.
• FND_LANGUAGES — provides the valid LANGUAGE codes used in the translation rows.
• OKC_ROLES_TL_PK / OKC_ROLES_TL_U1 — the primary key and unique index enforcing one row per CODE and LANGUAGE.
• Other OKC _TL tables — sibling translation tables sharing the same SOURCE_LANG / SFWT_FLAG convention.
• FND_LOOKUPS / FND_LOOKUPS_TL — analogous lookup-translation structures that follow the same TL modelling pattern.
• OKC_CONTRACTS and OKC_ROLE parties — Contracts objects that consume role identity, where the translated MEANING is later displayed.