Search Results okc_rules_bh




Overview
Explore in AI Chat

Overview

OKC_RULES_BH is the history (audit) table for OKC_RULES_B within the OKC – Contracts Core product of Oracle E-Business Suite. The _BH suffix is the standard Oracle EBS convention for a shadow table that preserves prior versions of a base transactional table: whenever a rule row in OKC_RULES_B is updated or deleted, the pre-change image is copied into OKC_RULES_BH, together with an incrementing version stamp. OKC_RULES_B itself stores the rules that govern contract clauses, templates, and related contract objects — for example which standard or non-standard clauses may be combined, which combinations should trigger a warning, and the display ordering of answers. OKC_RULES_BH therefore provides the temporal record of those governance definitions.

Because the table carries both ID and MAJOR_VERSION and no foreign keys to any transactional entity other than a security grouping, the mined Data Vault classification is standalone. A reasonable modeling suggestion is to treat it as a satellite-style version history over the OKC_RULES_B hub, with (ID, MAJOR_VERSION) acting as the effective-dated key.

Key Information Stored

The table is documented with 61 columns. The most significant are:

Common Use Cases and Queries

The primary use case is auditing rule changes over time — determining who changed a contract rule, when, and what the prior definition looked like.

  • Current version lookup: select the highest MAJOR_VERSION per ID.
  • Change history for one rule: SELECT id, major_version, last_updated_by, last_update_date, warn_yn, priority FROM okc_rules_bh WHERE id = :rule_id ORDER BY major_version;
  • Comparison of base versus history: join OKC_RULES_B to OKC_RULES_BH on ID to spot discrepancies.
  • Point-in-time reconstruction: filter on LAST_UPDATE_DATE to see the rule definition in force on a past date.
  • Security-scoped reporting: join to FND_SECURITY_GROUPS via SECURITY_GROUP_ID.

Because the table can grow quickly, reporting queries should always be bounded by ID or a date range and should avoid full scans.

Related Objects

  • OKC_RULES_B – the base table whose prior images this history table stores; join on ID.
  • OKC_RULES_BH_PK / OKC_RULES_BH_U1 – the primary key and unique index over (ID, MAJOR_VERSION).
  • FND_SECURITY_GROUPS – referenced by SECURITY_GROUP_ID, providing data-security grouping.
  • OKC_RULE_GROUPS (via RGP_ID) – the rule-group parent that organizes rules.
  • OKC_TERMS / OKC_TEMPLATES – contract terms and template definitions governed by these rules and linked via DNZ_CHR_ID and template flags.
  • OKC_RULES_TL – translated rule names/descriptions for the corresponding ID.