Search Results pon_auction_item_prices_all




Overview

The PON_AUCTION_ITEM_PRICES_ALL table is a core data repository within the Oracle E-Business Suite Sourcing (PON) module for versions 12.1.1 and 12.2.2. It functions as the primary transactional table for storing line-level details of negotiation items, most critically their pricing information. Every line item created within a sourcing negotiation, such as a Request for Quotation (RFQ) or a Reverse Auction, is recorded in this table. Its role is integral to the entire sourcing lifecycle, serving as the definitive source for item descriptions, quantities, target prices, and other line-specific attributes that suppliers bid against. The table's structure supports complex sourcing events by maintaining relationships to project accounting, inventory categories, and procurement line types.

Key Information Stored

The table's primary key is a composite of AUCTION_HEADER_ID and LINE_NUMBER, uniquely identifying each item line within a specific negotiation header. While the full column list is extensive, critical columns include AUCTION_HEADER_ID (link to PON_AUCTION_HEADERS_ALL), LINE_NUMBER, GROUP_TYPE (for lot or group lines), CATEGORY_ID (link to MTL_CATEGORIES_B for the item category), ITEM_DESCRIPTION, QUANTITY, and PRICE. It also stores pricing-related fields such as PRICE_DISPLAY_TARGET_FLAG and PRICE_TYPE. For project-centric procurement, it holds PROJECT_ID, PROJECT_TASK_ID, and PROJECT_EXPENDITURE_TYPE, linking to the Project Accounting (PA) module. The LINE_TYPE_ID column references PO_LINE_TYPES_B to define the accounting and control characteristics of the procurement line.

Common Use Cases and Queries

This table is central to reporting and data extraction for sourcing analysis. Common use cases include generating item price comparisons across auctions, analyzing category spending through sourcing events, and auditing the item setup for specific negotiations. A typical query joins this table with the auction header and bid tables to analyze line item performance. For example, to list all items and their target prices for a specific auction, one might use:

  • SELECT p.line_number, p.item_description, p.quantity, p.price FROM pon_auction_item_prices_all p WHERE p.auction_header_id = <header_id> ORDER BY p.line_number;

Another common pattern involves joining with PON_BID_ITEM_PRICES to compare target prices against received supplier bids for cost-saving analysis. Data from this table is also essential for integration flows that create purchase orders or requisitions from awarded negotiation lines.

Related Objects

The table maintains extensive foreign key relationships, acting as a hub for sourcing line-item data. The documented relationships are:

These relationships underscore the table's critical position in the sourcing data model, connecting master data, transactional bids, and supporting attributes.