Search Results okc_articles_all

Overview

The OKC_ARTICLES_ALL table is a core data repository within the Oracle E-Business Suite Contracts Core (OKC) module. It serves as the master table for storing all clause definitions, which are the fundamental building blocks of contract documents. Its primary role is to manage both standard clauses from the centralized clause library and non-standard clauses created for specific contracts. This table is central to the contract authoring and management processes, enabling the reuse, versioning, and assembly of legal and business terms across an organization's contract portfolio. It is designed to support multiple organizations (as indicated by the '_ALL' suffix and the ORG_ID column) and multilingual content.

Key Information Stored

The table's primary key is the ARTICLE_ID, which uniquely identifies each clause record. Key descriptive columns include ARTICLE_NUMBER and ARTICLE_TITLE for identification, and ARTICLE_TEXT for storing the full clause content. The ORG_ID column associates each clause with a specific operating unit, enforcing data security. The ARTICLE_LANGUAGE column, linked to FND_LANGUAGES, supports multilingual clause management. Other critical columns track the clause's status (e.g., standard, approved), type, and categorization, facilitating library management and search. The table also includes standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) for auditing.

Common Use Cases and Queries

A primary use case is querying the clause library to find standard clauses for contract authoring. For example, a report to list all active, standard clauses for a specific organization and language would query OKC_ARTICLES_ALL with filters on ORG_ID, ARTICLE_LANGUAGE, and a status indicator. Another common scenario involves identifying all contracts that reference a specific clause, which requires joining OKC_ARTICLES_ALL to OKC_K_ARTICLES_B via REF_ARTICLE_ID. Technical implementations often query this table to validate clause existence or to extract clause text for document generation workflows. Sample SQL to retrieve core clause details:

• SELECT article_number, article_title, article_text FROM okc_articles_all WHERE org_id = :p_org_id AND standard_yn = 'Y' AND article_language = USERENV('LANG');

Related Objects

OKC_ARTICLES_ALL has integral relationships with several other Contracts Core tables, as documented by its foreign keys. The OKC_ARTICLE_VERSIONS table stores historical versions of each clause, joined on ARTICLE_ID. The OKC_K_ARTICLES_B table links contract lines to specific clause instances using REF_ARTICLE_ID. Clause relationships and hierarchies are managed in OKC_ARTICLE_RELATNS_ALL, which references this table via TARGET_ARTICLE_ID. For library organization, OKC_FOLDER_CONTENTS uses MEMBER_ID to link folders to articles. Furthermore, it references foundational EBS tables: HR_ALL_ORGANIZATION_UNITS via ORG_ID for operating unit validation and FND_LANGUAGES via ARTICLE_LANGUAGE for language code validation.