Search Results okc_condition_occurs




Overview
Explore in AI Chat

Overview

The OKC_CONDITION_OCCURS table is a core transactional entity within the Oracle E-Business Suite Contracts Core (OKC) module. It serves as the detailed implementation table for storing individual occurrences or instances of contractual conditions. Each record in this table represents a specific manifestation of a condition template defined in the master table, OKC_CONDITION_HEADERS_B. This structure allows for the reuse of standardized condition language while capturing the specific details, attributes, and resolved values for each unique application of that condition within a contract or contract line. Its primary role is to manage the granular, operational data that drives condition evaluation, fulfillment tracking, and reporting.

Key Information Stored

The table's central purpose is to link a condition instance to its parent definition and to store instance-specific attributes. The most critical column is the ID, which serves as the primary key for each unique condition occurrence. The CNH_ID is a mandatory foreign key column that links the occurrence directly back to its source condition header in OKC_CONDITION_HEADERS_B. While the full column list is not detailed in the provided metadata, typical data stored in such an occurrence table includes sequence numbers for ordering, effective dates (start and end), status flags (e.g., ACTIVE, SATISFIED), and attributes that personalize the generic condition text for the specific contract party, item, or geography. It acts as the child record where condition parameters are concretely resolved.

Common Use Cases and Queries

This table is central to queries that audit condition fulfillment or generate deliverables based on contract terms. A common reporting use case involves listing all active conditions for a specific contract, joining from the contract header through the condition headers to their occurrences. For performance or compliance audits, analysts may query occurrences where conditions have been met or have expired within a date range. Technical integrations often query this table to determine which actions or time-based events are triggered by a specific condition instance. A fundamental SQL pattern retrieves the occurrence details alongside the parent condition text:

  • SELECT och.condition_text, oco.* FROM okc_condition_occurs oco, okc_condition_headers_b och WHERE oco.cnh_id = och.id AND och.khr_id = :contract_id;

Related Objects

The OKC_CONDITION_OCCURS table sits at a key junction in the Contracts Core data model, with defined relationships to several other important tables.

  • Parent Reference (Foreign Key): It is a direct child of OKC_CONDITION_HEADERS_B via the column CNH_ID. Every condition occurrence must reference a valid condition header.
  • Child References (Primary Key Referenced): Its primary key (ID, stored in the column COE_ID in child tables) is referenced by two key transactional tables:
    • OKC_ACTION_ATT_VALS: Stores attribute values for actions associated with this specific condition occurrence.
    • OKC_RESOLVED_TIMEVALUES: Stores calculated date/time values that have been resolved for time-based conditions linked to this occurrence.

This relationship structure confirms that OKC_CONDITION_OCCURS is the central instance table from which specific action attributes and resolved schedule dates are derived.