Results for “ap_recurring_payments_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AP_RECURRING_PAYMENTS_V is a VALID view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Payables (AP) product family and exposes recurring payment templates — the periodic invoice definitions that Payables uses to generate repeat invoices automatically according to a defined schedule. The view presents one row per recurring payment definition, combining payment scheduling attributes with supplier, bank, payment method, terms, and purchasing context resolved through joins to their respective base objects.

Because it consolidates scheduling and payment-detail attributes into a single queryable structure, the view is commonly used in reporting, data extraction, and integration routines that need to inspect recurring payment setups without navigating the underlying normalized Payables tables. The view text selects directly from AP_RECURRING_PAYMENTS (aliased ARP) and uses ARP.ROWID as ROW_ID, confirming a near row-for-row projection with supporting joins.

Underlying Base Objects

The documented base objects underlying AP_RECURRING_PAYMENTS_V include the following:

• AP_RECURRING_PAYMENTS (SYNONYM) — the primary table supplying the recurring payment definition rows.
• AP_AWT_GROUPS (SYNONYM) — withholding tax group assignment.
• AP_DISTRIBUTION_SETS_ALL (SYNONYM) — default distribution set for invoice lines.
• AP_LOOKUP_CODES (VIEW) and FND_LOOKUPS (VIEW) — code and lookup value resolution.
• AP_SUPPLIERS (SYNONYM) and AP_SUPPLIER_SITES_ALL (SYNONYM) — supplier and supplier site context.
• AP_TERMS (SYNONYM) — payment terms used for scheduled due dates.
• CE_BANK_BRANCHES_V (VIEW), IBY_EXT_BANK_ACCOUNTS (SYNONYM), IBY_DELIVERY_CHANNELS_VL (VIEW), IBY_PAYMENT_METHODS_VL (VIEW), and IBY_PAYMENT_REASONS_VL (VIEW) — banking, payment method, delivery channel, and payment reason details.
• PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_RELEASES_ALL (SYNONYMS) — purchasing document context for recurring payments tied to purchase orders.
• FND_GLOBAL (PACKAGE) — typically used to resolve organization or user context (for example, ORG_ID).

The heavy dependency on the IBY (payments) views reflects the R12 payment architecture, where payment methods, bank accounts, and delivery channels were externalized from AP into the IBY schema.

Key Columns

• ROW_ID — the underlying AP_RECURRING_PAYMENTS ROWID.
• ACCOUNTING_DATE — accounting date applied to generated invoices.
• FIRST_PERIOD / FIRST_PERIOD_NUM / NEXT_PERIOD — the starting period and the current next period for generation.
• NUM_OF_PERIODS / NUM_OF_PERIODS_REM — total periods defined and periods remaining.
• INCREMENT_PERCENT — percentage escalation applied to the recurring amount.
• NEXT_PAYMENT / EXPIRY_DATE — the next scheduled payment date and the template expiry date.
• AMOUNT_APPLICABLE_TO_DISCOUNT / CONTROL_AMOUNT / AUTHORIZED_TOTAL — amount controls for the recurring template.
• INVOICE_CURRENCY_CODE / PAYMENT_CURRENCY_CODE / EXCHANGE_RATE / EXCHANGE_RATE_TYPE / EXCHANGE_DATE / PAYMENT_CROSS_RATE — currency and conversion attributes.
• PAY_GROUP_LOOKUP_CODE / PAYMENT_METHOD_LOOKUP_CODE / HOLD_LOOKUP_CODE / HOLD_REASON — payment grouping, method, and hold information.
• ACCTS_PAY_CODE_COMBINATION_ID / DISTRIBUTION_SET_ID / AWT_GROUP_ID — accounting and withholding configuration.
• EXCLUSIVE_PAYMENT_FLAG / PAID_FLAG1 / PAID_FLAG2 — status indicators for exclusivity and payment completion.
• ORG_ID — the operating unit (multi-org) identifier.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard descriptive flexfield (DFF) context and columns.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — standard WHO audit columns.

The user's search term "rec_pay_period_type" relates to recurring payment period typing. In the underlying model, period behavior is governed by columns such as FIRST_PERIOD, FIRST_PERIOD_NUM, NEXT_PERIOD, NUM_OF_PERIODS, and NUM_OF_PERIODS_REM, which together determine how the period type drives generation cadence.

Common Use Cases and Queries

Typical uses include auditing active recurring payment templates, validating remaining periods and expiry, and extracting scheduling data for reporting. A basic query follows:

SELECT ROW_ID,
       FIRST_PERIOD,
       NEXT_PERIOD,
       NUM_OF_PERIODS,
       NUM_OF_PERIODS_REM,
       INCREMENT_PERCENT,
       NEXT_PAYMENT,
       EXPIRY_DATE
FROM   APPS.AP_RECURRING_PAYMENTS_V
WHERE  ORG_ID = :p_org_id
AND    NVL(NUM_OF_PERIODS_REM,0) > 0;

To reconcile templates nearing expiry or exhaustion of periods:

SELECT ROW_ID, NEXT_PAYMENT, EXPIRY_DATE, NUM_OF_PERIODS_REM
FROM   APPS.AP_RECURRING_PAYMENTS_V
WHERE  EXPIRY_DATE IS NOT NULL
AND    EXPIRY_DATE <= SYSDATE + 30;

Because the view exposes ORG_ID and the ATTRIBUTE1–15 DFF columns, it is frequently joined to AP_SUPPLIERS, AP_TERMS, and IBY_PAYMENT_METHODS_VL in custom reports and interfaces to present a full picture of recurring payment configuration.