Search Results source_flag

Overview

OKC_TERMS_ARTICLES_HV is an APPS-owned, VALID view in the Oracle E-Business Suite Contracts Core (OKC) module. It exposes the article-level content of contract terms and conditions (T&Cs) as stored in the Contracts repository. In the OKC data model, a contract (or contract template) is composed of one or more terms, and each term is further decomposed into ordered articles. The "HV" suffix conventionally denotes a "Header/Version" or historical-style view pattern used by the Contracts architecture to surface versioned, document-centric data. This view therefore presents individual article records — their labels, source flags, amendment state, display sequencing, and descriptive flexfield attributes — in a flattened, query-friendly form suitable for reporting, DBI/business intelligence extracts, and integration interfaces.

Because it is a view defined with the same column set as its underlying base table, it functions primarily as a stable read-only access layer. Applications and custom code should query this view rather than the base table to insulate themselves from structural changes.

Underlying Base Objects

The view is defined over a single documented base object:

• OKC_K_ARTICLES_BH (referenced through a SYNONYM) — the base articles table in the OKC schema. The _BH suffix indicates the primary article store used by the Contracts terms engine.

The view text is a straightforward projection: SELECT KART.ROWID, KART.ID, ... FROM OKC_K_ARTICLES_BH KART. It selects ROWID plus the full set of business and administrative columns, adding no joins, filters, or transformations. Consequently, OKC_TERMS_ARTICLES_HV is a 1:1 pass-through view. One row in the view corresponds to exactly one row in OKC_K_ARTICLES_BH, and the two may be used interchangeably for read purposes, with the view being the preferred public interface. Note that because it is built on a _BH (history/base-holding) object rather than a _BV/_TL object, callers should confirm whether they need current or historical article rows depending on their contract versioning requirements.

Key Columns

• ID — Primary identifier of the article record.
• ROW_ID / ROWID — Physical row address; useful for high-performance direct row access.
• DOCUMENT_TYPE / DOCUMENT_ID — Identify the owning contract document, linking the article to its parent contract or template.
• LABEL — The article's display label or title within the term.
• ARTICLE_VERSION_ID / MAJOR_VERSION / OBJECT_VERSION_NUMBER — Versioning and optimistic-locking attributes controlling which revision of the article is in effect.
• REF_ARTICLE_ID / REF_ARTICLE_VERSION_ID — The reference-article linkage. These are the columns the user's search term "ref_article_id" targets: they point to the source (reference) article and its version from which the current article derives, supporting article reuse and template inheritance.
• SOURCE_FLAG / MANDATORY_YN — Indicate the article's origin and whether it is mandatory.
• SCN_ID / SAV_SAE_ID — System-change and subject-area-view identifiers used by the amendment framework.
• AMENDMENT_OPERATION_CODE / SUMMARY_AMEND_OPERATION_CODE / AMENDMENT_DESCRIPTION — Describe pending or applied amendments to the article.
• PRINT_TEXT_YN / CHANGE_NONSTD_YN — Control printing and non-standard change behavior.
• ORIG_SYSTEM_REFERENCE_CODE / ID1 / ID2 — External system cross-references for integrations.
• DISPLAY_SEQUENCE — Determines article ordering within the term.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield segments.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — Standard audit columns.
• LAST_AMENDED_BY / LAST_AMENDMENT_DATE — Audit trail specific to the amendment process.

Common Use Cases and Queries

Typical uses include resolving which articles derive from a given reference article, reporting all articles belonging to a contract, and extracting amendment history for auditing.

• Find articles referencing a specific reference article:

  SELECT id, document_id, label, ref_article_id, ref_article_version_id FROM okc_terms_articles_hv WHERE ref_article_id = :p_ref_article_id;

• List all articles for a contract document in display order:

  SELECT id, label, display_sequence, mandatory_yn FROM okc_terms_articles_hv WHERE document_id = :p_document_id ORDER BY display_sequence;

• Identify recently amended articles:

  SELECT id, document_id, label, last_amended_by, last_amendment_date FROM okc_terms_articles_hv WHERE last_amendment_date >= :p_from_date;

All queries should be issued from the APPS schema or a schema with the appropriate synonym and privileges. As with any OKC reporting view, restrict results by document identifiers and use the audit and version columns to reconcile against the contract versioning model.