Search Results okc_subject_groups_u1

Overview

OKC.OKC_SUBJECT_GROUPS is a reference and classification table in the Oracle E-Business Suite Contracts (OKC) schema. It provides the mechanism by which contract articles and standard articles are organized by subject, and it permits those subjects to be arranged hierarchically so that users can more easily locate and manage articles across a contract repository. The subject codes themselves are defined in the FND_LOOKUPS reference data, while OKC_SUBJECT_GROUPS records the relationships between subjects and the subjects that group them. The table is classified as VALID and is maintained under the OKC.OKC_SUBJECT_GROUPS FND Design Data designation, residing in the APPS_TS_TX_DATA tablespace with a PCT Free of 10.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone. It does not carry a dependent link relationship to another OKC business entity; instead it functions as a self-referencing grouping construct keyed on subject codes. Modelers should therefore treat it as a reference hierarchy rather than as a transactional hub or link.

Key Information Stored

The table contains nine documented columns. The most significant are the two that form the composite primary key and the unique business key:

• SBT_CODE (VARCHAR2(30)) — the subject code being grouped; this is the subject defined in FND_LOOKUPS.
• SBT_CODE_GROUPED (VARCHAR2(30)) — the subject code of the grouping (parent) subject. The column comment describes it as a surrogate key used for primary unique identifiers.
• OBJECT_VERSION_NUMBER (NUMBER) — sequential number initialized to 1 on insert and incremented on update; used by the public APIs to detect concurrent modifications.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who columns that record audit and user attribution.
• SECURITY_GROUP_ID (NUMBER) — used in hosted environments to isolate data by security group; it references FND_SECURITY_GROUPS.

The unique index OKC_SUBJECT_GROUPS_U1, defined on (SBT_CODE, SBT_CODE_GROUPED) in the APPS_TS_TX_IDX tablespace, enforces the business-key candidate, while OKC_SUBJECT_GROUPS_PK is the composite primary key over the same two columns. No other unique indexes are documented.

Common Use Cases and Queries

The primary use case is resolving the hierarchical grouping of article subjects for display and navigation. A typical query lists each subject alongside its grouping subject:

• SELECT SBT_CODE, SBT_CODE_GROUPED FROM OKC.OKC_SUBJECT_GROUPS ORDER BY SBT_CODE_GROUPED, SBT_CODE;
• Joining to FND_LOOKUPS on the subject codes to obtain the descriptive meaning of each subject for reporting.
• Filtering by SECURITY_GROUP_ID in hosted deployments to restrict results to the caller's security group.
• Extracting the full nine-column record using the documented query text, which selects SBT_CODE, SBT_CODE_GROUPED, OBJECT_VERSION_NUMBER and the Who and security columns.

Reporting scenarios include generating a subject hierarchy tree for the Contracts authoring UI, auditing which subjects have been grouped and by whom, and exporting subject classifications to downstream reporting or data warehouse layers.

Related Objects

The most significant related objects, based on the documented dependencies and FK structure, are:

• OKC.OKC_SUBJECT_GROUPS# — the underlying editioning object that supports the table.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for hosted environment data isolation.
• OKC_K_ARTICLES_B — contract articles that are categorized by subject through this grouping data.
• OKC_STD_ARTICLES_B — standard articles that likewise use subject categorization.
• FND_LOOKUPS — the reference source in which the article subject codes are defined.

No database objects are referenced by OKC_SUBJECT_GROUPS other than through its foreign key to FND_SECURITY_GROUPS; all other associations are application-level rather than enforced constraints.