Results for “for_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OKC_SAE_INCMPT_V view is a reporting and integration object shipped in the APPS schema of Oracle E-Business Suite, belonging to the OKC – Contracts Core product. Its stated purpose is to expose incompatible standard articles — that is, pairs of standard contract articles (clauses) that have been flagged as mutually incompatible so that the Contract Authoring and clause-selection logic can prevent or warn against combining them in a single contract document.

The view does not store data of its own; it is a denormalized read model layered over the article and article-relationship entities. It resolves the source article identifier into a human-readable title via a join to OKC_ARTICLES_ALL, and it filters the underlying relationship records to only those rows whose relationship type is INCOMPATIBLE. Because it is a view, it inherits the standard EBS multi-org behavior of the Contract Core tables and enforces the caller's operating unit context through the USERENV('CLIENT_INFO') mechanism.

In the ETRM 12.2.2 documented metadata the object is reported with status VALID and owner APPS. It is intended primarily for internal use by the Contract Core application layer and for diagnostics, rather than as a public integration interface, so custom code should treat it as informational and stable only to the extent that the underlying base tables remain unchanged.

Underlying Base Objects

Per the ETRM metadata, the view is defined over two documented base objects, both referenced as synonyms:

• OKC_ARTICLES_ALL — the master repository of standard articles (clauses), including their titles and language/org partitioning.
• OKC_ARTICLE_RELATNS (referenced in the view text as OKC_ARTICLE_RELATNS_ALL) — the article-to-article relationship table that stores directional links between articles, keyed by relationship type.

The view joins these on A.ARTICLE_ID = B.SOURCE_ARTICLE_ID, so the row context is driven from the relationship table and enriched with the source article's title. A RELATIONSHIP_TYPE = 'INCOMPATIBLE' predicate restricts the result to incompatibility relationships only. The ORG_ID filter is applied against the operating unit derived from the client-info session string, with a fallback of -99 when no context is available.

Key Columns

• FOR_NAME — the article title of the source article (OKC_ARTICLES_ALL.ARTICLE_TITLE); supplies the human-readable label.
• ROW_ID — the physical rowid of the relationship record, useful for direct row addressing in diagnostics.
• SAE_ID — the source article identifier (SOURCE_ARTICLE_ID), the article for which incompatibilities are defined.
• SAE_ID_FOR — the target article identifier (TARGET_ARTICLE_ID), the article that is incompatible with the source.
• OBJECT_VERSION_NUMBER — the optimistic locking version, reflecting the last committed change to the relationship row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS who-columns for audit and change tracking.

Common Use Cases and Queries

The view is typically used to audit or troubleshoot clause incompatibility configuration, to validate that authoring rules are populated for a given operating unit, and to feed reconciliation extracts. The following query lists all incompatible article pairs visible in the current operating unit context:

SELECT for_name, sae_id, sae_id_for,
       last_updated_by, last_update_date
  FROM apps.okc_sae_incmpt_v;

To trace a specific article's incompatibilities, filter on the source identifier:

SELECT for_name, sae_id_for
  FROM apps.okc_sae_incmpt_v
 WHERE sae_id = :article_id;

Because the org filter is derived from CLIENT_INFO, results depend on the initialized application session; run such queries from within a properly initialized EBS session (for example via a concurrent program or an OA Framework page context) rather than from a bare SQL*Plus connection, where the fallback org value of -99 applies.