Search Results evaluation_object_name




Overview

AMW.AMW_EVALUATIONS_B is the evaluations base table within the Oracle E-Business Suite Audit Management (AMW) module. It stores procedure-control and assessment evaluations, providing the transactional foundation for audit scoring and evaluation activity across the ETRM application family. Records in this table represent individual evaluation instances tied to a parent evaluation set, with each row capturing the evaluation type, context, the object being evaluated, and the outcome metadata such as the evaluation date and the personnel involved.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its indexes are held in APPS_TS_TX_IDX. The ETRM documentation classifies this object with a heuristic Data Vault classification of standalone. In modeling terms, this suggests that AMW_EVALUATIONS_B functions primarily as an entity hub keyed on EVALUATION_ID, with the surrounding evaluation detail tables acting as satellites and the score/score-staging tables acting as links or dependent satellites. The classification is heuristic and should be treated as a modelling suggestion rather than a formal Data Vault design.

Key Information Stored

The table is documented with 37 columns. The most significant are summarized below.

Common Use Cases and Queries

Typical usage centers on retrieving evaluations for a given set, resolving evaluated objects through the generic PK columns, and reporting on evaluation activity by user or date range.

  • Retrieve all evaluations for a set: SELECT evaluation_id, evaluation_type, evaluation_context, date_evaluated FROM amw.amw_evaluations_b WHERE evaluation_set_id = :set_id;
  • Filter by status using the searched column: SELECT evaluation_id, evaluation_set_status_code FROM amw.amw_evaluations_b WHERE evaluation_set_status_code = :status;
  • Resolve the evaluated object: SELECT pk1_value, pk2_value FROM amw.amw_evaluations_b WHERE evaluation_object_name = 'PROCEDURE' AND evaluation_id = :id;
  • Audit activity by user: join ENTERED_BY_ID / EXECUTED_BY_ID to per-personnel tables or FND_USER to report evaluations performed within a date range.
  • Security-scoped reporting: constrain results by SECURITY_GROUP_ID when building reports for restricted operating units.
  • Detail drill-down: join AMW_EVALUATIONS_DETAILS on EVALUATION_ID to expand line-level responses.

Reporting workloads should account for the generic PK1–PK5 pattern, which requires application-level knowledge of what each key slot represents for the given EVALUATION_OBJECT_NAME.

Related Objects

The following objects are the most significant dependents and references based on the documented FK relationships.

  • AMW_EVALUATIONS_DETAILS — joins on EVALUATION_ID and holds evaluation detail rows.
  • POA_CM_EVALUATION and POA_CM_EVAL_SCORES — join on EVALUATION_ID for evaluation and score capture in the POA cost-management flow.
  • OTA_EVALUATIONS — joins on EVALUATION_ID, linking training-related evaluations.
  • POA_EDW_CSTM_MSR_F and POA_EDW_CSTM_MSR_FSTG — join on EVALUATION_ID; these are staging and fact tables for the EDW custom measure extract.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for security partitioning.