Search Results commitment_number

Overview

PON_MI_OFFERSUMMARY_V is a reporting view within the Oracle E-Business Suite Sourcing (PON) module. Its documented purpose is to support the Committed Offers Detail report, supplying summarized data for all committed offers generated through the Oracle Sourcing auction and negotiation process. The view consolidates buyer-side commitment information for offers that have been committed in a sourcing event, exposing a normalized result set that the reporting layer consumes directly rather than assembling the data from multiple underlying tables at runtime.

In the context of Oracle EBS 12.1.1 and 12.2.2, the view functions as a read-only reporting interface. It is not a transactional object; no DML is performed against it. Its name follows the PON_MI_* convention, where "MI" designates management information or reporting-oriented database objects in Sourcing. The view standardizes the presentation of committed offer amounts so that the Committed Offers Detail report can render buyer commitments consistently across auctions and negotiation events.

Underlying Base Objects

According to the documented view text, PON_MI_OFFERSUMMARY_V is defined as a single SELECT statement over one base object: PON_MI_AUC_OFFERTOBUY_V. No additional tables, joins, or inline views appear in the exposed definition, though the ETRM metadata notes that referenced base objects were not documented at the physical table level. PON_MI_AUC_OFFERTOBUY_V is therefore the immediate parent view, and PON_MI_OFFERSUMMARY_V inherits its sourcing offer data and re-labels it for the buyer commitment summary context.

The definition performs limited transformation. It injects a literal for the seller amount, computes the buyer amount from PRICE multiplied by QUANTITY, appends a literal OFFER_TYPE of 'BUYER', and projects a defined column list from the parent view. This indicates that the parent view supplies auction, party, category, date, and currency context, while PON_MI_OFFERSUMMARY_V narrows the presentation to buyer commitments and derives the summarized monetary value.

Key Columns

• COMMITMENT_NUMBER — The commitment identifier associated with the offered line. This is the column most directly relevant to commitment_number searches and links the report output back to the originating sourcing commitment record.
• BUYER_AMT — The committed buyer value, computed as NVL(PRICE*QUANTITY, 0). This is the primary financial measure surfaced by the view.
• SELLER_AMT — Hard-coded to 0, reflecting that this view summarizes buyer-side commitments only.
• OFFER_TYPE — Always 'BUYER' in this view, distinguishing the commitment orientation of each row.
• AUCTION_NUMBER / AUCTION_TITLE — Identify the sourcing event to which the commitment belongs.
• BUYER_ID / BUYER_NAME — The buying party responsible for the commitment.
• SELLER_ID / SELLER_NAME — The supplier party participating in the event.
• CATEGORY_ID — The purchasing category assigned to the offer.
• COMPLETED_DATE — The date the sourcing event or commitment was completed.
• CURRENCY_CODE — Currency in which the amounts are expressed.

Common Use Cases and Queries

Because the Committed Offers Detail report depends on this view, the principal use case is report data retrieval and downstream extraction. Analysts and developers frequently query it to reconcile commitment numbers against sourcing events, to aggregate buyer commitment values by category or currency, and to extract committed offer detail for external reporting or integration.

A representative query retrieving commitment-level detail is:

SELECT commitment_number, auction_number, auction_title, buyer_name, seller_name, category_id, buyer_amt, currency_code, completed_date FROM pon_mi_offersummary_v WHERE completed_date >= :start_date AND completed_date < :end_date ORDER BY commitment_number;

To summarize committed buyer value by category and currency:

SELECT category_id, currency_code, SUM(buyer_amt) total_committed FROM pon_mi_offersummary_v GROUP BY category_id, currency_code ORDER BY category_id;

To trace a specific commitment number:

SELECT * FROM pon_mi_offersummary_v WHERE commitment_number = :commitment_number;

As with all PON_MI_* views, results should be treated as read-only reporting output; any reconciliation back to transactional sourcing data must be performed against the underlying base tables.