Search Results okc_condition_occurs_v




Overview
Explore in AI Chat

Overview

The Oracle EBS view OKC_CONDITION_OCCURS_V resides in the APPS schema and belongs to the OKC — Contracts Core product family. It is classified in ETRM as a VALID view and is described as a "View for table OKC_CONDITION_OCCURS." Its purpose is to expose the condition occurrence data stored in the base Contracts table through a stable, decoupled interface for reporting, inquiry, and integration purposes. In Oracle EBS 12.1.1 and 12.2.2, contract conditions and their occurrences support the runtime evaluation of business rules attached to contract terms. The view name reflects the functional area: "CONDITION_OCCURS" denotes the point at which a defined contract condition becomes true and active on an actual contract instance.

Underlying Base Objects

The view is defined over a single recorded base object, OKC_CONDITION_OCCURS, referenced through a synonym in the APPS schema. The view text selects from this table using the alias COEB and simply renames ROWID to ROW_ID while passing all other columns through unchanged. This construction follows a common Oracle EBS pattern in which a thin view supplies a business-oriented, read-only projection of a base table. Because the projection is largely one-to-one, the view preserves the base table's cardinality and inheritance of primary key structure. Consuming the view rather than the table shields custom reports from future physical changes, though the documented 12.2.2 metadata does not indicate any column transformation beyond the ROWID alias.

Key Columns

  • ROW_ID — Maps to the base table ROWID, providing the physical address of the occurrence record for direct access or diagnostics.
  • ID — The primary surrogate key uniquely identifying each condition occurrence.
  • CNH_ID — The contract header foreign key linking the occurrence to its parent contract (the OKC_CONTRACT_HEADERS identifier). This column is central to joining occurrence data back to the contract.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications Framework to detect concurrent modification during update transactions.
  • DATETIME — The effective date and time the condition occurrence is recorded, used to evaluate temporal ordering of condition evaluation.
  • CREATED_BY, CREATION_DATE — Who-created audit attributes populated automatically at row insertion.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Who-updated audit attributes capturing the most recent change and the login session that performed it.

Common Use Cases and Queries

Typical use cases include contract condition auditing, occurrence timeline reporting, and diagnostic joins against contract headers. Analysts frequently join this view to OKC_CONTRACT_HEADERS through CNH_ID to render occurrences alongside the contract number and operating organization. A representative query is:

SELECT o.ID, o.CNH_ID, o.DATETIME, o.LAST_UPDATE_DATE
FROM   APPS.OKC_CONDITION_OCCURS_V o
WHERE  o.CNH_ID = :p_contract_id
ORDER BY o.DATETIME;

A second pattern retrieves all occurrences created after a given date for integration extracts:

SELECT o.ID, o.CNH_ID, o.DATETIME
FROM   APPS.OKC_CONDITION_OCCURS_V o
WHERE  o.CREATION_DATE >= TRUNC(SYSDATE) - 7;

Developers should note that the view is read-only in practice; insert and update operations against condition occurrences must target the base table through the supported Contracts APIs rather than the view. Restrictions on DML and the exposure of ROW_ID should be respected when building custom code to ensure upgrade-safe behavior across 12.1.1 and 12.2.2 environments.