Search Results okc_function_expr_params_h_u1

Overview

OKC.OKC_FUNCTION_EXPR_PARAMS_H is the history (version) table for the OKC_FUNCTION_EXPR_PARAMS entity within the Oracle E-Business Suite Contracts (OKC) schema. It stores the parameters supplied to a Function Expression, which is the runtime mechanism used by Oracle Contracts to evaluate conditional logic during contract authoring. Each row represents a parameter definition at a specific MAJOR_VERSION of a contract, allowing the full evolution of Function Expression parameters to be preserved and audited as contract terms are revised.

The base entity OKC_FUNCTION_EXPR_PARAMS records the live definition of a parameter, while this _H table retains prior and current versions keyed by contract MAJOR_VERSION. The object's status is VALID and it is registered in FND Design Data as OKC.OKC_FUNCTION_EXPR_PARAMS_H. Based on its column composition—an ID, contract-level denormalized key (DNZ_CHR_ID), a MAJOR_VERSION discriminator, and a set of descriptive attributes—a Data Vault modeling exercise would most plausibly classify this as a satellite attached to a contract version hub, since it carries descriptive, time-variant attributes rather than acting purely as a hub or link. This classification is a heuristic suggestion, not a documented constraint.

Key Information Stored

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

• ID — System generated unique identifier for the parameter within the base entity; part of the composite primary key.
• MAJOR_VERSION — The contract version to which this history record pertains; the second component of the composite primary key.
• DNZ_CHR_ID — Denormalized contract header identifier linking the parameter record to its parent contract.
• CNL_ID, PDP_ID, AAE_ID — Foreign-key style references to the corresponding column definitions in the base OKC_FUNCTION_EXPR_PARAMS table, carrying the linkage to the function expression, data point, and action attribute entities.
• VALUE (VARCHAR2, up to 2000) — The parameter value that is supplied to the function expression; its meaning depends on the parameter subtype (attribute-supplied versus user-supplied).
• OBJECT_VERSION_NUMBER — Optimistic locking counter used to detect concurrent updates.
• SEEDED_FLAG, APPLICATION_ID — Standard Oracle markers identifying which application owns the row and whether it is a seeded (delivered) definition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard "Who" audit columns.
• SECURITY_GROUP_ID — Used in hosted environments to partition data by security group.

The surrogate/composite primary key is OKC_FUNCTION_EXPR_PARAMS_H_PK on (ID, MAJOR_VERSION). The unique index OKC_FUNCTION_EXPR_PARAMS_H_U1 also spans (ID, MAJOR_VERSION) and therefore serves as the business-key candidate that enforces version uniqueness. A separate nonunique index, OKC_FUNCTION_EXPR_PARAMS_H_N1, exists on DNZ_CHR_ID to accelerate contract-level retrieval.

Common Use Cases and Queries

This table is primarily consulted by history/audit reporting and by change-tracking logic that reconstructs how a Function Expression was parameterized at a given contract version. Typical patterns include retrieving the latest parameter value for a contract, comparing parameters across versions, and joining to the base table to obtain the current definition.

Example: fetch all history rows for a contract header.

SELECT h.ID, h.MAJOR_VERSION, h.VALUE, h.LAST_UPDATE_DATE
FROM OKC.OKC_FUNCTION_EXPR_PARAMS_H h
WHERE h.DNZ_CHR_ID = :p_contract_id
ORDER BY h.MAJOR_VERSION, h.ID;

Example: identify the most recent version of each parameter.

SELECT ID, MAX(MAJOR_VERSION) AS LATEST_VERSION
FROM OKC.OKC_FUNCTION_EXPR_PARAMS_H
GROUP BY ID;

Because both the primary key and the unique index are built on (ID, MAJOR_VERSION), queries filtering on DNZ_CHR_ID or on a version range benefit from the OKC_FUNCTION_EXPR_PARAMS_H_N1 index. Reporting teams using these patterns should account for seeded rows (SEEDED_FLAG) when distinguishing delivered versus customer-defined parameters.

Related Objects

The following objects are most significant in relation to this table, based on the documented relationships:

• OKC.OKC_FUNCTION_EXPR_PARAMS — The base (non-history) table; most columns here are documented as "see the corresponding description" there, making it the primary source of current definitions.
• FND_SECURITY_GROUPS — Referenced by the foreign key on SECURITY_GROUP_ID, supporting hosting and multi-tenant filtering.
• OKC.OKC_FUNCTION_EXPR_PARAMS_H_PK — The composite primary key on (ID, MAJOR_VERSION) defining the object's uniqueness.
• OKC_FUNCTION_EXPR_PARAMS_H_U1 — The unique index on (ID, MAJOR_VERSION) that acts as the business-key candidate.
• OKC_FUNCTION_EXPR_PARAMS_H_N1 — The nonunique index on DNZ_CHR_ID used for contract-level access.

Queries generally join this history table to OKC_FUNCTION_EXPR_PARAMS on (ID) to reconcile the versioned value with the current definition.