Search Results okc_condition_headers_tl_u1

Overview

The table OKC.OKC_CONDITION_HEADERS_TL is the translation (MLS) table for Oracle Contracts condition headers in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the language-dependent descriptive attributes of condition headers — the name, description, short description, and comments that users see when defining and reviewing contract terms. The corresponding language-independent attributes (such as the condition identifier, status flags, and operational controls) reside in the companion base table OKC_CONDITION_HEADERS_B, and each row in this translation table is keyed back to that base table by ID plus LANGUAGE.

The object resides in the OKC schema, is registered under FND Design Data as OKC.OKC_CONDITION_HEADERS_TL, and has a VALID status. Its storage is allocated in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and its unique index OKC_CONDITION_HEADERS_TL_U1 is stored in APPS_TS_TX_IDX. In 12.2.2 the documented physical schema shows 15 columns and extends the unique key to include ZD_EDITION_NAME. From a modeling perspective, the heuristic Data Vault classification for this object is satellite — it holds descriptive, historically maintained attributes attached to the condition header business key. This is a suggestion only; the table is a standard EBS MLS translation table rather than a formal Data Vault construct.

Key Information Stored

All columns in this table are translatable columns copied from OKC_CONDITION_HEADERS_B per Oracle MLS standards. The most significant columns are:

• ID — System-generated unique identifier of the condition header, inherited from the base table. Part of the composite primary key OKC_CONDITION_HEADERS_TL_PK.
• LANGUAGE — Standard MLS column carrying the language code of the translated row. Part of the composite primary key and of the unique index.
• SOURCE_LANG — Standard MLS column identifying the language in which the row was originally entered, used to drive translation workflows.
• NAME — The translated condition name, up to 150 characters; the principal business-facing label for a condition header.
• DESCRIPTION — The translated long condition description, up to 1995 characters.
• SHORT_DESCRIPTION — A translated abbreviated description, up to 600 characters, typically used in list-of-values and summary regions.
• COMMENTS — Free-form translated user comments associated with the condition.
• SFWT_FLAG — Indicates that a value was changed in another language; documented as not used in 11i. It supports the "someone else wrote this" translation-indicator behavior.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording row creation and last modification.
• SECURITY_GROUP_ID — Used in hosted environments to partition data by security group; it references FND_SECURITY_GROUPS.

The surrogate primary key is the composite (ID, LANGUAGE). The business-key candidate is the unique index OKC_CONDITION_HEADERS_TL_U1 on (ID, LANGUAGE), extended in 12.2.2 to (ID, LANGUAGE, ZD_EDITION_NAME) to accommodate edition-based records.

Common Use Cases and Queries

This table is queried whenever condition header text must be displayed in a user's session language. Typical scenarios include contract terms reports, condition setup and maintenance forms, seeded translation verification, and data migration validation.

• Retrieving a translated condition header for a specific identifier and language:

  SELECT id, name, description, short_description
  FROM   okc.okc_condition_headers_tl
  WHERE  id = :p_id
  AND    language = USERENV('LANG');

• Joining the translation and base tables to obtain both language-independent and translated attributes:

  SELECT b.id, t.language, t.name, t.description
  FROM   okc.okc_condition_headers_b b,
         okc.okc_condition_headers_tl t
  WHERE  b.id = t.id
  AND    t.language = USERENV('LANG');

• Reporting on conditions lacking a translation in a given language, using SOURCE_LANG and LANGUAGE to identify gaps for translation maintenance.
• Detecting rows flagged by SFWT_FLAG where a value was changed in another language and may require review.
• Listing available translations for a condition by selecting DISTINCT LANGUAGE for a given ID.

Because the table is large and frequently joined, queries should filter on ID and LANGUAGE to leverage the unique index rather than scanning on NAME or DESCRIPTION.

Related Objects

• OKC.OKC_CONDITION_HEADERS_B — The base language-independent table; the authoritative source of condition header attributes and parent of this translation table via (ID, LANGUAGE).
• OKC_CONDITION_HEADERS_TL_U1 — The unique index on (ID, LANGUAGE), extended with ZD_EDITION_NAME in 12.2.2, enforcing translation uniqueness.
• OKC_CONDITION_HEADERS_TL_PK — The composite primary key (ID, LANGUAGE).
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID; used to partition hosted-environment data.
• APPS.OKC_CONDITION_HEADERS_TL — The APPS synonym through which application code and reports access the table.

The table does not reference any other database object beyond SECURITY_GROUP_ID and is referenced by the APPS synonym. Translation maintenance is normally performed through the standard Oracle translation forms rather than direct DML.