Search Results ap_view_prepays_fr_prepay_v




Overview
Explore in AI Chat

Overview

AP_VIEW_PREPAYS_FR_PREPAY_V is a Payables (AP) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name and definition indicate that it surfaces prepayment-related invoice line activity associated with France localization requirements, and the ETRM records it with a status of VALID and a description of "Retrofitted." In practice, the view consolidates data about prepayment application lines — the negative-amount invoice lines generated when a prepayment is applied to a standard invoice — so that reporting, reconciliation, and localization extracts can retrieve prepay application detail without navigating the underlying base tables directly.

The view is primarily a read-only reporting and integration object. It joins invoice headers, invoice lines, supplier data, purchasing data, and receiving data so that a single query can return the applied prepayment amount, the tax applied, and the associated document references.

Underlying Base Objects

The documented base objects underlying this view are:

The primary driving table is AP_INVOICE_LINES, filtered to rows where AMOUNT is negative, DISCARDED_FLAG is not Y, and LINE_TYPE_LOOKUP_CODE equals 'PREPAY'. The view joins AP_INVOICES_ALL on INVOICE_ID, with an invoice type restriction excluding PREPAYMENT, CREDIT, and DEBIT invoice types. The definition is a UNION of at least two branches: the first retrieves prepay application lines tied to invoices, while the second derives recoupment amounts via AP_MATCHING_UTILS_PKG.GET_RECOUP_AMT_PER_P. The PO and receiving tables are joined with Oracle outer join syntax, so missing PO or receipt references do not eliminate rows.

Key Columns

Because the user searched for "invoice_line_number," the most directly relevant column is INVOICE_LINE_NUMBER, which corresponds to AIL.LINE_NUMBER and identifies the invoice line on the invoice. A second line-number column, PREPAY_LINE_NUMBER, identifies the line on the originating prepayment invoice, while PREPAY_INVOICE_ID (also aliased PREPAY_ID) identifies that prepayment invoice.

Common Use Cases and Queries

Typical uses include reconciling prepayments applied against standard invoices, reporting prepay application and tax amounts by accounting period, and extracting France-specific prepayment data. A simple query to list applied prepayments with line numbers would be:

  • SELECT INVOICE_NUM, INVOICE_LINE_NUMBER, PREPAY_INVOICE_ID, PREPAY_LINE_NUMBER, PREPAY_AMOUNT_APPLIED, TAX_AMOUNT_APPLIED FROM APPS.AP_VIEW_PREPAYS_FR_PREPAY_V WHERE INVOICE_LINE_NUMBER = :line_number;
  • SELECT VENDOR_NAME, VENDOR_NUMBER, PERIOD_NAME, SUM(PREPAY_AMOUNT_APPLIED) FROM APPS.AP_VIEW_PREPAYS_FR_PREPAY_V GROUP BY VENDOR_NAME, VENDOR_NUMBER, PERIOD_NAME;
  • SELECT INVOICE_NUM, PREPAY_INVOICE_ID, PO_NUMBER, RECEIPT_NUMBER, PREPAY_AMOUNT_APPLIED FROM APPS.AP_VIEW_PREPAYS_FR_PREPAY_V WHERE ORG_ID = :org_id;

Because the view already encapsulates the prepay line filter, join conditions, outer joins to purchasing and receiving, and the recoupment calculation, it reduces the complexity of writing equivalent SQL against the base tables. Users should nonetheless be aware of the negative-amount and line-type filters, which mean only applied prepayment activity is returned, and of the UNION structure, which can produce multiple rows per invoice line where recoupment logic applies.