Results for “invoice_received_date”

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

Overview

AP_INVOICES_UNION_PREPAYS_V is an APPS-owned database view within the Oracle E-Business Suite Payables (AP) module. As its name indicates, the view provides a unified presentation of standard supplier invoices and prepayment invoices, allowing them to be queried through a single interface. This consolidated structure is particularly useful for reporting and integration scenarios where consumers require a complete picture of invoice activity without having to explicitly combine multiple source sets in their own SQL.

The ETRM documentation labels the view with the description "(Release 10SC Only)," reflecting its origins in an early release of the Payables data model. Despite this historical annotation, the object remains marked as VALID in the APPS schema as documented for EBS 12.1.1 and 12.2.2, meaning it continues to resolve and can be referenced by dependent objects and custom code in these environments. Its primary role is to serve as a read-only reporting surface, insulating developers and report authors from the physical distribution of invoice data across the underlying Payables tables.

Underlying Base Objects

The view is defined over a set of core Payables objects, several of which are accessed via synonyms and views rather than the physical tables directly. The documented referenced base objects are AP_INVOICES, AP_INVOICE_DISTRIBUTIONS, AP_PAYMENT_SCHEDULES, AP_HOLDS, AP_SELECTED_INVOICES, AP_LOOKUP_CODES (a view), PO_VENDORS (a view), PO_VENDOR_SITES (a view), and the FND_GLOBAL package.

The union of standard invoices and prepayments is driven principally by the AP_INVOICES table, which stores header-level invoice information. The pay schedule information, joined through AP_PAYMENT_SCHEDULES, supplies the amount-remaining values that feed the aggregated payment column. Lookups and supplier information are resolved through AP_LOOKUP_CODES, PO_VENDORS, and PO_VENDOR_SITES, while FND_GLOBAL typically contributes session context such as the current user and responsibility. Selected invoice data from AP_SELECTED_INVOICES and hold information from AP_HOLDS round out the invoice picture for reporting purposes.

Key Columns

The view exposes a broad set of invoice attributes. Identity and control columns include INVOICE_ID, DOC_CATEGORY_CODE, and DOC_SEQUENCE_ID/DOC_SEQUENCE_VALUE, which together support unique identification and document sequencing. Monetary columns such as BASE_AMOUNT, AMOUNT_PAID, APPROVED_AMOUNT, CANCELLED_AMOUNT, DISCOUNT_AMOUNT_TAKEN, FREIGHT_AMOUNT, and AMOUNT_APPLICABLE_TO_DISCOUNT capture the financial substance of each invoice. Currency and conversion details are provided through INVOICE_CURRENCY_CODE, EXCHANGE_RATE, EXCHANGE_RATE_TYPE, and EXCHANGE_DATE.

A distinctive column is PAY_CURR_INVOICE_AMOUNT, defined as SUM(APS.AMOUNT_REMAINING) drawn from the payment schedules. This aggregation yields the outstanding payment-currency balance for the invoice, a value widely used in aging and cash-requirement reporting. Auditing columns (CREATED_BY, CREATION_DATE, AUTHORIZED_BY, CANCELLED_BY, CANCELLED_DATE), the ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 descriptive flexfield columns, and payment-related flags such as EXCLUSIVE_PAYMENT_FLAG and AWT_FLAG complete the structure.

Common Use Cases and Queries

Typical uses include supplier balance reporting, prepayment application analysis, and invoice aging extracts. A simple retrieval might select the invoice identifier, date, currency, and outstanding amount for a given supplier:

• SELECT INVOICE_ID, INVOICE_DATE, INVOICE_CURRENCY_CODE, PAY_CURR_INVOICE_AMOUNT FROM APPS.AP_INVOICES_UNION_PREPAYS_V WHERE DOC_CATEGORY_CODE IN ('STANDARD','PREPAY');
• SELECT INVOICE_ID, APPROVED_AMOUNT, AMOUNT_PAID, CANCELLED_AMOUNT FROM APPS.AP_INVOICES_UNION_PREPAYS_V WHERE INVOICE_DATE BETWEEN :start_date AND :end_date;
• Correlating invoice headers with distributions via INVOICE_ID to validate accounting splits for reconciliation extracts.

Because the view is a reporting construct rather than a transactional interface, it should be queried read-only. Its column aliasing and aggregation from AP_PAYMENT_SCHEDULES mean results reflect the current state of payment schedules at query time.