Search Results okc_sections_tl_u1

Overview

OKC.OKC_SECTIONS_TL is the translation (TL) table for the OKC_SECTIONS entity within the Oracle Contracts (OKC) module of Oracle E-Business Suite. It stores the language-dependent descriptive content associated with contract sections — most notably the section heading — while the language-independent structural attributes of a section are held in the corresponding base table OKC_SECTIONS_B. The "_TL" suffix and the presence of the LANGUAGE and SOURCE_LANG columns identify this as a standard Oracle Multi-Language Support (MLS) translation table, meaning a single logical section row can have one physical row per installed language.

From a heuristic Data Vault modeling standpoint, this object is best classified as a satellite. It carries descriptive, language-qualified attributes (the HEADING text) keyed to the parent section identifier, and its payload changes independently of the structural relationships between entities. The translation key of (ID, LANGUAGE) acts as the effective primary key for each language-specific record.

Key Information Stored

The table is documented with eleven columns. The most significant are:

• ID — Number; the primary key column that ties each translated row back to its parent section in OKC_SECTIONS_B.
• LANGUAGE — VARCHAR2(12); the standard MLS column indicating the language of the row. Together with ID it forms the composite unique key OKC_SECTIONS_TL_U1 and the primary key OKC_SECTIONS_TL_PK.
• SOURCE_LANG — VARCHAR2(12); the MLS column recording the language from which the row was originally derived, used by the translation framework to determine whether re-translation is required.
• SFWT_FLAG — VARCHAR2; a flag indicating that a value was changed in another language. The ETRM metadata explicitly notes this is "not fully implemented in 11i."
• HEADING — VARCHAR2(300); the section heading text, and the principal business attribute that this translation table exists to store.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who columns providing audit lineage for each row.
• SECURITY_GROUP_ID — NUMBER; used in hosted environments and referenced by a foreign key to FND_SECURITY_GROUPS.

The documented unique index, OKC_SECTIONS_TL_U1, defines the business-key candidate as the combination of ID and LANGUAGE, confirming that any query intended to be deterministic must constrain on both columns. The surrogate primary key is the same pair, with no single-column surrogate.

Common Use Cases and Queries

Reporting against this table is typically performed to retrieve section headings in a specific language, or to audit which translations exist. Because it is an MLS table, a common pattern is to join it to OKC_SECTIONS_B on ID while filtering LANGUAGE to the session or reporting language. A representative query is:

SELECT s.ID
     , t.LANGUAGE
     , t.HEADING
  FROM OKC.OKC_SECTIONS_B  s
     , OKC.OKC_SECTIONS_TL t
 WHERE s.ID = t.ID
   AND t.LANGUAGE = USERENV('LANG');

Other frequent scenarios include translation-gap analysis (identifying sections whose SOURCE_LANG differs from the current LANGUAGE), documentation exports for contract templates, and multilingual contract deliverables. Note that Oracle restricts direct access to this object; it is intended to be accessed through standard Oracle Contracts programs and the MLS APIs rather than through ad hoc DML.

Related Objects

The following objects are most significant in relation to OKC_SECTIONS_TL:

• OKC_SECTIONS_B — the language-independent base table holding the structural section attributes; joins to this table on ID.
• FND_SECURITY_GROUPS — referenced via the SECURITY_GROUP_ID foreign key.
• OKC_SECTIONS_TL# — the internal object listed as referencing this table in the dependency metadata.
• OKC_SECTIONS_TL_U1 — the unique index on (ID, LANGUAGE) that enforces the business-key candidate.
• OKC_SECTIONS_TL_PK — the primary key constraint on (ID, LANGUAGE).

Consumers should treat OKC_SECTIONS_TL as a read-oriented translation satellite and rely on Oracle Contracts APIs for any data maintenance.