Search Results future_pay_posted_flag

Overview

AP_INVOICE_PAYMENTS_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite (validated in 12.1.1 and 12.2.2). It presents a denormalized, reporting-friendly projection of invoice payment activity from the Oracle Payables module. The view joins the core invoice payment transaction table (AP_INVOICE_PAYMENTS) to invoice, payment, payment schedule, accounting batch, and payment method reference data, exposing payment amounts, discount activity, exchange rate information, and accounting posting flags in a single logical row set. Its principal role is to support Payables reporting and integration: rather than requiring consumers to navigate the normalized distribution and payment schedule structures, the view surfaces one row per invoice payment line with the join context already resolved. This makes it directly relevant to reconciliation, cash posting analysis, and third-party payment feeds.

Underlying Base Objects

The view is defined over the following documented base objects:

• AP_INVOICE_PAYMENTS (SYNONYM) — the driving table; each view row corresponds to a payment line recorded against an invoice.
• AP_INVOICES_ALL (SYNONYM) — invoice header context (invoice number, supplier, currency).
• AP_CHECKS_ALL (SYNONYM) — payment document information, including payment number and bank account details.
• AP_PAYMENT_SCHEDULES_ALL (SYNONYM) — scheduled payment amounts and due dates used for joining invoice distributions to payments.
• AP_LOOKUP_CODES (VIEW) — lookup descriptions such as bank account type.
• GL_JE_BATCHES (SYNONYM) and GL_SETS_OF_BOOKS (VIEW) — journal batch and ledger context for accounting postings.
• IBY_PAYMENT_METHODS_VL (VIEW) — payment method descriptions used for reporting.
• FND_GLOBAL (PACKAGE) — supplies session context (user, responsibility, org) for security and defaults.

The view therefore sits above the transactional Payables tables and enriches them with both Payables and General Ledger reference data in a single queryable object.

Key Columns

The view exposes columns directly mapped from AP_INVOICE_PAYMENTS. Notable columns include:

• INVOICE_PAYMENT_ID — the primary key of the underlying payment line.
• INVOICE_ID — foreign key to AP_INVOICES_ALL; ties the payment back to its invoice.
• CHECK_ID — foreign key to AP_CHECKS_ALL; identifies the payment document.
• AMOUNT, INVOICE_BASE_AMOUNT, PAYMENT_BASE_AMOUNT — payment amount, invoice amount in ledger currency, and payment amount in ledger currency respectively; essential for reconciliation across currencies.
• DISCOUNT_TAKEN and DISCOUNT_LOST — early-payment discount amounts realized or forgone.
• EXCHANGE_RATE, EXCHANGE_RATE_TYPE, EXCHANGE_DATE — currency conversion parameters applied to the payment.
• ACCOUNTING_DATE and PERIOD_NAME — the accounting date and GL period for the payment distribution.
• POSTED_FLAG, ACCRUAL_POSTED_FLAG, CASH_POSTED_FLAG, FUTURE_PAY_POSTED_FLAG — posting status flags for the accrual, cash, and future pay accounting events. These are frequently queried (for example, when validating whether a payment has been transferred to GL).
• JE_BATCH_ID and CASH_JE_BATCH_ID — journal batch identifiers used to trace the payment distribution to GL_JE_BATCHES.
• BANK_ACCOUNT_NUM, BANK_ACCOUNT_TYPE, BANK_NUM — bank account attributes for reporting/disbursement reconciliation.
• PAYMENT_NUM and INVOICE_PAYMENT_ID columns support direct search by payment number.

Common Use Cases and Queries

Typical scenarios include invoice-to-payment reconciliation, unresolved accounting transfer analysis, audit of discounts taken or lost, and supplier payment history reporting. The view is also a convenient source for integrations requiring joined invoice/payment document attributes.

Sample query — payment summary by invoice:

SELECT invoice_id, payment_num, amount, discount_taken, posted_flag
FROM   apps.ap_invoice_payments_v
WHERE  invoice_id = :p_invoice_id;

Sample query — payments pending GL transfer:

SELECT payment_num, invoice_id, amount, accounting_date
FROM   apps.ap_invoice_payments_v
WHERE  posted_flag = 'N'
AND    accounting_date >= :p_start_date;

Sample query — discount audit:

SELECT invoice_id, payment_num, discount_taken, discount_lost
FROM   apps.ap_invoice_payments_v
WHERE  discount_lost > 0
ORDER  BY discount_lost DESC;

Because the view spans several base tables, queries should filter on indexed columns such as INVOICE_ID, PAYMENT_NUM, or ACCOUNTING_DATE to avoid full-table scans on large Payables volumes.