Search Results date_reported

Overview

AP_INVOICE_PREPAYS_V is a Payables (AP) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes prepayment invoice information joined with supplier and supplier site attributes, and it is documented as a legacy reporting object originally introduced in Release 10SC. The view is defined as a UNION of two queries, both anchored on the AP_INVOICE_PREPAYS and AP_INVOICES tables. The first branch returns records flagged internally as 'PREPAYMENT' (the prepayment invoices themselves and the amounts applied against them), while the second branch returns rows flagged as 'INVOICE' under a literal PREPAYMENT_FLAG value, exposing the target invoices against which prepayments can be applied. The embedded comments indicate the view was designed as a base table for Oracle Forms 4.5 programs in Release 10G, specifically the Apply Prepayment form (APXIWPAA). In modern EBS releases it remains available for ad hoc reporting and legacy integrations, though Oracle's standard application logic has largely migrated to set-based APIs and newer views.

Underlying Base Objects

The documented referenced objects include AP_INVOICES (SYNONYM), AP_INVOICE_PREPAYS (SYNONYM), AP_PAYMENT_SCHEDULES (SYNONYM), the FND_GLOBAL package, and the PO_VENDORS and PO_VENDOR_SITES views. The view text joins AP_INVOICE_PREPAYS (alias AIPP) to AP_INVOICES (alias AI) on AIPP.PREPAY_ID = AI.INVOICE_ID, and then to PO_VENDORS (alias PV) on AI.VENDOR_ID = PV.VENDOR_ID and PO_VENDOR_SITES (alias PVS) on AI.VENDOR_SITE_ID = PVS.VENDOR_SITE_ID. The UNION operator concatenates the prepayment branch with the invoice branch, so callers may filter on PREPAYMENT_FLAG to isolate either side. Because AP_INVOICES and AP_INVOICE_PREPAYS are accessed through APPS synonyms, the view resolves to the AP base tables at runtime. Note that PO_VENDORS and PO_VENDOR_SITES are themselves views in later releases, resolving to the supplier tables formerly named PO_VENDORS.

Key Columns

• PAYMENT_CURRENCY_CODE — sourced from AI.PAYMENT_CURRENCY_CODE on AP_INVOICES; identifies the currency in which the invoice and prepayment are paid. This is the column most often queried for currency-based reporting and reconciliations.
• PAY_CURR_INVOICE_AMOUNT — computed as NVL(AI.PAY_CURR_INVOICE_AMOUNT, AI.INVOICE_AMOUNT); returns the invoice amount expressed in the payment currency, defaulting to the invoice amount when the pay-currency figure is null.
• PREPAYMENT_AMOUNT_APPLIED — the portion of a prepayment that has been applied, drawn from AP_INVOICE_PREPAYS.
• PREPAY_ID — the invoice identifier of the prepayment record; joins back to AP_INVOICES.INVOICE_ID.
• INVOICE_ID, INVOICE_NUM, INVOICE_DATE, DESCRIPTION — core invoice attributes from AP_INVOICES.
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_NAME, VENDOR_NUMBER (SEGMENT1), VENDOR_SITE_CODE — supplier and supplier site identification from PO_VENDORS and PO_VENDOR_SITES.
• VENDOR_PREPAY_AMOUNT — prepayment amount held at the supplier level.
• SET_OF_BOOKS_ID — the ledger context for the invoice.
• ORG_ID — the operating unit context, supporting multi-org security filtering.
• PREPAYMENT_FLAG — literal discriminator; 'PREPAYMENT' for the first UNION branch and 'INVOICE' for the second.
• ROW_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, DATE_REPORTED — standard WHO columns and row locator used by Forms and auditing.

Common Use Cases and Queries

Typical uses include identifying unapplied prepayments by supplier, reconciling prepayment balances in the payment currency, and driving the Apply Prepayment form. Where multi-org is enabled, filter by ORG_ID to respect operating unit security. A representative query listing applied prepayments and their payment currency follows:

• SELECT invoice_num, vendor_name, payment_currency_code, prepayment_amount_applied FROM ap.ap_invoice_prepays_v WHERE prepayment_flag = 'PREPAYMENT' AND org_id = :p_org_id;
• SELECT vendor_number, vendor_site_code, invoice_num, pay_curr_invoice_amount FROM ap.ap_invoice_prepays_v WHERE payment_currency_code = 'USD' AND prepayment_flag = 'INVOICE';
• SELECT prepay_id, SUM(prepayment_amount_applied) applied FROM ap.ap_invoice_prepays_v GROUP BY prepay_id;

Because the object is a view, it is read-only and should not be used for DML; write operations must target the underlying AP_INVOICES and AP_INVOICE_PREPAYS tables or, preferably, the supported Payables APIs.