Results for “target_article_id”

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

Overview

OKC_ARTICLE_RELATNS_ALL is a Contracts Core (OKC) transactional table that stores the relationship definitions between clauses (articles) within a given operating unit. It supports relationship semantics such as INCOMPATIBLE and ALTERNATE, allowing the contract authoring engine to enforce or suggest clause combinations during contract assembly. The table replaces the legacy OKC_STD_ART_INCMPTS structure used prior to release 11.5.10, and it is organization-striped, exposing a single _ALL physical table with ORG_ID-based logical partitioning across operating units.

From a Data Vault modeling perspective, the mined FK structure classifies this object heuristically as a link: it is an associative structure connecting two article entities (source and target) within an organization context, rather than a descriptive satellite of either clause. This classification is a modeling suggestion derived from its foreign key topology, not a documented Oracle attribute.

Key Information Stored

Ten columns are documented for the 12.2.2 physical schema. The most significant are:

• SOURCE_ARTICLE_ID — identifies the originating clause in the relationship pair.
• TARGET_ARTICLE_ID — identifies the destination clause; this is the column most frequently referenced in user searches and represents the "other side" of the clause pairing.
• ORG_ID — operating unit discriminator; combined with the two article identifiers it forms the composite primary key.
• RELATIONSHIP_TYPE — the semantic classification of the link, for example INCOMPATIBLE or ALTERNATE.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OA Framework for concurrent update control.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns tracking insert and update provenance.

The surrogate primary key is OKC_ARTICLE_RELATNS_ALL_PK1, defined over (TARGET_ARTICLE_ID, ORG_ID, SOURCE_ARTICLE_ID). A unique business-key candidate is documented separately as OKC_ARTICLE_RELATNS_ALL_U1 over (SOURCE_ARTICLE_ID, TARGET_ARTICLE_ID, ORG_ID). Both enforce uniqueness of a given source-target-organization triple, guaranteeing that at most one relationship definition exists between two clauses in an operating unit.

Common Use Cases and Queries

Typical usage centers on clause conflict detection, contract template validation, and clause dependency reporting. A frequent query pattern resolves the target clause for a known source clause:

• SELECT t.target_article_id, t.relationship_type FROM okc_article_relatns_all t WHERE t.source_article_id = :article_id AND t.org_id = :org_id;
• Reverse lookup by target, useful when tracing which clauses restrict a given clause: SELECT r.source_article_id, r.relationship_type FROM okc_article_relatns_all r WHERE r.target_article_id = :article_id AND r.org_id = :org_id;
• Joining to OKC_ARTICLES_ALL to resolve names for both sides of the link, using separate aliases for source and target against the same article table.
• Reporting all INCOMPATIBLE pairings per operating unit for contract authoring rule audits.

Because the table is org-striped, every query should include ORG_ID as a predicate when operating under multi-org access controls, and it should be treated as read-only reference configuration in most integrations.

Related Objects

• OKC_ARTICLES_ALL — referenced through OKC_ARTICLE_RELATNS_ALL.TARGET_ARTICLE_ID, and implicitly through SOURCE_ARTICLE_ID, providing clause master attributes on both sides of the relationship.
• HR_ALL_ORGANIZATION_UNITS — referenced through OKC_ARTICLE_RELATNS_ALL.ORG_ID, supplying the operating unit definition and its name.
• OKC_STD_ART_INCMPTS — the legacy predecessor table, superseded by this structure from 11.5.10 onward and relevant only for historical migration analysis.
• OKC_ARTICLE_RELATNS_ALL_PK1 / _U1 — the primary and unique indexes that enforce the composite uniqueness described above.

Together these objects form the clause-conflict backbone used by the OKC contract authoring API layer and its surrounding Oracle Forms and OAF pages.