Results for “okc_function_expr_params”

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

Overview

The OKC_FUNCTION_EXPR_PARAMS table in the OKC (Contracts Core) schema stores the parameter values that are supplied to a function referenced within a Contracts condition line. In Oracle E-Business Suite 12.1.1 and 12.2.2, this table underpins the configurable rule and expression framework used by Oracle Contracts, allowing business rules, validation logic, and conditional processing to be evaluated dynamically against runtime data. Each row represents a single supplied argument that feeds into a function invoked by a condition line, thereby binding a function's input signature to concrete values drawn from process definitions, action attributes, or condition context.

From a data modeling perspective, the metadata's Data Vault classification heuristic identifies this table as a link. This is consistent with its structure: the table's primary key, OKC_FUNCTION_EXPR_PARAMS_PK on the ID column, is a surrogate key, while the substantive relationships it captures connect multiple independent entities — condition lines, process definition parameters, and action attributes. Modeling it as a link table between those entities is a reasonable suggestion, as it records the association and the carried measure (the parameter VALUE) between them.

Key Information Stored

The documented physical schema comprises 16 columns. The most significant are summarized below; the surrogate primary key is distinguished from the business-key candidates identified by the unique indexes.

• ID — Surrogate primary key (OKC_FUNCTION_EXPR_PARAMS_PK). Not a business identifier; used for row-level referencing and joins to child or audit structures.
• CNL_ID — Foreign key to OKC_CONDITION_LINES_B, identifying the condition line whose function invocation this parameter supports. Part of unique index OKC_FUNCTION_EXPR_PARAMS_U2.
• PDP_ID — Foreign key to OKC_PROCESS_DEF_PARMS_B, linking the parameter to its formal process definition parameter (the expected argument). Part of U2.
• AAE_ID — Foreign key to OKC_ACTION_ATTRIBUTES_B, associating the supplied value with an action attribute where applicable.
• DNZ_CHR_ID — Denormalized contract/characteristic identifier supporting contract-level query and reporting without traversing condition structures.
• VALUE — The actual parameter value passed to the function in the condition line; the core payload of each row.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework to detect concurrent updates.
• SEEDED_FLAG — Indicates whether the row is Oracle-seeded (delivered) versus customer-defined.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group access control.
• APPLICATION_ID — Identifies the owning application for the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns capturing audit and user context.
• ZD_EDITION_NAME — Editioning column supporting online patching under the 12.2.x AD/TXK editioning architecture; appears in both unique indexes U1 and U2.

The business-key candidates are the unique indexes OKC_FUNCTION_EXPR_PARAMS_U1 (ID, ZD_EDITION_NAME) and OKC_FUNCTION_EXPR_PARAMS_U2 (CNL_ID, PDP_ID, ZD_EDITION_NAME), with U2 representing the natural composite that uniquely locates a parameter within a condition line.

Common Use Cases and Queries

Typical uses include diagnosing why a contract condition rule or clause validation failed, auditing the parameter values that drive contract terms, and extracting rule configurations for reporting or migration.

• Retrieving all parameters for a condition line:

  SELECT p.id, p.pdp_id, p.aae_id, p.value
  FROM   okc.okc_function_expr_params p
  WHERE  p.cnl_id = :cnl_id;

• Resolving the function signature by joining to process definition parameters:

  SELECT p.value, d.parameter_name
  FROM   okc.okc_function_expr_params p,
         okc.okc_process_def_parms_b d
  WHERE  p.pdp_id = d.id
  AND    p.cnl_id = :cnl_id;

• Reporting seeded versus customer-defined parameter usage via SEEDED_FLAG, and filtering by SECURITY_GROUP_ID for restricted access.
• Contract-level extraction using DNZ_CHR_ID to report all parameters affecting a given contract without traversing condition lines.

Related Objects

The following objects are most significant in relation to OKC_FUNCTION_EXPR_PARAMS, based on documented foreign keys and primary-key relationships.

• OKC_CONDITION_LINES_B — Join on OKC_FUNCTION_EXPR_PARAMS.CNL_ID = OKC_CONDITION_LINES_B.ID; the parent condition line owning the function invocation.
• OKC_PROCESS_DEF_PARMS_B — Join on OKC_FUNCTION_EXPR_PARAMS.PDP_ID = OKC_PROCESS_DEF_PARMS_B.ID; defines the expected parameter.
• OKC_ACTION_ATTRIBUTES_B — Join on OKC_FUNCTION_EXPR_PARAMS.AAE_ID = OKC_ACTION_ATTRIBUTES_B.ID; supplies the action-attribute context.
• FND_SECURITY_GROUPS — Join on OKC_FUNCTION_EXPR_PARAMS.SECURITY_GROUP_ID for access-control filtering.
• OKC_FUNCTION_EXPR_PARAMS_PK / U1 / U2 — Primary and unique constraints enforcing row identity and natural-key uniqueness.