Results for “auction_number”

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

Overview

PON_AUC_NOTIF_DELIV_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema within the PON – Sourcing product family. It is a notification and delivery view used by the contract team to report on active bids together with their associated auction information. In the sourcing lifecycle, auctions and bids are stored across separate transactional tables, so this view serves as a consolidated read-only interface that joins an auction header to its active bid headers, exposing both auction-level attributes and supplier (trading partner) details in a single result set.

The view is documented as VALID in ETRM 12.1.1 and 12.2.2 metadata. Because it is a view rather than a table, it contains no independent data storage; all values are derived at query time from the underlying base objects. It is most commonly leveraged for reporting, notifications, and integration queries that need to identify which suppliers currently hold active bids on open negotiations, along with the contract team's visibility into supplier contact information.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms under the APPS schema:

• PON_AUCTION_HEADERS_ALL — the auction header table holding auction document numbers, titles, and bidding open/close dates.
• PON_BID_HEADERS — the bid header table holding bid numbers, trading partner (supplier) identifiers, supplier names, supplier contact identifiers and names, and bid status.

The join is performed on AUCTION_HEADER_ID (AH.AUCTION_HEADER_ID = BH.AUCTION_HEADER_ID), restricting results to bids whose BID_STATUS equals 'ACTIVE'. Consequently, the view returns only active bids and their parent auction context, which is consistent with its stated purpose for the contract team regarding active bids. The view text selects DOCUMENT_NUMBER, AUCTION_TITLE, BID_NUMBER, TRADING_PARTNER_ID, TRADING_PARTNER_NAME, TRADING_PARTNER_CONTACT_ID, TRADING_PARTNER_CONTACT_NAME, OPEN_BIDDING_DATE and CLOSE_BIDDING_DATE, mapped in the published column list to the columns described below.

Key Columns

• AUCTION_NUMBER — the auction document number (document_number from the auction header).
• AUCTION_TITLE — the descriptive title of the negotiation/auction.
• BID_NUMBER — the bid number identifying the supplier's submitted bid.
• SUPPLIER_PARTY_ID — the trading partner (supplier) party identifier, mapped from TRADING_PARTNER_ID.
• SUPPLIER_PARTY_NAME — the name of the trading partner, mapped from TRADING_PARTNER_NAME.
• SUPPLIER_CONTACT_ID — the supplier contact identifier, mapped from TRADING_PARTNER_CONTACT_ID. This is the column users frequently search for when locating supplier contacts associated with active bids.
• SUPPLIER_CONTACT_USER_NAME — the supplier contact name or username, mapped from TRADING_PARTNER_CONTACT_NAME.
• AUCTION_OPEN_DATE — the auction opening date (OPEN_BIDDING_DATE).
• AUCTION_CLOSE_DATE — the auction closing date (CLOSE_BIDDING_DATE).

Common Use Cases and Queries

Typical applications include supplier bid notification reports, contract team dashboards for active negotiations, and integration extracts that push supplier contact details to external systems. The following query returns all active bids with supplier contact information for a given auction:

SELECT auction_number,
       auction_title,
       bid_number,
       supplier_party_id,
       supplier_party_name,
       supplier_contact_id,
       supplier_contact_user_name,
       auction_open_date,
       auction_close_date
FROM   apps.pon_auc_notif_deliv_v
WHERE  auction_number = :auction_number;

To locate active bids by supplier contact, the commonly searched column can be filtered directly:

SELECT auction_number, bid_number, supplier_party_name, supplier_contact_user_name
FROM   apps.pon_auc_notif_deliv_v
WHERE  supplier_contact_id = :supplier_contact_id;

Because the view already restricts to BID_STATUS = 'ACTIVE', no additional bid-status predicate is required. Users should note that the view does not expose inactive or withdrawn bids, and multi-org or operating-unit filtering is not surfaced explicitly in the documented column list; any such restriction must be derived from the underlying auction header context where applicable.