Search Results okc_article_relatns




Overview
Explore in AI Chat

Overview

The view APPS.OKC_SAE_INCMPT_V is a reporting and integration object within the Oracle E-Business Suite Contracts (OKC) module, commonly associated with Oracle Advanced Product Catalog and the Oracle Trading Community Architecture. It exposes the set of "incompatible" relationships defined between articles (knowledge-base or catalog articles) in the OKC schema. Each row of the view represents a single directional incompatibility assertion, pairing a source article with a target article that is declared incompatible with it.

The view name derives from OKC (the Contracts/articles schema), SAE (Source Article Entity reference), and INCMPT (incompatible). Its role is to simplify the retrieval of incompatibility data that otherwise requires joining the relationship table OKC_ARTICLE_RELATNS to the article master table OKC_ARTICLES_ALL. By pre-joining these tables and filtering on RELATIONSHIP_TYPE = 'INCOMPATIBLE', the view provides a denormalized, business-friendly result set suitable for reporting, integration, and validation logic.

Underlying Base Objects

The view is defined over two documented base objects:

  • OKC_ARTICLE_RELATNS (SYNONYM) — the relationship table that stores typed associations between articles. Each row links a SOURCE_ARTICLE_ID to a TARGET_ARTICLE_ID, and carries a RELATIONSHIP_TYPE discriminator. The view filters this table for the type 'INCOMPATIBLE'.
  • OKC_ARTICLES_ALL (SYNONYM) — the article master table holding descriptive attributes such as ARTICLE_TITLE and ARTICLE_ID. This is joined to the relationship table solely to resolve the source article's title.

The join condition is A.ARTICLE_ID = B.SOURCE_ARTICLE_ID, meaning the view returns the source article's title as the display name (FOR_NAME) and does not resolve the target article's title. The view carries no aggregation or DISTINCT clause; its complexity is limited to this two-table equijoin and a constant predicate on the relationship type.

Key Columns

  • FOR_NAME — the ARTICLE_TITLE of the source article (alias of A.ARTICLE_TITLE), providing a human-readable label.
  • ROWID — the row identifier from the underlying OKC_ARTICLE_RELATNS row (aliased B.ROWID).
  • SAE_ID — the source article identifier (alias of SOURCE_ARTICLE_ID).
  • SAE_ID_FOR — the target article identifier (alias of TARGET_ARTICLE_ID), i.e., the article that the source is incompatible with.
  • OBJECT_VERSION_NUMBER — optimistic-locking version counter inherited from the relationship record.
  • CREATED_BY, CREATION_DATE — audit columns recording the creator and creation timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE — audit columns recording the last modifier and modification timestamp.
  • LAST_UPDATE_LOGIN — the login/user session identifier of the last update.

Common Use Cases and Queries

The view is typically used to validate compatibility rules, drive configuration/selection logic, and feed downstream reporting. A representative query retrieves all incompatibilities for a given source article:

  • SELECT for_name, sae_id, sae_id_for FROM apps.okc_sae_incmpt_v WHERE sae_id = :p_article_id
  • SELECT sae_id, sae_id_for, last_update_date FROM apps.okc_sae_incmpt_v ORDER BY for_name
  • Integration queries often select only sae_id and sae_id_for to build an incompatibility matrix consumed by external configuration engines.

Because the view does not expose the target article's title, drill-down reporting that requires the incompatible article's name must join the view result back to OKC_ARTICLES_ALL on sae_id_for = article_id. As with all APPS metadata views, access is governed by standard EBS security; direct querying should respect granted privileges and, where used in concurrent programs, the appropriate operating unit context.