Search Results ap_unselected_invoices_all




Overview
Explore in AI Chat

Overview

The AP_UNSELECTED_INVOICES_ALL table is a core transactional table within the Oracle E-Business Suite Payables module (AP). Its primary function is to serve as a log or holding area for invoices that were processed by a payment batch but ultimately could not be selected for payment. This occurs during the payment batch submission process when invoices meet the initial selection criteria but are subsequently filtered out due to validation failures, holds, or other payment constraints. The table is a multi-organization table, as indicated by the '_ALL' suffix, meaning it stores data for all operating units accessible to a responsibility, with data partitioned by the ORG_ID column. Its existence is critical for troubleshooting payment batch issues and understanding the payment workflow's exclusion logic.

Key Information Stored

The table's structure is designed to link an excluded invoice to the specific payment batch run that attempted to process it. While the full column list is not provided in the excerpt, the documented foreign keys reveal its essential components. The CHECKRUN_ID column links the record to the AP_INV_SELECTION_CRITERIA_ALL table, which defines the parameters and results of the payment batch (or check run). The INVOICE_ID column links directly to the AP_INVOICES_ALL table, identifying the specific invoice that was unselected. Typically, such a table would also include columns for the reason for exclusion (e.g., a code corresponding to "Invoice on Hold," "Discounts Available," or "Payment Terms Not Met"), a timestamp for when the exclusion occurred, and the ORG_ID for operating unit context.

Common Use Cases and Queries

The primary use case is diagnosing payment batch results. After submitting a payment batch, a payables manager can query this table to generate a report of all invoices excluded from payment, analyze the reasons, and take corrective action. A common diagnostic SQL pattern joins to the invoices and payment batch tables:

  • SELECT ai.invoice_num, ai.invoice_amount, aui.rejection_reason, aisc.checkrun_name FROM ap_unselected_invoices_all aui, ap_invoices_all ai, ap_inv_selection_criteria_all aisc WHERE aui.invoice_id = ai.invoice_id AND aui.checkrun_id = aisc.checkrun_id AND aisc.checkrun_name = '&BATCH_NAME';

This data is also foundational for custom reports analyzing payment process efficiency, identifying chronic issues with specific suppliers or invoice types, and auditing the payment workflow. The table is typically purged or archived over time as payment batch records are cleared.

Related Objects

As per the provided metadata, AP_UNSELECTED_INVOICES_ALL has direct, integral relationships with two key Payables tables. It is a child table of AP_INV_SELECTION_CRITERIA_ALL via the CHECKRUN_ID foreign key; this table stores the header information for each payment batch execution. It is also a child table of AP_INVOICES_ALL via the INVOICE_ID foreign key, which is the master table for all payable invoices. While not listed, the table may be referenced by standard Oracle Payables views or used by the Payment Manager's exclusion logic within the AP_PAYMENT_PKG or similar APIs. Understanding these relationships is essential for constructing accurate joins in any analytical or diagnostic query.