Results for “okc_subclasses_tl”

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

Overview

OKC_SUBCLASSES_TL is the translation (TL) table that stores the multilingual, language-dependent descriptive columns for contract subclasses defined in Oracle Contracts Core (OKC). In Oracle EBS 12.1.1 and 12.2.2, the base table OKC_SUBCLASSES_B holds the language-independent attributes, while OKC_SUBCLASSES_TL holds the translated MEANING and DESCRIPTION text per installed language, following Oracle Multi-Lingual Support (MLS) standards. Subclasses are the second-level classification beneath contract classes and are used to categorise contracts for template selection, numbering, security, and reporting. The table resides in the OKC schema and is marked VALID in the ETRM data dictionary.

From a Data Vault modelling perspective, the heuristic classification mined from the foreign key structure labels this object as standalone. No hub, link, or satellite dependencies are asserted by the FK metadata, so it should be treated as an independent reference/translation table that augments its base table rather than participating in a modelled hub-link-satellite chain.

Key Information Stored

The table carries 13 documented columns. The most significant are:

• CODE — The subclass identifier; part of the composite primary key and the join key back to the base table.
• LANGUAGE — The NLS language code for the translated row; the second component of the primary key.
• SOURCE_LANG — The language from which the translation originated, used by MLS tooling.
• SFWT_FLAG — Standard MLS "seed/flexfield translation" indicator used by the translation framework.
• MEANING — The translated display name of the subclass.
• DESCRIPTION — The translated long description of the subclass.
• ZD_EDITION_NAME — The editioning column introduced in 12.2 multi-tenant/editioning architecture.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, controlling multi-org/security-group access.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

The surrogate primary key is OKC_SUBCLASSES_TL_PK over (CODE, LANGUAGE). Two unique indexes act as business-key candidates: OKC_SUBCLASSES_TL_U1 (CODE, LANGUAGE, ZD_EDITION_NAME) and OKC_SUBCLASSES_TL_U2 (MEANING, LANGUAGE, ZD_EDITION_NAME), the latter enforcing uniqueness of the translated meaning within a language and edition.

Common Use Cases and Queries

Typical usage retrieves the translated subclass name for display in LOVs and reports. A standard pattern joins the base and TL tables filtered by the session language:

• SELECT t.code, t.meaning FROM okc_subclasses_tl t WHERE t.language = USERENV('LANG');
• Reporting on all available translations: SELECT code, language, meaning, description FROM okc_subclasses_tl WHERE code = :p_code ORDER BY language;
• Validating translation completeness by comparing base-table codes against TL rows for a target language.
• Bulk maintenance of subclass descriptions via the standard MLS concurrent programs rather than direct DML, since direct inserts bypass the translation framework.

Because reporting frequently requires audit and edition information, joins often include ZD_EDITION_NAME and the WHO columns to trace when a translation was last revised.

Related Objects

• OKC_SUBCLASSES_B — The base table; joined on CODE to supply language-independent attributes.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID to enforce security-group partitioning.
• OKC_CLASSES_B / OKC_CLASSES_TL — Parent class tables with parallel MLS translation structures.
• OKC_CONTRACTS_B / OKC_CONTRACTS_TL — Contract headers classified by subclass.
• OKC_TEMPLATES_B — Contract templates associated with a subclass.
• FND_LANGUAGES — Provides the valid LANGUAGE code set.

Together these objects form the classification and translation layer that drives Oracle Contracts Core display and selection behaviour.