Search Results okc_k_grpings_v




Overview
Explore in AI Chat

Overview

OKC_K_GRPINGS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, released under the OKC — Contracts Core product family. It is documented as a view over the OKC_CONTRACT_GROUPINGS entity and, in the 12.2.2 ETRM metadata, is registered as being defined over the OKC_K_GRPINGS synonym. The view exposes contract grouping records for reporting, integration, and inquiry purposes without requiring callers to reference the physical table or its synonym directly.

Contract groupings in OKC represent the hierarchical structures through which related contract documents are organized — for example, a master agreement and its associated subordinate contracts, or sets of contracts consolidated for a common administrative or billing purpose. The view surfaces the grouping parent, the included contract identifier, the included grouping identifier, and the system status code, making the parent-child relationships within a grouping accessible to downstream consumers such as concurrent programs, BI Publisher reports, OAF pages, and external integration endpoints.

The object is reported with status VALID, indicating that it is a supported, compiled object in the APPS schema in the environments examined.

Underlying Base Objects

The documented base object referenced by the view is OKC_K_GRPINGS (SYNONYM). In Oracle EBS naming conventions, the OKC_K_GRPINGS synonym typically resolves to the physical table OKC_CONTRACT_GROUPINGS, consistent with the description stating that the view is a "View for table OKC_CONTRACT_GROUPINGS."

The view text selects from this object using the alias CGCB and projects a stable, denormalized column list. Key structural relationships available through the view are:

  • Self-referencing hierarchy — CGP_PARENT_ID links a grouping row to its parent grouping, allowing recursive traversal of nested groupings.
  • Contract membership — INCLUDED_CHR_ID identifies the contract (CHR) included within a grouping.
  • Grouping membership — INCLUDED_CGP_ID identifies a child grouping included within a parent grouping.
  • Status context — SCS_CODE carries the system status code applied to the grouping record.

Because the view is defined over a synonym rather than naming the base table directly, it retains the standard EBS indirection that supports patching and editioning without invalidating dependent objects.

Key Columns

  • ROW_ID — The ROWID of the underlying row in the base table. Useful for direct row identification and for tools that operate on physical row addresses.
  • ID — The primary identifier of the grouping record.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Framework and by programmatic updates to detect concurrent modification.
  • CGP_PARENT_ID — The identifier of the parent grouping; defines the hierarchical position of the record.
  • INCLUDED_CHR_ID — The contract identifier included in the grouping.
  • INCLUDED_CGP_ID — The child grouping identifier included in the parent grouping.
  • SCS_CODE — The system status code for the grouping record.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified the row, when, and through which login session.

Common Use Cases and Queries

Typical usages include reporting contract grouping hierarchies, identifying all contracts belonging to a grouping, and joining grouping data to the contract headers and lines tables for contract summary reports. Sample queries against the view include:

  • Listing all groupings for a specific parent grouping:

    SELECT id, cgp_parent_id, included_chr_id, included_cgp_id, scs_code
    FROM okc_k_grpings_v
    WHERE cgp_parent_id = :p_parent_id;

  • Finding the groupings that include a given contract:

    SELECT id, cgp_parent_id, included_cgp_id, scs_code
    FROM okc_k_grpings_v
    WHERE included_chr_id = :p_chr_id;

  • Auditing recently modified grouping records:

    SELECT id, cgp_parent_id, included_chr_id, last_updated_by, last_update_date
    FROM okc_k_grpings_v
    WHERE last_update_date >= :p_since_date
    ORDER BY last_update_date DESC;

  • Traversing the grouping hierarchy using a CONNECT BY clause on CGP_PARENT_ID to explode a grouping structure to its leaf contracts.

Because the column list is fixed and the view performs no joins, queries against OKC_K_GRPINGS_V are inexpensive and can be safely embedded in high-volume reporting and integration logic.