Search Results evaluated_by

Overview

PO.POA_CM_EVALUATION is a transactional table in the Oracle E-Business Suite Procurement (PO) schema that stores supplier performance evaluation records generated by the Contract Manufacturing (CM) supplier scorecard framework. It captures evaluation results produced by Oracle Procurement Buyer's or Supplier Evaluation functionality for contract manufacturers, where results are segmented by operating unit, supplier, and period. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, and is documented in FND Design Data as PO.POA_CM_EVALUATION. Oracle classifies the object as VALID but explicitly flags it as Oracle Internal Use Only; supported access must occur through standard Oracle Applications programs rather than direct DML.

Relationship metadata indicates the table is standalone from a Data Vault perspective — it does not act as a hub, link, or satellite for downstream dependent objects. This classification is a heuristic modeling suggestion only: the table behaves as a leaf-level transactional store whose records feed upward into evaluation definition and reporting structures rather than participating in a broader integration hub.

Key Information Stored

The table contains 37 documented columns. The most operationally significant are:

• EVALUATION_ID — the surrogate primary key, enforced by unique index POA_CM_EVALUATION_U1. It is also the only foreign key documented on the table, referencing PO.POA_CM_EVALUATION.EVALUATION_ID to AMW_EVALUATIONS_B.
• OPER_UNIT_ID — the operating unit to which the evaluation result belongs. This is the column most frequently used in searches and joins, because it aligns evaluation data with the Oracle EBS multi-org security model and with PO_HEADERS_ALL-style operating unit filtering.
• ORG_ID — the organization identifier, the standard operating unit key used in multi-org enabled views and queries.
• SUPPLIER_ID and SUPPLIER_SITE_ID — identify the evaluated supplier and the specific supplier site.
• CATEGORY_ID and ITEM_ID — scope the evaluation to a purchasing category and, where applicable, a specific item.
• CUSTOM_MEASURE_CODE, PERIOD_TYPE, and PERIOD_NAME — define the measure being scored and the evaluation period, enabling period-over-period comparison.
• EVALUATED_BY — the user who performed the evaluation.
• COMMENTS — free-text remarks up to 240 characters.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) support audit and batch tracing.

Fifteen ATTRIBUTE columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15) provide a flexfield-style extension area.

Common Use Cases and Queries

The table is principally queried for supplier scorecard reporting and operating-unit scoped analytics. A typical filter retrieves all evaluations for a given operating unit and period:

• SELECT evaluation_id, supplier_id, oper_unit_id, period_name FROM po.poa_cm_evaluation WHERE oper_unit_id = :p_oper_unit_id AND period_name = :p_period;
• Joining to AMW_EVALUATIONS_B on EVALUATION_ID to obtain evaluation headers: SELECT e.evaluation_id, e.supplier_id, b.evaluation_name FROM po.poa_cm_evaluation e, amw_evaluations_b b WHERE e.evaluation_id = b.evaluation_id AND e.org_id = :p_org_id;
• Aggregating scores by supplier and category for procurement review dashboards, filtered through ORG_ID and PERIOD_NAME.
• Auditing concurrent evaluation runs using REQUEST_ID and PROGRAM_UPDATE_DATE.

Because the table is Oracle Internal Use Only, custom queries should be confined to read-only reporting views and should never issue direct DML. Multi-org views exposing this table automatically apply ORG_ID and often OPER_UNIT_ID predicates to enforce operating unit security.

Related Objects

• AMW_EVALUATIONS_B — related through POA_CM_EVALUATION.EVALUATION_ID → AMW_EVALUATIONS_B, supplying evaluation header definitions.
• POA_CM_EVALUATION_U1 — the unique index on EVALUATION_ID, the primary access path.
• PO_HEADERS_ALL / PO_LINES_ALL — supplier and item context used in reporting joins beyond the documented FK.
• POZ_SUPPLIERS_V / POZ_SUPPLIER_SITES_V — supplier and site name resolution given SUPPLIER_ID and SUPPLIER_SITE_ID.
• FND_USER and FND_CONCURRENT_REQUESTS — resolve EVALUATED_B, CREATED_BY, and REQUEST_ID.
• HR_OPERATING_UNITS and ORG_ORGANIZATION_DEFINITIONS — operating unit names for OPER_UNIT_ID and ORG_ID.