Results for “okc_cnl_function_expr_v”

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

Overview

OKC_CNL_FUNCTION_EXPR_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKC — Contracts Core product (Oracle Contracts). The view exposes the function-expression condition lines that Oracle Contracts uses to assemble Boolean rule expressions for contract terms, clauses, and event definitions. Its documented purpose is to serve as a view for the base table OKC_EVENT_DEF_LINES_B, but at the physical level it is defined over the Contracts Core condition-line tables OKC_CONDITION_LINES_B and OKC_CONDITION_LINES_TL, filtered to the condition-line type 'FEX' (function expression).

Because Contracts stores condition logic as ordered, nested lines rather than as free text, the view provides a denormalized, language-aware read model in which each row represents a single expression node together with its sequence position and the logical operator that joins it to its sibling nodes. This makes the view the natural access point for reports, conversions, and integration programs that must reconstruct or audit contract rule definitions without parsing the base tables directly. It is a read-only, non-key-preserved view: there is no DML support, and consumers should treat it strictly as a query surface. The presence of OBJECT_VERSION_NUMBER, CREATED_BY, and the LAST_UPDATE_* columns confirms that the underlying rows are subject to Oracle Applications concurrent-program locking and standard WHO audit tracking.

Underlying Base Objects

The view is defined over two documented base objects:

• OKC_CONDITION_LINES_B — the base (non-translated) condition-line table, aliased CNLB in the view text. It supplies the surrogate primary key, the condition-line header reference (CNH_ID), document/PDF context identifiers, sort sequence, LOGICAL_OPERATOR, the DFF ATTRIBUTE1–15 columns, and all audit columns.
• OKC_CONDITION_LINES_TL — the translated condition-line table, aliased CNLT. It supplies SFWT_FLAG and the language-specific DESCRIPTION.

The two are joined on CNLB.ID = CNLT.ID, with the additional restriction CNLT.LANGUAGE = USERENV('LANG'), which resolves descriptions to the session's current language. The defining predicate CNLB.CNL_TYPE = 'FEX' restricts the result to function-expression lines, excluding other condition-line types stored in the same table. ROWID of the base row is exposed as ROW_ID, allowing precise back-reference to OKC_CONDITION_LINES_B. In a 12.1.1 versus 12.2.2 comparison, the definition and column list are consistent; behavior is driven by the underlying tables, which remain synonymous objects in the APPS schema.

Key Columns

• ROW_ID — ROWID of the underlying OKC_CONDITION_LINES_B row; useful for targeted updates by a controlled API or for diagnostics.
• ID — surrogate primary key of the condition line, and the join key to the translation row.
• LOGICAL_OPERATOR — the operator (for example AND/OR) that combines this expression node with adjacent nodes at the same level in the assembled rule; this is the column returned by searches on "logical_operator".
• CNH_ID — foreign key to the condition header that owns the expression.
• DNZ_CHR_ID / PDF_ID — contract/document context identifiers linking the line to the governing contract or document definition.
• SORTSEQ — evaluation order of the node within its parent expression.
• DESCRIPTION — language-resolved description of the condition line from OKC_CONDITION_LINES_TL.
• SFWT_FLAG — software flag carried from the translated row.
• OBJECT_VERSION_NUMBER — optimistic locking version, essential when the row is subsequently updated through the Contracts API.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — descriptive flexfield segments for customer-defined expression metadata.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include auditing how a contract's function expressions are combined, extracting operator/sequence pairs for migration into another environment, and joining to the condition header to report rule logic per contract. A basic extraction ordered for expression reconstruction:

SELECT l.ID, l.CNH_ID, l.SORTSEQ, l.LOGICAL_OPERATOR, l.DESCRIPTION FROM APPS.OKC_CNL_FUNCTION_EXPR_V l WHERE l.CNH_ID = :p_cnh_id ORDER BY l.SORTSEQ;

To locate all expression nodes using a specific operator:

SELECT l.ID, l.CNH_ID, l.LOGICAL_OPERATOR, l.DESCRIPTION FROM APPS.OKC_CNL_FUNCTION_EXPR_V l WHERE l.LOGICAL_OPERATOR = 'AND' ORDER BY l.CNH_ID, l.SORTSEQ;

To reconcile against the base table and its translation, or to check current version state before an API update:

SELECT l.ROW_ID, l.ID, l.OBJECT_VERSION_NUMBER, l.LAST_UPDATED_BY, l.LAST_UPDATE_DATE FROM APPS.OKC_CNL_FUNCTION_EXPR_V l WHERE l.ID = :p_id;

Because the view restricts to CNL_TYPE = 'FEX' and to the session language, queries should always pass CNH_ID or ID where possible to avoid full scans, and should not attempt DML. For changes, use the supported Oracle Contracts condition APIs against OKC_CONDITION_LINES_B rather than updating through the view.