Results for “okc_rule_groups_b”

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

Overview

OKC_RULE_GROUPS_B is a core table in the Oracle Contracts (OKC) module of Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. It stores rule groups, which are collections of rules that inform automated processes about a business function within contract authoring and management. Each rule group acts as a logical container that binds individual rules to a contract header, contract line, or a broader organizational context, enabling the Contracts engine to evaluate and enforce business logic during contract creation, approval, and execution.

From a Data Vault modeling perspective, the mined heuristic classification of this table is hub-leaning. It carries a surrogate primary key and multiple foreign-key relationships to parent business entities, which is characteristic of a hub that defines a distinct business concept and links outward to descriptive and dependent satellites. The table is the anchor for rule group identity, while detail tables such as OKC_RULES_B and the DFF extensions hold the descriptive and rule-level attributes.

Key Information Stored

The table contains 31 documented columns. The most significant include:

• ID — The surrogate primary key, enforced by OKC_RULE_GROUPS_B_PK and the unique index OKC_RULE_GROUPS_B_U1. It uniquely identifies each rule group.
• RGD_CODE — A business code identifying the rule group, useful as a natural business-key candidate for lookups and reporting.
• CHR_ID — Foreign key to OKC_K_HEADERS_B, indicating the contract header to which the rule group applies.
• CLE_ID — Foreign key to OKC_K_LINES_B, indicating the contract line context.
• DNZ_CHR_ID — Denormalized contract header identifier used for query performance and context propagation.
• PARENT_RGP_ID — Self-referencing foreign key enabling hierarchical nesting of rule groups.
• SAT_CODE — Classification or status code associated with the rule group.
• RGP_TYPE — The rule group type, characterizing its business function.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data security and access control.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Framework and concurrent programs.
• WHO/audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN track record provenance.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield segments for extensibility.

While ID is the documented surrogate key, RGD_CODE combined with the owning CHR_ID or CLE_ID typically forms the practical business key used by application logic.

Common Use Cases and Queries

Typical usage centers on retrieving the rule groups attached to a contract and the rules they contain. A representative query joining the header context and dependent rules:

• SELECT rg.ID, rg.RGD_CODE, rg.RGP_TYPE, r.RULE_CODE FROM OKC_RULE_GROUPS_B rg, OKC_RULES_B r WHERE rg.ID = r.RGP_ID AND rg.CHR_ID = :contract_header_id;

Hierarchical navigation uses the self-join on PARENT_RGP_ID to render rule group trees. Reporting scenarios include auditing which business functions are governed by rules for a given contract line, validating that mandatory rule groups exist before contract approval, and reconciling security group assignments. Integration points use CHR_ID/CLE_ID to correlate rule groups with contract documents, and DFF queries join to OKL_RULES_DFF and OKS_RULES_DFF for additional descriptive attributes.

Related Objects

OKC_RULE_GROUPS_B is the hub of a rule-grouping network. The most significant related objects are:

• OKC_K_HEADERS_B — joined via OKC_RULE_GROUPS_B.CHR_ID.
• OKC_K_LINES_B — joined via OKC_RULE_GROUPS_B.CLE_ID.
• OKC_RULES_B — child rules referencing RGP_ID.
• OKC_RG_PARTY_ROLES — party role assignments referencing RGP_ID.
• OKC_RULE_GROUPS_B (self) — hierarchy via PARENT_RGP_ID.
• OKL_RULES_DFF and OKS_RULES_DFF — flexfield extensions joined by RGP_ID.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for data security.