Results for “oke_boe_description”

50+ results




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

Overview

OKC_K_LINES_TL is the translation table (TL) for the Contracts Core line-level entity OKC_K_LINES_B, maintained in the OKC schema under the OKC - Contracts Core product. In Oracle EBS 12.1.1 and 12.2.2, this object exists to satisfy Oracle Multi-Lingual Support (MLS) standards: user-facing descriptive text is stored in the TL table for each installed language, while language-independent attributes remain in the base table. The title-level companion, OKC_K_HEADERS_TL, follows the same MLS pattern in the Contracts repository.

From a dimensional modeling perspective, the mined Data Vault classification for OKC_K_LINES_TL is standalone. In practical terms, this suggests the table functions as a satellite-style, attribute-bearing child of the line base, rather than a hub or link, since it carries no foreign key relationships other than SECURITY_GROUP_ID references FND_SECURITY_GROUPS. It is not an independent hub of business identity but a language-scoped descriptive extension.

Key Information Stored

The table contains 16 documented columns in the 12.2.2 physical schema. The most significant are:

  • ID — surrogate/foreign identifier joining back to OKC_K_LINES_B. Part of the primary key.
  • LANGUAGE — the MLS language code, the second component of the primary key.
  • SOURCE_LANG — the source language for the translated text.
  • SFWT_FLAG — Software Flag, indicating whether the row was seeded by Oracle (Y) or entered by a user.
  • NAME — the translated line name.
  • COMMENTS — translated free-form comments.
  • ITEM_DESCRIPTION — translated description of the contract line item.
  • BLOCK23TEXT — a translated text block used in contract line presentation.
  • OKE_BOE_DESCRIPTION — translated description associated with the bill-of-entry linkage.
  • COGNOMEN — an additional translated label/identifier for the line.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
  • SECURITY_GROUP_ID — references FND_SECURITY_GROUPS, supporting multi-organization data security.

The primary key is the unique index OKC_K_LINES_TL_PK on (ID, LANGUAGE). A second unique index, OKC_K_LINES_TL_U1, is also defined on (ID, LANGUAGE) and serves as the business-key candidate. The surrogate is the (ID, LANGUAGE) composite; ID alone is the business identifier inherited from the base line.

Common Use Cases and Queries

The primary use case is retrieving a contract line description in a specific language for reports, forms, or OAF pages. A typical query joins the translation to the base line and filters by the session language:

  • SELECT t.NAME, t.COMMENTS FROM OKC_K_LINES_TL t WHERE t.ID = :line_id AND t.LANGUAGE = USERENV('LANG');
  • Join to retrieve all languages: SELECT b.ID, t.LANGUAGE, t.NAME FROM OKC_K_LINES_B b, OKC_K_LINES_TL t WHERE b.ID = t.ID ORDER BY b.ID, t.LANGUAGE;
  • Reporting of translated descriptions in extracts where ITEM_DESCRIPTION or OKE_BOE_DESCRIPTION is required per locale.

Because security is applied through SECURITY_GROUP_ID, queries and reports secured by operating unit should include the appropriate security predicate linking to FND_SECURITY_GROUPS.

Related Objects

  • OKC_K_LINES_B — the base line table; OKC_K_LINES_TL.ID joins to OKC_K_LINES_B.ID. This is the primary relationship.
  • OKC_K_HEADERS_TL — the contract header translation, sharing the same MLS design.
  • OKC_K_HEADERS_B — the contract header base, providing the parent contract context for lines.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for data security.
  • FND_LANGUAGES — the underlying language catalog that defines valid LANGUAGE values for MLS tables.
  • OKC_CONTRACTS_API / OKC_TERMS_UTIL public APIs — used to create and maintain contract line text, which populates the TL rows.

These relationships define the object's role within Contracts Core and its dependency on the multilingual framework of Oracle EBS.