Results for “okc_std_art_classings”

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

Overview

The OKC_STD_ART_CLASSINGS table resides in the OKC schema, the Contracts Core product of Oracle E-Business Suite, and is available in both release 12.1.1 and 12.2.2. As documented in the ETRM repository, the table "defines which Standard Article Sets are commonly used in a certain subclass of contract." In other words, it functions as a configuration and mapping table that links contract subclasses to the standard clause or article sets that are typically applied when contracts of that subclass are authored. This association drives defaulting behavior within Oracle Contracts, allowing users to inherit a pre-approved body of standard articles rather than assembling contract terms manually.

The metadata's heuristic Data Vault classification identifies this object as satellite-leaning. Under that modeling suggestion, OKC_STD_ART_CLASSINGS is best understood as a descriptive satellite attached to a business key composed of the subclass and standard-article combination, rather than as an independent hub of business entities or a pure associative link. The table carries full audit and security columns consistent with this role, reinforcing its position as an attribute-bearing dependent object.

Key Information Stored

The documented physical schema contains eleven columns. The most operationally significant are:

• ID — the surrogate primary key, enforced by the OKC_STD_ART_CLASSINGS_PK constraint and also carried by the unique index OKC_STD_ART_CLASSINGS_U1. This is a system-generated identifier with no business meaning.
• SCS_CODE — the contract subclass code. This column is the sole documented foreign key to OKC_SUBCLASSES_B and identifies the subclass of contract for which the standard article set is applicable.
• SAT_CODE — the standard article set code, identifying the set of standard articles being associated with the subclass. It participates in the SAC_SAIT1_UK unique key.
• PRICE_TYPE — the pricing type context for the classification. Together with SAT_CODE and SCS_CODE it forms the SAC_SAIT1_UK business-key candidate, distinguishing multiple applicability records.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Applications Framework to detect concurrent updates.
• SECURITY_GROUP_ID — the multi-tenant / data-security grouping column, referencing FND_SECURITY_GROUPS, which restricts row visibility by operating unit or security context.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns capturing creation and modification provenance.

Common Use Cases and Queries

Administrators and developers query this table to determine which standard article sets will default for a given contract subclass, to audit configuration drift between environments, and to support custom reporting on contract authoring defaults. A typical retrieval pattern joins the subclass and standard article set context:

• Listing all article classifications for a subclass: SELECT id, sat_code, price_type, scs_code FROM okc.okc_std_art_classings WHERE scs_code = :p_subclass;
• Identifying all subclasses linked to a specific standard article set: SELECT scs_code, price_type FROM okc.okc_std_art_classings WHERE sat_code = :p_sat_code;
• Security-aware reporting: filter on security_group_id to respect the active security profile, and join to fnd_security_groups when presenting cross-organization views.
• Change auditing: order by last_update_date and last_updated_by to trace who altered defaulting rules before and after a patch or configuration migration.

Related Objects

The FK and PK metadata defines the principal relationships surrounding this table:

• OKC_SUBCLASSES_B — referenced via OKC_STD_ART_CLASSINGS.SCS_CODE; the parent master of contract subclasses.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs row-level access.
• OKC_STD_ARTICLES_B / standard article set tables — referenced logically through SAT_CODE, supplying the article set definitions that are classified here.
• OKC_STD_ART_CLASSINGS_PK and OKC_STD_ART_CLASSINGS_U1 — the primary key and unique index enforcing ID and business-key integrity respectively.
• OKC contract authoring views and APIs — consume these rows when defaulting standard articles during contract creation in the Contracts Core module.