Search Results okc_section_contents_v




Overview
Explore in AI Chat

Overview

OKC_SECTION_CONTENTS_V is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the OKC – Contracts Core product family and exposes the section-level content structure of contracts documents managed within Oracle Contracts. The view consolidates data from the contract articles repository and the contract article definition table to present a flat, query-friendly representation of every content line associated with a contract section (SCN_ID).

Its primary role is to support reporting and integration requirements where consumers need to enumerate the ordered contents of a section without navigating the master-detail relationships in the underlying transaction tables. Because the view resolves the source article for each content entry through a DECODE expression, it presents a normalized SAE_ID value regardless of whether the content originates from a standard article or a referenced article. This makes the view suitable for contract template inspection, document assembly auditing, and interfaces that publish contract text metadata to external systems.

The view is declared VALID in the data dictionary and is documented in ETRM 12.2.2 with APPS as the owner and OKC_ARTICLES_ALL and OKC_K_ARTICLES_B as the referenced base objects (exposed as synonyms).

Underlying Base Objects

The view text defines a join between two documented base objects:

  • OKC_K_ARTICLES_B (alias SCC) — the contract article instance table. It supplies the section identifier (SCN_ID), content identifier (ID), label, clearance identifier (CLE_ID), source article references (SAV_SAE_ID and REF_ARTICLE_ID), display sequencing, and standard WHO/version columns.
  • OKC_ARTICLES_ALL (alias ART) — the article definition/master table. It supplies the STANDARD_YN flag, which the view uses to determine whether the content entry points to a standard article (SAV_SAE_ID) or to a referenced article (REF_ARTICLE_ID).

The join predicate is SCC.SAV_SAE_ID = ART.ARTICLE_ID. Because the definition uses OKC_K_ARTICLES_B, only the base-table rows flow through; translations are not included, so the view returns the base-language content set. The DECODE on ART.STANDARD_YN performs the source-article resolution that most consumers rely on.

Key Columns

  • ROW_ID — the ROWID of the OKC_K_ARTICLES_B row, useful for identification but not update.
  • ID — the primary key of the contract article instance; also aliased as CAT_ID in the projection.
  • SCN_ID — the section identifier that groups content entries into a logical document section.
  • LABEL — the display label assigned to the content line.
  • CLE_ID — the clearance/entitlement identifier associated with the content.
  • SAE_ID — the resolved source article identifier, derived via DECODE(ART.STANDARD_YN, 'Y', SCC.SAV_SAE_ID, SCC.REF_ARTICLE_ID). This is the key attribute for tracing a content entry back to its originating article.
  • CONTENT_SEQUENCE — derived from SCC.DISPLAY_SEQUENCE; governs the ordering of content within the section.
  • OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard concurrency and audit columns inherited from the base table.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — exposed as empty string literals ('') in the view text; these are placeholder descriptive flexfield columns that carry no data in this view definition.

Common Use Cases and Queries

Typical scenarios include listing the ordered content of a given contract section, reconciling standard versus referenced articles used in a template, and extracting content metadata for downstream document generation or archiving.

Retrieving all contents for a specific section, ordered by display sequence:

  • SELECT id, scn_id, label, sae_id, content_sequence
  • FROM okc_section_contents_v
  • WHERE scn_id = :p_section_id
  • ORDER BY content_sequence;

Counting content entries per section to profile template size:

  • SELECT scn_id, COUNT(*) content_count
  • FROM okc_section_contents_v
  • GROUP BY scn_id
  • ORDER BY content_count DESC;

Because ATTRIBUTE columns are hard-coded as empty strings, queries should not rely on them for filtering or reporting. Consumers requiring translation-aware output should join to the appropriate translation tables rather than using this base view alone.