Search Results icx_por_buyer_approval_jobs




Overview
Explore in AI Chat

Overview

The ICX_POR_BUYER_APPROVAL_JOBS table is a core data object within the Oracle iProcurement (ICX) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as a detailed log and tracking mechanism for batch processes related to buyer pricing approvals and rejections. When a buyer runs a batch job to review and approve or reject supplier pricing submissions from catalogs or requisitions, this table stores the specific execution details for each job. Its primary role is to maintain a historical and operational record of these automated approval workflows, enabling traceability, reporting, and integration with the broader procurement approval hierarchy.

Key Information Stored

The table's structure is centered around linking a batch job execution to the specific price list data being processed. Its primary key is JOB_NUMBER, which uniquely identifies each approval batch job instance. A critical foreign key column is PRICE_LIST_HEADER_ID, which links the job to the specific price list header record in the ICX_POR_PRICE_LISTS table that contains the pricing information under review. While the provided metadata does not list all columns, typical data stored would include job status (e.g., PENDING, RUNNING, COMPLETED, ERRORED), timestamps for job start and completion, the initiating buyer or user ID, and parameters or summary counts related to the number of lines approved or rejected during that specific batch run.

Common Use Cases and Queries

This table is essential for monitoring and auditing batch approval activities. Common operational and reporting scenarios include tracking the status of long-running approval jobs, diagnosing failed processes, and generating historical reports on buyer workload or approval cycle times. A typical diagnostic query would join to the batch jobs table to get status details and to the price lists table to understand the data scope.

  • Job Status Inquiry: SELECT job_number, status, start_date, end_date FROM icx_por_buyer_approval_jobs WHERE status = 'ERROR';
  • Detailed Job Audit: SELECT bj.job_number, bj.status, bj.concurrent_program_id, jobs.price_list_header_id, pl.name FROM icx_por_buyer_approval_jobs jobs JOIN icx_por_batch_jobs bj ON jobs.job_number = bj.job_number JOIN icx_por_price_lists pl ON jobs.price_list_header_id = pl.header_id WHERE bj.actual_start_date > SYSDATE - 7;

Related Objects

The ICX_POR_BUYER_APPROVAL_JOBS table has defined foreign key relationships with two key iProcurement tables, forming a critical part of the pricing approval data model.

  • ICX_POR_BATCH_JOBS: Linked via ICX_POR_BUYER_APPROVAL_JOBS.JOB_NUMBER. This relationship connects the approval-specific details to the generic batch job execution and control information managed by the concurrent processing manager.
  • ICX_POR_PRICE_LISTS: Linked via ICX_POR_BUYER_APPROVAL_JOBS.PRICE_LIST_HEADER_ID. This is the fundamental link to the catalog price list data that is the subject of the buyer's batch approval or rejection action.