Search Results okc_art_var_sections

Overview

OKC_ART_VAR_SECTIONS is a Contracts Core (OKC) transactional table that stores variable substitution values associated with specific article versions within Oracle E-Business Suite contract documents. In the Oracle Contracts architecture, contract templates are composed of articles, and each article version contains mergeable "variables" — placeholders such as party name, effective date, or monetary amount — that must be resolved at contract generation time. OKC_ART_VAR_SECTIONS persists the resolved or assigned value for each variable in the context of a particular article version and section (SCN_CODE), allowing the same variable to carry distinct values across different sections of a document.

The ETRM relationship metadata classifies this object heuristically as standalone within a Data Vault model. This classification reflects the fact that, although the table carries foreign keys to parent entities, its grain is defined by the combination of an article version, variable code, variable value identifier, and section code, and it does not sit at the center of a network of dependent children. It is therefore best modeled as a satellite-like descriptive record attached to the article version hub rather than as a link between multiple business hubs.

Key Information Stored

The table contains eleven documented columns. The most significant are:

• ARTICLE_VERSION_ID — Identifier of the article version to which the variable value belongs; part of the foreign key to OKC_ARTICLE_VERSIONS and a component of the unique business key.
• ARTICLE_ID — Identifier of the owning article; foreign key to OKC_ARTICLES_ALL.
• VARIABLE_CODE — The code designating which variable (placeholder) is being populated; part of the unique key.
• VARIABLE_VALUE_ID — Identifier of the specific variable value definition being referenced; part of the unique key.
• VARIABLE_VALUE — The actual resolved value substituted into the document text for the variable.
• SCN_CODE — Section code, scoping the variable value to a particular section; part of the unique key and the column that allows repeated use of the same variable within one article version.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified each row.

No surrogate single-column primary key is documented. The unique index OKC_ART_VAR_SECTIONS_U1 on (ARTICLE_VERSION_ID, VARIABLE_CODE, VARIABLE_VALUE_ID, SCN_CODE) functions as the business-key candidate and is the strongest basis for identifying a row.

Common Use Cases and Queries

Typical usage centers on contract generation diagnostics and template maintenance reporting. A common query retrieves all variable values for a given article version:

• SELECT VARIABLE_CODE, VARIABLE_VALUE, SCN_CODE FROM OKC_ART_VAR_SECTIONS WHERE ARTICLE_VERSION_ID = :p_version_id;
• Join to OKC_ARTICLES_ALL on ARTICLE_ID to report variable values by article and contract template.
• Filter by VARIABLE_CODE to audit how a specific variable — for example, a customer name or price field — was populated across versions.
• Detect unresolved placeholders by checking for null or empty VARIABLE_VALUE across a version's section rows.
• Compare values across SCN_CODE values to confirm that section-specific overrides were maintained correctly.

Related Objects

The most significant related objects, based on documented referential relationships, are:

• OKC_ARTICLE_VERSIONS — joined on ARTICLE_VERSION_ID; the immediate parent of each variable value row.
• OKC_ARTICLES_ALL — joined on ARTICLE_ID; the article master that owns the versions.
• Section and variable definition tables in the OKC schema that supply VARIABLE_VALUE_ID and SCN_CODE semantics.
• Contract template and document generation components that consume these rows to render final contract text.

Because the table is classified as standalone, it carries no documented downstream children; all relationships are directed toward its parent article structures.