Search Results okc_rules_tl




Overview
Explore in AI Chat

Overview

OKC_RULES_TL is the translation (multi-language support, MLS) table for the Contracts Core module (OKC) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the translatable columns extracted from OKC_RULES_B, following Oracle's standard MLS architecture in which language-independent attributes reside in a base table (_B) and their language-specific counterparts reside in a translation table (_TL). Each rule defined in the Contracts module is therefore represented once in OKC_RULES_B and once per installed language in OKC_RULES_TL.

From a Data Vault modeling perspective, the mined relationship metadata classifies this object heuristically as a standalone entity. In practice, however, its tight coupling to OKC_RULES_B and its primary key of (ID, LANGUAGE) suggest a natural fit as a satellite table attached to a rule hub keyed on ID, with LANGUAGE acting as the driving key. This classification should be treated as a modeling suggestion rather than a documented constraint.

The table is owned by the OKC schema, is marked VALID, and exposes twelve documented columns. Its translations are consumed primarily through the Oracle Forms and OAF-based Contracts authoring screens, and through concurrent programs and reports that render rule descriptions in the session language.

Key Information Stored

The table's primary key, OKC_RULES_TL_PK, is the composite (ID, LANGUAGE). Both columns are required:

  • ID — Surrogate foreign key to the parent rule row in OKC_RULES_B; it carries no business meaning on its own but anchors the translation to its base record.
  • LANGUAGE — The installed language code (for example, US, DE, FR) in which the translated text is stored. Together with ID it forms the primary key and the unique index OKC_RULES_TL_U1.
  • SOURCE_LANG — The language in which the source text was originally authored; used by the MLS translation framework to detect the origin of a translated string.
  • SFWT_FLAG — The "Seed/Force/Whatever" style flag used by Oracle's translation tooling to protect seeded data from automatic overwrite during patching.
  • TEXT — The translatable text payload; typically the rule's user-facing label or short description as displayed in the Contracts UI.
  • COMMENTS — A free-text, translatable comment field associated with the rule.
  • SECURITY_GROUP_ID — Multi-tenant security discriminator. It is the only foreign key documented on this table, referencing OKC_RULES_TL.SECURITY_GROUP_ID → FND_SECURITY_GROUPS.
  • CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — The standard "WHO" audit columns populated automatically by the Oracle Forms/OAF framework.

Notably, the table contains no business-key columns of its own; all naming semantics live with the parent OKC_RULES_B record.

Common Use Cases and Queries

Typical usage patterns include:

  • Localized rule reporting — Retrieving rule labels in a specific language for a report or a custom OAF page.
  • Translation completeness checks — Identifying base rules that lack a row in OKC_RULES_TL for a given LANGUAGE.
  • Reverse mapping — Pulling all translations for a single rule to support multi-language UI or export.
  • Seed data verification — Confirming SFWT_FLAG values when diagnosing patch-related text overwrites.

A representative query joins the translation table to its base table and filters by language:

SELECT t.id, t.language, t.text
  FROM okc_rules_b b, okc_rules_tl t
 WHERE b.id = t.id
   AND t.language = USERENV('LANG')
   AND t.security_group_id = :p_security_group_id;

To find missing translations for a non-base language, use an outer join against the base table with the target language as a filter. All queries should be restricted by SECURITY_GROUP_ID in multi-org or multi-tenant deployments.

Related Objects

  • OKC_RULES_B — The parent base table. Join on ID = ID; it holds the language-independent rule attributes.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID; controls which rows are visible to which operating unit or business group.
  • FND_LANGUAGES — Not a declared FK, but LANGUAGE codes typically reconcile to this standard lookup table.
  • OKC_RULES_TL_PK — The primary key constraint enforced at the database level over (ID, LANGUAGE).
  • OKC_RULES_TL_U1 — The unique index on (ID, LANGUAGE) that doubles as the business-key candidate for the translation row.
  • FND_APPLICATION / FND_PRODUCT_INSTALLATIONS — Used indirectly to determine installed languages that drive which rows should exist in the _TL table.
  • OKC_CONTINGENCIES_B and other OKC rule-adjacent base tables — Reference rule definitions that are surfaced to users through OKC_RULES_TL translations.

Because the table is a translation satellite of OKC_RULES_B, most reporting requirements can be satisfied by joining the two tables on ID and filtering on the session LANGUAGE. Direct DML against OKC_RULES_TL is discouraged outside of the Oracle translation framework.