Results for “poa_rtx_bs_mv”

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

Overview

POA_RTX_BS_MV is a materialized view owned by the APPS schema in Oracle E-Business Suite, registered in the Application Object Library (FND) product family. The suffix _MV denotes a materialized view, while POA identifies the Procurement On-Line Analytical Processing (OLAP) / Procurement Analytics schema lineage, and RTX_BS indicates a receipt-transaction balance summary construct. Within Oracle EBS 12.1.1 and 12.2.2, this object serves as a pre-aggregated analytical store that summarizes procurement receipt, return, reject, inspection, and supplier delivery-performance metrics across multiple time and organizational dimensions. Rather than querying high-volume transactional tables such as RCV_TRANSACTIONS directly, reporting tools and Procurement dashboards read POA_RTX_BS_MV to obtain fast, dimensionally consistent results.

The documented physical schema contains 101 columns, and the materialized view holds business metrics at a finely partitioned grain defined by organization, commodity, supplier, item, category, buyer, reason, and a suite of time identifiers. A heuristic Data Vault classification, mined from the foreign-key structure, suggests this object behaves as a satellite: it carries descriptive and quantitative measures attached to a set of dimensional business keys, rather than acting as a hub or link. Practitioners may treat this as a modeling suggestion when reverse-engineering the analytical star or Data Vault equivalent.

Key Information Stored

Because the object stores aggregated metrics, its most significant columns fall into two groups: dimensional business keys and quantitative measures. The unique index I_SNAP$_POA_RTX_BS_MV defines the business-key candidate set that establishes row grain. That index covers ORG_ID (operating unit), COMMODITY_ID, SUPPLIER_ID, CATEGORY_ID, PO_ITEM_ID, SUPPLIER_SITE_ID, RECEIVING_ORG_ID, BUYER_ID, REASON_ID, BASE_UOM, and the time hierarchy columns ENT_YEAR_ID, ENT_QTR_ID, ENT_PERIOD_ID, WEEK_ID, DAY_ID, plus GRP_ID and AGGREGATION_LEVEL. These columns collectively determine the aggregation level at which each row is maintained.

The most important measure columns include AMT_RECEIPT_B, AMT_RECEIPT_G, and AMT_RECEIPT_SG (receipted amounts in entered, accounted, and secondary-ledger currency representations), QTY_RECEIPT, QTY_RETURN, and QTY_REJECT (receipt, return, and rejection quantities), and the parallel QTY_RECEIPT_AND_DROPSHIP quantity that combines standard receipts with drop-ship receipts. Rejection and inspection activity is captured through AMT_REJECT_B and AMT_INSPECTED_B families. Delivery-timing performance is represented by NUM_DAYS_EARLY, NUM_DAYS_LATE, QTY_BEFOREDUE, QTY_AFTERDUE, and QTY_INTOL. The C_-prefixed columns (for example C_AMT_RECEIPT_B, C_QTY_RECEIPT, C_TOTAL) hold cumulative or year-to-date equivalents of the corresponding base measures, supporting trend and period-over-period reporting. TIME_ID and PERIOD_TYPE_ID assist in resolving the active time context.

Common Use Cases and Queries

Typical applications include supplier scorecarding, receipt and reject trend analysis, on-time delivery measurement, and commodity spend aggregation. A supplier delivery-performance query might sum late and early transactions by supplier for a period:

• SELECT supplier_id, SUM(num_days_late), SUM(num_days_early) FROM poa_rtx_bs_mv WHERE ent_period_id = :period AND org_id = :org GROUP BY supplier_id;
• SELECT category_id, SUM(qty_receipt), SUM(qty_reject), SUM(amt_receipt_b) FROM poa_rtx_bs_mv WHERE aggregation_level = :lvl AND time_id BETWEEN :start AND :end GROUP BY category_id;
• SELECT commodity_id, SUM(c_amt_receipt_b) FROM poa_rtx_bs_mv WHERE ent_year_id = :year GROUP BY commodity_id ORDER BY 2 DESC;

Because the grain includes AGGREGATION_LEVEL, reports must filter to avoid double-counting; failure to constrain this column yields inflated totals. Refresh timing of the materialized view should be considered when reporting near-real-time receipt data.

Related Objects

The documented foreign-key relationship links POA_RTX_BS_MV.COMMODITY_ID to PO_COMMODITIES_B, the base commodity definition table. The dimensional keys referenced within the unique index imply dependencies on standard EBS master and transactional entities, including:

• PO_COMMODITIES_B — commodity definitions (documented FK).
• PO_VENDORS / PO_VENDOR_SITES_ALL — supplier and supplier-site attributes for SUPPLIER_ID and SUPPLIER_SITE_ID.
• PO_CATEGORIES_B — purchasing category for CATEGORY_ID.
• MTL_SYSTEM_ITEMS_B — item master for PO_ITEM_ID.
• HR_OPERATING_UNITS — operating unit for ORG_ID and RECEIVING_ORG_ID.
• PO_AGENTS — buyer reference for BUYER_ID.
• FND_CURRENCIES — currency context for the _B, _G, and _SG amount columns.

Reporting schemas and Procurement Analytics dashboards consume this materialized view as a read-only aggregate source; direct DML against it is not supported.