Search Results pon_bid_attribute_values_pk

Overview

PON_BID_ATTRIBUTE_VALUES is a transactional table in the Oracle EBS Sourcing (PON) module. It stores the attribute values captured against each line item of a supplier's response (bid) to a negotiation. When a buyer publishes a negotiation — such as an RFQ, RFI, or auction — with defined attributes, suppliers respond with values for those attributes at the bid line level. This table persists those responses alongside scoring information, enabling structured evaluation and comparison of supplier submissions.

In Oracle EBS 12.1.1 and 12.2.2, the table resides in the PON schema and is considered VALID. From a Data Vault modeling perspective, the metadata classifies this object as standalone (heuristic, mined from FK structure). This suggests it functions as a satellite-like detail table that captures descriptive attribute data keyed to a parent negotiation line context; it does not behave as a hub or link, though it carries a foreign key to PON_AUCTION_HEADERS_ALL.

Key Information Stored

The table contains 27 documented columns. The most significant are summarized below, distinguishing the surrogate primary key from business-key candidates.

• Primary key (PON_BID_ATTRIBUTE_VALUES_PK): Composed of BID_NUMBER, LINE_NUMBER, and ATTRIBUTE_NAME — this surrogate/composite key uniquely identifies one attribute value per bid line.
• AUCTION_HEADER_ID: Foreign key referencing PON_AUCTION_HEADERS_ALL; links the value to its parent negotiation header.
• AUCTION_LINE_NUMBER: Identifies the negotiation line to which the attribute belongs.
• BID_NUMBER and LINE_NUMBER: Business-key candidates identifying the supplier bid and its line.
• ATTRIBUTE_NAME: The name of the attribute being answered.
• DATATYPE: Indicates the value's data type (text, number, date, etc.).
• VALUE / OLD_VALUE: The current and prior attribute values, supporting change tracking.
• SCORE / WEIGHTED_SCORE: Evaluator scoring applied to the response, including weighting.
• ATTR_LEVEL / ATTR_GROUP_SEQ_NUMBER / ATTR_DISP_SEQ_NUMBER / SEQUENCE_NUMBER: Control attribute hierarchy and display ordering.
• INTERNAL_NOTE: Buyer-side notes not visible to suppliers.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID.
• WORKSHEET_NAME / WORKSHEET_SEQUENCE_NUMBER: Relate values to evaluation worksheets.

Common Use Cases and Queries

Typical reporting scenarios include extracting supplier attribute responses for a negotiation, comparing scores across bids, and auditing value changes. A representative query retrieves all attribute values for a given negotiation:

• SELECT b.BID_NUMBER, b.LINE_NUMBER, b.ATTRIBUTE_NAME, b.VALUE, b.SCORE, b.WEIGHTED_SCORE FROM PON_BID_ATTRIBUTE_VALUES b WHERE b.AUCTION_HEADER_ID = :header_id ORDER BY b.AUCTION_LINE_NUMBER, b.SEQUENCE_NUMBER;
• Joining to PON_AUCTION_HEADERS_ALL to obtain negotiation context: ...FROM PON_BID_ATTRIBUTE_VALUES b JOIN PON_AUCTION_HEADERS_ALL h ON b.AUCTION_HEADER_ID = h.AUCTION_HEADER_ID;
• Filtering by DATATYPE to isolate numeric versus text responses for scoring analysis.

Related Objects

• PON_AUCTION_HEADERS_ALL: Parent negotiation header, joined on AUCTION_HEADER_ID.
• PON_BID_HEADERS / supplier bid tables: Provide bid-level context via BID_NUMBER.
• PON_AUCTION_LINES_ALL: Supplies line definitions via AUCTION_LINE_NUMBER.
• PON_AUCTION_ATTRIBUTES: Defines attribute metadata referenced by ATTRIBUTE_NAME.
• PON_BID_ATTRIBUTE_VALUES_PK: Constraint enforcing uniqueness across the composite key.