Search Results full_quantity_bid_code

Overview

PON_AUCTION_HEADERS_V is a Multi-Org Access Control (MOAC) sensitive view owned by the APPS schema in the Oracle E-Business Suite. It belongs to the PON (Sourcing) product family and exposes the header-level detail of sourcing auctions — the negotiation documents created through Oracle Sourcing and Sourcing Pro. The view is defined over the base table PON_AUCTION_HEADERS and applies organization-based row filtering so that only auctions accessible to the session's current operating unit context are returned. This makes it the preferred reporting and integration entry point for auction data, since it respects the same security semantics as the Sourcing application forms rather than surfacing all rows across operating units.

Although the object is documented as the MOAC-sensitive view of PON_AUCTION_HEADERS, the underlying view text includes a range of derived and decoded columns (for example, the recalculated CLOSE_BIDDING_DATE), which makes it useful both for transactional extraction and for status reporting on live negotiations.

Underlying Base Objects

The documented metadata lists the following referenced base objects: PON_AUCTION_HEADERS (synonym), FND_LOOKUP_VALUES (synonym), HR_ALL_ORGANIZATION_UNITS_TL (synonym), HZ_PARTIES (synonym), and PON_LOCALE_PKG (package).

• PON_AUCTION_HEADERS — the primary base table supplying virtually all column values in the view, including identifiers, statuses, dates, terms, and auction configuration flags.
• FND_LOOKUP_VALUES — resolves coded values (such as auction status and bid visibility) into their displayed meanings.
• HR_ALL_ORGANIZATION_UNITS_TL — provides organization name translations used to filter records according to the operating unit context, and is central to the MOAC behavior.
• HZ_PARTIES — supplies trading partner (supplier) party detail associated with the auction.
• PON_LOCALE_PKG — a PL/SQL package invoked within the view to render locale-sensitive formatting, typically for numeric or monetary presentation.

Key Columns

The view exposes a broad set of header attributes. Notable columns include:

• AUCTION_HEADER_ID — unique identifier and primary join key to lines, bidders, and award tables.
• AUCTION_TITLE, AUCTION_TYPE, CONTRACT_TYPE — descriptive classification of the negotiation.
• AUCTION_STATUS and AUCTION_STATUS_NAME — the coded status and its decoded display value; AWARD_STATUS and AWARD_STATUS_NAME follow the same pattern.
• TRADING_PARTNER_ID, TRADING_PARTNER_NAME, TRADING_PARTNER_CONTACT_ID — supplier and contact identification.
• OPEN_BIDDING_DATE, CLOSE_BIDDING_DATE, ORIGINAL_CLOSE_BIDDING_DATE, VIEW_BY_DATE, AWARD_BY_DATE — schedule columns. CLOSE_BIDDING_DATE is recalculated using a DECODE on IS_PAUSED, adding the elapsed pause interval when an auction is suspended.
• CURRENCY_CODE, RATE_TYPE, RATE_DATE, RATE — currency conversion context for the negotiation.
• SHIP_TO_LOCATION_ID, BILL_TO_LOCATION_ID, PAYMENT_TERMS_ID, FREIGHT_TERMS_CODE, FOB_CODE — commercial and logistics defaults.
• WORKFLOW_ITEM_KEY / WF_ITEM_KEY, WF_ROLE_NAME — workflow association for the approval and notification process.
• PO_TXN_FLAG, PO_START_DATE, PO_END_DATE, PO_AGREED_AMOUNT — indicators and dates relating the auction to downstream purchasing documents.
• SEALED_AUCTION_STATUS, SEALED_ACTUAL_UNLOCK_DATE — sealed bidding control attributes.

Common Use Cases and Queries

Typical uses include monitoring open negotiations, auditing award activity, and feeding sourcing data into custom reports or interfaces. The view is especially relevant where the user's search term PO_STYLE_ID appears in related Sourcing objects; while PO_STYLE_ID is a purchasing document style attribute, this view is joined to auction lines and purchasing documents to resolve style context in integrated reporting.

List currently open auctions for the operating unit:

SELECT auction_header_id, auction_title, auction_status_name,
       close_bidding_date, trading_partner_name
  FROM apps.pon_auction_headers_v
 WHERE auction_status_name IN ('Active','Open')
 ORDER BY close_bidding_date;

Extract auction headers for a specific supplier:

SELECT auction_header_id, auction_title, currency_code,
       po_agreed_amount, award_status_name
  FROM apps.pon_auction_headers_v
 WHERE trading_partner_id = :p_vendor_id;

Because MOAC filtering is applied within the view, these queries automatically restrict results to the operating unit context established by the session, avoiding the need for explicit org_id predicates in most reporting scenarios.