Search Results buyer_long_amt

Overview

The PON_MI_AUCTIONSUMMARY_V view is a reporting object owned by the APPS schema within the Oracle E-Business Suite PON (Sourcing) module. It is a supporting data source for the Awarded Bids Detail report and consolidates awarded auction activity into a single, denormalized result set. The view presents one row per auction award, capturing the outcome (spot or long), the buyer and seller parties, the winning bid reference, and the monetary amounts attributed to each side of the transaction. Notably, the data serves both Standard Purchase Orders and Blanket Purchase Agreements, so the same view supports reporting across multiple procurement document types without requiring separate queries.

From a reporting and integration perspective, PON_MI_AUCTIONSUMMARY_V acts as a stable abstraction over the raw buyer-auction base view. Rather than exposing internal sourcing tables directly, it fixes a consistent projection of columns such as AUCTION_NUMBER, AUCTION_TYPE, and the amount buckets, allowing custom reports, Oracle BI Publisher templates, and interface extracts to reference a single governed object. In Oracle EBS 12.1.1 and 12.2.2 the view remains VALID and unchanged in role, providing a durable foundation for auditing awarded sourcing activity.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over a single referenced base object: PON_MI_AUC_BUYERAUC_V, itself a view in the PON schema. The definition is a straight projection with no joins or aggregations. Its SELECT list applies a few DECODE and NVL expressions to reshape the buyer auction data:

• SELLER_AMT is hard-coded to 0, reflecting that this view reports the buyer-side view of the award.
• BUYER_SPOT_AMT returns PRICE * QUANTITY only when AUCTION_OUTCOME = 'SPOT', otherwise zero.
• BUYER_LONG_AMT returns PRICE * QUANTITY only when AUCTION_OUTCOME = 'LONG', otherwise zero.
• BUYER_AMT returns the full PRICE * QUANTITY, defaulting to zero where price or quantity is null.

All other columns — including AUCTION_NUMBER, BID_NUMBER, BUYER_ID, SELLER_ID, and COMPLETED_DATE — are passed through unchanged from the underlying view. Because the relationship is one-to-one, row counts and filtering behavior are inherited directly.

Key Columns

• AUCTION_NUMBER and AUCTION_DISPLAY_NUMBER — the internal and user-facing identifiers for the sourcing auction; these are central to any search keyed on auction_number.
• AUCTION_TITLE — the descriptive name of the auction event.
• AUCTION_TYPE — populated with the literal 'BUYER' in this view, indicating the buyer-side perspective.
• AUCTION_OUTCOME — distinguishes 'SPOT' from 'LONG' awards and drives the amount bucketing.
• BID_NUMBER — the winning bid reference associated with the award.
• BUYER_ID, BUYER_NAME, SELLER_ID, SELLER_NAME — the trading parties on the awarded transaction.
• CATEGORY_ID — the purchasing category of the awarded line or bid.
• COMPLETED_DATE — the date the auction was completed.
• CURRENCY_CODE — the currency in which the award amounts are expressed.
• SELLER_AMT, BUYER_SPOT_AMT, BUYER_LONG_AMT, BUYER_AMT — monetary measures split by perspective and outcome.

Common Use Cases and Queries

The primary use case is the Awarded Bids Detail report, but the view is equally suitable for ad hoc analysis of awarded sourcing events and reconciliation against downstream POs and BPAs. Typical queries include:

• Locating awards by auction number:

SELECT auction_number, auction_display_number, auction_title,
       bid_number, buyer_amt, currency_code, completed_date
FROM   apps.pon_mi_auctionsummary_v
WHERE  auction_number = :p_auction_number;

• Summarizing buyer spend by auction outcome:

SELECT auction_outcome, COUNT(*) awards, SUM(buyer_amt) total_amt
FROM   apps.pon_mi_auctionsummary_v
GROUP  BY auction_outcome;

• Extracting awards within a date range for a specific seller:

SELECT auction_number, seller_name, category_id,
       buyer_spot_amt, buyer_long_amt, completed_date
FROM   apps.pon_mi_auctionsummary_v
WHERE  seller_id = :p_seller_id
AND    completed_date BETWEEN :p_from AND :p_to;

When embedding this view in custom reports, note that SELLER_AMT is always zero by design and that spot and long amounts are mutually exclusive, so BUYER_AMT equals whichever outcome-specific column is populated. Standard APPS data security and MOAC operating unit context should be applied where the underlying sourcing data requires it.