Search Results okc_art_var_sections_u1

Overview

OKC.OKC_ART_VAR_SECTIONS is a transactional table in the Oracle E-Business Suite Contracts (OKC) schema that stores variable (merge field) values associated with specific versions of contract terms articles. Within the Oracle Contracts Terms and Conditions repository, articles are authored as reusable text templates into which named variables are embedded; these variables are resolved to concrete values at runtime. OKC_ART_VAR_SECTIONS captures that resolved binding, recording which variable code, value identifier, and value apply to a given article version and section code. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and it participates in the standard EBS auditing convention through CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

From a data-vault modeling perspective, the metadata classifies this object as a standalone table (no inbound or outbound foreign keys were detected in the FK structure). Because OKC_ART_VAR_SECTIONS records attribute values attached to an article version, a satellite classification is the most natural modeling suggestion, keyed by the article version it describes. Practitioners should treat the classification as a heuristic rather than an authoritative designation.

Key Information Stored

The table contains eleven documented columns. The business-key candidate is defined by the unique index OKC_ART_VAR_SECTIONS_U1, a NORMAL/UNIQUE index in APPS_TS_TX_IDX spanning four columns: ARTICLE_VERSION_ID, VARIABLE_CODE, VARIABLE_VALUE_ID, and SCN_CODE. There is no separate single-column surrogate primary key documented; the unique index effectively serves as the primary key. The relationship metadata indicates that ARTICLE_ID and ARTICLE_VERSION_ID function as foreign keys to OKC.OKC_ARTICLES_ALL and OKC.OKC_ARTICLE_VERSIONS respectively, though the reference list notes the table does not explicitly reference database objects.

• ARTICLE_VERSION_ID (NUMBER) — Identifies the specific version of the article to which the variable value applies; the leading key column.
• VARIABLE_CODE (VARCHAR2 30) — The merge-field/variable name embedded in the article text.
• VARIABLE_VALUE_ID (NUMBER) — Surrogate reference to the resolved value record.
• VARIABLE_VALUE (VARCHAR2 60) — The actual textual value substituted at runtime.
• ARTICLE_ID (NUMBER) — The parent article identifier, linking to the article master.
• SCN_CODE (VARCHAR2 30) — Section or structural code associated with the variable placement.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage centers on contract template maintenance and merge-field resolution diagnostics. A common pattern resolves all variable values for an article version:

• Variable substitution audit: SELECT VARIABLE_CODE, VARIABLE_VALUE FROM OKC.OKC_ART_VAR_SECTIONS WHERE ARTICLE_VERSION_ID = :version_id;
• Article-level value report: join to the parent article by ARTICLE_ID to list all values across versions.
• Duplicate or conflicting value detection: group by ARTICLE_VERSION_ID and VARIABLE_CODE to compare VARIABLE_VALUE_ID assignments.
• Change tracking: filter by LAST_UPDATE_DATE to report recently modified variable bindings.

These queries support contract generation troubleshooting, template quality checks, and migration validation when article versions are copied or upgraded.

Related Objects

The most significant related objects are those identified in the dependency and relationship metadata:

• OKC.OKC_ARTICLES_ALL — parent article master, joined by ARTICLE_ID.
• OKC.OKC_ARTICLE_VERSIONS — version master, joined by ARTICLE_VERSION_ID.
• OKC.OKC_ART_VAR_SECTIONS# — the internal/synonym-referenced counterpart object.
• OKC_ART_VAR_SECTIONS_U1 — the unique index enforcing the business key.

Application interfaces that read or write this table typically operate through the Oracle Contracts terms authoring and contract generation flows rather than direct DML.