Search Results invoice_functional_amount

Overview

APBV_AP_INVOICES is a business view in the Oracle E-Business Suite Payables (AP) module, owned by the APPS schema and documented as VALID in both release 12.1.1 and 12.2.2. The view presents a curated, read-only projection of invoice header data drawn from AP_INVOICES, intended primarily for reporting, integration, and Oracle Business Intelligence (DBI) consumption rather than for transactional processing. Its defining characteristic is that it exposes business-friendly column names — INVOICE_DESCRIPTION, INVOICE_NUMBER, INVOICE_ENTERED_AMOUNT, INVOICE_POSTING_STATUS — mapped onto the underlying AP_INVOICES attributes such as DESCRIPTION, INVOICE_NUM, INVOICE_AMOUNT, and POSTING_STATUS. The view text confirms the read-only nature through the WITH READ ONLY clause, which prevents DML through the view and reinforces its role as a query-only interface.

Because AP_INVOICES is a wide, denormalized table with legacy naming conventions, APBV_AP_INVOICES provides an abstraction that improves readability for downstream consumers and isolates them from certain underlying naming changes — the inline comment marking PAYMENT_METHOD_CODE as changed for DBI illustrates that this view has been adapted to support the Payables/Procurement analytics schema.

Underlying Base Objects

The view is defined over a single documented base object, the AP_INVOICES synonym in the APPS schema, which resolves to the AP.AP_INVOICES table. The ETRM metadata for 12.2.2 lists the referenced base object explicitly as AP_INVOICES (SYNONYM), confirming there is no join, union, or aggregation logic. Every row in APBV_AP_INVOICES corresponds one-to-one with a row in AP_INVOICES, filtered only by whatever predicate the caller applies. Consequently, the view inherits the full row population of the invoice header table, including cancelled, unapproved, and fully paid invoices. No security predicate is embedded in the view text, so any access restriction is applied by the caller or by Oracle application-level security rather than by the view itself.

Key Columns

• INVOICE_ID — Primary key of the invoice, the join key to distributions, lines, payments, and holds.
• INVOICE_DESCRIPTION — Maps to AP_INVOICES.DESCRIPTION and carries the free-text description entered by the user; this is the column most relevant to searches framed around invoice description.
• INVOICE_NUMBER — The supplier-facing invoice number stored in INVOICE_NUM.
• INVOICE_ENTERED_AMOUNT / INVOICE_FUNCTIONAL_AMOUNT — Invoice amount in the entered currency and the ledger (functional) currency respectively.
• INVOICE_CURRENCY_CODE / PAYMENT_CURRENCY_CODE — Transaction and payment currencies, enabling currency-conversion reporting.
• INVOICE_POSTING_STATUS — Accounting status of the invoice (for example, unposted or posted).
• PAYMENT_STATUS — Indicates whether the invoice is unpaid, partially paid, or fully paid.
• INVOICE_APPROVED_AMOUNT / MANUALLY_APPROVED_STATUS — Approval amounts and status, supporting approval-cycle reporting.
• INVOICE_CANCELED_AMOUNT / INVOICE_CANCELED_DATE — Cancellation details for reconciliation.
• VENDOR_SITE_ID / TERMS_ID / BATCH_ID — Foreign references to supplier site, payment terms, and invoice batch.
• INVOICE_DATE / INVOICE_RECEIVED_DATE — Invoice date and the date the invoice was received.
• INV_TO_FUNCTIONAL_EXCH_RATE / INV_TO_PMT_RATE — Exchange rates used for functional-currency and payment-currency conversion.

Common Use Cases and Queries

The view is typically used for invoice listings, aging and approval reporting, and extract programs feeding a data warehouse. A straightforward query retrieving invoice descriptions and amounts for a period might read:

• SELECT INVOICE_NUMBER, INVOICE_DESCRIPTION, INVOICE_ENTERED_AMOUNT, INVOICE_CURRENCY_CODE, INVOICE_DATE FROM APPS.APBV_AP_INVOICES WHERE INVOICE_DESCRIPTION LIKE '%service%';
• SELECT VENDOR_SITE_ID, COUNT(*), SUM(INVOICE_ENTERED_AMOUNT) FROM APPS.APBV_AP_INVOICES WHERE INVOICE_POSTING_STATUS = 'UNPOSTED' GROUP BY VENDOR_SITE_ID;
• SELECT INVOICE_ID, INVOICE_NUMBER, PAYMENT_STATUS, INVOICE_APPROVED_AMOUNT FROM APPS.APBV_AP_INVOICES WHERE INVOICE_DATE BETWEEN :from_date AND :to_date;

Because the view exposes INVOICE_ID, it can serve as the driving query for drill-down into AP_INVOICE_DISTRIBUTIONS_ALL or AP_INVOICE_PAYMENTS_ALL. Reporting tools such as Oracle BI Publisher and the DBI subject areas consume it directly. Developers should note the WITH READ ONLY restriction and always qualify the view with the APPS schema in SQL scripts.