Search Results pon_team_member_attr_scores




Overview
Explore in AI Chat

Overview

The PON_TEAM_MEMBER_ATTR_SCORES table is a core data structure within the Oracle E-Business Suite Sourcing (PON) module, specifically for versions 12.1.1 and 12.2.2. It is designed to capture granular scoring data during the evaluation of supplier responses (bids) in a sourcing event, such as a reverse auction or RFx. Its primary role is to record the individual scores assigned by each member of a scoring team for every scorable attribute associated with a supplier's response. This enables a detailed, multi-evaluator scoring process, which is fundamental to complex, collaborative sourcing decisions. The table's data is essential for calculating aggregate attribute scores, determining overall bid rankings, and providing audit trails for the scoring process.

Key Information Stored

The table stores the linkage between a sourcing event, a supplier response, a specific attribute, and the evaluator's score. Its primary key uniquely identifies a score record through the combination of BID_NUMBER (the supplier's response), USER_ID (the scoring team member), and ATTRIBUTE_SEQUENCE_NUMBER (the specific scored attribute). Key columns include AUCTION_HEADER_ID, which links to the parent sourcing event in PON_AUCTION_HEADERS_ALL, and BID_NUMBER, which links to the specific supplier bid in PON_BID_HEADERS. The table would also contain a column (or columns) to store the actual numeric SCORE or rating provided by the user, along with potential fields for comments or last update dates, as inferred from its functional purpose.

Common Use Cases and Queries

This table is central to reporting and analysis on sourcing event evaluations. Common use cases include generating detailed scoring breakdowns to understand discrepancies between evaluators, auditing the scoring process for compliance, and reconciling final award decisions. A typical query would join this table to supplier, user, and attribute dimension tables to produce a readable scoring report.

  • Sample Query for Scoring Detail: SELECT b.TRADING_PARTNER_NAME, u.USER_NAME, a.ATTRIBUTE_NAME, tms.SCORE FROM PON_TEAM_MEMBER_ATTR_SCORES tms JOIN PON_BID_HEADERS b ON tms.BID_NUMBER = b.BID_NUMBER JOIN FND_USER u ON tms.USER_ID = u.USER_ID JOIN PON_AUCTION_ATTRIBUTES a ON tms.AUCTION_HEADER_ID = a.AUCTION_HEADER_ID AND tms.ATTRIBUTE_SEQUENCE_NUMBER = a.ATTRIBUTE_SEQUENCE_NUMBER WHERE tms.AUCTION_HEADER_ID = :p_auction_id ORDER BY b.BID_NUMBER, a.ATTRIBUTE_SEQUENCE_NUMBER;
  • Data Integrity Checks: Queries to identify missing scores from required team members before finalizing an event evaluation.

Related Objects

PON_TEAM_MEMBER_ATTR_SCORES is deeply integrated within the Sourcing schema, maintaining critical foreign key relationships with other principal tables.

  • PON_BID_HEADERS: Links via BID_NUMBER to the supplier response being scored.
  • PON_AUCTION_HEADERS_ALL: Links via AUCTION_HEADER_ID to the master sourcing event definition.
  • FND_USER: Links via USER_ID to the application user (scoring team member) who assigned the score.
  • PON_AUCTION_ATTRIBUTES: Related via AUCTION_HEADER_ID and ATTRIBUTE_SEQUENCE_NUMBER to the definition of the attribute being scored.