Results for “okc_art_int_errors”

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

Overview

The OKC_ART_INT_ERRORS table in the OKC (Contracts Core) schema stores all errors encountered during the clause import process in Oracle EBS 12.1.1 and 12.2.2. Clause import is part of the Contracts Core module's authoring and template infrastructure, and this table functions as the central error repository keyed to the batch process and interface record that generated each failure. Because it captures per-record diagnostics rather than business transactions, the table is primarily a diagnostic and reconciliation object used by concurrent program owners, integration developers, and support analysts troubleshooting clause uploads through the Contracts interface.

A heuristic Data Vault classification, mined from the foreign key structure, suggests modeling this object as a link. The classification reflects its associative nature: each row connects a batch process run to an interface record and anchors them with an error sequence number, rather than describing a standalone business entity.

Key Information Stored

The table consists of 16 documented columns. The most operationally significant are:

• BATCH_PROCESS_ID — Identifies the clause import batch run that produced the error. Part of the primary key and the join key to OKC_ART_INT_BATPROCS_ALL.
• INTERFACE_ID — Identifies the specific interface row (clause import record) that failed. Part of the primary key and the join key to OKC_ART_INTERFACE_ALL.
• ERROR_NUMBER — Sequence number distinguishing multiple errors raised for the same interface record within the same batch. Completes the composite primary key.
• ERROR_TYPE — Categorizes the error (for example, validation or processing failure), enabling filtering and aggregation by failure class.
• ERROR_DESCRIPTION — Free-text message detailing the failure, the primary field for human diagnosis.
• ENTITY — Identifies the entity or construct against which the error was raised.
• OBJECT_VERSION_NUMBER — Optimistic locking column standard to EBS tables.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns describing who created the error row and when, and who last touched it.
• LAST_UPDATE_LOGIN — Login context of the last update.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_LOGIN_ID, REQUEST_ID — Concurrent program and request context, allowing the error to be traced back to the specific concurrent request that executed the import.

The surrogate primary key is OKC_ART_INT_ERRORS_PK1, defined on (BATCH_PROCESS_ID, INTERFACE_ID, ERROR_NUMBER). A unique index, OKC_ART_INT_ERRORS_U1, carries the same three-column business-key definition, confirming the natural key for the entity.

Common Use Cases and Queries

Typical scenarios include diagnosing a failed clause import batch, reporting error volumes by type, and reconciling errored interface rows back to their source batch. A representative query lists all errors for a given batch:

• SELECT e.INTERFACE_ID, e.ERROR_NUMBER, e.ERROR_TYPE, e.ERROR_DESCRIPTION FROM OKC.OKC_ART_INT_ERRORS e WHERE e.BATCH_PROCESS_ID = :batch_id ORDER BY e.INTERFACE_ID, e.ERROR_NUMBER;
• Grouping by ERROR_TYPE to summarize failure categories across a batch run.
• Joining to OKC_ART_INTERFACE_ALL to retrieve the source clause data that failed.
• Joining to OKC_ART_INT_BATPROCS_ALL to obtain batch status and program context.
• Filtering by REQUEST_ID or PROGRAM_ID to isolate errors from a specific concurrent request.

Reporting use cases include daily error trending, root-cause analysis for recurring clause import failures, and post-import reconciliation dashboards.

Related Objects

• OKC_ART_INT_BATPROCS_ALL — Referenced via OKC_ART_INT_ERRORS.BATCH_PROCESS_ID; holds batch process definitions and status.
• OKC_ART_INTERFACE_ALL — Referenced via OKC_ART_INT_ERRORS.INTERFACE_ID; holds the clause interface records.
• OKC_ART_INT_ERRORS_PK1 — Primary key constraint on (BATCH_PROCESS_ID, INTERFACE_ID, ERROR_NUMBER).
• OKC_ART_INT_ERRORS_U1 — Unique index reinforcing the business key.
• OKC_ART_INT_ERRORS — Base table itself, frequently queried with the two parent tables above for full diagnostic context.
• OKC_ART_INT_ERRORS — Also consumed by Contracts Core concurrent programs that populate and read error rows during clause import execution.