Results for “okc_k_grpings”

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

Overview

OKC_K_GRPINGS is a transactional table in the OKC (Contracts Core) schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the membership of a contract group, recording which contracts and which subordinate contract groups belong to a given parent group. In practical terms, it is the associative structure that lets a contract group behave as a container whose members may be individual contract headers or other contract groups, thereby supporting nested hierarchical groupings of contracts.

Under the heuristic Data Vault classification mined from its foreign key structure, OKC_K_GRPINGS is best modelled as a link table. It resolves many-to-many associations between a parent group and its included members, rather than acting as a hub of unique business entities or a satellite carrying descriptive attributes. The two foreign keys to OKC_K_GROUPS_B and the single foreign key to OKC_K_HEADERS_ALL_B confirm its role as a connective artifact.

Key Information Stored

The table exposes twelve documented columns. The most operationally significant are:

• ID — the surrogate primary key, uniquely identified by the unique index OKC_K_GRPINGS_U1. This is the technical identifier of each membership row.
• CGP_PARENT_ID — the parent contract group to which membership is assigned; it carries a foreign key to OKC_K_GROUPS_B. This is also a component of the composite business-key candidate.
• INCLUDED_CGP_ID — the contract group included as a child member, referencing OKC_K_GROUPS_B. This permits group-within-group nesting.
• INCLUDED_CHR_ID — the contract header included as a member, referencing OKC_K_HEADERS_ALL_B.
• SCS_CODE — a source or subsystem code column retained for lineage and integration purposes.
• SECURITY_GROUP_ID — the multi-org/security grouping identifier, with a documented foreign key to FND_SECURITY_GROUPS, which constrains row visibility in a secured environment.
• OBJECT_VERSION_NUMBER — used for optimistic locking during concurrent updates.
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — record who created and last modified each membership row and when.

Two key definitions coexist: the surrogate key on ID (OKC_K_GRPINGS_U1) and the business-key candidate CGC_CGC1_UK, a composite unique constraint over CGP_PARENT_ID, INCLUDED_CHR_ID, and INCLUDED_CGP_ID. The composite constraint enforces that a given parent group cannot include the same contract header or the same child group more than once.

Common Use Cases and Queries

Typical reporting scenarios include resolving the full membership of a contract group, detecting nested group hierarchies, and auditing which contracts roll up to a given group for entitlement or pricing purposes. A common pattern joins the membership rows to the group and header base tables:

SELECT g.cgp_parent_id, h.contract_number
FROM   okc.okc_k_grpings m,
       okc.okc_k_headers_all_b h
WHERE  m.included_chr_id = h.id
AND    m.cgp_parent_id = :parent_group_id;

To walk nested groups, the table is self-joined by treating INCLUDED_CGP_ID as a new parent:

SELECT m1.cgp_parent_id, m2.included_chr_id
FROM   okc.okc_k_grpings m1,
       okc.okc_k_grpings m2
WHERE  m1.included_cgp_id = m2.cgp_parent_id;

Security-aware queries should filter on SECURITY_GROUP_ID to respect FND security policies, and duplicate-detection queries can be written against the CGC_CGC1_UK columns to validate group integrity before data loads.

Related Objects

• OKC_K_GROUPS_B — the base table for contract groups; referenced twice via CGP_PARENT_ID and INCLUDED_CGP_ID.
• OKC_K_HEADERS_ALL_B — the contract header base table, referenced via INCLUDED_CHR_ID.
• OKC_K_HEADERS_ALL_TL — the translation table supplying contract header descriptive text in joins.
• OKC_K_GROUPS_TL — group name translations joined through OKC_K_GROUPS_B.
• OKC_K_GROUP_ENTS — the entity-level grouping structure that complements group membership.
• FND_SECURITY_GROUPS — the security group reference behind SECURITY_GROUP_ID.
• OKC_K_GRPINGS itself, used reflexively for hierarchy traversal.
• OKC Contracts Core public APIs that manage group membership operate against this table alongside OKC_K_GROUPS_B.