Search Results discount_lost




Overview
Explore in AI Chat

Overview

APFV_AP_INVOICE_PAYMENTS is a business view owned by the APPS schema within the Oracle Payables (AP) product. Registered in ETRM with the description "Business view," it exposes the association between invoices and their payments as recorded in Oracle E-Business Suite. Each row represents one invoice payment record — the link between a specific invoice and a specific payment — enriched with denormalized attributes drawn from the related invoice, payment (check), and set of books records. Unlike an operational form or a base table accessed directly by concurrent programs, this view is intended for reporting, inquiry, and integration scenarios where a flattened, human-readable projection of the invoice-to-payment relationship is required.

Underlying Base Objects

The view text is defined over five documented base objects referenced through APPS synonyms: AP_INVOICE_PAYMENTS, AP_CHECKS_ALL, AP_INVOICES_ALL, AP_PAYMENT_SCHEDULES_ALL, and the GL_SETS_OF_BOOKS view. AP_INVOICE_PAYMENTS (aliased as AIP) supplies the driving rows and the core payment-against-invoice attributes. AP_CHECKS_ALL (aliased as AC) supplies the payment instrument attributes, including the check number, check date, check amount, currency, and the bank account name. AP_INVOICES_ALL (aliased as AI) contributes invoice header information such as invoice number, invoice date, invoice amount, amount paid, and description. AP_PAYMENT_SCHEDULES_ALL (aliased as APS) is referenced for identifiers such as the external bank account. GL_SETS_OF_BOOKS provides the set of books name through GSOB.NAME. The view text also carries UNIQUE ATTRIBUTES and REGULAR ATTRIBUTES annotations, a pattern typical of Oracle ETRM-designated business views, and embeds lookup resolution directives (for example, resolving INVOICE_PAYMENT_TYPE and CHECK_TYPE against AP_LOOKUP_CODES).

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling invoice payments to checks, listing payments by bank account type, auditing discount activity, and feeding downstream reporting where a single flattened row per invoice-payment pairing is preferable to multi-table joins. A representative query using the searched attribute is:

  • SELECT INVOICE_NUMBER, PAYMENT_NUMBER, BANK_ACCOUNT_NUMBER, BANK_ACCOUNT_TYPE, CHECK_NUMBER, CHECK_DATE, AMOUNT FROM APPS.APFV_AP_INVOICE_PAYMENTS WHERE BANK_ACCOUNT_TYPE = :p_type;
  • SELECT INVOICE_NUMBER, PAYMENT_NUMBER, CHECK_STATUS, CHECK_AMOUNT, SET_OF_BOOKS_NAME FROM APPS.APFV_AP_INVOICE_PAYMENTS WHERE CHECK_DATE BETWEEN :from_date AND :to_date;

Because the view resolves lookups and foreign keys internally, report authors avoid writing their own joins to AP_LOOKUP_CODES, AP_CHECKS_ALL, and AP_INVOICES_ALL, reducing maintenance overhead and keeping reporting logic consistent with Oracle's delivered metadata.