Search Results okc_subclass_roles

Overview

The OKC_SUBCLASS_ROLES table is a core reference table within the Oracle E-Business Suite Contracts Core (OKC) module. Its primary function is to define and manage the association between a contract line subclass and the specific roles that can be assigned to parties involved in those lines. This table acts as a junction, linking the definition of a subclass (from OKC_SUBCLASSES_B) with applicable role definitions. By establishing these relationships, it enables the Contracts application to enforce valid role assignments based on the business context of a contract line, ensuring data integrity and proper workflow functionality for party management throughout the contract lifecycle.

Key Information Stored

The table's structure is designed to store the essential link between a subclass and a role. While the full column list is not detailed in the provided metadata, the primary and foreign key relationships reveal the critical data points. The primary key column is ID, ensuring each association record is unique. The table holds at least one foreign key column, SCS_CODE, which references the OKC_SUBCLASSES_B table to identify the specific contract line subclass. It also stores a reference to a role definition, which is linked via the SRE_ID column. This SRE_ID is referenced as a foreign key by both the OKC_LINE_STYLE_ROLES and OKC_RG_ROLE_DEFS tables, indicating it points to a master role definition record.

Common Use Cases and Queries

The primary use case for this table is to validate and control which roles (e.g., Approver, Signatory, Buyer, Supplier) are permissible for a given contract line type, such as a "Professional Services" or "Goods" line. A common operational query would retrieve all valid roles for a specific subclass to populate a list of values in the application's user interface. For reporting and analysis, administrators might query the table to audit role-to-subclass mappings or identify subclasses that lack certain role definitions. A typical SQL pattern would involve joining OKC_SUBCLASS_ROLES with OKC_SUBCLASSES_B and the relevant role definition table.

SELECT scs.scs_code, scs.name subclass_name, sre.role_code
FROM okc_subclass_roles scr,
     okc_subclasses_b scs,
     okc_rg_role_defs sre
WHERE scr.scs_code = scs.scs_code
  AND scr.sre_id = sre.sre_id
  AND scs.scs_code = '<Your_Subclass_Code>';

Related Objects

• OKC_SUBCLASSES_B: The master table for contract line subclasses. OKC_SUBCLASS_ROLES.SCS_CODE is a foreign key to this table.
• OKC_LINE_STYLE_ROLES: References OKC_SUBCLASS_ROLES, likely extending role definitions with style-specific attributes for contract lines.
• OKC_RG_ROLE_DEFS: The master table for role definitions within the Contracts Core module. OKC_SUBCLASS_ROLES.SRE_ID is the foreign key link to this table.
• OKC_SUBCLASS_ROLES_PK: The primary key constraint on the ID column of this table.