Results for “attribute_sequence_number”

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

Overview

PON_TEAM_MEMBER_ATTR_SCORES is a transactional table in the PON (Sourcing) module of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. It stores the individual scores awarded by each scoring team member for a specific sourcing attribute against a specific supplier response. In Oracle Sourcing, buyers define scoring teams and requirement attributes for a negotiation; when the negotiation closes, each team member evaluates supplier responses attribute by attribute. This table is the persistent record of that evaluation activity, making it the system of record for team-based, multi-attribute scoring.

The table participates in both auction-style and bid-style negotiations, as evidenced by its dual foreign key paths to PON_AUCTION_HEADERS_ALL and PON_BID_HEADERS. Its role is therefore downstream of negotiation setup and response submission, and upstream of score aggregation and award recommendation logic.

From a heuristic Data Vault modeling perspective mined from the foreign key structure, this object is best classified as a link. It resolves the many-to-many relationship between scoring team members (FND_USER), negotiation header context, and scored attributes, carrying descriptive measures (SCORE, INTERNAL_NOTE) as link attributes. A modeler adopting Data Vault conventions would treat this as a link satellite or an extended link depending on historical tracking requirements.

Key Information Stored

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

• BID_NUMBER — Identifier of the bid or negotiation to which the score belongs; part of the primary key and a foreign key to PON_BID_HEADERS.
• USER_ID — The scoring team member who entered the score; part of the primary key and a foreign key to FND_USER.
• ATTRIBUTE_SEQUENCE_NUMBER — Identifies the scored requirement attribute; part of the primary key.
• AUCTION_HEADER_ID — Foreign key to PON_AUCTION_HEADERS_ALL, distinguishing auction-based negotiations from bid-based ones.
• SECTION_ID — Groups attributes into negotiation sections, supporting section-level scoring rollups.
• SCORE — The numeric score entered by the team member for the attribute and response combination; the principal measure of the table.
• INTERNAL_NOTE — Free-text commentary recorded by the scorer alongside the numeric score.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns capturing who created and last modified each score record.

The surrogate-equivalent unique index PON_TEAM_MEMBER_ATTR_SCORES_U1, defined on (BID_NUMBER, USER_ID, ATTRIBUTE_SEQUENCE_NUMBER), is the business-key candidate and matches the declared primary key PON_TEAM_MEMBER_ATTR_SCORES_PK. This composite key enforces that each team member may hold only one score per attribute per bid.

Common Use Cases and Queries

Typical reporting scenarios include auditing score entry completeness, computing per-attribute average scores across the team, and reviewing the spread of scores to detect outliers. A representative query returns all scores for a bid with the responsible user:

SELECT t.BID_NUMBER, t.USER_ID, t.ATTRIBUTE_SEQUENCE_NUMBER,
       t.SECTION_ID, t.SCORE, t.INTERNAL_NOTE
FROM   PON_TEAM_MEMBER_ATTR_SCORES t
WHERE  t.BID_NUMBER = :bid_number
ORDER  BY t.ATTRIBUTE_SEQUENCE_NUMBER, t.USER_ID;

Averaging by attribute supports consensus analysis before award:

SELECT ATTRIBUTE_SEQUENCE_NUMBER,
       AVG(SCORE) avg_score,
       COUNT(*)   scorer_count
FROM   PON_TEAM_MEMBER_ATTR_SCORES
WHERE  BID_NUMBER = :bid_number
GROUP  BY ATTRIBUTE_SEQUENCE_NUMBER;

Joining to FND_USER retrieves scorer identities, while joining to PON_BID_HEADERS yields negotiation status and dates. These patterns are common in custom BI Publisher reports and OBIEE analyses that supplement the standard Sourcing scoring pages.

Related Objects

• PON_BID_HEADERS — joined on PON_TEAM_MEMBER_ATTR_SCORES.BID_NUMBER; the parent negotiation record.
• PON_AUCTION_HEADERS_ALL — joined on AUCTION_HEADER_ID; identifies auction-style negotiations.
• FND_USER — joined on USER_ID; supplies the scoring team member's identity.
• PON_BID_ATTRIBUTES (and related attribute definition tables) — resolve ATTRIBUTE_SEQUENCE_NUMBER to attribute names and weights.
• PON_TEAM_MEMBERS — defines the scoring team composition that drives expected score rows.
• PON_SCORES and aggregation structures — consume these member-level scores to produce consolidated results.

Because scoring feeds evaluation and award logic, integrators should treat this table as read-mostly and rely on the Sourcing application APIs rather than direct DML.