Search Results poa_cm_evaluation




Overview
Explore in AI Chat

Overview

The POA_CM_EVALUATION table is a Purchasing (PO) module object in Oracle EBS 12.1.1 and 12.2.2, owned by the PO schema and documented as VALID in ETRM. It is a transactional data store used by Oracle Procurement Contracts and supplier performance evaluation functionality (the POA / Procurement "Evaluation" and supplier scorecarding subsystem). Each row captures a single evaluation record — typically a supplier, supplier site, or operational unit performance assessment scoped to a defined period and measure — together with the standard Oracle EBS "who column" and multi-attribute (ATTRIBUTE1–15) audit and extensibility fields. It contains 37 documented columns in 12.1.1.

The ETRM Data Vault classification heuristic reports this table as standalone. It has a single outbound foreign key (EVALUATION_ID → AMW_EVALUATIONS_B) and no documented inbound foreign keys. In Data Vault terms, this object is best modeled as a satellite or hub-and-satellite combination, since it owns the business key (EVALUATION_ID, enforced via the unique index POA_CM_EVALUATION_U1) and carries descriptive and multi-attribute context around it. The classification is a modeling suggestion only.

Key Information Stored

Common Use Cases and Queries

Typical reporting scenarios include supplier scorecard reporting, period-over-period supplier performance trending, and item/category performance analysis. A common query pattern joins the evaluation to its parent definition to retrieve evaluation metadata:

  • Supplier scorecard extract: SELECT EVALUATION_ID, SUPPLIER_ID, SUPPLIER_SITE_ID, CUSTOM_MEASURE_CODE, PERIOD_NAME FROM POA_CM_EVALUATION WHERE PERIOD_NAME = :period;
  • Joining the parent evaluation definition: SELECT e.*, b.* FROM POA_CM_EVALUATION e, AMW_EVALUATIONS_B b WHERE e.EVALUATION_ID = b.EVALUATION_ID; (adjust for the exact AMW key column).
  • Evaluator workload: SELECT EVALUATED_BY, COUNT(*) FROM POA_CM_EVALUATION GROUP BY EVALUATED_BY;
  • Period trend: group by SUPPLIER_ID and PERIOD_NAME to chart score changes over time.

When building reports, filter on ORG_ID for multi-org safety and use the DFF columns only through the appropriate flexfield view rather than selecting raw ATTRIBUTEn values.

Related Objects

Because the table is classified as standalone with a single outbound FK, dependency analysis should center on the AMW evaluation tables and the resolving master-data tables listed above.