Search Results okc_qa_check_lists_tl




Overview
Explore in AI Chat

Overview

OKC_QA_CHECK_LISTS_TL is the translation (multi-language support, or MLS) table belonging to the Oracle Contracts Core (OKC) module in Oracle E-Business Suite. It stores the language-specific, translatable columns of the base table OKC_QA_CHECK_LISTS_B, which defines quality assurance check lists used during contract authoring and administration. In Oracle EBS 12.1.1 and 12.2.2, MLS architecture separates language-independent data into a base ("_B") table and language-dependent text into the corresponding "_TL" table, allowing the same functional record to carry distinct translated names and descriptions per installed language.

The table is owned by the OKC schema and is documented as VALID. Its role is to supply the translated list name and short description that users see in the Contracts workbench and in quality-assurance check list setup screens, while the base table retains the functional and audit attributes. The primary key is OKC_QA_CHECK_LISTS_TL_PK on (ID, LANGUAGE), confirming that each row represents one check list in one language.

The ETRM metadata classifies this object, via heuristic Data Vault mining, as standalone. In Data Vault terms, the "_B" parent behaves as a hub-like entity keyed by ID, and this "_TL" table functions as a descriptive satellite holding the translated NAME and SHORT_DESCRIPTION attributes; the absence of inbound functional foreign keys (other than the security group reference) supports the standalone classification.

Key Information Stored

The table contains 13 documented columns. The most significant are:

  • ID — Surrogate identifier of the check list; the first component of the primary key and the join back to OKC_QA_CHECK_LISTS_B.
  • LANGUAGE — The installed language code for the translated row; the second component of the primary key.
  • SOURCE_LANG — The language from which the row was originally derived.
  • NAME — The translated display name of the quality assurance check list.
  • SHORT_DESCRIPTION — The translated short description shown to users.
  • SFWT_FLAG — Standard MLS flag indicating whether the row has been manually translated or is a default placeholder.
  • CREATED_BY, CREATION_DATE — Who inserted the translated row and when.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent change and the session that made it.
  • SECURITY_GROUP_ID — References FND_SECURITY_GROUPS, supporting multi-organization security.
  • ZD_EDITION_NAME — Edition-based redefinition column present in the 12.2.2 documented schema, enabling online patching.

Business-key candidates are recorded in unique indexes: OKC_QA_CHECK_LISTS_TL_U1 (ID, LANGUAGE, ZD_EDITION_NAME) and OKC_QA_CHECK_LISTS_TL_U2 (NAME, LANGUAGE, ZD_EDITION_NAME). The first confirms uniqueness of a check list per language per edition; the second enforces uniqueness of the translated name within a language.

Common Use Cases and Queries

Typical access patterns resolve the translated text for a base check list and filter by the session language. A standard join pattern:

  • SELECT b.id, b.<functional_column>, tl.name, tl.short_description FROM okc_qa_check_lists_b b, okc_qa_check_lists_tl tl WHERE b.id = tl.id AND tl.language = USERENV('LANG');
  • Lookup by translated name: SELECT id FROM okc_qa_check_lists_tl WHERE name = :name AND language = USERENV('LANG');
  • Administrative audit of translations: SELECT language, sfwt_flag, last_updated_by, last_update_date FROM okc_qa_check_lists_tl WHERE id = :id;
  • Edition-aware reporting on 12.2.2: filter on ZD_EDITION_NAME to isolate the active edition.

Report use cases include contract quality-assurance dashboards, setup listings of available check lists by language, and validation that every base record has a translation row in the required languages (an MLS completeness check).

Related Objects

  • OKC_QA_CHECK_LISTS_B — Base table; join on ID (and ZD_EDITION_NAME in 12.2.2) to retrieve functional columns.
  • OKC_QA_CHECK_LISTS_TL_PK — Primary key constraint on (ID, LANGUAGE).
  • OKC_QA_CHECK_LISTS_TL_U1 / _U2 — Unique indexes enforcing business-key candidates.
  • FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID for security-group assignment.
  • FND_LANGUAGES — Provides the valid values for the LANGUAGE column.
  • OKC_QA_RESULTS — Downstream check list results that depend on the parent check list definition.
  • OKC_QA_CHECKLIST_GROUPS — Grouping structure that associates check lists during contract QA processing.

These relationships make the table essential to presenting localized quality-assurance check list definitions across the Contracts module.