Search Results okc_rule_groups_bh_pk

Overview

OKC_RULE_GROUPS_BH is a history (audit) table within the OKC — Contracts Core product of Oracle E-Business Suite, owning schema OKC. It stores historical major versions of rows held in the corresponding base table OKC_RULE_GROUPS_B, which is the base table for rule groups used by Oracle Contracts to organize and sequence contract terms, clauses, and rule hierarchies. Rule groups act as containers that group related rules and terms together so that they can be applied, versioned, and evaluated consistently across a contract template or authored contract.

Because OKC_RULE_GROUPS_BH retains prior major versions keyed separately from the current version, it supports version auditing, point-in-time reconstruction, and comparison of rule-group definitions across revisions. From a Data Vault perspective, the metadata’s heuristic classification lists this object as standalone, with no inbound or outbound foreign keys beyond a security-group reference. A reasonable modeling suggestion is to treat it as a satellite-like history structure: its natural grain is the rule-group identifier combined with a major version number, and it describes the changing descriptive attributes of a rule-group hub.

Key Information Stored

• ID — Surrogate identifier for the rule group; part of the composite primary key OKC_RULE_GROUPS_BH_PK and the unique index OKC_RULE_GROUPS_BH_U1.
• MAJOR_VERSION — The major version number of the rule group; the second component of both the primary key and unique index, and the discriminator that makes this a history table.
• RGD_CODE — The rule-group definition code that identifies the rule group in business terms.
• CHR_ID — Contract or contract-line heritage identifier used to associate the rule group with its owning contract document.
• CLE_ID — Clause or line entity identifier linking the rule group to the clause structure it governs.
• DNZ_CHR_ID — Denormalized contract identifier retained for efficient querying without additional joins.
• PARENT_RGP_ID — Self-referencing parent rule-group identifier, enabling hierarchical nesting of rule groups.
• RGP_TYPE — Classifies the rule group by type, which determines how its member rules are evaluated.
• SAT_CODE — Status or state code reflecting the lifecycle position of the versioned row.
• OBJECT_VERSION_NUMBER — Optimistic-locking counter used by the Oracle Forms/ODF framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS who-columns providing audit provenance for each historical row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard DFF (descriptive flexfield) columns for customer-defined extensions.
• SECURITY_GROUP_ID — References FND_SECURITY_GROUPS to support multi-tenant or security-group isolation.

Common Use Cases and Queries

Typical uses include version history reporting for rule groups, auditing changes to rule-group definitions, and reconstructing the state of a contract’s rule structure as of a given major version. Queries commonly join the history table back to the current base table on ID to compare current versus prior definitions, or join across CHR_ID/DNZ_CHR_ID to obtain contract context.

• List all historical versions for a rule group: SELECT id, major_version, rgd_code, rgp_type, last_update_date FROM okc.okc_rule_groups_bh WHERE id = :id ORDER BY major_version;
• Compare current vs. historical rows: join OKC_RULE_GROUPS_B to OKC_RULE_GROUPS_BH on ID where the base row’s version exceeds the historical version.
• Audit who changed a rule group: filter on LAST_UPDATED_BY and CREATION_DATE ranges.
• Reconstruct hierarchy: recursive query over PARENT_RGP_ID within a single MAJOR_VERSION.
• Security-scoped reporting: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to restrict output by responsibility/operating unit.

Related Objects

• OKC_RULE_GROUPS_B — The base table for which this object is the history table; joined on ID/MAJOR_VERSION.
• OKC_RULE_GROUPS_TL — Translation table for rule-group names/descriptions, joined on ID.
• OKC_RULES_B and OKC_RULES_BH — Rules belonging to a rule group, joined via rule-group identifier.
• OKC_TERMS_* — Contract terms and clause structures linked through CHR_ID/CLE_ID/DNZ_CHR_ID.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for security-group isolation.
• OKC_CONTRACTS_ALL / OKC_CONTRACT_HEADERS — Provide contract context via DNZ_CHR_ID.
• OKC_RULE_GROUPS_VL / OKC_RULE_GROUPS_V — Views exposing rule-group definitions for reporting.