Search Results pon_bid_price_differentials




Overview
Explore in AI Chat

Overview

The PON_BID_PRICE_DIFFERENTIALS table is a core transactional data store within the Oracle E-Business Suite Sourcing module (PON). It is designed to capture and persist price differentials associated with supplier responses (bids) in a sourcing auction or negotiation. A price differential is a modifier applied to a base price on a specific shipment line, allowing suppliers to offer tiered or conditional pricing based on predefined attributes, such as quantity breaks or geographic regions. This table's role is to maintain the detailed pricing logic of a supplier's bid, enabling the complex price evaluation and comparison functionalities that are central to strategic sourcing operations in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure organizes price differential data by linking it to the specific bid, line, and shipment. Its primary key is a composite of BID_NUMBER, LINE_NUMBER, SHIPMENT_NUMBER, and PRICE_DIFFERENTIAL_NUMBER, ensuring uniqueness for each differential entry. Critical columns include AUCTION_HEADER_ID, which links the differential back to the parent negotiation, and the foreign key columns (BID_NUMBER, LINE_NUMBER, SHIPMENT_NUMBER) that enforce referential integrity with the bid headers and shipments tables. While the provided metadata does not list all columns, typical data stored would encompass the differential type, the adjustment value or percentage, and the applicable attribute or tier (e.g., a specific quantity) that triggers the price change.

Common Use Cases and Queries

This table is primarily accessed for bid analysis, award recommendation, and historical price auditing. A common scenario involves generating a report to compare all price differentials offered by different suppliers for a given auction line. Analysts may query this table to understand the complete, tiered pricing structure of a bid. A sample SQL pattern to retrieve all differentials for a specific bid would be:

  • SELECT * FROM pon_bid_price_differentials WHERE bid_number = <BID_NUMBER> ORDER BY line_number, shipment_number, price_differential_number;

Another key use case is during the automated scoring of bids, where the system calculates the effective unit price by applying the relevant differentials based on the award quantity, sourcing directly from this table.

Related Objects

As indicated by its foreign keys, PON_BID_PRICE_DIFFERENTIALS has strong dependencies on several fundamental Sourcing tables. It is a child table of PON_BID_HEADERS (via BID_NUMBER) and PON_BID_SHIPMENTS (via the composite key of BID_NUMBER, LINE_NUMBER, SHIPMENT_NUMBER). It also references PON_AUCTION_HEADERS_ALL via AUCTION_HEADER_ID, connecting the bid response data to the original sourcing event. For comprehensive reporting, views such as PON_BID_PRICE_DIFFERENTIALS_V may exist to join this data with descriptive flexfield or translated value information. Data is typically created and manipulated through the standard Sourcing negotiation and bidding APIs rather than via direct DML.