Search Results potential_saving




Overview
Explore in AI Chat

Overview

APPS.POA_BIS_SAVINGS_RPT_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes procurement savings and spend analysis data sourced from the Purchasing intelligence (BIS) schema. The view presents a denormalized, reporting-ready projection of savings metrics alongside the transactional and dimensional attributes required to slice those metrics. It is intended for use by Business Intelligence (BI) extracts, XML Publisher reports, and ad-hoc analytical queries that measure negotiated savings on purchased goods and services.

The "BIS" component of the name identifies this object as part of the Oracle Procurement Business Intelligence (Purchasing) reporting layer, and the "_V" suffix denotes it as a view rather than a table. The "SAVINGS_RPT" naming indicates that the view is oriented toward savings reporting—specifically, highlighting the POTENTIAL_SAVING measure that procurement organizations use to quantify the difference between what was actually paid and what would have been paid absent a negotiated contract. Because it is a view, no physical data is stored; consumers query it and Oracle EBS resolves the definition against the underlying base object at runtime.

Underlying Base Objects

According to the documented view text, POA_BIS_SAVINGS_RPT_V is defined as a straightforward projection over a single base object: POA_BIS_SAVINGS_RPT. The definition selects every column from that base object without joins, filters, aggregation, or expressions. The column list in the SELECT clause matches the source exactly, including the enumerated column names in quotation marks, confirming a one-to-one mapping.

The ETRM metadata records no additional referenced base objects beyond POA_BIS_SAVINGS_RPT. In practice, POA_BIS_SAVINGS_RPT is a table in the Procurement BIS reporting layer, typically loaded by Purchasing intelligence concurrent programs that summarize purchasing transactions, contract and non-contract spend, and derived savings. Because the view is a pure projection, its column structure, data types, and row count are inherited entirely from POA_BIS_SAVINGS_RPT. Any grants, synonyms, and query performance characteristics affecting the base object carry through to the view.

Key Columns

The view exposes a broad set of columns that combine savings measures with transaction and dimension keys. Notable columns include:

All columns are exposed as-is from the base object; the view applies no transformation or aliasing beyond quoting identifiers.

Common Use Cases and Queries

The view is typically consumed for savings and spend dashboards, supplier negotiation analysis, and category-level savings trend reporting. A basic query retrieving savings by supplier follows:

  • SELECT supplier_id, SUM(potential_saving) FROM apps.poa_bis_savings_rpt_v GROUP BY supplier_id;
  • SELECT category_id, SUM(purchase_amount), SUM(potential_saving) FROM apps.poa_bis_savings_rpt_v WHERE purchase_creation_date >= :from_date GROUP BY category_id;
  • SELECT item_id, buyer_id, total_purchase_qty, potential_saving FROM apps.poa_bis_savings_rpt_v WHERE document_type_code = :doc_type;

Because the view performs no aggregation, callers apply GROUP BY and filter predicates directly. Queries should restrict on date and organizational dimensions to limit the volume of rows returned from the base reporting object. Consumers should also respect the currency context (CURRENCY_CODE, RATE_TYPE, RATE_DATE) when comparing monetary values across operating units.