Search Results pon_auction_headers_all_v




Overview

PON_AUCTION_HEADERS_ALL_V is an APPS-owned database view in the PON (Sourcing) module of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It is a common view defined over the PON_AUCTION_HEADERS_ALL base table, exposing header-level information for sourcing auctions, including negotiation status, award status, bid schedules, pricing controls, and sealed-auction tracking attributes. Because it presents auction header data in a single denormalized row per negotiation, the view serves as a primary reporting and integration surface for sourcing professionals, BI Publisher reports, OBIEE extracts, and custom PL/SQL that must read auction metadata without joining the raw base table directly. A distinguishing characteristic of this view is that it does not simply project the base columns; it applies a decode to compute a dynamic close bidding date, and it resolves descriptive flexfield, lookup, and party information through the referenced companion objects. This makes the view the recommended access point where a business-meaningful close time and descriptive values are required.

Underlying Base Objects

The documented reference tree for the view includes PON_AUCTION_HEADERS_ALL, HR_ALL_ORGANIZATION_UNITS_TL, HZ_PARTIES, FND_LOOKUP_VALUES, and PON_LOCALE_PKG, all accessed through APPS synonyms. PON_AUCTION_HEADERS_ALL is the core base table supplying nearly all projected columns. HR_ALL_ORGANIZATION_UNITS_TL resolves the operating unit or organization description associated with the auction, typically exposed through the trading partner or ship-to context. HZ_PARTIES supplies trading partner (supplier) party details. FND_LOOKUP_VALUES resolves coded values such as auction status, award status, bid visibility, bid list type, and freight terms into their displayed meanings; the STATUS_NAME and AWARD_STATUS_NAME columns in the projection are populated from this source. PON_LOCALE_PKG is a PL/SQL package invoked for locale-sensitive formatting and territory or language handling, ensuring the view returns values consistent with the session locale rather than raw stored codes.

Key Columns

The view exposes the full auction header column set. Identity and descriptive columns include AUCTION_HEADER_ID (the primary key and the join anchor to lines, bidders, and awards), AUCTION_TITLE, AUCTION_TYPE, and CONTRACT_TYPE. Status columns include AUCTION_STATUS and AUCTION_STATUS_NAME plus AWARD_STATUS and AWARD_STATUS_NAME, which together drive dashboard filtering. Schedule columns include OPEN_BIDDING_DATE, ORIGINAL_CLOSE_BIDDING_DATE, VIEW_BY_DATE, AWARD_BY_DATE, PUBLISH_DATE, CLOSE_DATE, and CANCEL_DATE, along with TIME_ZONE. Notably, CLOSE_BIDDING_DATE is computed: when IS_PAUSED is 'Y', the view returns SYSDATE plus the remaining interval between CLOSE_BIDDING_DATE and LAST_PAUSE_DATE; otherwise it returns the stored close date. Trading partner columns include TRADING_PARTNER_ID, TRADING_PARTNER_NAME, TRADING_PARTNER_NAME_UPPER, and TRADING_PARTNER_CONTACT_NAME. Bidding control columns include BID_VISIBILITY_CODE, BID_SCOPE_CODE, BID_FREQUENCY_CODE, AUTO_EXTEND_FLAG, AUTO_EXTEND_NUMBER, AUTO_EXTEND_DURATION, MIN_BID_DECREMENT, MIN_BID_INCREMENT, MIN_BID_CHANGE_TYPE, NUMBER_OF_BIDS, NUMBER_PRICE_DECIMALS, PROXY_BID_ALLOWED_FLAG, ALLOW_OTHER_BID_CURRENCY_FLAG, and FULL_QUANTITY_BID_CODE. Sealed-auction tracking is supported by SEALED_AUCTION_STATUS, SEALED_ACTUAL_UNLOCK_DATE, SEALED_ACTUAL_UNSEAL_DATE, SEALED_UNLOCK_TP_CONTACT_ID, and SEALED_UNSEAL_TP_CONTACT_ID. Workflow and audit columns include WF_ITEM_KEY, WF_ROLE_NAME, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY.

Common Use Cases and Queries

Typical uses include open-auction dashboards, supplier participation reports, award-cycle aging analysis, and integration extracts that feed external sourcing portals. Because CLOSE_BIDDING_DATE is dynamically computed for paused auctions, any report on remaining bid time should read this view rather than the base table. The STATUS_NAME columns eliminate the need to decode lookups manually.

  • List active auctions with their effective close time:
    SELECT auction_header_id,
           auction_title,
           auction_status_name,
           close_bidding_date
      FROM apps.pon_auction_headers_all_v
     WHERE auction_status IN ('ACTIVE','PUBLISHED');
  • Award-cycle aging by trading partner:
    SELECT trading_partner_name,
           auction_title,
           award_status_name,
           award_by_date
      FROM apps.pon_auction_headers_all_v
     WHERE award_status = 'PENDING'
     ORDER BY award_by_date;
  • Detect paused or auto-extended negotiations:
    SELECT auction_header_id,
           auction_title,
           auto_extend_flag,
           number_of_extensions
      FROM apps.pon_auction_headers_all_v
     WHERE auto_extend_flag = 'Y';
  • Sealed-auction monitoring:
    SELECT auction_header_id,
           sealed_auction_status,
           sealed_actual_unseal_date
      FROM apps.pon_auction_headers_all_v
     WHERE sealed_auction_status IS NOT NULL;

Joins to PON_AUCTION_HEADERS_ALL on AUCTION_HEADER_ID, and to auction lines and bidder tables on the same key, support detail-level drill-down. As with all APPS views, queries should qualify the APPS schema and respect operating unit security where the underlying table is org-striped.