Results for “okc_subclass_rg_defs”

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

Overview

OKC_SUBCLASS_RG_DEFS is a Contracts Core (OKC) configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2 that associates a contract subclass with a rule group definition. In the Oracle Contracts architecture, subclasses represent the specific document types and business classifications a contract can assume (for example, a purchase agreement, a sales contract, or a lease), while rule groups define groups of rules that govern behavior such as clause inclusion, generation, and validation during the contract lifecycle. This table is the bridging construct that determines which rule groups apply to a given subclass.

The table is owned by the OKC schema and is documented as VALID in ETRM 12.2.2, comprising 14 physical columns. It participates in the standard Oracle EBS multi-tenant security model through SECURITY_GROUP_ID and ACCESS_LEVEL, and in the 12.2.2 editioning model through ZD_EDITION_NAME. Heuristically, the mined foreign-key structure classifies this table as hub-leaning in a Data Vault sense, suggesting it can serve as a central reference anchor around which operational rule definitions orbit; implementers modeling Contracts data for warehousing may treat it as a hub rather than a pure link or satellite.

Key Information Stored

The primary key is OKC_SUBCLASS_RG_DEFS_PK, defined on the surrogate ID column. Two unique indexes act as business-key candidates: OKC_SUBCLASS_RG_DEFS_U1 (ID, ZD_EDITION_NAME) and OKC_SUBCLASS_RG_DEFS_U2 (SCS_CODE, RGD_CODE, ZD_EDITION_NAME), the latter indicating that a subclass-to-rule-group-code pairing is unique within an edition.

• ID — surrogate primary key, the FK target for dependent rule tables.
• SCS_CODE — foreign key to OKC_SUBCLASSES_B; identifies the subclass being configured.
• RGD_CODE — the rule group definition code assigned to the subclass.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Applications framework.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — standard WHO audit columns.
• START_DATE / END_DATE — date-range effectiveness controlling when the subclass-to-rule-group association is active.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS, enforcing operating-unit data isolation.
• ACCESS_LEVEL — row-level access control indicator.
• ZD_EDITION_NAME — editioning column used in 12.2 online patching.

Common Use Cases and Queries

Typical uses include auditing which rule groups are attached to a subclass, verifying effective-dated configuration after upgrade or patch, and joining to rule and role tables for completeness reporting.

SELECT d.id, d.scs_code, d.rgd_code, s.name, d.start_date, d.end_date
FROM   okc.okc_subclass_rg_defs d,
       okc.okc_subclasses_b s
WHERE  d.scs_code = s.scs_code
AND    SYSDATE BETWEEN NVL(d.start_date, SYSDATE - 1)
                   AND NVL(d.end_date, SYSDATE + 1);

A second common pattern returns rule rows governed by each subclass through the SRD_ID relationships:

SELECT d.scs_code, g.srd_id, r.role_code
FROM   okc.okc_subclass_rg_defs d,
       okc.okc_lse_rule_groups g,
       okc.okc_rg_role_defs r
WHERE  g.srd_id = d.id
AND    r.srd_id = d.id;

Reporting use cases include rule-coverage analysis (subclasses lacking any rule group) and impact analysis before changing a shared rule group definition.

Related Objects

• OKC_SUBCLASSES_B — parent subclass table, joined on SCS_CODE.
• OKC_LSE_RULE_GROUPS — rule group headers referencing this table via SRD_ID.
• OKC_RG_ROLE_DEFS — role definitions within rule groups, FK SRD_ID.
• OKL_OPT_RULES — lease option rules referencing this table via SRD_ID_FOR.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for access control.

These relationships position OKC_SUBCLASS_RG_DEFS as the configuration pivot linking contract subclasses to the rule and role definitions that drive Contracts behavior.