Results for “okc_subclass_roles”

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

Overview

OKC_SUBCLASS_ROLES is a Contracts Core (OKC) foundation table in Oracle E-Business Suite 12.1.1 and 12.2.2. It associates a contract subclass with a role, forming the bridge that determines which Oracle user roles are permitted to act within a given subclass. In functional terms, the table answers the question: "For this type of contract document (subclass), which roles are valid participants?" This metadata is consulted when the Contracts Authoring and Contracts Repository modules resolve default role participation, responsibility-based access, and clause or line-level authorization behavior.

From a Data Vault modeling perspective, the mined heuristic classifies OKC_SUBCLASS_ROLES as hub-leaning. In practice, this reflects that the table carries its own surrogate identity (ID) and participates as the parent of two downstream reference tables (OKC_LINE_STYLE_ROLES and OKC_RG_ROLE_DEFS), which reference it via the SRE_ID column. A Data Vault implementation might therefore treat this as a lightweight hub or link rather than a pure satellite, since it consolidates the relationship between subclass and role as an addressable entity.

Key Information Stored

The table exposes 14 documented physical columns. The most significant are:

• ID — surrogate primary key defined by OKC_SUBCLASS_ROLES_PK. Referenced by child tables as SRE_ID.
• SCS_CODE — the subclass code; foreign key to OKC_SUBCLASSES_B.
• RLE_CODE — the role code associated with the subclass.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J stack.
• START_DATE / END_DATE — effective dating for the role-subclass association.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enabling multi-tenant or responsibility-scoped visibility.
• ACCESS_LEVEL — controls the degree of authority the role holds within the subclass.
• Standard WHO columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• ZD_EDITION_NAME — editioning column introduced for online patching in 12.2.

Two unique indexes act as business-key candidates. OKC_SUBCLASS_ROLES_U1 covers (ID, ZD_EDITION_NAME), while OKC_SUBCLASS_ROLES_U2 covers (SCS_CODE, RLE_CODE, ZD_EDITION_NAME) — confirming that a given subclass may be paired with a given role only once per edition.

Common Use Cases and Queries

Typical reporting scenarios include auditing which roles are configured for a subclass, validating that a role is eligible before assigning a contract line style, and reconciling role definitions against line styles for a given subclass.

SELECT scs_code, rle_code, start_date, end_date, access_level
FROM   okc_subclass_roles
WHERE  sysdate BETWEEN start_date AND NVL(end_date, sysdate);

SELECT scr.id, scr.scs_code, scr.rle_code
FROM   okc_subclass_roles scr,
       okc_line_style_roles lsr
WHERE  lsr.sre_id = scr.id
AND    scr.scs_code = :subclass;

Common queries also join to OKC_SUBCLASSES_B to resolve subclass names and to FND_SECURITY_GROUPS to scope results to the correct operating unit.

Related Objects

• OKC_SUBCLASSES_B — parent of SCS_CODE; supplies subclass definitions.
• OKC_LINE_STYLE_ROLES — references SRE_ID; holds line-style level role assignments.
• OKC_RG_ROLE_DEFS — references SRE_ID; holds role group role definitions.
• FND_SECURITY_GROUPS — parent of SECURITY_GROUP_ID; drives multi-org security filtering.
• OKC_SUBCLASS_ROLES_PK — primary key constraint on ID.