Results for “okc_art_interface_all”

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

Overview

OKC_ART_INTERFACE_ALL is the Contracts Core (OKC) open-interface table used to load standard clauses from external or legacy systems into Oracle E-Business Suite. Rows staged in this table are validated and then processed by the Clause Import Concurrent program, which transfers valid records into the production clause tables OKC_ARTICLES_ALL, OKC_ARTICLE_VERSIONS, and OKC_ARTICLE_ADOPTIONS. The table is seeded in the OKC schema and is marked VALID in release 12.1.1 and 12.2.2. Its documented physical schema comprises 61 columns, with the surrogate primary key enforced by OKC_ART_INTERFACE_ALL_PK1 on INTERFACE_ID.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object as hub-leaning. INTERFACE_ID behaves as a durable business key that anchors the interface record, and it is not a natural attribute of the clause itself. Modelers should therefore treat OKC_ART_INTERFACE_ALL as a staging hub for clause imports, with the same key reused by the companion error table rather than as a true dependent satellite of the target clause entities.

Key Information Stored

The columns of primary interest for import processing and reconciliation include:

• INTERFACE_ID — surrogate primary key and unique index (OKC_ART_INTERFACE_ALL_U1); the value referenced by the error table.
• BATCH_NUMBER — groups interface rows submitted together for a single import run.
• PROCESS_STATUS — indicates whether the row is pending, successfully processed, or in error.
• ACTION — the operation to perform on the target clause, such as insert or update.
• ORG_ID — operating unit context for multi-org security and ownership of the clause.
• ARTICLE_TITLE, ARTICLE_NUMBER, ARTICLE_INTENT, ARTICLE_TYPE, ARTICLE_LANGUAGE — descriptive clause attributes carried into OKC_ARTICLES_ALL.
• ARTICLE_VERSION_NUMBER, ARTICLE_TEXT, DATE_APPROVED, DATE_PUBLISHED, ARTICLE_STATUS — version-level content destined for OKC_ARTICLE_VERSIONS.
• START_DATE, END_DATE — effective dating of the clause version.
• ART_SYSTEM_REFERENCE_CODE, ART_SYSTEM_REFERENCE_ID1, ART_SYSTEM_REFERENCE_ID2, VER_SYSTEM_REFERENCE_CODE, VER_SYSTEM_REFERENCE_ID1, VER_SYSTEM_REFERENCE_ID2 — cross-references back to the source system for article-level and version-level records.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the importing logic.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments for customer-defined import data.
• Standard WHO/audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent-program context columns (PROGRAM_ID, PROGRAM_LOGIN_ID, PROGRAM_APPLICATION_ID, REQUEST_ID).

Common Use Cases and Queries

Typical scenarios include bulk migration of legacy clause libraries, scheduled feeds from external contract repositories, and reconciliation of failed imports. A common monitoring query retrieves pending or erroneous rows by batch:

SELECT interface_id, batch_number, process_status, article_number FROM okc_art_interface_all WHERE process_status = 'PENDING' OR process_status IS NULL ORDER BY batch_number;

Error diagnosis joins the interface table to OKC_ART_INT_ERRORS on INTERFACE_ID to surface rejection reasons before correcting and resubmitting a batch. Reporting queries frequently group by BATCH_NUMBER, ACTION, ORG_ID, or PROCESS_STATUS to measure throughput and failure rates, while source-system reconciliation uses the ART_SYSTEM_REFERENCE and VER_SYSTEM_REFERENCE columns to trace imported clauses back to their origin identifiers.

Related Objects

• OKC_ART_INT_ERRORS — child table; its INTERFACE_ID column is a foreign key to OKC_ART_INTERFACE_ALL.INTERFACE_ID, capturing validation and import failures.
• OKC_ARTICLES_ALL — target table receiving article-level clause records.
• OKC_ARTICLE_VERSIONS — target table receiving version-level content such as ARTICLE_TEXT and ARTICLE_VERSION_NUMBER.
• OKC_ARTICLE_ADOPTIONS — target table recording clause adoption relationships produced during import.
• Clause Import Concurrent Program — the processing routine that validates and promotes rows from this interface table to the three target tables above.