Search Results pon_mi_auc_rfq_v




Overview
Explore in AI Chat

Overview

PON_MI_AUC_RFQ_V is a reporting view owned by the APPS schema within the PON (Sourcing) product family of Oracle E-Business Suite. Its documented purpose is narrow and well defined: it supplies the data set consumed by the Buyer's Activity Summary report, restricted to accepted quotations. In EBS sourcing terminology, an accepted quotation corresponds to a bid line that has been awarded, meaning the buyer has completed evaluation and finalized the award decision for the RFQ. The view therefore exposes the closed-out, transacted portion of the sourcing lifecycle rather than the open solicitation pipeline.

The object is classified as VALID in the ETRM repository for release 12.2.2. Its name follows the standard EBS convention of a "MI" (management information) reporting view layered on transactional sourcing tables, and it is intended primarily for read-only reporting access rather than for application processing logic.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through APPS synonyms: PON_AUCTION_HEADERS, PON_AUC_DOCTYPES, PON_BID_HEADERS, and PON_BID_ITEM_PRICES. These tables represent the auction or RFQ header, the document-type lookup, the supplier bid headers, and the bid line price and award details respectively.

The joins are constructed as follows: PON_AUCTION_HEADERS joins to PON_BID_HEADERS on AUCTION_HEADER_ID; PON_BID_HEADERS joins to PON_BID_ITEM_PRICES on AUCTION_HEADER_ID and BID_NUMBER; and PON_AUCTION_HEADERS joins to PON_AUC_DOCTYPES on DOCTYPE_ID. Two filter predicates complete the definition: BI.AWARD_STATUS must equal 'AWARDED', and the document type internal name must equal 'REQUEST_FOR_QUOTE'. Consequently, the view returns only RFQ-type sourcing events with awarded bid lines, excluding reverse auctions and any non-awarded or cancelled bid activity.

Key Columns

The view exposes nineteen columns covering price, quantity, identification, party, classification, and timing attributes.

Common Use Cases and Queries

The principal consumer is the Buyer's Activity Summary report, which aggregates awarded quotation activity by buyer, category, and time period. Beyond that report, the view is useful for ad hoc spend and procurement analytics that require a denormalized, award-only RFQ data set without joining the underlying four tables manually. A typical query filters on completion date to constrain a reporting period:

  • SELECT buyer_name, category_id, currency_code, SUM(price * quantity) awarded_value FROM pon_mi_auc_rfq_v WHERE completed_date BETWEEN :start_date AND :end_date GROUP BY buyer_name, category_id, currency_code;
  • SELECT auction_display_number, bid_number, seller_name, auction_outcome, price, quantity FROM pon_mi_auc_rfq_v WHERE buyer_id = :buyer_id;
  • SELECT auction_outcome, COUNT(*) award_count FROM pon_mi_auc_rfq_v GROUP BY auction_outcome;

Because the view is filtered to AWARDED status and REQUEST_FOR_QUOTE document types, queries against it cannot be used to inspect pending, cancelled, or auction-type events; those require the underlying tables directly. Standard EBS read-only privileges on the APPS schema objects are sufficient to query it.