Search Results evaluate_date_condition




Overview
Explore in AI Chat

Overview

The APPS.OKC_CONDITION_EVAL_PUB package body is the public evaluation layer of the Oracle E-Business Suite Contracts (OKC) condition engine. Its business purpose is to determine whether the conditions attached to a contract or plan are satisfied at a given point in time, and to return the resulting outcomes back to the calling application. In Oracle EBS 12.1.1 and 12.2.2, the OKC schema supports the Terms and Conditions authoring and enforcement model used by Service Contracts, Project Contracts, and related modules. Conditions are authored on condition headers and evaluated at runtime to drive actions such as billing, renewal, escalation, or workflow branch selection. The public package exists so that external callers — forms, concurrent programs, workflows, and integrations — do not call the private engine directly; instead they invoke this PUB wrapper, which delegates the actual evaluation logic to OKC_CONDITION_EVAL_PVT.

Key Procedures and Functions

The package exposes the following documented procedures:

  • EVALUATE_PLAN_CONDITION — Evaluates the conditions attached to a specified plan. Per the source excerpt, it accepts a condition header identifier (p_cnh_id), an API version, and an initialization flag for the message list, and returns a standard return status together with an outcome table (x_sync_outcome_tab) that records the conditions found true. The procedure applies the standard OKC API pattern: START_ACTIVITY, delegation to the private engine, and END_ACTIVITY.
  • EVALUATE_CONDITION — A general entry point for evaluating a single condition or condition set. The internal API name constant in the source is EVALUATE_CONDITION, confirming this is the central routing procedure within the package body.
  • EVALUATE_DATE_CONDITION — The procedure targeted by the search term evaluate_date_condition. It evaluates date-based conditions, that is, conditions whose truth depends on a comparison against a date (effective, expiry, or offset windows). This is the routine invoked when a caller needs to know whether a date-typed condition currently holds.

Three further callers in the EBS code base reference this package, confirming it is a stable public integration point rather than an internal-only wrapper.

Tables Accessed

The documented tables referenced through APPS synonyms are:

  • OKC_CONDITION_HEADERS_B — The base table holding condition header definitions. The package reads header rows to resolve the condition identified by p_cnh_id and to obtain the attributes needed for evaluation.
  • OKC_ACTIONS_B — The base table holding the actions that result from satisfied conditions. Reading this table allows the evaluation engine to associate true conditions with the actions that must subsequently be executed.

No inserts or updates to these tables are implied by the metadata; the package is a read-oriented evaluation component whose output is returned in memory through the outcome table type.

Usage Notes

In Oracle EBS 12.1.1 and 12.2.2, this package is typically invoked from the Contracts forms and from concurrent or workflow-driven processing that must decide whether a contract's conditions are met. Because it targets the public API classification, it is also the appropriate entry point for custom code and extensions that need condition evaluation. Callers should honor the standard OKC API conventions: initialize the message list, check x_return_status against OKC_API.G_RET_STS_SUCCESS, and inspect x_msg_count and x_msg_data for diagnostics before consuming the returned outcome table. Direct calls to OKC_CONDITION_EVAL_PVT are discouraged, as the PUB layer supplies the savepoint, compatibility checking, and message handling required for correct transaction behavior.