Search Results evaluation_context

Overview

AMW_EVALUATIONS_VL is a bilingual (MLS-compliant) view owned by the APPS schema within Oracle E-Business Suite. It belongs to the AMW product, Internal Controls Manager, a module used to document, test, and certify internal controls in support of regulatory compliance initiatives such as Sarbanes-Oxley. The view presents evaluation records — the individual assessment results generated when controls, processes, or other auditable objects are evaluated — together with their translated comments and status information.

The "_VL" suffix indicates a "view with language" that joins a base table to its translation table, returning descriptive attributes in the session's current language. This makes the view suitable for concurrent programs, OAF pages, and custom reports that must display evaluation data in the user's language without requiring explicit joins to the translation table. For technologists searching on evaluation_set_status_code, this view is the accessible entry point that exposes that attribute alongside the full evaluation record.

Underlying Base Objects

The view is defined over two base tables: AMW_EVALUATIONS_B, which stores the transactional and descriptive columns of each evaluation, and AMW_EVALUATIONS_TL, which stores language-specific translated content such as comments. The join is performed on EVALUATION_ID, with the translation row filtered by T.LANGUAGE = USERENV('LANG'), ensuring only the row matching the session language is returned.

Because the view is a simple inner join across these two tables, it is read-only in practical terms; DML against evaluations is normally performed directly on the base tables by the AMW application. All columns except COMMENTS are sourced from the _B table, while COMMENTS is sourced from the _TL table. The view includes ROW_ID (the base table ROWID), which permits row-level identification of the underlying evaluation.

Key Columns

• EVALUATION_ID — Primary identifier for the evaluation record; the join key between the base and translation tables.
• EVALUATION_TYPE / EVALUATION_OBJECT_NAME — Classify the evaluation and identify the object being assessed.
• EVALUATION_SET_ID — Associates the evaluation with the evaluation set (for example, a control test or certification cycle) to which it belongs.
• EVALUATION_SET_STATUS_CODE — Status of the evaluation within its set; this is the column users most often search for when tracking progress or filtering actionable evaluations.
• PK1_VALUE through PK5_VALUE — Generic key components that identify the evaluated entity when the object type varies.
• EVALUATION_CONTEXT — Provides context for interpreting the evaluation.
• DATE_EVALUATED, ENTERED_BY_ID, EXECUTED_BY_ID — Timeline and responsibility information for the assessment.
• SECURITY_GROUP_ID — Supports multi-org/security group filtering.
• OBJECT_VERSION_NUMBER — Optimistic locking indicator for the base record.
• COMMENTS — Language-specific narrative supplied from AMW_EVALUATIONS_TL.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — DFF (descriptive flexfield) columns for extensibility.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include building compliance dashboards, extracting evaluation results for external reporting, and joining evaluations to control or process definitions via EVALUATION_SET_ID. The view spares developers from writing the translation join manually and automatically returns comments in the correct language.

To list evaluations by status for a given set:

• SELECT evaluation_id, evaluation_object_name, evaluation_set_status_code, date_evaluated FROM apps.amw_evaluations_vl WHERE evaluation_set_id = :p_set_id ORDER BY date_evaluated DESC;

To count evaluations grouped by status:

• SELECT evaluation_set_status_code, COUNT(*) FROM apps.amw_evaluations_vl GROUP BY evaluation_set_status_code;

Because the view is defined with USERENV('LANG'), queries executed under different language sessions return translated comments but identical status codes and identifiers. Access is restricted to responsibilities granted the AMW module, and users should query through the APPS schema synonym to ensure the correct synonym resolution.