Results for “paid_amount”

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

Overview

POR_INVOICES_SUMMARY_V is a view owned by the APPS schema within Oracle E-Business Suite, classified under the ICX (Oracle iProcurement) product family. In the ETRM repository for releases 12.1.1 and 12.2.2, the view carries a status of VALID, though its documented description explicitly states that it is obsolete. This designation means the object remains present and compiled in the database for backward compatibility, but Oracle no longer supports or enhances it, and it should not be used for new development or customizations.

The view was originally designed to present a consolidated summary of supplier invoice activity tied to requisition lines and purchase order line locations. It joins procurement requisition data with receiving shipment records to surface invoice number, invoice date, and the invoiced amount associated with a given requisition line or line location. For users searching on the column name "paid_amount," this view is the historical location where that column name appears, representing the invoice amount for the shipment tied to the requisition line. Reporting tools and iProcurement pages that referenced this view consumed that column to display invoice information alongside requisition details.

Because the object is obsolete, its presence in a 12.1.1 or 12.2.2 instance is best treated as legacy metadata. Any requirement that once drove a query against POR_INVOICES_SUMMARY_V should be re-pointed at supported alternatives, typically the base tables and newer invoice summary views delivered with the procurement and payables modules.

Underlying Base Objects

The view is defined over a join of multiple procurement, receiving, and financials objects. The documented referenced base objects are:

• PO_REQUISITION_LINES (synonym) — source of the requisition line identifiers.
• PO_LINE_LOCATIONS (synonym) — provides the line location detail and links requisition lines to receiving records.
• RCV_SHIPMENT_HEADERS (synonym) — supplies invoice number, invoice date, and invoice amount for the shipment.
• RCV_SHIPMENT_LINES (synonym) — bridges line locations to shipment headers via PO_LINE_LOCATION_ID.
• PO_LOOKUP_CODES (view) — used in the YES/NO decode that derives the invoiced flag from the presence of an invoice number.
• GL_SETS_OF_BOOKS (view) — supplies the functional currency code for amount formatting.
• FINANCIALS_SYSTEM_PARAMETERS (synonym) — provides the set of books identifier used to join to GL_SETS_OF_BOOKS.
• FND_CURRENCY (package) — the SAFE_GET_FORMAT_MASK function formats the invoice amount using the set of books currency.
• FND_GLOBAL (package) — referenced by the view metadata for session context.

The join path is driven from the requisition line to its line location, then to the corresponding shipment line, and finally to the shipment header that carries the invoice attributes. The lookup code join conditionally returns 'Y' or 'N' based on whether an invoice number exists, producing the invoiced flag exposed by the view.

Key Columns

• REQUISITION_LINE_ID — the unique identifier of the requisition line, joining back to PO_REQUISITION_LINES.
• LINE_LOCATION_ID — the purchase order line location identifier, linking the requisition to receiving and shipment activity.
• INVOICED_FLAG — a derived indicator ('Y' or 'N') reflecting whether an invoice number is present for the shipment.
• INVOICE_NUMBER — the supplier invoice number recorded on the receiving shipment header.
• INVOICE_DATE — the date of the invoice, taken from the shipment header.
• PAID_AMOUNT — the invoice amount, formatted using the functional currency of the set of books via FND_CURRENCY.SAFE_GET_FORMAT_MASK. Despite the name, this column reflects the invoice amount rather than a separately settled or payment-applied amount.

Note that the implementation view text selects RSH.INVOICE_AMOUNT while the documented column list labels the same position as PAID_AMOUNT. Consumers searching on "paid_amount" should be aware of this naming discrepancy, as the underlying value is the invoice amount from RCV_SHIPMENT_HEADERS.

Common Use Cases and Queries

Historically, this view supported iProcurement requisition and receiving inquiry pages that displayed invoice references next to requisition lines. A typical legacy query retrieving invoice details for a requisition would resemble the following:

SELECT requisition_line_id, line_location_id, invoiced_flag, invoice_number, invoice_date, paid_amount FROM apps.por_invoices_summary_v WHERE requisition_line_id = :p_requisition_line_id;

A reporting query aggregating invoice amounts by line location might use:

SELECT line_location_id, SUM(TO_NUMBER(REPLACE(paid_amount, ',', ''))) total_invoiced FROM apps.por_invoices_summary_v WHERE invoiced_flag = 'Y' GROUP BY line_location_id;

Because PAID_AMOUNT is returned as a formatted currency string rather than a numeric value, arithmetic on it requires conversion, which further limits its usefulness in analytic workloads. Given the view's obsolete status, any such query should be treated as diagnostic only, and the underlying RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and PO_REQUISITION_LINES tables should be queried directly for supported results. No new dependencies should be built against POR_INVOICES_SUMMARY_V in either 12.1.1 or 12.2.2.