Search Results amw_project_lists_v




Overview
Explore in AI Chat

Overview

AMW_PROJECT_LISTS_V is a consolidated reporting view belonging to the AMW — Internal Controls Manager module, historically shipped with Oracle E-Business Suite releases in the 12.1.1 and 12.2.2 code lines. The view presents a unified list of audit engagements managed by the Internal Controls Manager (ICM) application, merging audit projects that exist purely within ICM with those that have been linked to standard Oracle Projects (PA) project records. Its principal role is to drive the engagement selection lists and audit project list pages within the ICM user interface, and to support ad hoc reporting against the audit universe. Because ICM is flagged as obsolete in the ETRM metadata, the view is retained largely for backward compatibility; Oracle notes that it is not implemented in every database, meaning it will only appear where the legacy ICM schema objects exist. The view is also notable for exposing AUDIT_MANAGER_PERSON_ID and the corresponding manager name resolution, which is the attribute most commonly searched for under the term audit_manager_name.

Underlying Base Objects

The ETRM metadata does not enumerate referenced base objects, but the embedded view text defines them precisely. The first branch of the UNION reads from AMW_AUDIT_PROJECTS (the audit project header), AMW_AUDIT_PROJECTS_TL (the translated name and description columns), AMW_WORK_CATEGORIES_B, and AMW_WORK_TYPES_B, joining category code 'ENGAGEMENT' to the audit project's engagement type. The second branch reads from PA_PROJECTS_ALL, AMW_AUDIT_PROJECTS, PA_PROJECT_TYPES_ALL, AMW_WORK_CATEGORIES_B, and AMW_WORK_TYPES_B to surface projects already established in Oracle Projects. The two branches are combined with UNION and distinguished by a literal source flag of 'ICM' or 'PA'. Manager identity in the ICM branch is resolved through a scalar subquery on PER_ALL_PEOPLE_F; in the PA branch it is resolved through the PA_PROJECT_PARTIES_UTILS package functions.

Key Columns

Common Use Cases and Queries

Typical use is listing engagements with their managers and statuses, or filtering to only native ICM engagements. For example:

  • SELECT project_number, name, audit_project_status FROM amw_project_lists_v WHERE audit_manager_person_id = :person_id;
  • SELECT project_number, audit_project_status FROM amw_project_lists_v WHERE project_id IS NULL ORDER BY creation_date DESC;

Because manager name resolution depends on current PER_ALL_PEOPLE_F effective dates, historical manager assignments may not be reproduced; reporting that requires point-in-time manager attribution should query the audit project tables directly rather than relying on this view.