Search Results earliest_settlement_date




Overview
Explore in AI Chat

Overview

APPS.AP_APPLY_PREPAYS_V is a supplementary Oracle EBS view owned by the APPS schema and registered under FND Design Data as SQLAP.AP_APPLY_PREPAYS_V. Its purpose is to simplify forms coding within the Payables application by presenting prepayment application data in a denormalized, query-ready form. Oracle explicitly warns that this is a supplementary view used to simplify forms coding and that querying or altering data through it is not recommended, since its definition may change dramatically in subsequent minor or major releases. The view is therefore best treated as a read-only reporting and diagnostic surface, not as an integration interface.

The view exposes prepayment invoices together with the amount remaining to be applied, tax amount remaining, and associated purchasing, receiving, and vendor context. It is particularly relevant to the searched term earliest_settlement_date, which is exposed as a DATE column at the end of the projection list, immediately following RECEIPT_NUMBER.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, AP_APPLY_PREPAYS_V is defined over a substantial set of base objects accessed through APPS synonyms and views: AP_HOLDS, AP_HOLD_CODES, AP_INVOICES, AP_INVOICE_DISTRIBUTIONS_ALL, AP_INVOICE_LINES_ALL, PO_HEADERS_ALL, PO_LINE_LOCATIONS_ALL, PO_VENDORS (view), PO_VENDOR_SITES_ALL (view), RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and RCV_TRANSACTIONS. It also calls the package AP_PREPAY_UTILS_PKG and the FINANCIALS_SYSTEM_PARAMS_ALL and FND_GLOBAL packages.

The join graph is consistent with the column list: AP_INVOICES and AP_INVOICE_LINES_ALL supply the prepayment invoice and line attributes (PREPAY_NUMBER, PREPAY_LINE_NUMBER, INVOICE_AMOUNT, ACCOUNTING_DATE, PERIOD_NAME, SET_OF_BOOKS_ID); AP_INVOICE_DISTRIBUTIONS_ALL provides distribution-level accounting context; PO_HEADERS_ALL and PO_LINE_LOCATIONS_ALL supply PO_NUMBER, PO_HEADER_ID, PO_LINE_LOCATION_ID, and PO_DISTRIBUTION_ID; the RCV tables supply RECEIPT_NUMBER and RCV_TRANSACTION_ID; and PO_VENDORS and PO_VENDOR_SITES_ALL supply VENDOR_NAME, VENDOR_NUMBER, and VENDOR_SITE_CODE.

Key Columns

  • INVOICE_ID / PREPAY_NUMBER / INVOICE_DATE / INVOICE_AMOUNT — identify the prepayment invoice header.
  • PREPAY_LINE_NUMBER, PREPAY_AMOUNT_REMAINING, TAX_AMOUNT_REMAINING, AMOUNT — quantify the unapplied prepayment balance at line level, the values most often aggregated in reports.
  • ACCOUNTING_DATE, PERIOD_NAME, SET_OF_BOOKS_ID — accounting context for the prepayment.
  • VENDOR_ID, VENDOR_SITE_ID, VENDOR_NAME, VENDOR_NUMBER, VENDOR_SITE_CODE — supplier identification.
  • PO_HEADER_ID, PO_NUMBER, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID — purchasing linkage.
  • RCV_TRANSACTION_ID, RECEIPT_NUMBER, ORG_ID — receiving and operating unit context.
  • INVOICE_CURRENCY_CODE, PAYMENT_CURRENCY_CODE, PAYMENT_CROSS_RATE — currency conversion attributes.
  • EARLIEST_SETTLEMENT_DATE — the date on which the prepayment may first be settled; used to control or schedule application of the prepayment against a later standard invoice.

Common Use Cases and Queries

Typical use is to list unapplied prepayments available for application, or to inspect the earliest settlement timing for a given supplier, PO, or receipt.

SELECT prepay_number, invoice_id, vendor_name,
       prepay_amount_remaining, tax_amount_remaining,
       earliest_settlement_date
FROM   apps.ap_apply_prepays_v
WHERE  org_id = :p_org_id
AND    prepay_amount_remaining > 0
ORDER BY earliest_settlement_date;

For PO-level analysis, filter by PO_NUMBER or PO_HEADER_ID and join to standard Payables tables using INVOICE_ID. Because the view is not a supported interface, production code should generally read the underlying AP_INVOICES and AP_INVOICE_LINES_ALL tables directly, using this view only for ad-hoc investigation.