Search Results okc_article_variables_u1
Overview
The OKC.OKC_ARTICLE_VARIABLES table is a core repository object within the Oracle Contracts (OKC) application module of Oracle E-Business Suite. It stores the variables associated with a clause version, capturing the embedded tokens that appear within clause or article text. These rows are not created manually by users; they are generated systematically by the application when it parses clause text and extracts the embedded variables defined for that clause version. Because clause variables drive the dynamic resolution of contract terms at runtime, this table forms an essential bridge between static clause definitions and the business variables that supply runtime values.
Under the heuristic Data Vault classification derived from its foreign key structure, this object is best modeled as a link. It resolves a many-to-many relationship between clause versions and business variables, sitting between the two parent hubs rather than describing the attributes of either one independently. This classification is a modeling suggestion and reflects the associative nature of the table.
Key Information Stored
The table contains eight documented columns. The most significant are the two components that together constitute the primary key and the composite business key:
- ARTICLE_VERSION_ID (NUMBER) — Identifies the clause version that contains the variable. It is a foreign key to
OKC_ARTICLE_VERSIONS. - VARIABLE_CODE (VARCHAR2(30)) — Identifies the specific variable referenced within that clause version. It is a foreign key to
OKC_BUS_VARIABLES_B. - OBJECT_VERSION_NUMBER (NUMBER) — A sequential number set to 1 on insert and incremented on update. It is used by APIs to detect stale records and enforce optimistic concurrency control.
- CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard "Who" audit columns that record the user and timestamp details for row creation and the most recent modification.
The two unique indexes are structurally identical in content but reversed in column order: OKC_ARTICLE_VARIABLES_U1 is defined on (ARTICLE_VERSION_ID, VARIABLE_CODE), while OKC_ARTICLE_VARIABLES_U2 — the index the user searched for — is defined on (VARIABLE_CODE, ARTICLE_VERSION_ID). Both enforce uniqueness across the same logical pair of columns, guaranteeing that any given clause version can reference a particular variable only once. The primary key constraint, OKC_ARTICLE_VARIABLES_PK1, is likewise defined over (VARIABLE_CODE, ARTICLE_VERSION_ID). The table resides in the APPS_TS_TX_DATA tablespace, with its indexes stored in APPS_TS_TX_IDX, and carries a PCT Free of 10.
Common Use Cases and Queries
Typical usage centers on identifying which variables are embedded in a given clause version, or conversely, determining where a given variable is used across clause versions. A baseline query returning all associative rows is:
SELECT ARTICLE_VERSION_ID, VARIABLE_CODE, OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE FROM OKC.OKC_ARTICLE_VARIABLES;- To list variables for a specific clause version: filter on
ARTICLE_VERSION_ID, which benefits from indexOKC_ARTICLE_VARIABLES_U1. - To find all clause versions using a particular variable: filter on
VARIABLE_CODE, which benefits from indexOKC_ARTICLE_VARIABLES_U2.
Reporting scenarios include impact analysis before modifying or retiring a business variable, validation of clause template completeness, and reconciliation of extracted variables against the source clause text during implementation or upgrade testing.
Related Objects
The table participates in the following documented relationships:
OKC_ARTICLE_VERSIONS— parent of theARTICLE_VERSION_IDforeign key; supplies clause version details.OKC_BUS_VARIABLES_B— parent of theVARIABLE_CODEforeign key; supplies variable definitions.OKC_BUS_VARIABLES_TL— the translated child of the variable base table, commonly joined to render variable names.OKC_ARTICLES_BandOKC_ARTICLES_TL— provide the article context for the clause versions.OKC_ARTICLE_VARIABLES#— the companion object referenced by this table, supporting editioning or synonym structures.
Together these objects enable contract authors and technical teams to trace the full path from article text through clause version to the business variables resolved at runtime.
-
INDEX: OKC.OKC_ARTICLE_VARIABLES_U1
12.1.1
owner:OKC, object_type:INDEX, object_name:OKC_ARTICLE_VARIABLES_U1, status:VALID,
-
INDEX: OKC.OKC_ARTICLE_VARIABLES_U1
12.2.2
owner:OKC, object_type:INDEX, object_name:OKC_ARTICLE_VARIABLES_U1, status:VALID,
-
TABLE: OKC.OKC_ARTICLE_VARIABLES
12.2.2
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_ARTICLE_VARIABLES, object_name:OKC_ARTICLE_VARIABLES, status:VALID,
-
TABLE: OKC.OKC_ARTICLE_VARIABLES
12.1.1
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_ARTICLE_VARIABLES, object_name:OKC_ARTICLE_VARIABLES, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
eTRM - OKC Tables and Views
12.1.1
description: Intersection entity between templates and rules. ,
-
eTRM - OKC Tables and Views
12.2.2
description: Intersection entity between rules and templates ,