Results for “apfv_ap_invoices”

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

Overview

APFV_AP_INVOICES is a business view owned by the APPS schema in Oracle E-Business Suite, belonging to the Payables (AP) product family. It is documented as VALID in ETRM for releases 12.1.1 and 12.2.2. The view presents invoice header information sourced from AP_INVOICES and exposes a curated, reporting-friendly projection of that table rather than its full column set. This makes it suitable for operational reporting, integration extracts, and downstream data warehousing where a stable and simplified invoice interface is preferred over direct access to the transactional base table.

The view is defined with the WITH READ ONLY clause, reinforcing its intended use as a query-only construct. Consumers cannot perform DML against it, which preserves the integrity of the underlying Payables invoice data and ensures that all maintenance continues to flow through the standard AP_INVOICES transaction paths and Payables application logic. Column aliases in the view text map many base columns to descriptive business names, and several lookup-driven columns are pre-resolved against AP_LOOKUP_CODES so that report authors receive human-readable descriptions instead of raw lookup codes.

Underlying Base Objects

The ETRM documentation records a single referenced base object: AP_INVOICES, exposed to the view as a synonym. The view text confirms this by selecting from AP_INVOICES INV, meaning APFV_AP_INVOICES is a thin, single-table projection with no joins to supplier, site, or distribution tables. All filtering, decoding, and enrichment beyond the lookup aliases must therefore be performed by the consumer.

Two descriptor tokens appear in the view definition: _DF:SQLAP:AP_INVOICES:INV and _DF:JG:JG_AP_INVOICES:INV. These are Oracle Applications flexfield and descriptive flexfield context markers associated with the AP_INVOICES entity, and they indicate that the view text was generated with awareness of the invoice flexfield structures even though the DFF columns themselves are not projected. Because the dependent synonym AP_INVOICES resolves to the AP base table, the view always reflects the current transactional state of invoice headers without any materialization or caching.

Key Columns

The documented column list is partially excerpted from the full view definition, but the underlying view text confirms the following significant columns:

• INVOICE_NUMBER, INVOICE_DATE, INVOICE_DESCRIPTION — core invoice identification and narrative fields.
• INVOICE_ENTERED_AMOUNT, INVOICE_FUNCTIONAL_AMOUNT, INVOICE_DISCOUNTABLE_AMOUNT, INVOICE_FREIGHT_AMOUNT — amount metrics covering entered currency, functional (base) currency, discountable portion, and freight.
• INVOICE_POSTING_STATUS, APPROVAL_STATUS, PAYMENT_STATUS_FLAG — lifecycle status indicators for accounting, approval, and payment.
• INVOICE_SOURCE, INVOICE_TYPE_CODE, PAYMENT_STATUS, PAY_GROUP — lookup values accompanied by generated _LA description columns resolved through AP_LOOKUP_CODES for source, invoice type, and payment status.
• VENDOR_ID, VENDOR_SITE_ID, INVOICE_CURRENCY_CODE, PAYMENT_CURRENCY_CODE, TERMS_ID — supplier and currency context required for payment and matching analysis.
• BATCH_ID, PO_HEADER_ID, PROJECT_ID, TASK_ID, EXPENDITURE_TYPE — linkage to invoice batches, purchase orders, and project accounting.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — audit columns for change tracking.

Common Use Cases and Queries

Typical uses include invoice aging and status reporting, feeds into custom payment analysis, and extraction of invoice headers for reconciliation against general ledger postings. A representative query retrieves active invoices by supplier and currency:

SELECT invoice_number, invoice_date, invoice_entered_amount, invoice_functional_amount, payment_status FROM apfv_ap_invoices WHERE vendor_id = :p_vendor_id AND invoice_currency_code = 'USD' ORDER BY invoice_date DESC;

Because the view is read-only and single-table, it is safe for concurrent reporting workloads and straightforward to join to AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, and GL code combination tables as needed.