Results for “okc_variable_doc_types”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKC_VARIABLE_DOC_TYPES is a Contracts Core (OKC) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the association between system-defined contract variables and the document types to which they apply. Its purpose is to determine the source of system variable values, so that when the contracting engine resolves a variable during document generation or merge processing, it can identify the correct document type context from which the value should be drawn. In this sense the table acts as a controlled cross-reference between the variable definitions held in OKC_BUS_VARIABLES_B and the contract document types held in OKC_BUS_DOC_TYPES_B.

From a Data Vault modeling perspective, the mined foreign-key metadata suggests a link classification. This is a heuristic suggestion rather than a native EBS attribute: the table resolves a many-to-many style relationship between variables and document types and carries no significant descriptive payload of its own, which is characteristic of a link construct rather than a hub or satellite.

Key Information Stored

The retained business content of the table is compact. The most significant columns are:

• VARIABLE_CODE — foreign key to OKC_BUS_VARIABLES_B; identifies the system-defined variable whose source is being qualified.
• DOC_TYPE — foreign key to OKC_BUS_DOC_TYPES_B; identifies the contract document type associated with the variable.
• VIEW_OBJECT_NAME — the view or object name used to resolve the variable value at runtime.
• APPLICATION_ID — the owning Oracle application context for the variable/document type pairing.
• ATTRIBUTE_NAME and ATTRIBUTE_INDEX — identify the specific attribute and its positional index within the source object from which the value is sourced.
• OBJECT_VERSION_NUMBER — the standard EBS optimistic-locking column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard audited WHO columns maintained automatically by the framework.
• ZD_EDITION_NAME — the editioning column introduced by the EBR (Edition-Based Redefinition) architecture in 12.2.x, which supports online patching.

The table has a composite primary key, OKC_VARIABLE_DOC_TYPES_PK1, defined on (VARIABLE_CODE, DOC_TYPE). Two unique indexes act as business-key candidates: OKC_VARIABLE_DOC_TYPES_U1 on (DOC_TYPE, VARIABLE_CODE, ZD_EDITION_NAME) and OKC_VARIABLE_DOC_TYPES_U2 on (VARIABLE_CODE, DOC_TYPE, ZD_EDITION_NAME). Both enforce the same logical uniqueness, differing only in column order and the editioning suffix added in 12.2.2. There is no separate single-column surrogate key.

Common Use Cases and Queries

The table is principally queried when diagnosing or configuring system variable resolution during contract document generation. A typical pattern joins the variable and document type parents to produce a readable map:

• Listing all document types associated with a given variable: SELECT DOC_TYPE FROM OKC_VARIABLE_DOC_TYPES WHERE VARIABLE_CODE = :code;
• Resolving the value source for a merge: join to OKC_BUS_VARIABLES_B on VARIABLE_CODE and OKC_BUS_DOC_TYPES_B on DOC_TYPE, selecting VIEW_OBJECT_NAME, ATTRIBUTE_NAME, and ATTRIBUTE_INDEX.
• Reporting orphaned or unconfigured variables by outer-joining variables to this table to find ones with no document type mapping.
• Verifying editioned rows in 12.2.2 by filtering on ZD_EDITION_NAME when working within an active patching edition.

Related Objects

• OKC_BUS_VARIABLES_B — parent of VARIABLE_CODE; holds the variable definitions.
• OKC_BUS_DOC_TYPES_B — parent of DOC_TYPE; holds the document type definitions.
• Both FK relationships (DOC_TYPE → OKC_BUS_DOC_TYPES_B and VARIABLE_CODE → OKC_BUS_VARIABLES_B) are the primary joins for any resolution query.
• The unique indexes OKC_VARIABLE_DOC_TYPES_U1 and OKC_VARIABLE_DOC_TYPES_U2 and the primary key OKC_VARIABLE_DOC_TYPES_PK1 constrain access paths and should be considered when tuning reporting queries.