Results for “aae_id”

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

Overview

The OKC_FUNCTION_EXPR_PARAMS_V view is a reporting and integration object within the Oracle E-Business Suite Contracts Core (OKC) module. It belongs to the APPS schema and holds STATUS: VALID across release levels 12.1.1 and 12.2.2. The view presents contract function expression parameters, which are the individual argument values bound to programmable expressions evaluated by the Contracts Core runtime engine. In EBS, contract terms, deliverables, and pricing logic frequently depend on expressions that resolve at runtime against contract header, party, or line context. The parameters captured in this view supply the concrete values those expressions consume.

Because it is a view rather than a table, OKC_FUNCTION_EXPR_PARAMS_V provides a read-only projection suitable for reporting, data extraction, and integration without exposing the underlying table to direct DML. It is the standard access point for tools such as Oracle Reports, BI Publisher, and the OA Framework when contract expression metadata must be surfaced.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined exclusively over the synonym OKC_FUNCTION_EXPR_PARAMS (aliased FEPB in the view text). All columns are passed through from that single base object using a straightforward SELECT list — the view performs no joins and applies no filter predicates. Consequently, every row and column of OKC_FUNCTION_EXPR_PARAMS is visible through OKC_FUNCTION_EXPR_PARAMS_V, including the ROWID exposed as ROW_ID.

This one-to-one relationship means the view can be treated as a synonym-style projection: row counts, cardinality, and column semantics are identical to the base table. Any change to the table's structure propagates to the view only when the view definition is recompiled.

Key Columns

• ROW_ID — the base table ROWID, exposed for row-level identification.
• ID — primary identifier of the expression parameter record.
• OBJECT_VERSION_NUMBER — optimistic locking version for concurrent update control.
• CNL_ID — identifier of the contract line associated with the parameter.
• PDP_ID — identifier of the related pricing or process data point.
• AAE_ID — identifier of the associated AAE (application attribute / expression) entity.
• DNZ_CHR_ID — contract header identifier linking the parameter to a specific contract.
• VALUE — the actual parameter value supplied to the expression at runtime.
• APPLICATION_ID — the owning application, used to scope expression ownership.
• SEEDED_FLAG — indicates whether the record is Oracle-seeded (system) or user-defined.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO audit columns tracking creation and modification history.

Common Use Cases and Queries

Typical uses include auditing seeded versus user-defined expression parameters, extracting parameter values for integration with external pricing or document-generation systems, and diagnosing why a contract expression evaluates incorrectly. The SEEDED_FLAG and APPLICATION_ID columns are especially useful for governance reporting.

Retrieve all parameters for a given contract header:

SELECT id, cnl_id, pdp_id, aae_id, value
FROM   apps.okc_function_expr_params_v
WHERE  dnz_chr_id = :p_contract_id;

List user-defined parameters only:

SELECT id, dnz_chr_id, aae_id, value
FROM   apps.okc_function_expr_params_v
WHERE  seeded_flag = 'N'
ORDER  BY creation_date DESC;

Audit recently changed parameters with WHO columns:

SELECT id, dnz_chr_id, value,
       last_updated_by, last_update_date
FROM   apps.okc_function_expr_params_v
WHERE  last_update_date >= SYSDATE - 30;

Because the view exposes no joins, queries remain lightweight, but callers should apply the same access and security filters used for the base table to avoid exposing contract data across operating units.