Search Results invoice_approved_amount




Overview
Explore in AI Chat

Overview

APPS.APFV_AP_INVOICES is a Business Intelligence System (BIS) view in the Oracle E-Business Suite Payables application, owned by the APPS schema and registered under FND Design Data SQLAP.APFV_AP_INVOICES. It presents invoice information — documents containing the details of charges to be remitted to or deducted from a supplier payment — in a flattened, denormalized form intended for reporting and analytical consumption. Unlike purely transactional tables, BIS views such as this one render coded values into human-readable descriptions through _LA (lookup attribute) columns, which simplifies ad hoc querying and downstream extract-transform-load processes. The view is documented as VALID in both 12.1.1 and 12.2.2, and because it carries no date-effective or multi-org partitioning semantics of its own, it is typically used as a convenience layer over the invoice entity for operational reporting, reconciliation, and integration extracts.

The user search term "invoice_posting_status" corresponds directly to the INVOICE_POSTING_STATUS column exposed by this view, one of its most frequently queried attributes.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, APFV_AP_INVOICES is defined over a single referenced base object: the synonym AP_INVOICES, which resolves to the AP.AP_INVOICES table (alias AP_INVOICES_ALL in multi-org contexts). The view therefore inherits the core invoice record — invoice header amounts, dates, vendor identifiers, approval and payment attributes — and layers on translations. The _LA columns (for example _LA:SOURCE_DESCRIPTON, _LA:INVOICE_TYPE_DESCRIPTION, and _LA:PMT_STATUS_DESCRIPTION) are populated from Oracle Application Object Library lookup values, while _DF and _DF:GLBL are descriptive flexfield segments that would otherwise require a separate join to the flexfield tables. This dependency structure means the view is sensitive to changes in the base synonym and to lookup configuration in the applications schema.

Key Columns

Common Use Cases and Queries

The view is commonly used to report unposted invoices, to reconcile Payables to GL, and to feed data warehouses where decoded descriptions are preferred over raw codes. A typical query filters on posting status and joins supplier and currency references:

SELECT invoice_number, invoice_date, vendor_id, invoice_currency_code, invoice_functional_amount, invoice_posting_status, _LA:invoice_type_description, _LA:pmt_status_description FROM apps.apfv_ap_invoices WHERE invoice_posting_status = 'UNPOSTED' AND invoice_date >= :from_date AND invoice_date < :to_date ORDER BY invoice_date;

Analysts also aggregate approved balances by vendor and currency, or count invoices by posting and payment status to monitor period-end close. Because the view is read-only and backed by the AP_INVOICES synonym, it is safe for reporting workloads; for transactional updates, the underlying base table must be used.