Results for “internal_note”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PON_TEAM_MEMBER_BID_SCORES is a transactional table in the PON (Sourcing) schema of Oracle E-Business Suite, holding the per-evaluator scoring records generated when a negotiation (auction or sourcing event) is configured for team-based scoring. When the team scoring feature is enabled on a negotiation, each team member independently evaluates supplier responses, and this table persists the result of that evaluation: which user scored which bid, the associated negotiation header, when the score was entered, and the current status of that score. It therefore acts as the bridge between individual evaluator activity and the aggregated negotiation outcome.

From a dimensional modeling perspective, the mined foreign-key structure suggests this object is best treated as a link table. It resolves a many-to-many relationship between team members (FND_USER) and supplier bids (PON_BID_HEADERS) within the context of a negotiation (PON_AUCTION_HEADERS_ALL), rather than functioning as a hub of independent business entities or a satellite of descriptive attributes on a single parent.

Key Information Stored

The documented physical schema contains 11 columns. The most significant are the identifying and scoring attributes:

• BID_NUMBER — identifies the supplier response being scored; part of the composite primary key and a foreign key to PON_BID_HEADERS.
• USER_ID — the team member (evaluator) who entered the score; the second component of the primary key and a foreign key to FND_USER.
• AUCTION_HEADER_ID — the negotiation header to which the bid and evaluation belong; foreign key to PON_AUCTION_HEADERS_ALL.
• LAST_SCORE_DATE — the date on which the response was most recently scored by that evaluator.
• SCORE_STATUS — the current status of the evaluator's score, supporting workflow states such as in-progress or completed scoring.
• INTERNAL_NOTE — buyer-side internal commentary associated with the evaluation.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns tracking who created and last modified the row and through which login session.

The primary key is PON_TEAM_MEMBER_BID_SCORES_PK, defined on the composite of (BID_NUMBER, USER_ID). A separate unique index, PON_TEAM_MEMBER_BID_SCORES_U1 on (AUCTION_HEADER_ID, BID_NUMBER, USER_ID), serves as the business-key candidate, guaranteeing that a given evaluator scores a given bid only once within a negotiation.

Common Use Cases and Queries

Typical reporting scenarios include monitoring team scoring progress before an award decision, auditing which evaluators have completed their scores, and reconciling individual evaluations against the aggregate negotiation result.

SELECT s.bid_number,
       s.user_id,
       u.user_name,
       s.score_status,
       s.last_score_date
FROM   pon_team_member_bid_scores s,
       fnd_user u
WHERE  s.auction_header_id = :auction_header_id
AND    s.user_id = u.user_id
ORDER BY s.bid_number, u.user_name;

A second common pattern joins to PON_BID_HEADERS to display the supplier response alongside each evaluator's score status, and a third identifies outstanding evaluators by filtering SCORE_STATUS for incomplete values. Because INTERNAL_NOTE is buyer-facing only, queries exposing it should be restricted to internal sourcing users.

Related Objects

The table participates in the following documented relationships:

• PON_AUCTION_HEADERS_ALL — joined on AUCTION_HEADER_ID; supplies the negotiation context for the scoring record.
• PON_BID_HEADERS — joined on BID_NUMBER; provides the supplier response being evaluated.
• FND_USER — joined on USER_ID; resolves the evaluator's user name and identity.
• PON_TEAM_MEMBER_BID_SCORES_PK / _U1 — the primary and unique indexes that enforce uniqueness and drive efficient lookups by negotiation, bid, and evaluator.
• PON team scoring setup and scoring UI — the Sourcing application logic that creates and updates rows here when team scoring is enabled.