Search Results content_sequence




Overview
Explore in AI Chat

Overview

OKC_SECTIONED_ARTICLES_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKC – Contracts Core product family. It exposes the sectioned article text of Oracle Contracts documents by resolving the individual article records stored in the CLOB-backed OKC repository into a flattened, queryable form. Unlike the underlying OKC_K_ARTICLES_B table, which stores article content as large objects, this view presents the article text as a standard character column (TEXT) so that it can be consumed by SQL*Plus, Oracle Reports, BI Publisher, SQL-based extracts, and integration layers without the caller having to manage LOB locators or DBMS_LOB calls directly.

The view is especially useful for reporting and inspection purposes, where the structure of a contract — the sequence in which articles appear, their labels, titles, and subject classifications — must be presented alongside the article body. The user query term content_sequence maps directly to a column projected by this view, which is derived from KART.DISPLAY_SEQUENCE in the base article table.

Underlying Base Objects

The view is defined over four principal sources, joined through equality predicates on article and version identifiers:

  • OKC_K_ARTICLES_B (SYNONYM) — bears the sectioned article rows keyed by SCN_ID and DISPLAY_SEQUENCE, and supplies the SAV_SAE_ID and ARTICLE_VERSION_ID join keys.
  • OKC_ARTICLES_V (VIEW) — provides the canonical article identity (ARTICLE_ID, ARTICLE_VERSION_ID) and article type and title metadata.
  • OKC_ARTICLE_VERSIONS (SYNONYM) — supplies version-specific attributes, notably DISPLAY_NAME (used as fallback display name) and ARTICLE_TEXT (the CLOB-origin text exposed as TEXT).
  • FND_LOOKUPS (VIEW) — resolves the article type to a human-readable value through the lookup type OKC_SUBJECT, producing the SUBJECT column.

FND_GLOBAL is also documented as a referenced package, consistent with standard APPS view conventions for security and context resolution. The join logic binds article rows to their article definition and to the matching article version, so each row represents one sectioned article in the context of a specific version.

Key Columns

  • SCN_ID — identifier of the sectioned article record from OKC_K_ARTICLES_B.
  • CONTENT_SEQUENCE — the display ordering of the article within the section, sourced from KART.DISPLAY_SEQUENCE. This is the column most commonly used in ORDER BY clauses to render articles in authored sequence.
  • LABEL — the article’s short label or tag as defined on the base article row.
  • NAME — the article display name, resolved as NVL(VERS.DISPLAY_NAME, ART.ARTICLE_TITLE); the version display name takes precedence, with the article title as fallback.
  • SUBJECT — the decoded meaning of the article type, resolved from FND_LOOKUPS for lookup type OKC_SUBJECT.
  • TEXT — the article body text retrieved from the CLOB storage via the version object, exposed as TEXT.

Common Use Cases and Queries

Typical uses include contract clause reporting, audit and discovery extracts, template article verification, and downstream document generation where sectioned article text must be sequenced by CONTENT_SEQUENCE. The following pattern orders articles by their authored sequence:

  • SELECT content_sequence, label, name, subject, text FROM apps.okc_sectioned_articles_v ORDER BY content_sequence;
  • SELECT scn_id, content_sequence, label, name FROM apps.okc_sectioned_articles_v WHERE subject = 'Warranty' ORDER BY content_sequence;
  • SELECT content_sequence, DBMS_LOB.SUBSTR(text, 200, 1) snippet FROM apps.okc_sectioned_articles_v ORDER BY content_sequence; — useful when only a preview of the article text is required.

Because the view flattens version and lookup relationships, callers should apply the appropriate version or article filters when extracting a specific contract’s content, and use ORDER BY CONTENT_SEQUENCE wherever the presentation order matters.