Search Results okc_rule_groups_tl




Overview
Explore in AI Chat

Overview

OKC_RULE_GROUPS_TL is the translation table for the OKC_RULE_GROUPS_B base table within the OKC (Contracts Core) module of Oracle E-Business Suite. As defined by Oracle Multi-Lingual Support (MLS) standards, it stores the language-dependent, translatable columns of a rule group. Every translatable attribute recorded in the base table is mirrored here per installed language, allowing rule group definitions — such as rule group names and descriptive comments — to be presented in the user's session language. The table is owned by the OKC schema and is marked VALID in the documented ETRM 12.2.2 metadata. Its structure is consistent between Oracle EBS 12.1.1 and 12.2.2, since it conforms to the standard MLS translation pattern (_TL suffix).

Within a heuristic Data Vault classification, OKC_RULE_GROUPS_TL behaves as a satellite. It carries descriptive, language-specific attributes that hang off the natural business key (the rule group identifier) and change independently of the core entity. Modeling this as a satellite keeps the descriptive translation context separated from the stable hub of rule group identity, which is the recommended pattern when applying Data Vault techniques to EBS reference data.

Key Information Stored

The table contains eleven documented columns. The most important are:

  • ID — Surrogate identifier of the parent rule group. Combined with LANGUAGE, it forms the primary key OKC_RULE_GROUPS_TL_PK.
  • LANGUAGE — The language code for the translation row, part of the composite primary key.
  • SOURCE_LANG — The language in which the source text was originally entered, used by MLS to determine whether translation is required.
  • SFWT_FLAG — The "Seed/Force/Where/Translate" flag controlling whether the row is a seeded record and whether it is maintained by translation tooling.
  • COMMENTS — The translatable descriptive text associated with the rule group, the principal human-readable attribute in this table.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant/operating-unit data security.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns tracking row audit history.

The surrogate primary key is (ID, LANGUAGE). The unique index OKC_RULE_GROUPS_TL_U1 (ID, LANGUAGE) confirms that (ID, LANGUAGE) is the business-key candidate, ensuring one translation row per rule group per language. There is no separate surrogate business key beyond the composite of ID and LANGUAGE.

Common Use Cases and Queries

The dominant use case is presenting rule group labels in the user's session language by joining this translation table to its base table. A typical query filters on the session language and falls back to the source language where translation is absent:

  • Reporting: join OKC_RULE_GROUPS_TL to OKC_RULE_GROUPS_B on ID to retrieve translated COMMENTS for a given LANGUAGE.
  • Translation gap analysis: identify rule groups where SOURCE_LANG differs from available LANGUAGE rows.
  • Security-scoped extracts: filter by SECURITY_GROUP_ID to respect operating-unit security.

A representative pattern is: SELECT b.id, t.language, t.comments FROM okc_rule_groups_b b, okc_rule_groups_tl t WHERE b.id = t.id AND t.language = USERENV('LANG'). Administrators also use this table to audit which languages have been seeded for each rule group.

Related Objects

  • OKC_RULE_GROUPS_B — The base table holding language-independent columns; joined on ID.
  • OKC_RULE_GROUPS_TL_PK — Primary key constraint over (ID, LANGUAGE).
  • OKC_RULE_GROUPS_TL_U1 — Unique index enforcing the business-key candidate.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for row-level security.
  • OKC_RULES_B / OKC_RULES_TL — Rule definitions that typically group beneath a rule group.
  • FND_LANGUAGES — Source of valid LANGUAGE values and MLS fallback logic.