Results for “okl_context_groups_b”

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

Overview

OKL_CONTEXT_GROUPS_B is a base table in the OKL (Oracle Lease and Finance Management) schema. Its documented purpose is to store the grouping of lists of parameters that are required by formulae. In the OKL pricing and rules engine, a formula cannot be evaluated without a defined set of context values; OKL_CONTEXT_GROUPS_B provides the named container that assembles those parameter sets into a reusable unit, which is then referenced by formula definitions rather than being repeated for each individual formula.

The table is the definition (or "base") table of a translated or edition-enabled entity, indicated by the _B suffix and the presence of the ZD_EDITION_NAME column, which is used by the editioning infrastructure introduced with the multi-tenant and online patching architecture. From a Data Vault modeling perspective, the FK structure suggests this object behaves as a hub: its primary key is an immutable surrogate identifier, and other business entities (notably OKL_FORMULAE_B) reference it through a foreign key rather than the reverse. Its descriptive attributes would typically be modeled as a satellite in a Data Vault design.

Key Information Stored

Nine columns are documented for this table. The most significant are:

• ID — the surrogate primary key, constrained by OKL_CONTEXT_GROUPS_B_PK. It is the value propagated to child tables as a foreign key.
• NAME — the user-meaningful identifier of the context group. Together with ZD_EDITION_NAME it forms the unique business-key index OKL_CGR_U2, meaning a group name must be unique within an edition.
• ZD_EDITION_NAME — the edition discriminator. It participates in both unique indexes (OKL_CGR_U2 on NAME + ZD_EDITION_NAME, and OKL_CONTEXT_GROUPS_B_U1 on ID + ZD_EDITION_NAME), which preserves uniqueness across editions during online patching.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Framework (OAF) to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS "WHO" audit columns recording creation and last modification context.

The surrogate key (ID) should be distinguished from the business-key candidates exposed through the unique indexes: NAME is the human-facing unique key, while ID is the technical join key used throughout the OKL formula schema.

Common Use Cases and Queries

Typical scenarios include identifying which context groups exist, resolving a formula's parameter group, and auditing edition-specific definitions. A representative query to list active context groups is:

• SELECT ID, NAME, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM OKL.OKL_CONTEXT_GROUPS_B ORDER BY NAME;
• Joining to formulae to see which context group each formula uses: SELECT f.ID, f.NAME, c.NAME AS context_group FROM OKL.OKL_FORMULAE_B f JOIN OKL.OKL_CONTEXT_GROUPS_B c ON f.CGR_ID = c.ID;
• Business-key lookup by name within an edition: SELECT ID FROM OKL.OKL_CONTEXT_GROUPS_B WHERE NAME = :name AND ZD_EDITION_NAME = :edition;

Reporting use cases center on formula configuration documentation, functional setup migration between environments (where ID values must be reconciled), and impact analysis before deleting or renaming a context group that is still referenced by a formula.

Related Objects

The documented foreign-key relationship shows OKL_FORMULAE_B referencing this table, and it is the dominant integration point:

• OKL_FORMULAE_B — references OKL_CONTEXT_GROUPS_B via OKL_FORMULAE_B.CGR_ID to OKL_CONTEXT_GROUPS_B.ID. Each formula points to the context group that supplies its parameters.
• OKL_FORMULAE_TL — the translated (language) table for formula names and descriptions, typically used alongside OKL_FORMULAE_B when reporting formula-to-context-group mappings.
• OKL_CONTEXT_GROUPS_TL — the corresponding translated table for context group names, joined on the same ID for multilingual reporting.
• The parameter lines that populate a group's parameter list reside in the associated context-group detail tables, joined on ID, and provide the individual parameter members of each group.