AP Preliminary Payment Register 11i
Description:
Imported from Concurrent Program Application: Payables Source: Preliminary Payment Register Short Name: APXPBPPR
Parameters
Payment Batch, Payment Date From, Payment Date To
Used tables
ap_bank_accounts, ap_invoice_selection_criteria, ap_checks, ap_holds_all, fnd_attached_documents, fnd_documents_vl, ap_check_stocks, ap_system_parameters, gl_sets_of_books, gl_daily_conversion_types, ap_selected_invoice_checks, ap_selected_invoices, ap_invoices, fnd_document_sequences
Categories
Related reports
Dependencies
If you would like to try one of these Oracle EBS SQLs without having Blitz Report installed, note that some of the reports require functions from utility package xxen_util.
Example Report
AP Preliminary Payment Register 11i 26-Aug-2024 035838.xlsx
Report SQL
www.enginatics.com/reports/ap-preliminary-payment-register-11i/
Blitz Report™ import options
AP_Preliminary_Payment_Register_11i.xml
Case Study & Technical Analysis: AP Preliminary Payment Register 11i
Executive Summary
The AP Preliminary Payment Register 11i is a critical financial control report designed for Oracle Payables (11i). It provides Accounts Payable managers and payment administrators with a detailed preview of proposed payments before the final payment batch is confirmed and printed. By enabling a pre-disbursement review, this report mitigates the risk of erroneous payments, fraud, and cash flow mismanagement, ensuring that only verified and approved invoices are processed for payment.
Business Challenge
In high-volume accounts payable environments, payment batches can contain hundreds or thousands of invoices. Without a preliminary review mechanism, organizations face significant risks:
- Erroneous Payments: Paying incorrect amounts, duplicate invoices, or the wrong vendors.
- Cash Flow Visibility: Lack of foresight into the exact cash outflow required for a specific payment batch.
- Compliance & Control: Inability to verify that all selected invoices meet internal approval and hold criteria before funds are committed.
- Operational Inefficiency: The manual effort required to reverse or void payments after they have been printed or transmitted to the bank is costly and time-consuming.
The Solution: Operational View
The AP Preliminary Payment Register 11i solves these challenges by offering a comprehensive “Operational View” of the payment batch lifecycle.
- Pre-Payment Verification: Allows users to review every invoice selected for payment in the current batch, including amounts, discounts taken, and supplier details.
- Hold Identification: Highlights invoices that may have issues or holds, ensuring they are addressed before the final print run.
- Cash Requirement Planning: Provides a total batch amount, enabling Treasury teams to ensure sufficient funds are available in the disbursement bank account.
- Audit Trail: Serves as a supporting document for payment approval workflows, providing a snapshot of what was intended to be paid at a specific point in time.
Technical Architecture (High Level)
This report leverages the core Oracle Payables data model to reconstruct the proposed payment batch details.
- Primary Tables:
AP_INVOICE_SELECTION_CRITERIA: Stores the parameters and criteria used to initiate the payment batch.AP_SELECTED_INVOICES: Contains the specific invoices selected for payment within the batch.AP_SELECTED_INVOICE_CHECKS: Links the selected invoices to the proposed payment documents (checks/wires).AP_BANK_ACCOUNTS: Provides details on the disbursement bank account.AP_INVOICES: Source table for invoice header information.AP_CHECKS: (Referenced for context, though primarily for final payments) Stores payment document details.
- Logical Relationships:
- The report starts by identifying the Payment Batch from
AP_INVOICE_SELECTION_CRITERIA. - It joins to
AP_SELECTED_INVOICESto retrieve the list of invoices included in the run. - It further joins to
AP_SELECTED_INVOICE_CHECKSto group these invoices by the proposed payment document, calculating the total payment amount per supplier and per check. - Supplier details are retrieved by joining to
PO_VENDORS(implied via views or direct links in 11i).
- The report starts by identifying the Payment Batch from
Parameters & Filtering
The report accepts specific parameters to isolate the relevant payment batch data:
- Payment Batch: The specific name of the payment batch to be reviewed. This is the primary filter.
- Payment Date From / To: Allows filtering by the proposed payment date range, useful for reviewing multiple batches or specific periods.
Performance & Optimization
This report is optimized for performance during the critical payment processing window:
- Targeted Data Extraction: By querying the
AP_SELECTED_*tables, the report focuses only on the temporary data relevant to the open payment batch, avoiding the overhead of querying the massive historicalAP_INVOICE_PAYMENTS_ALLtable. - Indexed Retrieval: The query utilizes standard indexes on
BATCH_NAMEandCHECKRUN_NAMEto ensure rapid execution, even for large batches. - Direct Database Output: As a Blitz Report, it bypasses the XML parsing layer often used in standard Oracle reports, delivering data directly to Excel for immediate analysis and filtering.
FAQ
Q: Can this report be run after the payment batch is confirmed?
A: This report is primarily designed for the preliminary stage. Once a batch is confirmed, data moves from the AP_SELECTED_* tables to the permanent AP_CHECKS and AP_INVOICE_PAYMENTS tables. For confirmed payments, use the “AP Final Payment Register” or “AP Payment Register”.
Q: Does this report show invoices that were rejected from the batch? A: No, this report lists the invoices that were successfully selected. Rejected invoices would typically be reviewed in a separate exception report or the batch log file.
Q: Why is the check number missing or showing as a placeholder? A: Since this is a preliminary register, the final check numbers may not yet be assigned (especially for pre-numbered stock). The report shows the internal identifier or a temporary sequence until the print/confirm process assigns the legal document number.
Oracle E-Business Suite Reporting Library
We provide an open source Oracle EBS SQLs as a part of operational and project implementation support toolkits for rapid Excel reports generation.
Blitz Report™ is based on Oracle EBS forms technology, and hence requires minimal training. There are no data or performance limitations since the output files are created directly from the database without going through intermediate file formats such as XML.
Blitz Report can be used as BI Publisher and Oracle Discoverer replacement tool. Standard Oracle BI Publisher and Discoverer reports can also be imported into Blitz Report for immediate output to Excel. Typically, reports can be created and version tracked within hours instead of days. The concurrent request output automatically opens upon completion without the need for re-formatting.
The Filters, Columns, Rows and Values fields are used to create and deliver the data in pivot table format with full drill down to details.

The Excel template upload functionality in Blitz Report allows users to create their own layouts by uploading an Excel template with additional sheets and charts, automatically refreshed when the report runs again. This allows to create custom dashboards and more advanced visualizations of report data.

You can download and use Blitz Report free of charge for your first 30 reports.
The installation and implementation process usually takes less than 1 hour; you can refer to our installation and user guides for specific details.
If you would like to optimize your Oracle EBS implementation and or operational reporting you can visit www.enginatics.com to review great ideas and example usage in blog. Or why not try for yourself in our demo environment.
Useful Links
Blitz Report™ – World’s fastest data upload and reporting for Oracle EBS
Oracle Discoverer replacement – importing worksheets into Blitz Report™
Blitz Report™ Questions & Answers
Supply Chain Hub by Blitz Report™
© 2025 Enginatics