Results for “okc_operations_tl”

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

Overview

OKC_OPERATIONS_TL is a translatable (language-specific) table within the OKC – Contracts Core product of Oracle E-Business Suite. It stores the Multi-Lingual Support (MLS) translations of the descriptive and meaning-based attributes defined in the base table OKC_OPERATIONS_B. The "_TL" suffix follows Oracle's standard MLS convention: whereas the "_B" table holds language-independent columns and one row per operational entity, the "_TL" table holds one row per entity per installed language, keyed by the combination of the entity code and the language code. The table resides in the OKC schema and is marked VALID in the documented ETRM 12.2.2 physical schema, which lists 14 columns.

From a Data Vault modeling perspective, the metadata provides a heuristic classification of standalone. This suggests OKC_OPERATIONS_TL is best modeled as a satellite-like descriptive structure rather than a hub or a link, because its identity is inherited from the parent operational definition rather than from an independently generated business key. It is essentially a translation satellite attached to the operation code, carrying the text attributes that vary by language.

Key Information Stored

The primary key is OKC_OPERATIONS_TL_PK, defined on the columns CODE and LANGUAGE. This composite key identifies the specific operation being described and the language in which that description is rendered. Two additional unique indexes function as business-key candidates: OKC_OPERATIONS_TL_U1 (CODE, LANGUAGE, ZD_EDITION_NAME) and OKC_OPERATIONS_TL_U2 (MEANING, LANGUAGE, ZD_EDITION_NAME). The inclusion of ZD_EDITION_NAME in both indexes indicates support for the Edition-Based Redefinition (EBR) model used in Release 12.2.x.

The most significant columns include CODE, which links each translation row back to its base definition in OKC_OPERATIONS_B; LANGUAGE, the NLS language identifier; and SOURCE_LANG, which records the original language of the translated text. MEANING and DESCRIPTION hold the user-facing, translatable text of the operation — the label and longer explanation displayed to users. SFWT_FLAG is the standard "Seed/Force/Translatable" flag used by MLS to control whether the row may be updated or copied during language installation. OPN_TYPE captures the operational type classification associated with the operation. The audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN track the lifecycle of each row, while SECURITY_GROUP_ID supports the multi-tenant, security-group partitioning used across OKC contracts data. ZD_EDITION_NAME identifies the edition to which the row belongs.

Common Use Cases and Queries

Typical use cases center on multilingual reporting and lookup resolution. When presenting a list of available operations in a user's session language, queries must join the base table to the translation table and filter by the appropriate language, with a fallback to the source language where no translation exists. A representative pattern is a join from OKC_OPERATIONS_B to OKC_OPERATIONS_TL on CODE, restricted by LANGUAGE = USERENV('LANG') or a validated language preference. Reporting on the set of operation types and their localized meanings is another frequent requirement, as is validating completeness of translations by comparing the count of "_B" rows against "_TL" rows per language.

Because the table participates in EBR, diagnostic queries frequently include ZD_EDITION_NAME filters to isolate the current edition. Administrators also query MEANING and DESCRIPTION to audit user-defined operations that were seeded or customized, and to verify SFWT_FLAG values before applying patches or language installations.

Related Objects

The principal parent object is OKC_OPERATIONS_B, joined on the CODE column; it provides the language-independent attributes that OKC_OPERATIONS_TL translates. The foreign key documented on SECURITY_GROUP_ID references FND_SECURITY_GROUPS, tying each row to the applicable security partition. Translation activation and language installation are governed by the standard MLS infrastructure commonly associated with FND_LANGUAGES and related NLS objects. In practice, the table is consumed by OKC contract authoring and setup pages, and by concurrent programs and reports that resolve localized operation meanings. Together these relationships confirm OKC_OPERATIONS_TL as a dependent translation satellite supporting the multilingual display of Oracle Contracts operations.