Search Results distribution_transaction_id




Overview
Explore in AI Chat

Overview

APPS.POA_BIS_SAVINGS_RPT_V is a reporting view in the Oracle E-Business Suite Procurement module, shipped under the POA (Procurement Analytics) schema family. It exposes pre-aggregated and pre-joined procurement savings data for Business Intelligence (BIS) reporting against purchasing activity. The view is a thin projection over the base table POA_BIS_SAVINGS_RPT: its defining query selects an explicit, ordered column list from that single table with no joins, filters, or computed expressions. In Oracle EBS 12.1.1 and 12.2.2 this view serves the standard Procurement savings and spend analysis dashboards, including the "Savings Analysis" and "Procurement Spend" reports driven by Oracle Business Intelligence and the POA schema.

The column of interest to the searcher, PURCHASE_CREATION_DATE, is one of the view's projected attributes. It carries the creation (transaction) date of the underlying purchase document and is the primary date dimension for time-based savings and spend reporting.

Underlying Base Objects

The documented base object for this view is the single table POA_BIS_SAVINGS_RPT. No other tables or views are referenced in the view text. Functionally, POA_BIS_SAVINGS_RPT is a denormalized reporting table populated by a concurrent program that extracts and summarizes data from purchasing tables such as PO_HEADERS_ALL, PO_LINES_ALL, PO_DISTRIBUTIONS_ALL, and the associated supplier and item tables. The view therefore represents a one-to-one pass-through of the base table columns; it does not itself perform any aggregation, join, or data transformation. As such, the two objects share identical row counts, and all filtering, grouping, and aggregation must be supplied by the calling query or reporting layer. There is no documented WHERE clause on the view, so the entire content of the table is visible to any consumer with SELECT privilege on APPS.POA_BIS_SAVINGS_RPT.

Key Columns

The view exposes the following notable columns:

Common Use Cases and Queries

Typical usage is for savings trend analysis by period, buyer, supplier, and category.

SELECT purchase_creation_date,
       SUM(potential_saving) saving
FROM   apps.poa_bis_savings_rpt_v
WHERE  purchase_creation_date BETWEEN :from_date AND :to_date
GROUP  BY purchase_creation_date;

SELECT supplier_id, buyer_id,
       SUM(purchase_amount) spend,
       SUM(potential_saving) savings
FROM   apps.poa_bis_savings_rpt_v
WHERE  TRUNC(purchase_creation_date,'YYYY') = :year
GROUP  BY supplier_id, buyer_id;

Because the view performs no filtering, always bound queries on PURCHASE_CREATION_DATE or another selective column to control result size in large datasets.