Search Results okc_condition_lines_b




Overview
Explore in AI Chat

Overview

The OKC_CONDITION_LINES_B table is a core data object within the Oracle E-Business Suite (EBS) Contracts Core module (OKC). It functions as the detailed repository for the boolean expressions that define specific conditions within a contract. In the context of the Contracts application, a Condition Header (stored in OKC_CONDITION_HEADERS_B) establishes a high-level rule or requirement. This table stores the individual lines that combine to form the complete logical expression (e.g., using AND, OR operators) that further qualifies and precisely defines the circumstances under which the header condition is applicable or must be evaluated.

Key Information Stored

The table's primary purpose is to store the components of a boolean expression linked to a condition header. While the full column list is not detailed in the provided metadata, the foreign key relationships and primary key reveal critical data elements. The ID column serves as the primary unique identifier for each condition line. The CNH_ID column is a foreign key to OKC_CONDITION_HEADERS_B, linking each line to its parent condition header. The AAE_ID column is a foreign key to OKC_ACTION_ATTRIBUTES_B, indicating a relationship to specific contract action attributes, likely used within the expression logic. Other columns typically found in such structures would store the sequence of the line within the expression, the operator (e.g., 'AND', 'OR'), and references to the operands or values being compared.

Common Use Cases and Queries

This table is central to the runtime evaluation of contract terms and conditions. Common use cases include generating a complete view of all detailed logic for a contract's conditions for auditing or reporting purposes, and supporting the application's engine in determining if a specific condition is met based on transactional data. A typical query would join this table to its header and related attribute tables to reconstruct the full conditional logic. For example:

  • Retrieving Condition Details: SELECT cl.* FROM okc_condition_lines_b cl, okc_condition_headers_b ch WHERE cl.cnh_id = ch.id AND ch.document_id = :p_contract_id ORDER BY cl.cnh_id, cl.seq_number;
  • Analysis of Condition Structure: Reports analyzing the complexity of contract conditions (e.g., number of expression lines per header) would aggregate data from this table grouped by CNH_ID.

Related Objects

As indicated by the foreign keys, OKC_CONDITION_LINES_B has integral relationships with several other core Contracts tables. OKC_CONDITION_HEADERS_B is the direct parent table. OKC_ACTION_ATTRIBUTES_B is referenced, linking condition logic to specific contract actions and their attributes. Furthermore, OKC_FUNCTION_EXPR_PARAMS holds a foreign key (CNL_ID) back to this table, meaning that OKC_CONDITION_LINES_B is a parent table for storing more granular function parameters used within the boolean expressions. This hierarchy underscores its role as a central node in the condition definition data model.