Search Results ap_recurring_payments_all




Overview
Explore in AI Chat

Overview

The AP_RECURRING_PAYMENTS_ALL table is a core data object within the Oracle E-Business Suite Payables module (AP). It serves as the master repository for defining and storing the parameters of recurring payment schedules. These schedules automate the generation of periodic invoices for regular, fixed-amount obligations such as rent, leases, subscriptions, or loan payments. The table's role is to centralize the template information—including vendor details, amounts, payment terms, and accounting distributions—which the system uses to create actual invoice records (AP_INVOICES_ALL) at defined intervals. Its multi-org structure, indicated by the "_ALL" suffix, supports the storage of data across multiple operating units within a single installation.

Key Information Stored

The table stores the complete definition of a recurring payment template. Its primary key is RECURRING_PAYMENT_ID. Critical columns, as indicated by its foreign key relationships, define the template's core attributes. These include VENDOR_ID and VENDOR_SITE_ID to identify the supplier, INVOICE_CURRENCY_CODE and PAYMENT_CURRENCY_CODE for financial amounts, and SET_OF_BOOKS_ID for the accounting context. The template's financial coding is specified via ACCTS_PAY_CODE_COMBINATION_ID (the liability account) and DISTRIBUTION_SET_ID for detailed accounting lines. Operational controls are managed through columns like RECURRING_PAY_NUM (a unique identifier per vendor), BATCH_ID for grouping, HOLD_LOOKUP_CODE for approval controls, and AWT_GROUP_ID for automatic withholding tax. The table also holds scheduling and amount details such as payment terms, exchange rate type, and a link to purchase order lines (LINE_LOCATION_ID) for matched invoices.

Common Use Cases and Queries

The primary use case is the automated creation of periodic invoices via the "Create Recurring Invoices" process. Administrators and accountants query this table to audit schedules, troubleshoot generation issues, and report on upcoming payment obligations. Common SQL patterns include joining to vendor and site tables to list all active schedules and their details. For example, a report to show schedules for a specific vendor would filter on VENDOR_ID and join to PO_VENDORS and PO_VENDOR_SITES_ALL. Another critical query involves identifying schedules that failed to generate invoices by checking for templates without recent corresponding child records in AP_INVOICES_ALL via the RECURRING_PAYMENT_ID foreign key. Analysts also frequently query the table to review the accounting setup by joining to GL_CODE_COMBINATIONS and AP_DISTRIBUTION_SETS_ALL.

Related Objects

  • AP_INVOICES_ALL: The primary child table. Each generated invoice from a recurring schedule stores the parent RECURRING_PAYMENT_ID.
  • PO_VENDORS & PO_VENDOR_SITES_ALL: Provide supplier and site information for the VENDOR_ID and VENDOR_SITE_ID foreign keys.
  • GL_CODE_COMBINATIONS & AP_DISTRIBUTION_SETS_ALL: Define the accounting distributions (liability and expense accounts) for the recurring invoice.
  • AP_BATCHES_ALL, AP_HOLD_CODES, AP_AWT_GROUPS: Control processing features like batching, holds, and tax withholding for the generated invoices.
  • FND_CURRENCIES & GL_DAILY_CONVERSION_TYPES: Support the multi-currency and exchange rate definitions for the payment.
  • GL_SETS_OF_BOOKS_11I: Links the template to its financial reporting entity (Set of Books).