Search Results icx_por_batch_jobs




Overview
Explore in AI Chat

Overview

The ICX_POR_BATCH_JOBS table is a core data object within the Oracle iProcurement (ICX) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It functions as the central control and tracking repository for catalog batch processes submitted through the iProcurement application. These batch processes are critical for maintaining the supplier catalog data that drives the requisitioning experience, including operations like bulk item and price list uploads. The table assigns a unique job number to each submitted batch, enabling administrators to monitor the status, progress, and outcome of these asynchronous data loads throughout their lifecycle.

Key Information Stored

While the provided metadata does not list specific columns beyond the keys, the table's primary key and foreign key relationships define its essential structure. The JOB_NUMBER column serves as the unique identifier (primary key) for every batch job. The table tracks the associated supplier for the catalog data through the SUPPLIER_ID column, which references the HZ_PARTIES table. A separate LOAD_SUPPLIER_ID column, also referencing HZ_PARTIES, indicates the supplier on whose behalf the data is being loaded, which may differ in certain scenarios. Other typical columns in such a control table would include job status (e.g., PENDING, RUNNING, COMPLETED, ERROR), submission date and time, the initiating user, and parameters specific to the batch process type.

Common Use Cases and Queries

The primary use case is monitoring and troubleshooting catalog batch uploads. System administrators and functional users leverage this table to answer critical operational questions. Common queries include identifying recently failed jobs to initiate corrective action, checking the status of long-running uploads, or generating a history of jobs submitted for a specific supplier. A fundamental reporting query would join ICX_POR_BATCH_JOBS with HZ_PARTIES to display supplier names alongside job details.

  • Sample Query (Find Recent Failed Jobs): SELECT job_number, supplier_id, status, creation_date FROM icx_por_batch_jobs WHERE status = 'ERROR' AND creation_date > SYSDATE - 1 ORDER BY creation_date DESC;
  • Integration Point: The data in this table is often accessed via custom reports or directly queried to diagnose issues logged in the related error detail tables, such as ICX_POR_FAILED_LINES.

Related Objects

The ICX_POR_BATCH_JOBS table sits at the center of a key data model for catalog batch processing, as evidenced by its documented foreign key relationships.