Results for “inv”

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

Overview

The APPS.AP_VIEW_PREPAYS_V view is a Payables module reporting object that consolidates prepayment application activity across invoices, invoice lines, purchase orders, and receiving records. Prepayments in Oracle Payables are advances issued to a supplier that are later applied against standard invoices; this view presents both sides of that relationship, exposing the prepayment invoice line, the applied amount, remaining unapplied balances, and the associated purchasing and receipt context. Its status is VALID in both 12.1.1 and 12.2.2, and it is owned by the APPS schema.

The view is not part of the core transactional table set; it is a read-only reporting and integration construct intended for inquiry, extract, and reconciliation purposes. Because it joins AP, PO, and RCV data in a single result set, it is particularly useful for buyers, Payables analysts, and technical teams building supplier advance reports or data warehouse feeds.

Underlying Base Objects

AP_VIEW_PREPAYS_V is defined over the following documented objects:

• AP_INVOICES_ALL — supplies the prepayment invoice header, vendor, vendor site, and currency.
• AP_INVOICE_LINES — the primary driving table, filtered on LINE_TYPE_LOOKUP_CODE = 'PREPAY' and negative amounts.
• AP_INVOICE_DISTRIBUTIONS — referenced for distribution-level prepayment application data via the second UNION branch.
• PO_VENDORS and PO_VENDOR_SITES_ALL — provide vendor name, vendor number, and vendor site code.
• PO_HEADERS_ALL — supplies the purchase order number where a prepayment is linked to a PO.
• RCV_TRANSACTIONS, RCV_SHIPMENT_HEADERS, and RCV_SHIPMENT_LINES — provide the receipt number and receiving context where a prepayment is associated with a receipt.
• AP_PREPAY_UTILS_PKG and AP_MATCHING_UTILS_PKG — PL/SQL packages invoked for remaining prepayment amount calculation and matching logic.
• FND_GLOBAL — provides session context such as organization and user environment values.

The view text shows a UNION of at least two branches: the first selects prepay invoice lines directly, and the second correlates an invoice line to its originating prepay line. Outer joins to PO and RCV objects mean PO and receipt columns can be null when a prepayment is not tied to purchasing activity.

Key Columns

• ROW_ID — the AP_INVOICE_LINES row identifier, useful for deduplication or drill-down.
• INVOICE_ID, INVOICE_LINE_NUMBER — the applied (target) invoice and line.
• PREPAY_INVOICE_ID, PREPAY_LINE_NUMBER — the source prepayment invoice and line.
• PREPAY_AMOUNT_APPLIED — the amount of prepayment applied, derived as (-1) * (AMOUNT - INCLUDED_TAX_AMOUNT).
• TAX_AMOUNT_APPLIED — tax component of the applied amount, including recoverable and non-recoverable tax, nullified when zero.
• PREPAY_AMOUNT_REMAINING — remaining unapplied prepayment balance, returned by AP_PREPAY_UTILS_PKG.GET_LINE_PREPAY_AMT_REMAINING.
• ACCOUNTING_DATE, PERIOD_NAME, SET_OF_BOOKS_ID — accounting and ledger context.
• PREPAY_NUMBER, VENDOR_ID, VENDOR_NAME, VENDOR_NUMBER, VENDOR_SITE_CODE — supplier identifiers.
• PO_NUMBER, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID — purchasing linkage.
• RECEIPT_NUMBER, RCV_TRANSACTION_ID — receiving linkage.
• INVOICE_CURRENCY_CODE, ORG_ID, INVOICE_INCLUDES_PREPAY_FLAG — currency, operating unit, and prepay indicator.

Common Use Cases and Queries

Typical uses include reconciling prepayment applications per supplier, identifying prepayments with remaining balances, and tracing prepayments to PO or receipt transactions. A representative query for open prepayment balances is:

SELECT prepay_number, vendor_name, prepay_amount_applied, prepay_amount_remaining, invoice_currency_code FROM ap_view_prepays_v WHERE prepay_amount_remaining > 0 ORDER BY vendor_name, prepay_number;

A second common query groups activity by supplier and period:

SELECT vendor_name, period_name, SUM(prepay_amount_applied) applied, SUM(prepay_amount_remaining) remaining FROM ap_view_prepays_v GROUP BY vendor_name, period_name;

Because the view enforces the PREPAY line type and non-discarded filter internally, consumers do not need to re-apply those predicates, though adding ORG_ID and SET_OF_BOOKS_ID filters is recommended for multi-org and multi-ledger environments.