Results for “okc_condition_headers_bh”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKC_CONDITION_HEADERS_BH is the history (audit) table for OKC_CONDITION_HEADERS_B in the Oracle Contracts Core (OKC) module. It belongs to the E-Business Suite ETRM (Enterprise Trading and Risk Management) data model and is registered in the OKC schema as a VALID table. In Oracle EBS 12.1.1 and 12.2.2, the "_BH" suffix denotes a shadow or history table that preserves prior versions of records from its base table, OKC_CONDITION_HEADERS_B. The base table holds the header-level definitions of contract conditions — the clauses and terms that govern pricing, commitments, and obligations on a contract or contract template. The _BH table captures superseded versions of those headers whenever a condition header is updated, so that historical states remain queryable even after the live row is overwritten.

The documented ETRM metadata classifies this object, through a heuristic mined from its foreign-key structure, as standalone, meaning it has no strongly inferred Data Vault hub, link, or satellite role from FK topology alone. Modeling-wise, the composite primary key of (ID, MAJOR_VERSION) with associated descriptive columns suggests the table behaves as a versioned satellite, where ID represents the business object and MAJOR_VERSION the version sequence. This classification should be treated as a suggestion rather than a definitive model.

Key Information Stored

The table's 44 documented columns capture the identity, versioning, and descriptive attributes of condition headers. The most significant include:

Fifteen ATTRIBUTE1–ATTRIBUTE15 columns provide the standard EBS extensibility (DDF) layer, and SEEDED_FLAG identifies Oracle-seeded records.

Common Use Cases and Queries

Because this is a history table, its principal use is auditing and point-in-time reconstruction of condition headers. Typical queries include retrieving all versions of a header:

SELECT id, major_version, name, cnh_type, date_active, date_inactive, last_update_date
FROM   okc.okc_condition_headers_bh
WHERE  id = :header_id
ORDER BY major_version DESC;

Comparing a current base row against its most recent history version joins OKC_CONDITION_HEADERS_BH to OKC_CONDITION_HEADERS_B on ID and MAJOR_VERSION. Reporting scenarios include change-tracking for compliance, reconstructing the terms in force on a given contract date via the DATE_ACTIVE/DATE_INACTIVE window, and reconciling template-versus-contract condition drift (TEMPLATE_YN). Security-filtered extracts should join SECURITY_GROUP_ID to FND_SECURITY_GROUPS when row-level access must be respected.

Related Objects

The most significant related objects are:

  • OKC_CONDITION_HEADERS_B — The base (current) table from which this history table derives; joined on ID and MAJOR_VERSION.
  • OKC_CONDITION_HEADERS_BH_PK / OKC_CONDITION_HEADERS_BH_U1 — Primary key and unique index on ID, MAJOR_VERSION.
  • CS_COUNTER_GROUPS — Referenced by COUNTER_GROUP_ID.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID.
  • OKC_CONDITION_LINES_B / _BH — Line-level conditions that belong to these headers.
  • OKC_CONTRACT_HEADERS — Owning contract correlated through ACN_ID or DNZ_CHR_ID.

These relationships make the table a supporting artifact for contract-condition audit and reporting, rather than a transactional driver in the OKC data model.