Search Results okc_section_contents




Overview
Explore in AI Chat

Overview

The OKC_SECTION_CONTENTS table is a core data object within the Oracle E-Business Suite Contracts Core (OKC) module, specifically in releases 12.1.1 and 12.2.2. It functions as a junction table that defines the structural composition of contract sections. Its primary role is to manage the association between a parent contract section and the various components that constitute its content. These components can be standard or contract-specific articles, labels, or even other contract lines. By maintaining these relationships, the table enables the modular assembly and hierarchical organization of complex contract documents, which is fundamental to the flexible contract authoring and management capabilities of Oracle Contracts.

Key Information Stored

The table stores metadata that links a section to its constituent parts. The most critical columns are foreign keys that establish these relationships. The SCN_ID column references the parent section from the OKC_SECTIONS_B table. The content type is determined by which other foreign key column is populated. The SAE_ID links to a standard article from OKC_STD_ARTICLES_B, while the CAT_ID links to a contract-specific article from OKC_K_ARTICLES_B. The CLE_ID column can link to a contract line from OKC_K_LINES_B. The table's primary key is the ID column, which uniquely identifies each section-content association record. Additional columns typically manage sequencing, version control, and audit information, though these are not detailed in the provided metadata.

Common Use Cases and Queries

A primary use case is generating a complete contract document by traversing the hierarchy from a contract header down through its sections and their contents. Support teams often query this table to diagnose missing articles or incorrect section assembly. For reporting, it is essential for listing all components within a specific section. A common SQL pattern retrieves all standard article content for a given section:

  • SELECT sc.id, sa.article_title, sa.article_text
  • FROM okc_section_contents sc, okc_std_articles_b sa
  • WHERE sc.sae_id = sa.id
  • AND sc.scn_id = <section_id>;

Another critical scenario involves impact analysis when a standard article is updated, requiring queries to identify all sections across contracts that incorporate that specific article via its SAE_ID.

Related Objects

The OKC_SECTION_CONTENTS table is central to the contract structure, with documented foreign key relationships to several key tables:

  • OKC_SECTIONS_B: The parent table. The SCN_ID column in OKC_SECTION_CONTENTS joins to this table to identify the containing section.
  • OKC_STD_ARTICLES_B: References standard, reusable contract clauses. The SAE_ID column joins to this table.
  • OKC_K_ARTICLES_B: References contract-specific (k) articles. The CAT_ID column joins to this table.
  • OKC_K_LINES_B: References contract lines. The CLE_ID column joins to this table, allowing lines to be included as section content.

These relationships illustrate that OKC_SECTION_CONTENTS acts as a flexible mapping table, allowing sections to be populated with diverse types of content from multiple source tables within the Contracts Core schema.