Search Results swft_flag

Overview

APPS.OKC_SECTIONS_HV is a reporting and integration view in the Oracle E-Business Suite Contracts (OKC / ETRM) module. It presents contract section header data at the historical ("_HV" suffix indicating a history-style or versioned projection) level, exposing section metadata such as section type, character ID, sequence, label, heading, and document association. The view is part of the OKC_SECTIONS family, which underpins section-level structure for contracts, amendments, and related deliverables within Oracle Contracts Core.

The view serves as a stable read interface for section header information across Oracle EBS 12.1.1 and 12.2.2, allowing external reports, integrations, and extensions to query section data without directly referencing the base table. Consistent with the ETRM documentation, the view is owned by APPS and resolves to a single documented base object, OKC_SECTIONS_BH (accessed through a synonym).

Underlying Base Objects

According to the documented metadata, the view is defined over exactly one referenced base object: OKC_SECTIONS_BH, accessed via a synonym in the APPS schema. The view text confirms this, selecting all columns from that base table while aliasing it as SCNH. The "_BH" suffix conventionally denotes a "base history" or "before/header" table in OKC structures, holding section header rows keyed by ID and MAJOR_VERSION.

Because the view is a direct projection over OKC_SECTIONS_BH, it inherits the base table's row population, versioning semantics, and audit columns. No joins or filters are applied in the documented view definition, so the view reflects the base object content one-to-one.

Key Columns

• ID — Primary identifier for the section row.
• MAJOR_VERSION — Version indicator for the section, supporting versioned queries.
• SCN_TYPE — Section type classification.
• CHR_ID — Character (contract header) identifier linking the section to its parent contract.
• SAT_CODE — Section attribute code.
• SCN_ID — Alternate section identifier.
• SECTION_SEQUENCE — Ordering of the section within its parent.
• LABEL, HEADING, DESCRIPTION — Display attributes for the section.
• DOCUMENT_TYPE, DOCUMENT_ID — Association to the referenced document.
• SCN_CODE, PRINT_YN — Contract code and print indicator.
• SWFT_FLAG — Exposed as a literal NULL in this view (the user's search term); it is not sourced from OKC_SECTIONS_BH.
• AMENDMENT_DESCRIPTION, AMENDMENT_OPERATION_CODE, SUMMARY_AMEND_OPERATION_CODE — Amendment tracking attributes.
• ORIG_SYSTEM_REFERENCE_CODE / _ID1 / _ID2 — External system reference keys.
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus OBJECT_VERSION_NUMBER and ATTRIBUTE1..15 flexible attributes.

Common Use Cases and Queries

Typical usage includes listing sections for a contract, retrieving version-specific section headers, and integrating section metadata with external systems. Because SWFT_FLAG is a NULL literal, queries filtering on it return no meaningful results and should generally avoid that predicate.

Sample query retrieving sections for a contract:

• SELECT ID, MAJOR_VERSION, SCN_TYPE, CHR_ID, SECTION_SEQUENCE, LABEL, HEADING FROM APPS.OKC_SECTIONS_HV WHERE CHR_ID = :p_chr_id ORDER BY SECTION_SEQUENCE;
• SELECT SCN_ID, SCN_CODE, DOCUMENT_TYPE, DOCUMENT_ID, PRINT_YN FROM APPS.OKC_SECTIONS_HV WHERE ORIG_SYSTEM_REFERENCE_CODE = :p_sys_code;
• SELECT ID, MAJOR_VERSION, AMENDMENT_OPERATION_CODE FROM APPS.OKC_SECTIONS_HV WHERE AMENDMENT_OPERATION_CODE IS NOT NULL;

These examples reflect the documented column set and demonstrate the view's role as the preferred accessible read path for OKC section header data.