Search Results okc_process_defs_tl




Overview
Explore in AI Chat

Overview

OKC_PROCESS_DEFS_TL is the translation (TL) table for the Contracts Core process definition entity in Oracle EBS. It stores the language-specific, translatable columns that accompany the base record held in OKC_PROCESS_DEFS_B. In the Oracle Multi-Lingual Support (MLS) architecture used throughout the E-Business Suite, a base table holds language-independent attributes and a paired _TL table holds the descriptive text that varies by installed language. This table belongs to the OKC schema and is valid in both release 12.1.1 and 12.2.2.

From a data-modeling perspective, the ETRM metadata classifies this object heuristically as a standalone Data Vault entity as mined from its foreign-key structure. A more precise modeling suggestion, given that OKC_PROCESS_DEFS_TL carries descriptive attributes dependent on the parent base row rather than a business key of its own, is that it functions as a satellite keyed on the base entity plus language. Analysts building downstream models should treat it as descriptive, version-of-language context rather than an independent hub.

Key Information Stored

The table contains fifteen documented columns. The physical surrogate identifier is the composite primary key OKC_PROCESS_DEFS_TL_PK, defined on ID and LANGUAGE. ID is the surrogate key that links the translation row to its base row in OKC_PROCESS_DEFS_B; LANGUAGE identifies the language of the descriptive text.

The remaining attributes convey the language-specific content and MLS/audit context:

  • DESCRIPTION and SHORT_DESCRIPTION — the translated descriptive text for the process definition, suitable for display and reporting.
  • NAME — the translated user-facing name of the process definition.
  • COMMENTS — free-form translated commentary associated with the definition.
  • SOURCE_LANG and SFWT_FLAG — MLS metadata identifying the source language and the standard "seed with translation" processing flag.
  • SECURITY_GROUP_ID — the operating-unit/security grouping that scopes access to the record; it is documented as a foreign key to FND_SECURITY_GROUPS.
  • ZD_EDITION_NAME — the editioning column introduced with the EBS online patching (Edition-Based Redefinition) model. It participates with ID and LANGUAGE in the unique index OKC_PROCESS_DEFS_TL_U1, making it a business-key candidate alongside the primary key.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard "who/when" traceability for each translated row.

Common Use Cases and Queries

The table is typically joined to its base table on ID and filtered to the session or report language to return readable process-definition text. A representative query for a single language is:

  • SELECT t.NAME, t.DESCRIPTION FROM OKC_PROCESS_DEFS_TL t, OKC_PROCESS_DEFS_B b WHERE t.ID = b.ID AND t.LANGUAGE = USERENV('LANG');

Reporting scenarios include listing all defined contract process flows with their localized names and descriptions, extracting source text for translation maintenance, and auditing which languages have been populated for a given process definition. Because MLS stores one row per language, a query filtered only on ID may return multiple rows; reports should always constrain LANGUAGE (or aggregate with a language preference). The SECURITY_GROUP_ID provides a further predicate for restricting output to the caller's operating unit. The EDITION_NAME and SFWT_FLAG columns are relevant when validating data migrated or seeded via translation-seeding programs.

Related Objects

The following documented relationships are most significant:

  • OKC_PROCESS_DEFS_B — the base table supplying the language-independent rows; joined on ID.
  • FND_SECURITY_GROUPS — referenced via the SECURITY_GROUP_ID foreign key for access scoping.
  • FND_LANGUAGES — supplies the valid LANGUAGE codes against which rows are validated.
  • OKC_PROCESS_DEFS_TL_PK — the primary-key constraint over ID and LANGUAGE.
  • OKC_PROCESS_DEFS_TL_U1 — the unique index over ID, LANGUAGE, and ZD_EDITION_NAME, identifying the business-key candidate.
  • OKC_PROCESS_DEFS_VL — the conventional MLS view layered over the base and translation tables, which application code queries rather than the physical _TL table.