Search Results pon_auction_attributes




Overview
Explore in AI Chat

Overview

The PON_AUCTION_ATTRIBUTES table is a core data object within the Oracle E-Business Suite Sourcing (PON) module, specifically for versions 12.1.1 and 12.2.2. It functions as the primary repository for storing detailed attribute information associated with individual lines (items) in a sourcing negotiation, such as a Request for Quotation (RFQ) or Reverse Auction. This table enables buyers to define and capture specific, non-price criteria for items, which is essential for conducting comprehensive bid evaluations. Its role is to persist the structured attribute data that supplements basic item pricing, allowing for a multi-dimensional analysis of supplier responses.

Key Information Stored

The table's structure is designed to link attributes to specific negotiation lines uniquely. Its primary key is a composite of four columns: AUCTION_HEADER_ID, LINE_NUMBER, ATTRIBUTE_LIST_ID, and ATTRIBUTE_NAME. This combination ensures that each attribute for a given item in a specific negotiation is uniquely identifiable. The AUCTION_HEADER_ID links to the parent negotiation header, while LINE_NUMBER ties the attribute to a specific item line. The ATTRIBUTE_LIST_ID references the master list of attributes, and ATTRIBUTE_NAME stores the name of the specific attribute (e.g., "Purity," "Lead Time," "Warranty"). While the provided metadata does not list all columns, typical attribute tables in this context would also include columns for the attribute's datatype, value, display sequence, and whether it is mandatory or scored.

Common Use Cases and Queries

This table is central to operations requiring analysis of bid responses beyond unit price. A common use case is generating a report that compares all submitted attribute values for a critical item across multiple suppliers to facilitate award decisions. Another scenario involves validating that all required (mandatory) attributes have been populated by suppliers before closing a negotiation. A typical query pattern would join this table with PON_AUCTION_ITEM_PRICES_ALL to correlate attribute data with pricing and supplier information. For example: SELECT paa.attribute_name, paa.attribute_value, paip.bid_number FROM pon_auction_attributes paa, pon_auction_item_prices_all paip WHERE paa.auction_header_id = paip.auction_header_id AND paa.line_number = paip.line_number AND paa.auction_header_id = :p_auction_id; This retrieves all attribute values with their associated bid numbers for a given negotiation.

Related Objects

The table maintains defined foreign key relationships with several other key Sourcing tables, as documented in the metadata. Its primary relationship is with the PON_AUCTION_ITEM_PRICES_ALL table, using the composite key of AUCTION_HEADER_ID and LINE_NUMBER. This links each attribute directly to its corresponding item price record. Furthermore, it references the PON_ATTRIBUTE_LISTS and PON_AUCTION_TEMPLATES tables via the ATTRIBUTE_LIST_ID column. This connection ties the negotiation line attributes back to the master attribute definitions and the sourcing templates from which they may have been derived, ensuring consistency and reusability of attribute configurations across the application.