Search Results contract_amount

Overview

POA_BIS_SAVINGS_RPT_V is an Oracle E-Business Suite view owned by the APPS schema and classified under the Purchasing (PO) product family. It is a Business Intelligence System (BIS) reporting view designed to expose procurement savings and spend-analysis metrics at a consolidated reporting grain. The view surfaces both purchase-side and contract-side monetary measures, enabling buyers, sourcing analysts, and procurement managers to evaluate realized versus potential savings, contract-leverage ratios, and purchasing patterns across dimensions such as supplier, buyer, operating unit, category, and project.

The object holds a VALID status in the data dictionary and is commonly consumed by Oracle Purchasing Analytics, Oracle Procurement dashboards, and custom BI Publisher or OBIEE reporting layers. Because the view is defined in the APPS schema, it is accessible to any responsibility or concurrent program with the appropriate grants, making it a convenient single-source abstraction over the underlying savings fact table.

Underlying Base Objects

The view is defined as a direct projection over the base table POA_BIS_SAVINGS_RPT. The view text is a simple column-list SELECT, listing every column of the base table without filters, joins, or aggregation. No other base objects, outer joins, or inline views are documented in the ETRM metadata. Consequently, the view is best understood as a synonym-style reporting façade rather than a transformation layer: any change to the base table's structure or data population logic (populated by the Purchasing BIS collection programs) is reflected immediately and transparently through the view.

From a maintenance standpoint, this means security grants, column masking, or VPD policies applied to POA_BIS_SAVINGS_RPT_V govern access, while data refresh is entirely dependent on the concurrent programs that stage the base table.

Key Columns

• CONTRACT_AMOUNT — the monetary value of spend transacted against negotiated contracts; the column most directly related to the user search term contract_amount.
• PURCHASE_AMOUNT — total purchase value captured for the reporting group.
• NON_CONTRACT_AMOUNT — spend not covered by a contract, useful for measuring maverick or off-contract buying.
• POT_CONTRACT_AMOUNT — potential contract amount, typically the value had all spend been contracted.
• POTENTIAL_SAVING — estimated savings opportunity derived from the contract vs. non-contract comparison.
• TOTAL_PURCHASE_QTY — aggregate purchased quantity for the grouping.
• GROUPNO — the aggregation group identifier linking the row to its reporting bucket.
• DOCUMENT_TYPE_CODE and PURCHASE_CREATION_DATE — document context and time dimension.
• Dimensional keys: ITEM_ID, CATEGORY_ID, SUPPLIER_ID, SUPPLIER_SITE_ID, BUYER_ID, REQUESTOR_ID, OPERATING_UNIT_ID, SHIP_TO_ORGANIZATION_ID, SHIP_TO_LOCATION_ID, PROJECT_ID, TASK_ID, COST_CENTER_ID, ACCOUNT_ID, COMPANY_ID.
• Currency and audit columns: CURRENCY_CODE, RATE_TYPE, RATE_DATE, plus standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent-program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

Typical usage includes contract-compliance reporting, savings-tracking dashboards, and spend-cube extraction. A representative query returning contract and non-contract spend by operating unit is:

SELECT operating_unit_id,
       SUM(contract_amount)      AS contract_spend,
       SUM(non_contract_amount)  AS non_contract_spend,
       SUM(potential_saving)     AS savings_opportunity
FROM   apps.poa_bis_savings_rpt_v
WHERE  currency_code = 'USD'
GROUP  BY operating_unit_id;

Analysts also join the view's dimensional keys (for example supplier_id to PO_VENDORS, or item_id to MTL_SYSTEM_ITEMS_B) to enrich spend analysis, and filter on purchase_creation_date for period-based trend reporting. Because the view exposes the base table's row-level grain without aggregation, aggregation must always be performed by the consuming query.