Search Results okc_art_int_batprocs_all




Overview
Explore in AI Chat

Overview

The table OKC_ART_INT_BATPROCS_ALL is a core technical table within the Oracle E-Business Suite Contracts Core module (OKC). It functions as a central audit and control mechanism for the batch import processes associated with the OKC Artifact Interface (ART_INT). Its primary role is to store the execution parameters and runtime statistics for each discrete run of the import process, enabling administrators to track, monitor, and analyze the performance and history of data integration jobs. This table is critical for operational support and troubleshooting within the Contracts domain, as it provides a persistent log of batch process executions.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the documented description indicates the table stores two primary categories of data. First, it holds batch process parameters, which likely include identifiers for the run, source data references, and control flags that dictate the import behavior. Second, it stores batch process statistics, which would encompass quantitative metrics such as start and end timestamps, record counts (total processed, successful, failed), and status indicators (e.g., 'RUNNING', 'COMPLETED', 'ERROR'). The primary key column, BATCH_PROCESS_ID, uniquely identifies each import run and is the central reference point for all related data.

Common Use Cases and Queries

A primary use case is generating audit reports on the history and success rate of contract data imports. Administrators can query this table to identify failed runs for investigation or to analyze processing trends over time. Common SQL patterns include retrieving the most recent runs for monitoring or joining with error tables to get a complete picture of a problematic import. For example, a basic status report might use: SELECT BATCH_PROCESS_ID, PROCESS_STATUS, START_DATE, END_DATE, RECORDS_PROCESSED FROM OKC_ART_INT_BATPROCS_ALL WHERE START_DATE > SYSDATE - 7 ORDER BY START_DATE DESC;. Another critical scenario involves troubleshooting, where the BATCH_PROCESS_ID from this table is used to locate corresponding error details in related logging tables.

Related Objects

This table maintains a direct parent-child relationship with the interface errors table, forming a key part of the import framework's error handling structure.

  • Primary Key: OKC_ART_INT_BATPROCS_PK1 on column BATCH_PROCESS_ID.
  • Foreign Key Relationship: The table OKC_ART_INT_ERRORS references OKC_ART_INT_BATPROCS_ALL via its BATCH_PROCESS_ID column. This links individual error records to the specific batch process run that generated them, allowing for consolidated error reporting and analysis per import job.