IBY Payment Process Request Details
Description:
Payment manager process request details including statuses, paid or rejected documents, amounts and rejection eror messages
Parameters
Operating Unit, Payment Process Request, Payment Process Request Status, Payment Status, Request Creation Date From, Request Creation Date To, Request Created By, Internal Bank Account, Trading Partner, Rejected or Failed Only, Exclude Removed Documents, Expand Error Details, Exchange Rate Type, Show Invoice Distributions
Used tables
iby_payments_all, gl_daily_conversion_types, ce_bank_accounts, iby_validation_sets_vl, iby_pay_service_requests, ap_inv_selection_criteria_all, iby_docs_payable_all, ap_invoices_all, ap_invoice_distributions_all, ap_checks_all, hz_parties, hz_party_sites, fnd_application_vl, iby_ext_bank_accounts_v, iby_ext_bank_accounts, iby_payment_reasons_vl, iby_payment_methods_vl, iby_acct_pmt_profiles_vl, iby_formats_vl, iby_delivery_channels_vl, iby_trxn_types_vl, iby_pay_instructions_all, hr_operating_units, gl_ledgers, xle_entity_profiles, iby_transaction_errors, mo_glob_org_access_tmp, dual
Categories
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
IBY Payment Process Request Details 25-Jan-2021 024851.xlsx
Report SQL
www.enginatics.com/reports/iby-payment-process-request-details/
Blitz Report™ import options
IBY_Payment_Process_Request_Details.xml
IBY Payment Process Request Details - Case Study & Technical Analysis
Executive Summary
The IBY Payment Process Request Details report provides a deep dive into the “Payment Process Request” (PPR) in Oracle Payments (IBY). A PPR is the central object that groups invoices for payment. This report details the lifecycle of a payment batch: which invoices were selected, which were rejected (and why), the status of the payment file generation, and the final payment amounts. It is a critical tool for the Accounts Payable department to manage mass payment runs.
Business Use Cases
- Payment Run Validation: Before confirming a payment batch, the AP Manager reviews this report to ensure the correct invoices are included and the total cash outflow matches expectations.
- Rejection Analysis: Identifies invoices that were pulled into the batch but rejected due to validation errors (e.g., “Missing Bank Account”, “Vendor on Hold”), allowing users to fix the issues and re-run.
- Audit Trail: Documents exactly which invoices were paid in a specific batch, providing a link between the bank withdrawal and the AP liability.
- Vendor Communication: Helps answer vendor queries like “Was my invoice included in the last payment run?”
Technical Analysis
Core Tables
IBY_PAY_SERVICE_REQUESTS: The header table for the Payment Process Request.IBY_DOCS_PAYABLE_ALL: The link between the PPR and the underlying AP Invoices (AP_INVOICES_ALL).IBY_PAYMENTS_ALL: The resulting payment records (Checks, Wires).IBY_TRANSACTION_ERRORS: Stores validation error messages.AP_INV_SELECTION_CRITERIA_ALL: Stores the criteria used to select invoices for the PPR.
Key Joins & Logic
- Selection to Payment: The report traces the flow from
AP_INV_SELECTION_CRITERIA_ALL->IBY_PAY_SERVICE_REQUESTS->IBY_DOCS_PAYABLE_ALL->IBY_PAYMENTS_ALL. - Status Logic: It decodes the complex status columns of the PPR (e.g., “INSERTED”, “SUBMITTED”, “TERMINATED”) and the individual documents.
- Error Handling: Joins to
IBY_TRANSACTION_ERRORSto display specific reasons why a document or payment failed validation.
Key Parameters
- Payment Process Request: The specific batch name.
- Payment Process Request Status: Filter by status (e.g., “Completed”, “Terminated”).
- Rejected or Failed Only: A useful flag to focus solely on exceptions.
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