Search Results okc_subject_groups_pk

Overview

OKC_SUBJECT_GROUPS is a reference and cross-reference table within the OKC (Contracts Core) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to allow contract-related subjects to be organized hierarchically, grouping one subject under another so that clauses, articles, and authored contract content can be categorized, navigated, and retrieved more efficiently. In practical terms, it defines the parent-child edges of the subject hierarchy used by the Contracts authoring and repository features.

The documented heuristic Data Vault classification for this object is standalone. This is best treated as a modeling suggestion rather than a definitive architectural statement: the table carries a two-column composite primary key composed entirely of business codes, and although it holds a foreign key to a security group, it does not sit in the center of a radiating star of dimension references. An analyst building a Data Vault representation could reasonably model SBT_CODE and SBT_CODE_GROUPED as a link between subject hubs, while the descriptive and audit columns behave as satellite attributes.

Key Information Stored

The documented physical schema exposes nine columns. The most significant are:

• SBT_CODE — the subject code being grouped. Together with SBT_CODE_GROUPED it forms the primary key OKC_SUBJECT_GROUPS_PK and the unique index OKC_SUBJECT_GROUPS_U1.
• SBT_CODE_GROUPED — the subject code that acts as the grouping (parent) subject. The pairing of the two code columns is the entire business key of the relationship.
• OBJECT_VERSION_NUMBER — optimistic locking counter maintained by the Oracle Applications framework; it increments on each update and protects concurrent modification of the row.
• CREATED_BY, CREATION_DATE — standard WHO columns recording the application user and timestamp of row insertion.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO columns recording the most recent modification, its author, and the login context.
• SECURITY_GROUP_ID — the multi-org/security grouping discriminator, documented as a foreign key to FND_SECURITY_GROUPS. This aligns the row with the appropriate security group for access control.

No single surrogate key column exists; the identification model is purely code-based, which is characteristic of a reference relationship table rather than a transactional entity. Because both key components are business codes, any integration or data migration must resolve subject codes through the subject definition table before loading.

Common Use Cases and Queries

Typical uses include building hierarchical subject pickers, validating subject groupings during clause authoring, and producing hierarchy reports for contract templates and the clause library. A common pattern retrieves all groupings for a given subject:

• SELECT SBT_CODE, SBT_CODE_GROUPED FROM OKC.OKC_SUBJECT_GROUPS WHERE SBT_CODE = :p_subject_code;
• SELECT SBT_CODE_GROUPED, COUNT(*) FROM OKC.OKC_SUBJECT_GROUPS GROUP BY SBT_CODE_GROUPED ORDER BY 2 DESC; — identifies the most heavily used grouping subjects.
• Recursive queries (CONNECT BY or recursive WITH) traverse the hierarchy from a root grouping subject down through nested groupings.

Reporting use cases include auditing orphaned groupings, detecting cycles in the subject hierarchy, and confirming that every grouping respects the intended security group. Because rows are audited, LAST_UPDATE_DATE supports incremental extraction into a reporting warehouse.

Related Objects

The following objects are the most significant in relation to this table:

• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; join on SECURITY_GROUP_ID = SECURITY_GROUP_ID to resolve the owning security group.
• OKC_SUBJECTS (subject definitions) — the authoritative source of SBT_CODE values; join SBT_CODE and SBT_CODE_GROUPED to subject records to obtain descriptions.
• OKC_SUBJECT_GROUPS_PK / OKC_SUBJECT_GROUPS_U1 — the primary key constraint and unique index enforcing uniqueness of (SBT_CODE, SBT_CODE_GROUPED).
• OKC contract clause and article tables — consume the subject hierarchy when organizing clauses and articles for retrieval.
• OKC Contracts Core APIs — the subject management and authoring APIs that read and maintain these groupings during contract creation.