Search Results okc_k_groups_tl_u1

Overview

OKC.OKC_K_GROUPS_TL is the translation (MLS) table for contract groups within the Oracle Contracts (OKC) module of Oracle E-Business Suite. It stores the language-dependent descriptive attributes of a contract group — specifically the group name and short description — for each installed language, while language-independent attributes reside in the companion base table OKC_K_GROUPS_B. The "_TL" suffix is the standard Oracle Multi-Language Support (MLS) convention: every translatable column from OKC_K_GROUPS_B is duplicated here, keyed by language, so that the same logical contract group can present different names and descriptions depending on the user's session language. In both EBS 12.1.1 and 12.2.2 the object is owned by the OKC schema, is registered in FND Design Data as OKC.OKC_K_GROUPS_TL, and carries a status of VALID. It resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, and its indexes are placed in APPS_TS_TX_IDX. Because contract groups are a foundational grouping mechanism for contracts, this table participates indirectly in contract search, categorization, and reporting wherever a user-visible group name is required. From a Data Vault modeling perspective, and based on the heuristic classification of "standalone" derived from its foreign-key structure, the table is best regarded as a satellite-like descriptive structure attached to the contract-group business key rather than as a hub or link in its own right.

Key Information Stored

The table comprises 13 documented columns. The surrogate primary key is defined by the constraint OKC_K_GROUPS_TL_PK on the combination (ID, LANGUAGE), where ID is a NUMBER generated via the sys_guid() database function and LANGUAGE is the standard MLS language code. The unique index OKC_K_GROUPS_TL_U1 (ID, LANGUAGE, ZD_EDITION_NAME) extends this with the editioning column and serves as the principal business-key candidate, while the non-unique index OKC_K_GROUPS_TL_N1 (LANGUAGE, NAME) supports name-based lookups. The most significant columns are:

• ID — surrogate primary key identifying the contract group; shared across all language rows for the same group and joined back to OKC_K_GROUPS_B.
• LANGUAGE — standard MLS column indicating the language of the row.
• SOURCE_LANG — standard MLS column recording the language from which the row was translated.
• NAME — the translated contract group name (VARCHAR2(150)); the most commonly queried business attribute and the leading column of the N1 index.
• SHORT_DESCRIPTION — user-entered free-format abbreviated description of the group (VARCHAR2(600)).
• ZD_EDITION_NAME — editioning column used by the Online Patching / Edition-Based Redefinition architecture; integral to the unique index U1.
• SFWT_FLAG — documented as not used; retained for MLS consistency.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns providing audit trail information.
• SECURITY_GROUP_ID — used in hosted environments; the only documented foreign key, referencing FND_SECURITY_GROUPS.

Common Use Cases and Queries

The primary use case is retrieving the translated display name of a contract group for forms, concurrent programs, and BI Publisher reports, filtered by the user's language. A typical query joins the translation table to the base table to obtain both language-dependent and language-independent attributes:

• Retrieve a group name for a given language:
  SELECT name, short_description FROM okc.okc_k_groups_tl WHERE id = :group_id AND language = USERENV('LANG');
• Join to the base table to combine translated and untranslated attributes:
  SELECT b.id, t.name, t.short_description FROM okc.okc_k_groups_b b, okc.okc_k_groups_tl t WHERE b.id = t.id AND t.language = USERENV('LANG');
• Reporting on all available translations for auditing or multi-language deployments, ordering by language and name.

Because the N1 index leads with LANGUAGE followed by NAME, queries that filter or sort by language and name benefit from index access. Typical consumers include contract search screens, group selection LOVs, and any extraction that needs to present contract groups in a localized manner.

Related Objects

The most significant related objects are:

• OKC_K_GROUPS_B — the language-independent base table; joined on ID and the source of all translatable columns.
• OKC_K_GROUPS_TL# — the editioning view over the translation table referenced in the dependency metadata.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for hosted-environment security grouping.
• OKC_K_GROUPS_VL — the MLS view that typically unions the base and translation tables for simplified querying.
• OKC_CONTRACTS / OKC_K_HEADERS — contracts that reference a contract group via the group identifier maintained in the base table.
• OKC_K_GROUPS_TL_U1 and OKC_K_GROUPS_TL_N1 — the unique and non-unique indexes central to key enforcement and name-based access.

Developers should treat the "_B" and "_TL" tables as a single logical entity and query through the "_VL" view wherever possible to avoid language-join errors.