Results for “pon_mi_rfqsummary_v”

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

Overview

PON_MI_RFQSUMMARY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the PON (Sourcing) product family. It exposes summarized Accepted Quotation data and is documented as the data source for the Accepted Quotations Detail report. The view is registered as VALID in both EBS 12.1.1 and 12.2.2, and in the ETRM 12.2.2 metadata it presents a denormalized, report-ready projection of sourcing auction results — one row per accepted bid — rather than a normalized transactional entity.

The view is primarily read-only and is intended for reporting and lightweight integration. Because it pre-aggregates and reformats monetary values, consumers do not need to compute award values themselves, and because it joins through to buyer, seller, and category names, it can be used directly by BI Publisher, Oracle Reports, or custom SQL without additional joins to party or item master tables. Users searching for the auction_display_number attribute will find it here as a first-class column, which is frequently the reason this view is queried in lieu of navigating the underlying auction and bid entities individually.

Underlying Base Objects

According to the documented view text, PON_MI_RFQSUMMARY_V is defined over a single base object: the view PON_MI_AUC_RFQ_V (referenced in APPS). No base tables are joined directly by this view; all joins, name resolution, and detail aggregation are performed inside PON_MI_AUC_RFQ_V.

The projection performs two notable transformations:

• Outcome decomposition — the AUCTION_OUTCOME column is decoded into two mutually exclusive monetary measures, SPOT_AMT and LONG_AMT, using NVL(PRICE * QUANTITY, 0). A row marked 'SPOT' contributes to SPOT_AMT and zeroes out LONG_AMT, and vice versa.
• Attribute pass-through — remaining columns such as AUCTION_NUMBER, AUCTION_DISPLAY_NUMBER, BID_NUMBER, buyer/seller identifiers and names, category, currency, and completion date are carried through unchanged from the base view.

Because it depends on a view rather than tables, any change to PON_MI_AUC_RFQ_V propagates implicitly. This view should therefore be treated as a dependency-sensitive layer, and direct DML against it is not supported.

Key Columns

• AUCTION_NUMBER — internal identifier of the sourcing auction (RFQ/negotiation).
• AUCTION_DISPLAY_NUMBER — the user-facing auction number shown in the Sourcing UI and reports; the column most often searched when reconciling an auction seen on screen.
• AUCTION_TITLE — descriptive title of the auction.
• BID_NUMBER — identifier of the accepted bid/quotation.
• AUCTION_OUTCOME — classifies the award type, with documented values 'SPOT' and 'LONG', driving the two amount columns.
• SPOT_AMT / LONG_AMT — award value for the corresponding outcome; zero when the row belongs to the other outcome.
• BUYER_ID / BUYER_NAME — purchasing party responsible for the auction.
• SELLER_ID / SELLER_NAME — supplier to whom the award was made.
• CATEGORY_ID — purchasing category of the awarded line.
• COMPLETED_DATE — date the auction completed or the award was finalized.
• CURRENCY_CODE — currency of the monetary amounts.

Common Use Cases and Queries

A typical reconciliation query locates an auction by its display number and reports its awards:

SELECT auction_display_number, auction_title, bid_number,
       auction_outcome, spot_amt, long_amt, currency_code
FROM   apps.pon_mi_rfqsummary_v
WHERE  auction_display_number = :p_display_number;

Aggregate spend by buyer and currency over a period:

SELECT buyer_name, currency_code,
       SUM(spot_amt) spot_total, SUM(long_amt) long_total
FROM   apps.pon_mi_rfqsummary_v
WHERE  completed_date BETWEEN :p_from AND :p_to
GROUP  BY buyer_name, currency_code;

Supplier award analysis uses SELLER_ID/SELLER_NAME and CATEGORY_ID to profile sourcing outcomes. Because the view already filters to accepted quotations, no additional award-status predicate is required. The view is the preferred source when matching on-screen auction numbers, as AUCTION_DISPLAY_NUMBER is exposed directly.