Results for “purchase”

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

Overview

POA_POD_002_MV is a materialized view owned by the APPS schema in Oracle E-Business Suite, documented under the FND – Application Object Library product family. It is a denormalized, pre-aggregated structure designed to support procurement spend and contract-compliance analytics in Oracle Procurement and Spend Analytics (part of the Oracle EBS/ETRM analytics stack). The "_MV" suffix confirms it is a materialized view rather than a base transactional table; the "POD" segment aligns it with Procurement On-Demand / spend-cube style reporting, and the "002" designator indicates it is one variant in a numbered family of aggregation definitions, each tuned to a distinct grain or measure set.

The ETRM metadata classifies the object heuristically as standalone, and this should be read as a modeling suggestion rather than a mandatory construct: the view does not sit as a clean hub, link, or satellite in a Data Vault sense. It behaves closest to a consolidated multi-dimensional fact aggregate, storing pre-summed monetary and quantity measures across a shared dimensional key set (company, cost center, time, category, commodity, supplier, item, UOM, contract type, and aggregation level). Because it carries measures and a composite key rather than descriptive history, it functions as a reporting "satellite-like" fact table rather than a classic hub.

Key Information Stored

The view comprises 59 columns. The most significant are the dimensional/business-key columns and the principal measures:

• Dimensional keys: COMPANY_ID, PARENT_COMPANY_ID, COST_CENTER_ID, PARENT_CC_ID, TIME_ID, ORG_ID, SUPPLIER_ID, CATEGORY_ID, PO_ITEM_ID, COMMODITY_ID, CONTRACT_TYPE, BASE_UOM, GRP_ID, and AGGREGATION_LEVEL.
• Purchase measures: PURCHASE_AMT_B, PURCHASE_AMT_G, PURCHASE_AMT_SG, QUANTITY.
• Contract measures: CONTRACT_AMT_B/G/SG, ABOVE_CONTRACT_AMT_B/G/SG, BELOW_CONTRACT_AMT_B/G/SG.
• Contract/savings measures: P_CONTRACT_AMT_B/G/SG, N_CONTRACT_AMT_B/G/SG, P_SAVINGS_AMT_B/G/SG.

Notably, there is no single documented surrogate primary key. The uniqueness constraint is instead a business-key composite captured by the index I_SNAP$_POA_POD_002_MV, whose SYS_OP_MAP_NONNULL() wrapped columns confirm that the grain is the full 14-column combination of PARENT_COMPANY_ID, COMPANY_ID, PARENT_CC_ID, COST_CENTER_ID, TIME_ID, CATEGORY_ID, COMMODITY_ID, ORG_ID, SUPPLIER_ID, PO_ITEM_ID, BASE_UOM, CONTRACT_TYPE, GRP_ID, and AGGREGATION_LEVEL. The "_SNAP$" naming convention identifies this as a materialized-view snapshot/refresh index. Currency-coded suffixes (B/G/SG) denote the currency groupings applied to the amounts.

Common Use Cases and Queries

This view is consumed primarily for spend-analysis dashboards, contract-leakage reporting, and savings tracking. A typical aggregation by category and period:

• SELECT CATEGORY_ID, TIME_ID, SUM(PURCHASE_AMT_G) FROM APPS.POA_POD_002_MV GROUP BY CATEGORY_ID, TIME_ID;
• Contract compliance: compare SUM(ABOVE_CONTRACT_AMT_G) versus SUM(BELOW_CONTRACT_AMT_G) by SUPPLIER_ID to flag off-contract purchasing.
• Savings analysis: filter on AGGREGATION_LEVEL and CONTRACT_TYPE to compare P_SAVINGS_AMT_G (planned) against achieved figures.
• Supplier performance: aggregate QUANTITY and PURCHASE_AMT_SG by SUPPLIER_ID and COMMODITY_ID, joining PN_COMPANIES_ALL and PO_COMMODITIES_B for descriptive labels.

Because refresh is snapshot-based, queries should account for the materialized view's last-refresh timestamp. Filtering aggressively on the composite key columns preserves partition/segment pruning where the underlying fact structure is partitioned on TIME_ID or ORG_ID.

Related Objects

The documented foreign-key relationships and shared dimensions anchor this view to the following significant objects:

• PN_COMPANIES_ALL — joined via COMPANY_ID for legal-entity and company-segment attributes.
• PO_COMMODITIES_B — joined via COMMODITY_ID for commodity classification.
• POA_POD_001_MV and sibling POA_POD_*_MV views — parallel aggregation definitions in the same family; common conformed dimensions are shared.
• PO Suppliers / AP_SUPPLIERS (SUPPLIER_ID) — supplier descriptive data.
• GL/HR cost-center references (COST_CENTER_ID, PARENT_CC_ID) — organizational hierarchy attributes.
• PO_ITEM_ID — resolves to PO item master (e.g., PO_ITEM_ATTRIBUTES) for item-level drill-down.
• FND_* reporting metadata — as an FND-owned object, it interacts with concurrent programs and materialized-view refresh schedules.

Analysts should treat POA_POD_002_MV as a read-only reporting surface and avoid direct DML; all maintenance is handled through its materialized-view refresh mechanism.