Results for “price_differential_number”

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

Overview

The PON_BID_PRICE_DIFFERENTIALS table resides in the PON schema and belongs to the Oracle E-Business Suite Sourcing (PON) product family. It stores the response price differentials associated with a supplier's bid or auction response. In Oracle Sourcing, buyers can define price differentials on a sourcing document to adjust the effective price of a line or shipment based on a supplier's entered response — for example, a fixed or percentage adjustment applied to the base price quoted for a specific shipment. Each row in this table captures one such differential for a given bid, line, shipment, and differential sequence.

Because the table records many differentially-valued rows that depend on a parent bid header, shipment, and auction context, the ETRM metadata heuristically classifies it as a link object within a Data Vault modeling convention — it connects a bid header, bid shipment, and auction header to a set of differential attributes and their values. This classification is a modeling suggestion only; the physical table is a standard third-normal-form transactional table with a composite primary key.

Key Information Stored

The table is defined with 18 documented columns. The composite primary key PON_BID_PRICE_DIFF_PK1 is formed from BID_NUMBER, LINE_NUMBER, SHIPMENT_NUMBER, and PRICE_DIFFERENTIAL_NUMBER. These four columns together act as the surrogate/unique business key and represent the natural grain of the record. The most significant columns include:

• BID_NUMBER — Identifier of the parent sourcing bid/response; foreign key to PON_BID_HEADERS.
• LINE_NUMBER — The bid line to which the differential applies; part of the key and of the shipment foreign key.
• SHIPMENT_NUMBER — The shipment within the line; foreign key to PON_BID_SHIPMENTS.
• PRICE_DIFFERENTIAL_NUMBER — Sequence identifying each discrete differential defined for the line/shipment.
• AUCTION_HEADER_ID — Links the record to the auction context; foreign key to PON_AUCTION_HEADERS_ALL.
• PRICE_TYPE — Indicates the type of price differential being applied.
• MULTIPLIER — The current multiplication/adjustment factor applied to the base price.
• OLD_MULTIPLIER — The prior multiplier value, preserved for change tracking and audit.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns identifying the process that last modified the row.
• INTERFACE_LINE_ID — Reference to an interface line, used when differentials flow through the sourcing interface/open interface tables.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit (WHO) columns.

Common Use Cases and Queries

Typical usage centres on reporting and validating the price differentials applied to supplier responses, particularly for auctions where competitive adjustments drive the awarded price.

• Listing all differentials for a bid or auction and inspecting current versus prior multipliers:

SELECT b.bid_number, b.line_number, b.shipment_number,
       b.price_differential_number, b.price_type,
       b.multiplier, b.old_multiplier
FROM   pon_bid_price_differentials b
WHERE  b.bid_number = :bid_number
ORDER  BY b.line_number, b.shipment_number,
          b.price_differential_number;

• Joining to the auction header to analyse differentials per auction:

SELECT h.auction_header_id, d.bid_number, d.price_type, d.multiplier
FROM   pon_bid_price_differentials d,
       pon_auction_headers_all h
WHERE  d.auction_header_id = h.auction_header_id;

• Auditing changes by examining rows where MULTIPLIER differs from OLD_MULTIPLIER.
• Tracing concurrent program activity through PROGRAM_ID and REQUEST_ID for interface-driven loads.

Related Objects

The following objects are most tightly coupled to PON_BID_PRICE_DIFFERENTIALS through the documented foreign key relationships:

• PON_BID_HEADERS — joined on BID_NUMBER; provides the parent response header.
• PON_BID_SHIPMENTS — joined on BID_NUMBER, LINE_NUMBER, and SHIPMENT_NUMBER; provides the shipment context for the differential.
• PON_AUCTION_HEADERS_ALL — joined on AUCTION_HEADER_ID; supplies the auction-level information governing the response.

These three parents anchor the row to its response, shipment, and auction contexts, making them the primary navigation targets for any query, report, or integration touching price differentials.