Results for “create_opp_yn”

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

Overview

OKC_SUBCLASSES_B is a foundational setup table within the Oracle Contracts Core (OKC) module of Oracle E-Business Suite, documented as VALID in releases 12.1.1 and 12.2.2. The table defines contract subclasses, which occupy the level immediately beneath contract classes in the Contracts Core classification hierarchy. Per the ETRM metadata, a subclass record determines the line style hierarchy of the contract, the valid rule groups, the valid party roles, and the commonly used standard article sets. Consequently, OKC_SUBCLASSES_B governs much of the behavioral configuration applied when a contract of a given subclass is authored, including how lines are structured, which business rules fire, which parties may be assigned roles, and which boilerplate articles appear by default.

From a dimensional modeling perspective, the mined Data Vault classification suggests a hub-leaning role. OKC_SUBCLASSES_B functions as a business-key-bearing reference entity: it carries the CODE business key, is referenced by many downstream transactional and setup tables, and anchors a family of satellite-style configuration tables (roles, responsibilities, rule group definitions, and top-line rules) keyed on SCS_CODE.

Key Information Stored

The table contains 14 documented columns. The most significant are:

• CODE — the business key of the subclass and the column underlying the primary key OKC_SUBCLASSES_B_PK, as well as the unique index OKC_SUBCLASSES_U1 (CODE, ZD_EDITION_NAME).
• CLS_CODE — foreign key to OKC_CLASSES_B, identifying the parent contract class to which the subclass belongs and establishing the class/subclass hierarchy.
• START_DATE and END_DATE — effective dating for the subclass definition.
• CREATE_OPP_YN — flag controlling whether an opportunity is created in association with contracts of this subclass.
• ACCESS_LEVEL — access control indicator for the subclass record.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-org/reference data security.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications Framework (OAF) and concurrent update protection.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns present in nearly all EBS transactional and setup tables.
• ZD_EDITION_NAME — editioning column introduced under the EBR (Edition-Based Redefinition) architecture in 12.2.x; part of the unique index in 12.2.2.

The primary key is the surrogate single-column key OKC_SUBCLASSES_B_PK on CODE; the unique index OKC_SUBCLASSES_U1 (CODE, ZD_EDITION_NAME) serves as the business-key candidate under editioning.

Common Use Cases and Queries

Subclass definitions are primarily consumed during contract authoring and reporting. A typical query joins subclasses to their parent class to list the full hierarchy:

• SELECT s.code, s.cls_code, c.name subclass_name FROM okc_subclasses_b s, okc_classes_b c WHERE s.cls_code = c.code;
• Reporting active subclasses by date: filter on START_DATE and END_DATE to return only currently effective subclass definitions.
• Configuration auditing: query OKC_SUBCLASS_ROLES, OKC_SUBCLASS_RESPS, OKC_SUBCLASS_RG_DEFS, and OKC_SUBCLASS_TOP_LINE joined on SCS_CODE to review the full behavioral setup of a subclass.
• Usage analysis: join OKC_K_HEADERS_B to OKC_SUBCLASSES_B on SCS_CODE to count contracts per subclass or identify subclasses with no active contracts.
• Article set reporting: join OKC_STD_ART_CLASSINGS to OKC_SUBCLASSES_B on SCS_CODE to see which standard articles are defaulted for each subclass.

Related Objects

OKC_SUBCLASSES_B is referenced by a wide set of dependent tables via the SCS_CODE column, and itself references OKC_CLASSES_B via CLS_CODE and FND_SECURITY_GROUPS via SECURITY_GROUP_ID. The most significant related objects are:

• OKC_CLASSES_B — parent table, joined on CLS_CODE = CODE.
• OKC_K_HEADERS_B (and OKC_K_HEADERS_ALL_B) — contract headers, joined on SCS_CODE.
• OKC_K_SEQ_LINES — contract lines, joined on SCS_CODE.
• OKC_SUBCLASS_ROLES — valid party roles per subclass, joined on SCS_CODE.
• OKC_SUBCLASS_RESPS — responsibilities authorized for the subclass, joined on SCS_CODE.
• OKC_SUBCLASS_RG_DEFS — valid rule group definitions, joined on SCS_CODE.
• OKC_SUBCLASS_TOP_LINE — top-line rule assignments, joined on SCS_CODE.
• OKC_STD_ART_CLASSINGS — standard article assignments, joined on SCS_CODE.
• OKC_ASSENTS — assent/acceptance rules, joined on SCS_CODE.
• OKL_CRTRN_SBCLSSES — lease/contract term subclass configuration, joined on SCS_CODE.