Results for “okc_outcomes_tlh”

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

Overview

OKC_OUTCOMES_TLH is the history (audit trail) table for OKC_OUTCOMES_TL, the translation base table that stores outcome definitions used by Oracle Contracts Core (OKC) in Oracle E-Business Suite 12.1.1 and 12.2.2. In the OKC schema, outcomes represent the result codes and associated descriptions that are attached to contract terms, deliverables, and related contracting events. The "_TLH" suffix designates a translation history table: whereas OKC_OUTCOMES_TL holds the currently effective translatable rows, OKC_OUTCOMES_TLH preserves prior versions of those rows, keyed by language and major version, so that historical translations remain available for audit and reporting.

The object is documented as VALID in the ETRM 12.2.2 physical schema with Owner OKC and a total of 12 columns. Heuristic Data Vault classification, mined from the foreign-key structure, is standalone. From a modeling perspective this classification suggests the table behaves as neither a pure hub nor a pure link, but rather as a versioned satellite-like companion to the base translation table; it should not be treated as an independent hub because it carries no inbound referenced relationships of its own.

Key Information Stored

The documented primary key is OKC_OUTCOMES_TLH_PK, composed of ID, LANGUAGE, and MAJOR_VERSION. A unique index, OKC_OUTCOMES_TLH_U1, is defined on the same three columns (ID, LANGUAGE, MAJOR_VERSION) and therefore represents the business-key candidate for the history rows.

• ID — Surrogate identifier inherited from the base outcome record; the primary key component linking the history row back to its parent outcome.
• LANGUAGE — Language code of the translated content; the second component of the composite primary key.
• MAJOR_VERSION — Version indicator that distinguishes successive stored versions of the same outcome/language combination; the third primary key component and the column that gives the table its history semantics.
• SOURCE_LANG — Source language from which the translation was derived.
• SFWT_FLAG — Standard Oracle "seed data / white space translation" indicator used to control translation processing behavior.
• COMMENTS — Descriptive text associated with the outcome at that version.
• CREATED_BY, CREATION_DATE — Standard WHO audit columns recording the user and timestamp of row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns capturing the most recent modification and the login context in which it occurred.
• SECURITY_GROUP_ID — The multi-org security grouping column, which is also the target of the documented foreign key from OKC_OUTCOMES_TLH.SECURITY_GROUP_ID to FND_SECURITY_GROUPS.

Common Use Cases and Queries

The primary use case is historical translation reporting: identifying how an outcome's translated text changed across versions, and reconstructing what a user saw at a given point in time.

• Version history for a specific outcome in one language:

  SELECT id, language, major_version, comments,
         last_updated_by, last_update_date
  FROM   okc.okc_outcomes_tlh
  WHERE  id = :outcome_id
  AND    language = :lang
  ORDER BY major_version;

• Comparison of the current translation against the history table, joined on the composite key (ID, LANGUAGE), to surface rows whose content differs from the latest archived version.
• Audit extraction by modification window, filtering on LAST_UPDATE_DATE to support internal control reviews.
• Security-filtered reporting, joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS to restrict output to the operating unit/security context of the running user.

Related Objects

• OKC_OUTCOMES_TL — the base translation table for which OKC_OUTCOMES_TLH is the history; joined on ID and LANGUAGE.
• OKC_OUTCOMES_B — the non-translatable base table holding outcome attributes; joins on ID.
• FND_SECURITY_GROUPS — referenced through the documented foreign key OKC_OUTCOMES_TLH.SECURITY_GROUP_ID.
• OKC_OUTCOMES_TLH_PK — the composite primary key constraint (ID, LANGUAGE, MAJOR_VERSION).
• OKC_OUTCOMES_TLH_U1 — the unique index supplying the business-key candidate.
• FND_LANGUAGES — supplies the language definition resolved against the LANGUAGE column.
• Contract Terms and Deliverables setup — outcome values surfaced through OKC contract term configuration reference OKC_OUTCOMES-backed data.