Search Results okc_condition_headers_b




Overview
Explore in AI Chat

Overview

The OKC_CONDITION_HEADERS_B table is a core data object within the Oracle E-Business Suite (EBS) Contracts Core (OKC) module. It serves as the primary repository for the definition of conditions, which are fundamental business rules governing the execution, performance, and administration of contracts. Conditions can dictate actions, outcomes, or validations based on specific criteria, such as dates, events, or performance metrics. This table stores the header-level or master definition of a condition, establishing its identity, type, and basic control attributes. Its role is central to the contract's operational logic, enabling automated workflows and compliance tracking within the EBS framework.

Key Information Stored

The table's primary key is the ID column, a unique system-generated identifier for each condition definition. While the provided metadata does not list all columns, the foreign key relationships indicate other critical fields. The ACN_ID column links the condition to a specific action definition in the OKC_ACTIONS_B table. This establishes the "if" part of a conditional rule. The table structure logically separates the condition's header (definition and control attributes stored here) from its detailed lines (specific criteria stored in OKC_CONDITION_LINES_B) and its associated outcomes (stored in OKC_OUTCOMES_B). This design allows for complex, multi-line conditions that trigger one or more defined outcomes.

Common Use Cases and Queries

This table is primarily accessed for configuration analysis, data integrity checks, and troubleshooting contract business rules. Common scenarios include identifying all conditions linked to a specific contract action or validating the setup of conditional logic. A typical query might join the condition header to its lines and outcomes to understand a complete rule.

  • Sample Query to List Condition Details:
    SELECT cnh.id AS condition_id, cnh.acn_id AS action_id, act.name AS action_name,
    COUNT(cln.id) AS number_of_criteria_lines
    FROM okc_condition_headers_b cnh
    JOIN okc_actions_b act ON act.id = cnh.acn_id
    LEFT JOIN okc_condition_lines_b cln ON cln.cnh_id = cnh.id
    GROUP BY cnh.id, cnh.acn_id, act.name;
  • Reporting Use Case: Generating a master list of all defined conditions within the system, their associated actions, and the number of criteria lines, which is essential for auditing and system documentation.

Related Objects

As indicated by the foreign keys, OKC_CONDITION_HEADERS_B is a pivotal table with several key dependencies. It is the parent table for condition details (OKC_CONDITION_LINES_B), outcomes (OKC_OUTCOMES_B), and time-based values (OKC_TIMEVALUES_B, OKC_TIMEVALUES). It is also referenced by the CSC_PLAN_LINES table from the Customer Care module, showing integration points for service plans. Crucially, it is a child table to OKC_ACTIONS_B, meaning every condition header must be associated with a defined action. This network of relationships underscores its position at the center of the contract's conditional rule engine.