Search Results okc_std_art_incmpts_v




Overview
Explore in AI Chat

Overview

The OKC_STD_ART_INCMPTS_V view is a Contracts Core (OKC) security-restricted reporting object within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. As documented in the ETRM repository, the view is owned by the APPS schema with a VALID status and is defined as a restricted projection of the base table OKC_STD_ART_INCMPTS (implemented physically via the synonym OKC_ARTICLE_RELATNS_ALL). The view exists to expose the subset of article-to-article relationships that represent incompatibility constraints. In contract authoring and standard article management, a standard article may be incompatible with another standard article; this view surfaces those pairwise incompatibility links in a format supported by the Oracle Contracts form and API layers. Because the view applies an ORG_ID filter based on the USERENV client information, it enforces multi-org (Operating Unit) security at the database layer, ensuring that users only see incompatibility relationships belonging to their currently selected organization context.

Underlying Base Objects

The documented base object is OKC_ARTICLE_RELATNS, referenced through the synonym OKC_ARTICLE_RELATNS_ALL in the view definition. The view's SELECT statement draws from OKC_ARTICLE_RELATNS_ALL aliased as SAIB and applies two governing predicates: ORG_ID is constrained to the value derived from USERENV('CLIENT_INFO'), defaulting to -99 when the client info is unavailable, and RELATIONSHIP_TYPE is fixed to the literal 'INCOMPATIBLE'. The view therefore acts as a pre-filtered, org-aware lens over the generic article relationships table, isolating one specific relationship category. The documented referenced base objects list confirms OKC_ARTICLE_RELATNS (SYNONYM) as the singular underlying object reported in ETRM 12.2.2. All columns are drawn directly from that table without joins to other entities, so the view carries no additional derivation logic beyond the two WHERE-clause predicates.

Key Columns

  • ROW_ID — Maps to SAIB.ROWID, exposing the physical row identifier of the underlying OKC_ARTICLE_RELATNS_ALL record; useful for direct row addressing and for correlated update or delete operations.
  • SAE_ID — Maps to SOURCE_ARTICLE_ID, identifying the source standard article in the incompatibility pairing.
  • SAE_ID_FOR — Maps to TARGET_ARTICLE_ID, identifying the target standard article that is incompatible with the source article.
  • OBJECT_VERSION_NUMBER — Supports optimistic locking and concurrency control, incremented on each update of the base row.
  • CREATED_BY, CREATION_DATE — Standard audit columns recording the creating user and creation timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification user, timestamp, and login context.

Common Use Cases and Queries

The view is typically queried to determine which standard articles may not be combined within a contract, to build validation logic before saving article lines, or to report on configured incompatibility matrices. Because ORG_ID filtering is embedded, callers must ensure the correct Operating Unit context is initialized, otherwise the predicate defaults to -99 and returns no rows. A representative query is:

  • List all incompatibilities in the current org: SELECT SAE_ID, SAE_ID_FOR FROM APPS.OKC_STD_ART_INCMPTS_V;
  • Check for a specific pairing: SELECT 1 FROM APPS.OKC_STD_ART_INCMPTS_V WHERE SAE_ID = :source AND SAE_ID_FOR = :target;
  • Audit recently maintained pairs: SELECT SAE_ID, SAE_ID_FOR, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM APPS.OKC_STD_ART_INCMPTS_V ORDER BY LAST_UPDATE_DATE DESC;

These patterns support both functional inquiry screens and custom validation extensions that must respect Contracts Core multi-org security and the incompatibility relationship type.