Results for “pon_auction_headers_all”

50+ results




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

Overview

PON_AUCTION_HEADERS_ALL is the master header table for the Oracle Sourcing module (product code PON), owned by the PON schema. It stores the header-level definition of every negotiation — including RFQs, RFIs, reverse auctions, forward auctions, and sourcing templates — across Oracle E-Business Suite releases 12.1.1 and 12.2.2. Each row represents a single negotiation document and carries the commercial, scheduling, currency, approval, and workflow attributes that drive the entire sourcing lifecycle from draft through publish, bidding, evaluation, award, and amendment.

In Data Vault terms, the ETRM heuristic classifies this object as hub-leaning. This is a modeling suggestion rather than a physical design: AUCTION_HEADER_ID functions as a durable business key that anchors a wide fan-out of dependent detail and interface tables, which is characteristic of a hub surrounded by numerous satellite and link structures.

Key Information Stored

The surrogate primary key is AUCTION_HEADER_ID, enforced by PON_AUCTION_HEADERS_ALL_PK and reinforced by the unique index PON_AUCTION_HEADERS_ALL_U1. The remaining 310 documented columns hold the substantive business content. The most operationally significant columns include:

Common Use Cases and Queries

The table is the primary source for sourcing dashboards, procurement analytics, and award tracking. Typical SQL patterns filter by operating unit and status:

  • Active negotiations by buyer: SELECT AUCTION_HEADER_ID, AUCTION_TITLE, AUCTION_STATUS_NAME FROM PON_AUCTION_HEADERS_ALL WHERE ORG_ID = :org AND BUYER_ID = :buyer;
  • Closing-soon report: filter on CLOSE_BIDDING_DATE between SYSDATE and SYSDATE + 7.
  • Award tracking: join PON_AWARD_ALLOCATIONS on AUCTION_HEADER_ID to reconcile awarded amounts.
  • Bid participation analysis: join PON_BID_HEADERS on AUCTION_HEADER_ID alongside NUMBER_OF_BIDS.
  • Amendment lineage: self-join on AUCTION_HEADER_ID_ORIG_AMEND to trace negotiation revisions.

Because columns such as ATTRIBUTE1–ATTRIBUTE15 (both INT_ and EXT_ prefixed) and ORG_ID are present, client extensions and multi-org security are applied through standard DFF and VPD mechanisms.

Related Objects

A large number of dependent tables reference AUCTION_HEADER_ID. The most significant include:

Parent references resolve to HZ_PARTIES, FND_USER, HR_LOCATIONS_ALL, PA_PROJECTS_ALL, FND_CURRENCIES, GL_DAILY_CONVERSION_TYPES, FND_LANGUAGES, PON_AUCTION_EVENTS, PON_AUC_DOCTYPES, and HR_ADE_STYLES, indicating the breadth of cross-module integration that this header supports.