Search Results iby_pay_service_requests




Overview
Explore in AI Chat

Overview

The IBY_PAY_SERVICE_REQUESTS table is a core data object within the Oracle E-Business Suite (EBS) Payments (IBY) module, specifically in versions 12.1.1 and 12.2.2. It serves as the master repository for payment process requests. A payment process request is a foundational entity created when a user or an automated process initiates a payment batch, typically through the 'Build Payments' program. This request encapsulates the intent to process a set of payment instructions for a specific combination of parameters, such as payment method, bank account, and payment date. The table acts as a central hub, linking the initial request from a source product like Payables (AP) to the subsequent detailed payment instructions and individual payment documents generated during the payment execution flow.

Key Information Stored

The table's primary key, PAYMENT_SERVICE_REQUEST_ID, uniquely identifies each payment batch request. Critical foreign key columns establish essential relationships that define the request's parameters. The PAYMENT_PROFILE_ID links to IBY_ACCT_PMT_PROFILES_B, storing the payment method and related rules. The INTERNAL_BANK_ACCOUNT_ID references CE_BANK_ACCOUNTS, specifying the bank account from which funds will be disbursed. Other significant columns likely include data tracking the request's status (e.g., NEW, SUBMITTED, FORMATTED), the request date, the requested payment date, the originating user and application, and the total amount or count of documents included in the request. This structure provides a complete audit trail for the initiation of every payment batch.

Common Use Cases and Queries

This table is pivotal for payment process auditing, troubleshooting, and reporting. Common use cases include tracking the status and history of payment batches, identifying the source of specific payments, and reconciling payment initiation data. A typical query might join IBY_PAY_SERVICE_REQUESTS to related payment tables to analyze batch performance.

  • Batch Summary Report: SELECT psr.payment_service_request_id, psr.creation_date, COUNT(pmt.payment_id) AS payment_count FROM iby_pay_service_requests psr, iby_payments_all pmt WHERE psr.payment_service_request_id = pmt.payment_service_request_id GROUP BY psr.payment_service_request_id, psr.creation_date;
  • Troubleshooting a Specific Request: SELECT * FROM iby_pay_service_requests WHERE payment_service_request_id = &req_id;
  • Linking to Source Documents: Queries often join through IBY_DOCS_PAYABLE_ALL or IBY_PAYMENTS_ALL to connect a batch request back to the original invoices or payments for end-to-end visibility.

Related Objects

As indicated by its foreign key relationships, IBY_PAY_SERVICE_REQUESTS is a central parent table within the Payments schema. Key dependent child tables, which store the detailed outcomes of the request, include IBY_DOCS_PAYABLE_ALL (payable documents selected for payment), IBY_PAY_INSTRUCTIONS_ALL (created payment instructions), and IBY_PAYMENTS_ALL (individual payment records). The IBY_PAYMENTS_H and IBY_DOCUMENTS_PAYABLE_H history tables also reference it, preserving the link to the original request for archived data. Furthermore, it references master data tables: CE_BANK_ACCOUNTS for the disbursement bank account and IBY_ACCT_PMT_PROFILES_B for the payment method profile. This network of relationships underscores the table's role as the cornerstone of the payment batch lifecycle.