Search Results pon_optimize_bid_class




Overview
Explore in AI Chat

Overview

The PON_OPTIMIZE_BID_CLASS table is a core data object within the Oracle E-Business Suite Sourcing (PON) module, specifically supporting the optimization functionality in Oracle Sourcing. Its primary role is to define and store the association between suppliers (bidders) and specific constraints within an optimization scenario. An optimization scenario is a configuration used to determine the best award decisions in a complex sourcing event, such as a multi-round or combinatorial auction. This table acts as a junction, linking the high-level scenario definition to the actual supplier bids that are subject to its rules, thereby enabling the system to apply sophisticated business constraints to a defined subset of participants during the optimization analysis.

Key Information Stored

The table's structure is defined by a composite primary key, which ensures a unique relationship between a scenario, a constraint, and a bid. The key columns are SCENARIO_ID, which references the parent optimization scenario from PON_OPTIMIZE_SCENARIOS; SEQUENCE_NUMBER, which identifies the specific constraint or class within that scenario; and BID_NUMBER, which references the specific supplier bid from PON_BID_HEADERS. While the provided metadata does not list non-key columns, the table's fundamental purpose is to store the list of BID_NUMBER values that belong to a given constraint class (identified by SCENARIO_ID and SEQUENCE_NUMBER). This allows constraints, such as limiting awards to a certain number of suppliers or enforcing capacity limits, to be applied to a pre-defined group of bidders.

Common Use Cases and Queries

The primary use case is during the execution and analysis of an optimization scenario within a sourcing negotiation. A sourcing analyst or manager would utilize data in this table to validate which suppliers are included in a constraint before running the optimization engine. Common reporting needs include listing all suppliers subject to a particular scenario's constraints or verifying bidder participation. A typical query would join this table to related entities to produce a readable report.

Sample Query:
SELECT poh.bid_number, poh.trading_partner_name, scn.scenario_name, cls.sequence_number
FROM pon_optimize_bid_class cls
JOIN pon_optimize_scenarios scn ON cls.scenario_id = scn.scenario_id
JOIN pon_bid_headers poh ON cls.bid_number = poh.bid_number
WHERE cls.scenario_id = :p_scenario_id
ORDER BY cls.sequence_number, poh.trading_partner_name;

Related Objects

The PON_OPTIMIZE_BID_CLASS table maintains critical foreign key relationships with two primary sourcing tables, ensuring referential integrity and defining its place in the data model.

  • PON_OPTIMIZE_SCENARIOS: This is the parent table for all optimization configurations. The relationship is defined by PON_OPTIMIZE_BID_CLASS.SCENARIO_ID referencing PON_OPTIMIZE_SCENARIOS. A single scenario record can have multiple associated bid class records.
  • PON_BID_HEADERS: This table stores the header information for all bids submitted in a negotiation. The relationship is defined by PON_OPTIMIZE_BID_CLASS.BID_NUMBER referencing PON_BID_HEADERS. A single bid can be associated with multiple constraints across different scenarios.

These relationships position PON_OPTIMIZE_BID_CLASS as a central linking table between the definition of optimization rules and the actual commercial bids upon which those rules are applied.