Search Results ap_checkrun_conc_processes_all




Overview
Explore in AI Chat

Overview

The AP_CHECKRUN_CONC_PROCESSES_ALL table is a temporary data object within the Oracle E-Business Suite Payables (AP) module. Its primary role is to serve as a tracking and coordination mechanism for concurrent programs that process payment batches, also known as check runs. This table acts as a transient repository, facilitating communication and state management between the various concurrent processes involved in the multi-step payment batch workflow. By storing key identifiers, it enables the system to link specific payment batch execution requests to their corresponding concurrent program instances, ensuring data integrity and process traceability throughout the payment cycle.

Key Information Stored

The table's structure is designed to hold minimal but critical identifiers for process tracking. Based on the provided metadata, the primary key is the REQUEST_ID column, which stores the unique identifier from the FND_CONCURRENT_REQUESTS table for the specific concurrent program execution. Another significant column is CHECKRUN_NAME, which holds the name of the payment batch being processed. This column is part of a foreign key relationship to the AP_INV_SELECTION_CRITERIA_ALL table, linking the process tracking record to the specific selection criteria and invoices chosen for the payment run. The combination of these fields allows the system to uniquely identify and monitor the progress of each payment batch job.

Common Use Cases and Queries

The primary use case for this table is troubleshooting and monitoring the status of payment batch submissions. System administrators and functional users can query it to determine if a specific payment batch is currently being processed, identify the concurrent request ID for a stalled job, or clean up orphaned records after an abnormal termination. A common diagnostic query would join this table with FND_CONCURRENT_REQUESTS to get the status and phase of a running payment process for a given CHECKRUN_NAME.

  • Monitoring an active payment batch: SELECT acp.checkrun_name, fcr.request_id, fcr.phase_code, fcr.status_code FROM ap_checkrun_conc_processes_all acp, fnd_concurrent_requests fcr WHERE acp.request_id = fcr.request_id AND acp.checkrun_name = '<BATCH_NAME>';
  • Identifying processes for cleanup: This table may be referenced to find and resolve situations where a payment batch appears stuck, by checking for processes without a corresponding active concurrent request.

Related Objects

As indicated by the foreign key constraints, AP_CHECKRUN_CONC_PROCESSES_ALL has direct dependencies on two core EBS tables. The REQUESTS_ID column is a foreign key to FND_CONCURRENT_REQUESTS, the central table that stores information for all concurrent program executions across EBS. The CHECKRUN_NAME column is a foreign key to AP_INV_SELECTION_CRITERIA_ALL, which stores the saved invoice selection criteria defining the payment batch. This relationship underscores the table's role as a bridge between the concurrent processing framework and the specific Payables data for a check run. It is primarily written to and read by the internal logic of the payment batch concurrent programs themselves.