Search Results okc_k_articles_b

Overview

The OKC_K_ARTICLES_B table is a core data object within the Oracle E-Business Suite Contracts Core (OKC) module. It serves as the central repository for recording the use of both standard and non-standard clauses, referred to as "articles," within business documents such as contracts, sales orders, and purchase agreements. Its primary role is to manage the governance rules for these documents. An article associated with a document header establishes terms that govern the entire document, whereas an article associated with a specific line governs only that line. This structure is fundamental to the flexible and rule-based contract management capabilities of Oracle EBS, enabling the precise application of legal and business terms.

Key Information Stored

The table stores metadata and relationships for each article instance. While the full column list is not detailed in the provided metadata, the primary and foreign key relationships indicate critical data points. The primary key is the ID column, uniquely identifying each article usage. Essential foreign keys include DOCUMENT_TYPE, linking to the OKC_BUS_DOC_TYPES_B table to define the type of business document; SCN_ID, linking to the OKC_SECTIONS_B table to associate the article with a specific document section; and CAT_ID, which is a self-referencing key and also links to related transactional data. This structure allows the system to track the article's source, its placement within a document hierarchy, and its specific governing scope.

Common Use Cases and Queries

A primary use case is auditing the clauses applied to a specific contract or document version. For instance, a report showing all custom clauses used in a set of contracts would query this table. Another common scenario is impact analysis before modifying a standard clause, requiring queries to identify all documents where that clause is referenced. Sample SQL patterns often involve joining to document header or line tables via the foreign key relationships. For example, to find articles governing a specific contract header, one would join OKC_K_ARTICLES_B to the contract header table, likely using the DOCUMENT_TYPE and ID (as a foreign key in the header) to establish the relationship, filtered by the specific document identifier.

Related Objects

The table is integral to the Contracts Core data model, with several documented foreign key relationships:

• OKC_BUS_DOC_TYPES_B: Joined via OKC_K_ARTICLES_B.DOCUMENT_TYPE to define the business document type.
• OKC_SECTIONS_B: Joined via OKC_K_ARTICLES_B.SCN_ID to associate an article with a parent document section.
• OKC_K_ARTICLES_B (Self-Reference): The CAT_ID column serves as a self-referencing foreign key, potentially for hierarchical article structures or versioning.
• OKC_ARTICLE_TRANS: References this table via OKC_ARTICLE_TRANS.CAT_ID for transactional data related to the article.
• OKC_SECTION_CONTENTS: References this table via OKC_SECTION_CONTENTS.CAT_ID, linking article content to its containing section.