Results for “okc_std_articles_b”

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

Overview

OKC_STD_ARTICLES_B is a table within the OKC schema, belonging to the Oracle Contracts Core (OKC) product family in Oracle E-Business Suite. It stores standard text — commonly referred to as boilerplate clauses or standard articles — used during the creation of contracts. Entries in this table serve as reusable contract language that can be incorporated into contract documents, sections, and article sets, reducing the effort required to author repetitive legal or commercial terms.

Per the ETRM documentation, this object carries the status VALID in the 12.1.1 and 12.2.2 data models, but is explicitly marked as desupported from release 11.5.10 onwards. It persists in the schema primarily for backward compatibility and historical data retention; new development should not depend on it, and functional replacements should be sought in the supported Contracts Core data model. The table is physically defined with 25 columns under the OKC owner in the 12.2.2 documented schema.

From a Data Vault modeling perspective, the heuristic classification of this object is hub-leaning. The central ID column, enforced by the OKC_STD_ARTICLES_B_PK primary key, behaves as a durable business key anchor around which several dependent objects cluster. This classification is a modeling suggestion derived from the foreign key topology rather than an Oracle-imposed designation.

Key Information Stored

The most significant columns in OKC_STD_ARTICLES_B are:

• ID — The surrogate primary key, enforced by OKC_STD_ARTICLES_B_PK and also covered by the unique index OKC_STD_ARTICLES_B_U1, which serves as the documented business-key candidate.
• SBT_CODE — A short code, consistent with the Oracle "Short Business Type" pattern, identifying or classifying the standard article text.
• OBJECT_VERSION_NUMBER — The optimistic locking column used to detect concurrent updates, standard in EBS 12.1.1 and 12.2.2 tables.
• CREATED_BY, CREATION_DATE — Standard audit columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Audit columns capturing the most recent modification user, timestamp, and login session.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The flexible descriptive flexfield (DFF) columns, providing fifteen extensible segments plus a structure category for customer-specific contract text metadata.
• SECURITY_GROUP_ID — The multi-tenant / data-security grouping column, which references FND_SECURITY_GROUPS.

The surrogate primary key (ID) should be distinguished from the business-key candidate represented by the unique index OKC_STD_ARTICLES_B_U1. Joins against dependent tables are consistently performed on the SAE_ID column, which references this table's ID.

Common Use Cases and Queries

Because the table is desupported, its most common uses are historical reporting, data migration validation, and reconciliation of legacy contract text. Typical scenarios include identifying which standard articles were included in a given contract section, or tracing article sets and versions backward to their source text.

A representative query retrieves a standard article with its audit context:

• SELECT ID, SBT_CODE, OBJECT_VERSION_NUMBER, CREATION_DATE, LAST_UPDATE_DATE FROM OKC.OKC_STD_ARTICLES_B WHERE ID = :p_id;

To find the section contents that consume a given article, join to OKC_SECTION_CONTENTS on SAE_ID. Similarly, joining to OKC_STD_ART_VERSIONS_B on SAE_ID reveals the version history of the article text. Reporting against the DFF columns (ATTRIBUTE_CATEGORY and ATTRIBUTE1–15) requires joining to the appropriate descriptive flexfield view to translate stored segment values into displayable labels. Reporting queries should always filter by SECURITY_GROUP_ID where multi-org or data-security partitioning applies.

Related Objects

The following objects reference or depend on OKC_STD_ARTICLES_B through documented foreign keys:

• OKC_STD_ART_INCMPTS — references SAE_ID and SAE_ID_FOR, supporting the incompatibility or exclusion rules between standard articles.
• OKC_STD_ART_SET_MEMS — references SAE_ID, defining membership of standard articles within article sets.
• OKC_STD_ART_VERSIONS_B — references SAE_ID, storing versioned copies of each standard article.
• OKC_SECTION_CONTENTS — references SAE_ID, linking standard articles into contract section content.
• FND_SECURITY_GROUPS — referenced by OKC_STD_ARTICLES_B.SECURITY_GROUP_ID, providing the security group definition for the row.

Together these relationships place OKC_STD_ARTICLES_B at the center of the standard article model, even though the table is formally desupported.