Search Results okc_article_relatns_all




Overview
Explore in AI Chat

Overview

The OKC_ARTICLE_RELATNS_ALL table is a core data structure within the Oracle E-Business Suite Contracts Core (OKC) module. It serves as the central repository for defining and storing relationships between standard clauses (articles) within a contract authoring library. These relationships govern how clauses can be combined during contract composition, enforcing business rules such as incompatibility or substitutability. A key historical note is that this table replaced the legacy OKC_STD_ART_INCMPTS table in release 11.5.10, consolidating and expanding relationship management. Its role is critical for maintaining data integrity and guiding users in creating compliant, logically consistent contracts by preventing invalid clause combinations or suggesting valid alternatives.

Key Information Stored

The table stores metadata that defines a directional relationship between two clauses within a specific operating unit (organization). While the full column list is not detailed in the provided metadata, based on its purpose and standard Oracle EBS design patterns, the table would typically contain the following key attributes: a unique relationship identifier (primary key), identifiers for the source and target clauses, a relationship type code (e.g., 'INCOMPATIBLE', 'ALTERNATE'), the effective date range for the relationship, and the operating unit identifier (ORG_ID) supporting the Multi-Org architecture. The description explicitly states it stores relationships "for an organization," confirming the presence of ORG_ID. The table acts as a junction between clause definitions, with foreign keys to the standard clauses table.

Common Use Cases and Queries

The primary use case is the validation of clause selection during contract authoring. When a user adds a clause to a contract, the application queries this table to check for any 'INCOMPATIBLE' relationships with clauses already present and warns or prevents the addition. Conversely, it can suggest 'ALTERNATE' clauses. Common reporting needs include auditing relationship definitions and understanding clause interdependencies. A sample query to find all incompatible clauses for a given standard article ID (e.g., 1000) in organization 204 would be:

  • SELECT target_article_id, relationship_type
  • FROM okc_article_relatns_all
  • WHERE source_article_id = 1000
  • AND relationship_type = 'INCOMPATIBLE'
  • AND org_id = 204
  • AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);

Related Objects

OKC_ARTICLE_RELATNS_ALL is intrinsically linked to the core tables storing clause definitions, most notably OKC_STD_ARTICLES_ALL or a similar articles master table. It would have foreign key relationships (FK) from columns like SOURCE_ARTICLE_ID and TARGET_ARTICLE_ID to the primary key (likely STD_ARTICLE_ID) of the articles table. The table's replacement of OKC_STD_ART_INCMPTS indicates a direct evolutionary relationship. It is also heavily referenced by the Contracts Core application logic, likely through public APIs or PL/SQL packages within the OKC schema that manage clause library administration and contract validation workflows. Any program or interface that validates or suggests clauses during contract creation will depend on data in this table.