Search Results seller_name




Overview
Explore in AI Chat

Overview

PON_MI_REPORTSUMMARY_V is a reporting view in the Oracle E-Business Suite Sourcing module (PON) that consolidates summarized transactional data for the Buyer's Activity Summary report. Its purpose is to present, in a single flattened result set, the monetary totals and associated buyer, seller, and contact information for three distinct Sourcing outcomes: Awarded Auctions, Committed Offers, and Accepted Quotations. The view is documented in ETRM 12.2.2 and is applicable to the 12.1.1 and 12.2.2 releases.

Because Oracle Sourcing stores auction, negotiation, and quotation activity across separate operational tables, the Buyer's Activity Summary report requires a uniform structure regardless of the underlying document type. PON_MI_REPORTSUMMARY_V provides that uniformity. Each source contributing to the view projects its own measure into a dedicated total column while zeroing the remaining two, and all rows share an identical column list of fourteen attributes. This design allows downstream report logic to aggregate totals across document types without conditional branching.

Underlying Base Objects

The view is defined as a three-way UNION ALL over the following objects:

Each branch applies the expression NVL((PRICE*QUANTITY), 0) to derive its respective total, ensuring that null price or quantity values resolve to zero rather than propagating nulls into report aggregates. The ETRM metadata for this view records no owner and no directly referenced base tables, indicating that it is a reporting layer built over the intermediate PON_MI_* views rather than over physical base tables. The UNION ALL operator is used deliberately instead of UNION, since the three branches describe mutually exclusive document categories and no de-duplication is required.

Key Columns

The view exposes fourteen columns. The measure columns are AUCTION_TOTAL, QUOTES_TOTAL, and OFFER_TOTAL; exactly one is populated per row and the others are returned as literal zero. The party columns are BUYER_ID, BUYER_NAME, SELLER_ID, and SELLER_NAME. Contact-level detail is carried in BUYER_CONTACT_ID, BUYER_CONTACT_NAME, SELLER_CONTACT_ID, and SELLER_CONTACT_NAME. The column SELLER_CONTACT_NAME is of particular relevance to searches on buyer and seller contact identification, as it returns the display name of the supplier-side contact associated with the completed transaction. Rounding out the structure are CATEGORY_ID (the purchasing category), COMPLETED_DATE (the transaction completion date), and CURRENCY_CODE (the transaction currency).

Common Use Cases and Queries

Typical usage centers on period-based buyer performance analysis across document types, category-level spend summaries, and identification of seller contacts for awarded business.

  • Retrieving all transactions with their seller contact name: 
    SELECT BUYER_NAME, SELLER_NAME, SELLER_CONTACT_NAME,
       AUCTION_TOTAL, QUOTES_TOTAL, OFFER_TOTAL,
       COMPLETED_DATE, CURRENCY_CODE
FROM   PON_MI_REPORTSUMMARY_V;
  • Aggregating total activity per buyer for a date range: 
    SELECT BUYER_NAME,
       SUM(AUCTION_TOTAL + QUOTES_TOTAL + OFFER_TOTAL) TOTAL_ACTIVITY
FROM   PON_MI_REPORTSUMMARY_V
WHERE  COMPLETED_DATE BETWEEN :from_date AND :to_date
GROUP  BY BUYER_NAME;
  • Filtering specifically for seller contact information on awarded auctions: 
    SELECT SELLER_NAME, SELLER_CONTACT_NAME, AUCTION_TOTAL
FROM   PON_MI_REPORTSUMMARY_V
WHERE  AUCTION_TOTAL > 0;

Because each row is currency-specific, cross-currency aggregation should be accompanied by currency conversion or grouping by CURRENCY_CODE.