Search Results okc_function_expr_params_h




Overview
Explore in AI Chat

Overview

OKC_FUNCTION_EXPR_PARAMS_H is a table in the OKC (Contracts Core) schema within Oracle E-Business Suite. As documented in the ETRM metadata for release 12.2.2, its purpose is to store the parameters to be supplied to a FUNCTION EXPRESSION. Within the Contracts Core module, expressions are the mechanism by which Oracle Contracts evaluates runtime logic — for example, deriving default values, computing terms, or conditionally routing contract clauses. This table holds the argument bindings that a given expression invocation requires, keyed against the contract, the expression definition, and the parameter definition involved.

The _H suffix identifies this as a history (versioned) table. The presence of both ID and MAJOR_VERSION in the primary key, together with the OKC_FUNCTION_EXPR_PARAMS_H_PK constraint on (ID, MAJOR_VERSION), confirms that each logical row is retained across multiple versions rather than overwritten. The heuristic Data Vault classification mined from the foreign-key structure is standalone, meaning no strict parent-child link is implied by the FK topology; from a modeling perspective it behaves most like a versioned satellite attached to the surrounding expression objects, though the classification provided is explicitly heuristic.

Key Information Stored

The documented physical schema contains sixteen columns. The most significant are listed below.

  • ID — Surrogate identifier for the parameter record; part of the composite primary key and of the unique index OKC_FUNCTION_EXPR_PARAMS_H_U1.
  • MAJOR_VERSION — Version discriminator; the second component of the primary key and of the unique business-key candidate.
  • VALUE — The parameter value actually supplied to the function expression. This is the principal payload of the row.
  • PDP_ID — Reference to the parameter definition (the parameter's metadata), identifying which argument this row populates.
  • CNL_ID — Contract line context to which the expression parameter applies.
  • AAE_ID — Reference to the associated expression entity, tying the parameter to a specific function expression.
  • DNZ_CHR_ID — Denormalized contract identifier, used to avoid additional joins in contract-scoped queries.
  • OBJECT_VERSION_NUMBER — Optimistic concurrency control column maintained by the framework.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS who-columns providing audit lineage.
  • SECURITY_GROUP_ID — Multi-tenant/security partitioning column, referencing FND_SECURITY_GROUPS.
  • APPLICATION_ID — Owning application identifier, consistent with EBS conventions.
  • SEEDED_FLAG — Indicates whether the row is Oracle-seeded as opposed to customer-defined.

The surrogate primary key is (ID, MAJOR_VERSION). The documented unique index OKC_FUNCTION_EXPR_PARAMS_H_U1 carries the identical column list, so it functions as the business-key candidate for the versioned record rather than introducing an alternate key.

Common Use Cases and Queries

Practical work with this table centres on auditing and troubleshooting expression-driven behaviour in contracts. A typical retrieval pattern joins the history table to its transactional counterparts and filters by contract or expression:

  • Reconstructing the parameter set supplied to a function expression at a point in time, using MAJOR_VERSION ordering to trace how values changed.
  • Reporting all parameters for a contract by filtering on DNZ_CHR_ID, avoiding joins to the contract header.
  • Identifying Oracle-seeded versus customer-extended parameter rows via SEEDED_FLAG.
  • Data-fix scripts that must respect OBJECT_VERSION_NUMBER to avoid concurrency conflicts.

A representative query shape is: select ID, MAJOR_VERSION, PDP_ID, AAE_ID, VALUE from OKC_FUNCTION_EXPR_PARAMS_H where DNZ_CHR_ID = :contract_id order by ID, MAJOR_VERSION. Security-conscious deployments must additionally restrict rows by SECURITY_GROUP_ID.

Related Objects

  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; the only documented foreign key from this table.
  • OKC_FUNCTION_EXPR_PARAMS — The non-history counterpart holding the current parameter definitions.
  • The expression definition tables referenced by AAE_ID and the parameter definition tables referenced by PDP_ID, which supply the metadata this table instantiates.
  • The contract header and line structures addressed by DNZ_CHR_ID and CNL_ID.
  • OKC expression and rule APIs that read these parameters at evaluation time.

Because the documented FK topology classifies this object as standalone, the relationships above are chiefly logical joins rather than enforced constraints, and integrators should validate join keys against their own instance.