Search Results okc_rule_groups_tl_u1

Overview

OKC.OKC_RULE_GROUPS_TL is the translation (MLS) table for Oracle Contracts rule groups in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the language-dependent descriptive attributes of rule groups defined in the base table OKC_RULE_GROUPS_B, allowing rule group names, comments, and other translatable text to be presented in the session language of the user. Rule groups are used throughout Oracle Contracts to organize and apply reusable sets of contract terms, clauses, and validation rules to contract templates and contract documents. The table resides in the OKC schema, uses the APPS_TS_TX_DATA tablespace, and is maintained by the Contracts (OKC) application module.

From a heuristic Data Vault modeling perspective, this object is best classified as a satellite, keyed to the rule group hub (ID) and qualified by LANGUAGE. It does not introduce new business entities; it describes existing ones and carries standard audit (Who) columns and multilingual support columns rather than independent transactional facts.

Key Information Stored

The table carries eleven documented columns. The most significant are:

• ID — Numeric surrogate primary key inherited from OKC_RULE_GROUPS_B; identifies the rule group.
• LANGUAGE — Standard MLS column holding the language code of the translated row.
• SOURCE_LANG — Standard MLS column indicating the language from which the row was translated.
• COMMENTS — User-entered descriptive comment for the rule group (VARCHAR2 1995).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who audit columns tracking row creation and modification.
• SECURITY_GROUP_ID — Used in hosted (multi-tenant) environments to isolate data by security group; foreign keyed to FND_SECURITY_GROUPS.
• SFWT_FLAG — Documented as not used.

Two index structures are relevant. The primary key OKC_RULE_GROUPS_TL_PK is composed of (ID, LANGUAGE). The unique index OKC_RULE_GROUPS_TL_U1 is also composed of (ID, LANGUAGE) and lives in APPS_TS_TX_IDX. Because both indexes cover the same columns, the business-key candidate for this table is effectively (ID, LANGUAGE): a rule group may have at most one translated record per language.

Common Use Cases and Queries

Typical usage involves joining the translation table to the base table to retrieve language-appropriate descriptive data for reporting and validation. For example, to retrieve rule group comments in a specific language:

• Query by primary key: SELECT ID, LANGUAGE, COMMENTS FROM OKC.OKC_RULE_GROUPS_TL WHERE ID = :p_id AND LANGUAGE = USERENV('LANG');
• Join to base table for full attribute sets: join on OKC_RULE_GROUPS_TL.ID = OKC_RULE_GROUPS_B.ID.
• Multilingual reporting across all rule groups and their translated comments.
• Data integrity checks confirming a translation exists for each supported language.
• Security-group filtered extracts in hosted deployments using SECURITY_GROUP_ID.

Related Objects

Dependency metadata identifies the following relationships:

• OKC.OKC_RULE_GROUPS_B — Base table supplying the untranslated rule group record; OKC_RULE_GROUPS_TL is its MLS counterpart (join column: ID).
• OKC_RULE_GROUPS_TL_PK — Primary key constraint on (ID, LANGUAGE).
• OKC_RULE_GROUPS_TL_U1 — Unique index on (ID, LANGUAGE), the business-key candidate.
• FND_SECURITY_GROUPS — Referenced by the SECURITY_GROUP_ID foreign key for hosted environment isolation.
• APPS.OKC_RULE_GROUPS_TL — Application synonym exposing the table to the Oracle Contracts schema layer.

The object does not reference any other database objects directly, confirming its role as a dependent satellite of the rule group hub rather than an origin of additional relationships.