Results for “okc_change_requests_tl”

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

Overview

OKC_CHANGE_REQUESTS_TL is the translation (TL) table for the Contracts Core module (OKC) in Oracle E-Business Suite, storing the multilingual, language-dependent attributes of contract change requests. In Oracle EBS Release 12.1.1 and 12.2.2, the Contracts Core schema follows the Oracle Multi-Lingual Support (MLS) architecture, in which descriptive and translatable columns are separated from a base (or "_B") table and placed in a corresponding translation ("_TL") table. Here, the base object is OKC_CHANGE_REQUESTS_B, which holds language-independent data such as identifiers, dates, flags, and status; OKC_CHANGE_REQUESTS_TL holds the columns whose values may differ by installed language, most notably the change request NAME and SHORT_DESCRIPTION. Every translatable row is keyed by the combination of the change request ID and the LANGUAGE code, enabling the same logical change request to be rendered in each configured language. From a heuristic Data Vault modeling perspective, this table is classified as standalone, meaning it is not identified as a traditional hub or link. It is best modeled as a satellite attached to the OKC_CHANGE_REQUESTS_B hub, carrying descriptive, language-qualified attributes and their audit and security metadata.

Key Information Stored

The documented physical schema for OKC_CHANGE_REQUESTS_TL in ETRM 12.2.2 consists of twelve columns. The most significant are:

• ID — Surrogate identifier of the change request; the first component of the primary key and the join back to OKC_CHANGE_REQUESTS_B.
• LANGUAGE — The language code for the translated content; the second component of the primary key.
• SOURCE_LANG — Indicates the source language from which the translation originated, used by MLS tooling.
• SFWT_FLAG — The "Seed/Force/Web/Translatable" flag indicating whether the translatable value is user-maintained or seeded, and how the translation is handled.
• NAME — The user-visible name of the change request in the given language.
• SHORT_DESCRIPTION — The descriptive text summarizing the change request, translated per language.
• CREATED_BY, CREATION_DATE — Standard WHO audit columns capturing who inserted the translation row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — WHO audit columns capturing who last modified the translation and the login context.
• SECURITY_GROUP_ID — The security group (operating unit) context used for data partitioning; a foreign key to FND_SECURITY_GROUPS.

The surrogate primary key is defined by OKC_CHANGE_REQUESTS_TL_PK on (ID, LANGUAGE). The unique index OKC_CHANGE_REQUESTS_TL_U1 also spans (ID, LANGUAGE), confirming that no more than one translation may exist per change request per language. The true business-key candidate is therefore the (ID, LANGUAGE) pair, while the display attributes NAME and SHORT_DESCRIPTION serve as descriptive, non-unique identifiers.

Common Use Cases and Queries

OKC_CHANGE_REQUESTS_TL is queried whenever a change request must be displayed in a specific language, or when reporting across translations. A canonical join retrieves the base attributes with their translated text:

• Translation lookup: SELECT t.name, t.short_description FROM okc_change_requests_tl t WHERE t.id = :id AND t.language = USERENV('LANG');
• Base-plus-translation join: SELECT b.id, t.name, t.short_description FROM okc_change_requests_b b, okc_change_requests_tl t WHERE b.id = t.id AND t.language = :lang;
• Audit reporting: filter on LAST_UPDATE_DATE or CREATED_BY to identify recent or unusual translation maintenance activity.
• Security group scoping: constrain by SECURITY_GROUP_ID to align results with the operating unit context.
• Gap analysis: find change requests lacking a translation in a given language by outer-joining to the translation table and testing for null NAME.

These patterns are common in custom Contracts reports, data migration validation, and localization QA.

Related Objects

• OKC_CHANGE_REQUESTS_B — The base MLS table; join on ID = OKC_CHANGE_REQUESTS_B.ID.
• OKC_CHANGE_REQUESTS_V — The MLS view that joins _B and _TL for language-resolved access.
• FND_SECURITY_GROUPS — Referenced by the SECURITY_GROUP_ID foreign key.
• FND_LANGUAGES — Provides the LANGUAGE code values.
• OKC_CHANGE_REQUESTS_TL_PK / _U1 — Primary key and unique index enforcing (ID, LANGUAGE) uniqueness.
• OKC_CONTRACTS / OKC_TERMS — Parent Contracts objects whose change requests are surfaced through this translation table.

Because it is a pure MLS satellite, direct inserts and updates should be performed through the Contracts APIs rather than manually, to preserve the base/translation integrity mandated by the OKC data model.