Results for “okc_outcomes_tl”

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

Overview

OKC_OUTCOMES_TL is the translation table for OKC_OUTCOMES_B within the OKC – Contracts Core module of Oracle E-Business Suite (validated on 12.1.1 and 12.2.2). It stores the multi-language support (MLS) translatable columns for contract outcome definitions, allowing organizations operating in multiple languages to maintain localized descriptions of outcomes used in contract authoring and lifecycle management. The base table, OKC_OUTCOMES_B, holds the language-independent attributes, while OKC_OUTCOMES_TL holds only the language-sensitive columns, keyed by the parent entity ID and the LANGUAGE code.

Based on the heuristic Data Vault classification mined from the foreign key structure, this object is modeled as standalone. In Data Vault terms, this reflects the fact that it does not itself act as a hub, link, or satellite radiating relationships to other entities; rather, it is a subordinate translation store whose identity is entirely owned by its parent table. Analysts should treat OKC_OUTCOMES_TL as a dependent satellite of OKC_OUTCOMES_B for modeling purposes.

Key Information Stored

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

• ID — Surrogate foreign key to OKC_OUTCOMES_B, identifying the parent outcome record.
• LANGUAGE — The language code for the translated row (e.g., US, AR, FR).
• SOURCE_LANG — The source language from which the translation originates, per MLS standards.
• COMMENTS — The primary translatable text column, holding the localized description or comment for the outcome.
• SFWT_FLAG — "Seed Framework Translation" flag indicating whether the row was seeded by Oracle or user-defined.
• ZD_EDITION_NAME — Editioning column supporting EBS Online Patching (12.2.x).
• SECURITY_GROUP_ID — Multi-tenant security group identifier, joined to FND_SECURITY_GROUPS.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

The surrogate primary key is OKC_OUTCOMES_TL_PK, defined on (ID, LANGUAGE). A unique business-key candidate, OKC_OUTCOMES_TL_U1, is defined on (ID, LANGUAGE, ZD_EDITION_NAME), reflecting the addition of the editioning column in 12.2.x.

Common Use Cases and Queries

Typical usage involves joining the translation table to its base table to retrieve outcome descriptions in the session's language. A standard pattern resolves the language via the NLS session or FND_GLOBAL language context:

• Retrieve outcomes for a specific language: SELECT tl.id, tl.comments FROM okc_outcomes_tl tl WHERE tl.language = USERENV('LANG');
• Join to the base table for full outcome detail: SELECT b.id, tl.comments FROM okc_outcomes_b b, okc_outcomes_tl tl WHERE b.id = tl.id AND tl.language = :p_lang;
• Detect missing translations by comparing row counts between OKC_OUTCOMES_B and OKC_OUTCOMES_TL per ID.
• Audit seeded versus user-defined content using SFWT_FLAG.
• Reporting extracts for contract outcome catalogs in multi-language implementations.

When querying under Online Patching environments (12.2.2), include ZD_EDITION_NAME or rely on the editioning view to reference the current edition.

Related Objects

The most significant related objects are:

• OKC_OUTCOMES_B — Parent base table joined on OKC_OUTCOMES_B.ID = OKC_OUTCOMES_TL.ID.
• FND_SECURITY_GROUPS — Referenced via OKC_OUTCOMES_TL.SECURITY_GROUP_ID for security group resolution.
• FND_LANGUAGES — Provides the language code lookup for the LANGUAGE and SOURCE_LANG columns.
• OKC_OUTCOMES_VL — The MLS view that unions base and translation columns for application display.
• OKC_OUTCOME_ASSOCIATIONS — Links outcomes to contract templates or clauses, joining via the outcome ID.
• OKC_TERMS_TL / OKC_TERMS_B — Parallel MLS structures in the same module, used for consistent translation modeling patterns.
• FND application APIs such as FND_LANGUAGES and the MLS insert/update routines used by the Contracts Core DML framework.