Search Results scn_code




Overview
Explore in AI Chat

Overview

OKC_SECTIONS_V is a reporting view owned by the APPS schema within the OKC — Contracts Core product of Oracle E-Business Suite. It presents contract section (clause structure) information maintained by the Contract Terms and Conditions authoring framework. In EBS 12.1.1 and 12.2.2, this view serves as the read interface for application logic, concurrent programs, and custom extensions that need to retrieve section-level metadata for contracts, templates, and other documents without directly querying the underlying base table. The view is defined as a simple projection over the base table, exposing the full column set including ROWID, who-columns, the fifteen descriptive flexfield attributes, and the business-specific attributes such as SCN_CODE and SECTION_SEQUENCE. Because it is a view rather than a table, it cannot be updated directly; insert, update, and delete operations must target the base entity through the appropriate APIs.

Underlying Base Objects

According to the documented ETRM metadata, OKC_SECTIONS_V is defined over a single referenced base object, OKC_SECTIONS_B, accessed in the view text through the synonym SCNB. The view text is a straightforward SELECT that maps each column of the base table without joins, aggregations, or filtering. The only derived value is SFWT_FLAG, which is emitted as a literal NULL because the corresponding flag does not exist on the base table in this release. All other columns — including the primary ID, SCN_ID, SCN_TYPE, CHR_ID, SAT_CODE, SECTION_SEQUENCE, LABEL, HEADING, DOCUMENT_TYPE, DOCUMENT_ID, and SCN_CODE — are direct pass-throughs. Consequently, the view carries no independent data and remains consistent with the base table at query time. ROW_ID is populated from SCNB.ROWID, preserving the physical row locator of the base record.

Key Columns

  • ROW_ID — the ROWID of the underlying OKC_SECTIONS_B row, useful for targeted single-row lookups.
  • ID — the primary identifier of the section record.
  • SCN_TYPE — the section type classification used to distinguish section kinds within the framework.
  • SCN_CODE — the section code; this is the value the user searched for, and it identifies the section in a business-readable manner.
  • SCN_ID / CHR_ID — surrogate and character-level identifiers linking the section to its parent document hierarchy.
  • SAT_CODE — the section attribute code.
  • SECTION_SEQUENCE — the ordering position of the section within its document.
  • LABEL / HEADING — the display label and heading text rendered in the contract output.
  • DOCUMENT_TYPE / DOCUMENT_ID — the owning document’s type and identifier.
  • OBJECT_VERSION_NUMBER — optimistic locking version used during concurrent updates.
  • AMENDMENT_DESCRIPTION / AMENDMENT_OPERATION_CODE / SUMMARY_AMEND_OPERATION_CODE — amendment tracking fields that describe how the section was changed.
  • ORIG_SYSTEM_REFERENCE_CODE / ID1 / ID2 — cross-system reference keys for integration with external systems.
  • PRINT_YN — flag controlling whether the section appears in printed output.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield context and segments.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical usage retrieves sections for a given document, locates a section by its code, or feeds downstream reporting and printing logic. For example, to list all sections of a document in sequence:

SELECT scn_code, label, heading, section_sequence
FROM okc_sections_v
WHERE document_id = :p_document_id
AND document_type = :p_document_type
ORDER BY section_sequence;

To locate a specific section by the searched code:

SELECT id, scn_code, label, heading, print_yn
FROM okc_sections_v
WHERE scn_code = :p_scn_code;

The view is also used in amendment auditing queries that compare AMENDMENT_OPERATION_CODE values, and in integration extracts relying on ORIG_SYSTEM_REFERENCE_CODE mapping. Because the view exposes the ROWID as ROW_ID and mirrors the base table columns exactly, it is well suited to reporting joins with other OKC contract objects while remaining read-only.