Search Results evaluate_plan_condition

Overview

OKC_CONDITION_EVAL_PVT is a private PL/SQL package in the APPS schema that implements the internal evaluation engine for contract conditions within Oracle E-Business Oracle Contracts (OKC) and the associated Enterprise Trading and Relationship Management (ETRM) modules. Contract conditions represent configurable business rules attached to contracts, contract templates, and process definitions. These rules determine whether contractual terms have been satisfied, whether entitlements or obligations should be triggered, and what downstream actions the system should perform. The package is classified as a Private API (PVT), meaning it is intended for internal consumption by Oracle's own public APIs and concurrent programs rather than by customer extensions. It encapsulates the low-level logic that interprets condition expressions, computes date-based qualification, and produces the outcome records that drive subsequent contract processing.

Key Procedures and Functions

The documented interface exposes four program units, three of which are named in the ETRM metadata:

• EVALUATE_PLAN_CONDITION — Evaluates the set of conditions associated with a contract plan or process definition, iterating over the condition headers and lines to determine which conditions pass or fail within the plan context.
• EVALUATE_CONDITION — Performs the core evaluation of an individual condition, applying the condition's expression against the applicable data, and recording the resulting outcome and arguments.
• EVALUATE_DATE_CONDITION — Specializes evaluation for date-driven conditions, comparing contract dates, milestones, or counter readings against the configured qualification criteria to determine whether a date-sensitive condition has been met.
• The metadata additionally lists a fourth unit; consistent with the naming of the above, it belongs to the same condition evaluation family and is invoked internally by the entry points above.

None of these units are intended for direct invocation by external code; they are called through the public wrapper OKC_CONDITION_EVAL_PUB and from contract processing flows.

Tables Accessed

The package reads and writes a broad set of OKC and shared ETRM entities, accessed through APPS synonyms:

• OKC_CONDITION_HEADERS_B, OKC_CONDITION_LINES_B, and OKC_CONDITION_OCCURS — the condition definition and occurrence data being evaluated.
• OKC_PROCESS_DEFS_B and OKC_PROCESS_DEF_PARMS_B — process definitions and their parameters that supply the execution context.
• OKC_OUTCOMES_B and OKC_OUTCOME_ARGUMENTS — where evaluation results and their argument values are persisted.
• OKC_ACTIONS_B, OKC_ACTION_ATTRIBUTES_B, and OKC_ACTION_ATT_VALS — action records and attribute values triggered by satisfied conditions.
• OKC_FUNCTION_EXPR_PARAMS — parameters of function expressions used inside condition rules.
• CSI_COUNTER_READINGS and JTF_TASKS_B — external inputs (installed base counter data and task records) referenced during evaluation.
• DBMS_AQ and DBMS_SQL — Oracle-supplied packages used for enqueueing and dynamic SQL.

Usage Notes

OKC_CONDITION_EVAL_PVT is invoked indirectly at runtime. Its principal caller is OKC_CONDITION_EVAL_PUB, the public API through which contract processing, forms, and concurrent programs request condition evaluation. The Customer Care (CSC) package CSC_ACTION_ASSEMBLER_PVT also references it, indicating integration with service and task action assembly. The package is recursively referenced by itself and depends on a large family of OKC private APIs (OKC_AAE_PVT, OKC_AAL_PVT, OKC_AAV_PVT, OKC_ACN_PVT, OKC_API, OKC_AQ_PVT, OKC_CNH_PVT, OKC_CNL_PVT, OKC_COE_PVT, OKC_FEP_PVT, OKC_PDF_PVT, OKC_PDP_PVT). Customers should not call it directly; extensions should use the corresponding public API so that validation, security, and outcome propagation are preserved. Behavior is consistent across EBS 12.1.1 and 12.2.2.