Results for “okc_k_groups_b”

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

Overview

OKC_K_GROUPS_B is a core Contracts Core (OKC) table within Oracle E-Business Suite Release 12.1.1 and 12.2.2 that stores user-defined "buckets" or groupings for contracts. It provides the classification mechanism through which contracts are organized into logical categories defined by the implementing enterprise, rather than by seeded Oracle lookup values. Because contracts frequently require grouping by business line, region, customer segment, or legal entity, this table serves as the master definition for those buckets, and other contracts objects reference it when a contract must be assigned to a specific group.

From a data modeling perspective, the ETRM metadata classifies OKC_K_GROUPS_B as hub-leaning. This is a heuristic suggestion: the table carries a single-column surrogate primary key (ID) and is referenced by multiple foreign keys from dependent tables, which is characteristic of a hub in a Data Vault style model. It should not be treated as a transactional satellite, since its rows describe persistent grouping definitions rather than the changing state of a business transaction.

Key Information Stored

The table contains 27 documented columns. The most significant are listed below.

• ID — Surrogate primary key, enforced by OKC_K_GROUPS_B_PK. This is the value referenced by all downstream foreign keys.
• PUBLIC_YN — Flag indicating whether the group definition is available for general use across the enterprise or restricted in scope.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle ADF/BC4J framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns capturing audit and user-session information.
• USER_ID — Identifies the user associated with the group record, typically the owning or creating user.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, used to partition the row for multi-org / security-group access control.
• ZD_EDITION_NAME — Editioning column supporting Oracle EBS 12.2 online patching; the unique index OKC_K_GROUPS_B_U1 is defined on (ID, ZD_EDITION_NAME).
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle flexfield (DDF) descriptive columns reserved for customer-specific extensions without schema modification.

The primary key is a surrogate identifier. The document metadata does not expose a natural business key column; the unique index OKC_K_GROUPS_B_U1 on (ID, ZD_EDITION_NAME) is an editioning constraint rather than a user-facing business key. Consumers should therefore resolve group names through related views or lookup tables rather than by name matching.

Common Use Cases and Queries

Typical scenarios include populating a contracts group list of values, validating group assignments during contract creation, and reporting contract counts by group.

• Retrieve all active group definitions for an LOV: select ID, PUBLIC_YN from OKC_K_GROUPS_B where PUBLIC_YN = 'Y'.
• Join contracts to their groups through the OKC_K_GRPINGS link table, resolving both parent and included group IDs back to this table.
• Identify default groups used by contract creation and renewal by joining OKS_K_DEFAULTS on CGP_NEW_ID and CGP_RENEW_ID.
• Audit changes over time using LAST_UPDATED_BY and LAST_UPDATE_DATE, which is particularly useful when reconciling group assignments after a patch cycle.
• Partition reporting output by SECURITY_GROUP_ID in multi-org or security-group enforced environments.

Related Objects

The following objects are the most significant dependents and references based on the documented foreign key relationships.

• OKC_K_GRPINGS — References OKC_K_GROUPS_B twice, via CGP_PARENT_ID and INCLUDED_CGP_ID, enabling hierarchical or nested group membership.
• OKS_K_DEFAULTS — References OKC_K_GROUPS_B via CGP_NEW_ID and CGP_RENEW_ID, defining default group assignments for new and renewed contracts.
• FND_SECURITY_GROUPS — The foreign table for SECURITY_GROUP_ID, providing security partitioning for group definitions.
• OKC_K_GROUPS_B_PK — The primary key constraint, and OKC_K_GROUPS_B_U1 — the unique editioning index on (ID, ZD_EDITION_NAME).

Together these relationships establish OKC_K_GROUPS_B as the grouping hub around which contract organization, defaulting, and security are structured.