Search Results evaluation_score_id

Overview

The PO.POA_CM_EVAL_SCORES table is a transactional data object within the Oracle E-Business Suite Purchasing (PO) schema. It is part of the Procurement Contracts / Contract Management evaluation framework (POA_CM), which supports the structured scoring of suppliers, bids, or contract candidates against defined evaluation criteria. Despite its PO ownership, the table is functionally part of the sourcing and supplier qualification domain, capturing the individual criterion-level scores that roll up into an overall evaluation.

Each row in POA_CM_EVAL_SCORES represents a single score awarded against one criterion for one evaluation event. The table is classified in the ETRM metadata as standalone under the heuristic Data Vault mining, though its documented foreign key to AMW_EVALUATIONS_B indicates it should be modeled as a satellite of the evaluation hub, with EVALUATION_ID acting as the parent link and CURIES on the score attributes describing the measurement context.

Key Information Stored

The table contains 33 documented columns. The most significant are:

• EVALUATION_SCORE_ID — surrogate primary key, enforced by unique index POA_CM_EVAL_SCORES_U1. This is the column most commonly referenced by the "evaluation_score_id" search term.
• EVALUATION_ID — foreign key to PO.AMW_EVALUATIONS_B, tying each score line to its parent evaluation.
• CRITERIA_CODE — the evaluation criterion against which the score applies; together with EVALUATION_ID it forms the business-key candidate POA_CM_EVAL_SCORES_U2.
• SCORE — the numeric score awarded for the criterion.
• WEIGHT — the weighting applied to the criterion when aggregating the total evaluation result.
• MIN_SCORE and MAX_SCORE — the permitted scoring range for the criterion.
• COMMENTS — free-text justification or remarks (VARCHAR2 240).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program WHO columns identifying the process that last touched the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard Oracle flexfield descriptive column set for extensibility.

Common Use Cases and Queries

Typical reporting scenarios include extracting total weighted scores per evaluation, comparing individual criterion scores across suppliers, and auditing who entered or modified scores.

SELECT s.evaluation_id, s.criteria_code, s.score, s.weight,
       s.score * s.weight weighted_score
FROM   po.poa_cm_eval_scores s
WHERE  s.evaluation_id = :p_evaluation_id
ORDER  BY s.criteria_code;

Aggregated supplier rankings can be produced by joining to AMW_EVALUATIONS_B and grouping on EVALUATION_ID:

SELECT s.evaluation_id, SUM(s.score * s.weight) total_score
FROM   po.poa_cm_eval_scores s
GROUP  BY s.evaluation_id;

Audit queries against CREATED_BY / LAST_UPDATED_BY joined to FND_USER support control and compliance review.

Related Objects

• PO.AMW_EVALUATIONS_B — parent evaluation header; join on EVALUATION_ID.
• PO.POA_CM_EVAL_HEADERS / evaluation APIs — evaluate_score rows are created and maintained through the standard Oracle evaluation programs identified by PROGRAM_ID, REQUEST_ID.
• FND_USER — via CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — via LAST_UPDATE_LOGIN.
• FND_CONCURRENT_REQUESTS — via REQUEST_ID.
• FND_APPLICATION and FND_CONCURRENT_PROGRAM — via PROGRAM_APPLICATION_ID and PROGRAM_ID.

As with all PO-schema contract management objects, Oracle does not support direct DML against POA_CM_EVAL_SCORES; access should be through standard Oracle Applications programs.