Search Results ap_pay_group




Overview
Explore in AI Chat

Overview

The AP_PAY_GROUP table is a core data object within the Oracle E-Business Suite Payables (AP) module. It serves as the master repository for defining and storing pay groups, which are logical groupings of payments used to streamline the payment processing workflow. The primary role of a pay group is to act as a key component within either a Payment Process Request Template or a specific Payment Process Request. These templates and requests are central to the Payables payment engine, enabling the automated selection, formatting, and creation of payments such as checks and electronic funds transfers. By organizing payments into distinct groups, the table facilitates controlled, batch-oriented payment processing and reporting.

Key Information Stored

While the full column list is not detailed in the provided metadata, the primary and foreign key relationships indicate the critical data elements. The table's primary key is PAY_GROUP_ID, which uniquely identifies each pay group record. Two significant foreign key columns define the table's relationships: TEMPLATE_ID links the pay group to its parent template in the AP_PAYMENT_TEMPLATES table, and CHECKRUN_ID links it to a specific payment process request (historically called a check run) in the AP_INV_SELECTION_CRITERIA_ALL table. Additional columns likely store descriptive information such as the pay group name, status, associated payment method, currency, and control totals for the grouped payments.

Common Use Cases and Queries

A primary use case is generating reports on payment batches prior to final submission. Analysts may query pay groups to review the total value and count of invoices selected for payment. A common SQL pattern involves joining AP_PAY_GROUP to payment detail tables to summarize activity. For troubleshooting, one might query pay groups associated with a failed or held payment process request. Sample queries include identifying pay groups for a specific template or retrieving details for a particular payment batch run.

  • Listing all pay groups within a specific template: SELECT pay_group_id, name FROM ap_pay_group WHERE template_id = <template_id>;
  • Summarizing payment amounts by pay group for a request: SELECT pg.pay_group_id, SUM(ila.amount) total_amount FROM ap_pay_group pg JOIN ap_invoice_selection_criteria_all isc ON pg.checkrun_id = isc.checkrun_id JOIN ap_invoice_lines_all ila ON isc.invoice_id = ila.invoice_id WHERE pg.checkrun_id = <request_id> GROUP BY pg.pay_group_id;

Related Objects

The AP_PAY_GROUP table maintains defined foreign key relationships with two other key Payables tables, as documented in the ETRM metadata.

  • AP_PAYMENT_TEMPLATES: A pay group is associated with a payment template via the TEMPLATE_ID column. This relationship defines the configuration and rules under which the pay group operates when used in a template.
  • AP_INV_SELECTION_CRITERIA_ALL: A pay group is linked to a specific payment process request (or check run) via the CHECKRUN_ID column. This table stores the invoices selected for payment within that request, and the pay group acts as an organizing entity for those payments.

The table is also intrinsically related to payment execution objects like AP_CHECKS_ALL and AP_PAYMENT_SCHEDULES_ALL, typically accessed via the invoice selection criteria or payment instructions generated from the pay group.