Search Results pon_attribute_scores_uk

Overview

PON_ATTRIBUTE_SCORES is a table in the PON (Sourcing) schema of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2, with status VALID. It stores the scoring criteria defined for a particular sourcing attribute, enabling buyers to assign numeric scores or score ranges to supplier responses during auctions, RFQs, and negotiated sourcing events. In practical terms, the table preserves the translation logic that converts a raw supplier answer, whether a discrete value or a value falling inside a numeric range, into a comparable score used for ranking and award decisions.

From a Data Vault modeling perspective, the metadata classifies this object as standalone, meaning no foreign key relationships were mined from the physical constraint structure. A heuristic reading therefore suggests modeling it as a satellite that captures the scoring definitions attached to an attribute-list/auction context, rather than as a hub or link. This classification should be treated as a design suggestion only, since functional relationships to attribute lists and auction headers clearly exist through the documented columns even where database-level constraints are absent.

Key Information Stored

The documented physical schema contains thirteen columns. The most significant are summarized below.

• AUCTION_HEADER_ID, LINE_NUMBER: Scope each scoring row to a specific auction and line, tying the criteria to the sourcing event and the line being evaluated.
• ATTRIBUTE_LIST_ID, ATTRIBUTE_SEQUENCE_NUMBER: Identify the attribute list and the specific attribute within it to which the scoring criteria apply.
• SEQUENCE_NUMBER: Orders the individual score bands or scoring rules defined for the attribute.
• VALUE: Holds the discrete attribute value that a scoring rule matches.
• FROM_RANGE, TO_RANGE: Define a lower and upper bound for range-based scoring, used when responses are numeric rather than discrete.
• SCORE: The numeric score awarded when a response matches the VALUE or falls within the FROM_RANGE/TO_RANGE interval.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY: Standard audit columns recording who created and last modified each scoring rule and when.

The unique index PON_ATTRIBUTE_SCORES_UK (ATTRIBUTE_LIST_ID, AUCTION_HEADER_ID, LINE_NUMBER, ATTRIBUTE_SEQUENCE_NUMBER, SEQUENCE_NUMBER) serves as the primary key. A second unique index, PON_ATTRIBUTE_SCORES_U1, orders the same columns differently (AUCTION_HEADER_ID, LINE_NUMBER, ATTRIBUTE_SEQUENCE_NUMBER, SEQUENCE_NUMBER, ATTRIBUTE_LIST_ID) and is a business-key candidate. Because both indexes cover the same column set, the primary key is effectively a composite business key rather than a single surrogate identifier.

Common Use Cases and Queries

Typical reporting requirements include reconstructing the scoring matrix for a live or historical auction, validating that scoring bands do not overlap, and tracing how awarded scores were derived. The following pattern retrieves the full scoring matrix for a given auction and line.

• Score band retrieval: SELECT attribute_sequence_number, sequence_number, value, from_range, to_range, score FROM pon_attribute_scores WHERE auction_header_id = :auction_id AND line_number = :line ORDER BY attribute_sequence_number, sequence_number;
• Attribute-level scoring rules: filter by attribute_list_id and attribute_sequence_number to isolate one attribute's criteria.
• Maintenance audit: filter on last_update_date to identify scoring rules changed after an auction opened.
• Range validation: compare from_range and to_range across consecutive sequence numbers to detect gaps or overlaps.

Related Objects

Because the mined classification is standalone, no database-level foreign keys are documented. Functional joins are nevertheless implied by the shared columns below.

• PON_AUCTION_HEADERS_ALL: joined on AUCTION_HEADER_ID to resolve auction context.
• PON_AUCTION_LINES_ALL (or equivalent auction line object): joined on AUCTION_HEADER_ID and LINE_NUMBER.
• PON_ATTRIBUTE_LISTS / PON_ATTRIBUTES: joined on ATTRIBUTE_LIST_ID and ATTRIBUTE_SEQUENCE_NUMBER to resolve attribute names.
• PON_BID_ATTRIBUTE_VALUES: compared against VALUE and FROM_RANGE/TO_RANGE to derive awarded scores.
• PON_AUCTION_SCORES / scoring result objects: consume the SCORE column for ranking and award analysis.