Search Results okc_rule_groups_bh_u1

Overview

The OKC.OKC_RULE_GROUPS_BH table is the history (audit) table for the base entity OKC_RULE_GROUPS_B within the Oracle Contracts (OKC) schema. It stores versioned snapshots of rule group records, where each row represents a specific major version of a contract rule group. Rule groups are the containers that organize rule definitions applied to a contract or contract line, and the history table preserves the state of these groups across contract versioning cycles.

The table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, following the standard transactional data storage convention in Oracle EBS 12.1.1 and 12.2.2. The heuristic Data Vault classification mined from the foreign key structure is standalone. As a modeling suggestion, this reflects the fact that the table does not depend on additional parent entities through enforced foreign keys beyond a security grouping reference; it is best understood as a versioned satellite attached to the contract versioning framework rather than a conventional hub or link.

Key Information Stored

The table carries thirty-two documented columns. The most significant are:

• ID — Numeric primary key column, part of the composite primary key OKC_RULE_GROUPS_BH_PK and of the unique index OKC_RULE_GROUPS_BH_U1.
• MAJOR_VERSION — The contract version associated with this history record; the second component of both the primary key and the unique index.
• RGD_CODE — Rule groups code identifying the group.
• CHR_ID — Identifier of the contract associated with the rule group.
• CLE_ID — Identifier of the contract line to which the rule group belongs.
• DNZ_CHR_ID — Denormalized contract identifier maintained for performance; indexed by the non-unique index OKC_RULE_GROUPS_BH_N1.
• PARENT_RGP_ID — Identifier of the parent rule group, supporting hierarchical (parent/child) rule group structures.
• SAT_CODE — Standard Article Set code used for formatting standard article sets.
• RGP_TYPE — Rule group type classification.
• OBJECT_VERSION_NUMBER — Concurrency-control counter set to 1 on insert and incremented on update, used by APIs to verify the current record.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing row-level security partitioning.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — Standard Who audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns.

The surrogate primary key is the composite (ID, MAJOR_VERSION). The unique index OKC_RULE_GROUPS_BH_U1 on the same columns is the documented business-key candidate, while OKC_RULE_GROUPS_BH_N1 on DNZ_CHR_ID provides the non-unique access path used by contract-oriented queries.

Common Use Cases and Queries

Because this is a history table, primary use cases involve version comparison, audit reconstruction, and reporting on rule group changes across contract versions.

• Retrieve all versions of a rule group: SELECT * FROM OKC.OKC_RULE_GROUPS_BH WHERE ID = :p_id ORDER BY MAJOR_VERSION;
• Fetch the latest version of a rule group: query the history table filtering on the maximum MAJOR_VERSION for a given ID.
• List rule groups for a contract: SELECT * FROM OKC.OKC_RULE_GROUPS_BH WHERE DNZ_CHR_ID = :p_chr_id ORDER BY RGD_CODE, MAJOR_VERSION; — this benefits from index OKC_RULE_GROUPS_BH_N1.
• Reconstruct rule group hierarchies: self-join on PARENT_RGP_ID to walk parent/child relationships within a single version.
• Audit historical changes: use ID, MAJOR_VERSION, and the Who columns to identify who changed rule group definitions and when.
• Contract line level reporting: filter by CLE_ID to report rule groups tied to specific lines.

Related Objects

The table participates in a small but well-defined dependency set:

• OKC.OKC_RULE_GROUPS_B — the base (non-history) table for which OKC_RULE_GROUPS_BH stores the historical versions.
• FND_SECURITY_GROUPS — referenced by the SECURITY_GROUP_ID foreign key to partition rows by security group.
• OKC_K_HEADERS — contract headers joined via CHR_ID / DNZ_CHR_ID.
• OKC_K_LINES — contract lines joined via CLE_ID.
• OKC_RULE_GROUPS_BH itself — self-referenced through PARENT_RGP_ID for hierarchy queries.
• OKC_RULE_GROUPS_TL / associated rule group definition tables — related entities in the rule group model.
• Contract APIs and concurrent programs that version contracts and populate this history table during the versioning process.