Results for “variable_value”

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

Overview

PO_OKC_VARS_GT is a global temporary table (indicated by the "_GT" suffix) owned by the PO (Purchasing) schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It serves as a transient staging structure used by the Oracle Contracts (OKC) and Purchasing integration to hold contract-related variable values during processing. Global temporary tables in EBS are commonly populated during concurrent program runs, contract generation, or document authoring flows, and their contents persist only for the duration of a session or transaction depending on the table's ON COMMIT clause.

The table models a bridge between purchasing documents and contract article variables. Each row associates a source document (identified by DOC_TYPE and DOC_ID) with a specific article version, a category, and a single variable name/value pair. This makes it a lightweight linking structure rather than a master entity.

From a Data Vault modeling perspective, the metadata classifies PO_OKC_VARS_GT heuristically as standalone. Because it carries two foreign key references but no uniquely identified parent hub within its own footprint, it is best treated as a transient link or staging artifact. Analysts modeling the underlying contract data should expect the persistent hubs and satellites to reside in the OKC (Contracts) tables, with PO_OKC_VARS_GT acting only as a processing bridge.

Key Information Stored

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

• DOC_TYPE — Classifies the source document (for example, a purchasing document type), used together with DOC_ID to identify the parent business object.
• DOC_ID — The identifier of the source document being processed. DOC_TYPE plus DOC_ID form the primary business-key candidate for locating rows for a given document.
• ARTICLE_VERSION_ID — Foreign key to OKC_ARTICLE_VERSIONS, identifying the exact contract article version whose variables are being staged.
• CAT_ID — Foreign key to BEN_TCS_CAT, the category under which the variable is grouped (typically a contracts or terms category).
• VARIABLE_CODE — The name or code of the contract variable being supplied.
• VARIABLE_VALUE — The value assigned to the corresponding VARIABLE_CODE for the document/article combination.

No surrogate system-generated primary key column is documented, and because this is a global temporary table, no persistent unique index is published. Business-key uniqueness is effectively the combination of DOC_TYPE, DOC_ID, ARTICLE_VERSION_ID, CAT_ID, and VARIABLE_CODE.

Common Use Cases and Queries

This table is typically read within PL/SQL or concurrent processes rather than queried ad hoc by end users. Reporting scenarios include extracting resolved contract variable values for a purchasing document or validating that all expected variables were staged before contract generation.

A representative query joins the staging rows back to the contract article version:

• SELECT g.doc_type, g.doc_id, g.variable_code, g.variable_value FROM po.po_okc_vars_gt g WHERE g.doc_id = :doc_id AND g.doc_type = :doc_type;
• Join to OKC_ARTICLE_VERSIONS on g.article_version_id = av.article_version_id to retrieve article context.
• Join to BEN_TCS_CAT on g.cat_id = c.cat_id to resolve category descriptions.

Because the table is transient, any extraction must occur within the same session or transaction that populated it. For audit or history, the persistent values should be sourced from the underlying OKC contract tables instead.

Related Objects

PO_OKC_VARS_GT depends on and relates to the following objects:

• OKC_ARTICLE_VERSIONS — joined via PO_OKC_VARS_GT.ARTICLE_VERSION_ID; supplies the contract article version definition.
• BEN_TCS_CAT — joined via PO_OKC_VARS_GT.CAT_ID; provides the category against which variables are grouped.
• OKC_ARTICLES and related OKC contract definition tables — parent entities for article versions referenced here.
• PO_HEADERS_ALL / PO_LINES_ALL — likely owners of the DOC_ID when DOC_TYPE indicates a purchasing document.
• OKC Contract APIs (such as OKC_CONTRACT_PVT) — the program logic that consumes these staged variables during contract authoring.

These relationships confirm the table's role as a transient integration bridge between Purchasing documents and the Oracle Contracts repository.