Search Results amw_evaluations_details

Overview

AMW_EVALUATIONS_DETAILS is a table in the AMW schema, belonging to the Oracle E-Business Suite Internal Controls Manager (ICM) module. It holds information about evaluation details. In the context of Oracle EBS 12.1.1 and 12.2.2, this table stores the granular components and conclusions associated with an evaluation record, complementing the header-level data maintained in AMW_EVALUATIONS_B. The table is classified as VALID in the data dictionary.

From a heuristic Data Vault modeling perspective, AMW_EVALUATIONS_DETAILS is best characterized as a satellite. It carries descriptive and contextual attributes—namely the evaluation component and the evaluation conclusion—that qualify a parent evaluation entity, along with the standard EBS auditing columns (creation and update metadata). As a satellite, it would attach to a hub or link anchored on EVALUATION_ID, since its foreign key maps to AMW_EVALUATIONS_B. This classification is a modeling suggestion derived from the FK structure and should not be treated as a formally documented Data Vault design.

Key Information Stored

The documented physical schema for ETRM 12.1.1 contains eight columns. The most significant are described below.

• EVALUATION_ID — The foreign key linking each detail row to its parent evaluation in AMW_EVALUATIONS_B. In the documented FK relationship, AMW_EVALUATIONS_DETAILS.EVALUATION_ID references AMW_EVALUATIONS_B. This is the principal business-key candidate and join column.
• EVALUATION_COMPONENT — Identifies the evaluation component being recorded, distinguishing one detail line from another within the same evaluation.
• EVALUATION_CONCLUSION — Holds the conclusion or outcome determined for that evaluation component.
• LAST_UPDATE_DATE — The date the row was last modified, a standard EBS audit column.
• LAST_UPDATED_BY — The user who last updated the row.
• CREATION_DATE — The date the row was created.
• CREATED_BY — The user who created the row.
• LAST_UPDATE_LOGIN — The login identifier associated with the last update, used for audit and session tracking.

The metadata does not document a surrogate primary key or unique index beyond the EVALUATION_ID reference. The FK to AMW_EVALUATIONS_B establishes EVALUATION_ID as the primary relationship key; a composite of EVALUATION_ID and EVALUATION_COMPONENT would be the natural uniqueness candidate for a detail table, though this is not confirmed in the documented metadata.

Common Use Cases and Queries

This table is primarily used by Internal Controls Manager evaluation and reporting functionality. Typical scenarios include retrieving all detail components for a given evaluation, reporting on evaluation conclusions by component, and auditing who created or modified detail rows.

• Listing details for a specific evaluation:

  SELECT EVALUATION_ID, EVALUATION_COMPONENT, EVALUATION_CONCLUSION
  FROM AMW.AMW_EVALUATIONS_DETAILS
  WHERE EVALUATION_ID = :evaluation_id;

• Joining to the parent evaluation header:

  SELECT d.EVALUATION_ID, d.EVALUATION_COMPONENT, d.EVALUATION_CONCLUSION, b.*
  FROM AMW.AMW_EVALUATIONS_DETAILS d
  JOIN AMW.AMW_EVALUATIONS_B b ON b.EVALUATION_ID = d.EVALUATION_ID;

• Audit reporting on recent changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

The documented relationship data identifies AMW_EVALUATIONS_B as the directly referenced parent table. The most significant related objects are:

• AMW_EVALUATIONS_B — The parent evaluation header table; joined on EVALUATION_ID.
• AMW_EVALUATIONS_TL — The translated attributes table for evaluations, associated through the evaluation entity.
• AMW_EVALUATION_ENTITIES — Records the entities subject to evaluation, linked through the evaluation.
• AMW_EVALUATION_RESULTS — Stores evaluation results, related at the evaluation level.
• AMW_EVALUATION_DOCUMENTS — Attaches supporting documentation to evaluations.
• AMW_EVALUATIONS_VL / views — Reporting views exposing evaluation header and detail data.

Because the metadata classifies this table as standalone in the Data Vault heuristic (aside from the parent FK), the related objects above are inferred from the AMW evaluation data model rather than exhaustively documented FK constraints.