Search Results task_manager_name

Overview

AMW_AUDIT_TASKS_V is a reporting view owned by the APPS schema within the AMW – Internal Controls Manager product of Oracle E-Business Suite. It presents a consolidated, read-only listing of audit tasks associated with audit projects, drawing together task definitions maintained inside the Internal Controls Manager data model and task records originating from Oracle Projects. The view exists to give reporting, inquiry, and integration consumers a single source for audit task information without requiring them to reconcile two structurally distinct task repositories.

The view is defined as a UNION of two SELECT statements. The first branch reads Project Accounting tasks (PA_TASKS) linked to an AMW audit project, while the second branch reads Internal Controls Manager tasks from AMW_AUDIT_TASKS_B and AMW_AUDIT_TASKS_TL. A SOURCE_CODE column distinguishes the origin of each row as either 'PA' or 'ICM', allowing downstream consumers to filter or segregate processing by task provenance. Because the object is a view rather than a table, it holds no data of its own and reflects the current state of the underlying tables at query time.

Underlying Base Objects

The documented view text references the following base objects:

• AMW_AUDIT_PROJECTS — the audit project header table, aliased AP in both UNION branches and used to link tasks to their audit project identifier.
• PA_TASKS — the Oracle Projects task table, supplying Project Accounting task records in the first branch.
• AMW_AUDIT_TASKS_B — the ICM task base table holding task attributes such as task number, dates, level, and parent.
• AMW_AUDIT_TASKS_TL — the ICM task translation table supplying language-dependent TASK_NAME and DESCRIPTION.
• PA_PROJECTS_ALL — used in a scalar subquery to derive the operating unit ORG_ID for the PA branch.
• PER_ALL_PEOPLE_F — used in a scalar subquery to resolve TASK_MANAGER_PERSON_ID into a manager name effective on the current date.

The UNION aligns both branches on a common column list, with literal values 'PA' and 'ICM' populating SOURCE_CODE. Notably, the second branch restricts rows to those where AP.PROJECT_ID IS NULL, ensuring that ICM-defined tasks are not duplicated against Project Accounting tasks. The ORG_ID column is populated only for the PA branch; for the ICM branch it is derived from the client information environment setting via USERENV('CLIENT_INFO').

Key Columns

• AUDIT_PROJECT_ID — identifier of the parent audit project.
• PROJECT_ID — the corresponding Oracle Projects project identifier, where one exists.
• TASK_ID, TASK_NUMBER, TASK_NAME, DESCRIPTION — the task identifier and its descriptive attributes, with name and description language-resolved for ICM rows.
• TOP_TASK_ID, PARENT_TASK_ID, LEVEL_ID — hierarchy columns describing the task's position in the work breakdown structure.
• TASK_MANAGER_PERSON_ID, TASK_MANAGER_NAME — the assigned task manager, with the name resolved from PER_ALL_PEOPLE_F for the person effective today.
• START_DATE, COMPLETION_DATE — planned or actual task dates.
• SOURCE_CODE — literal 'PA' or 'ICM', indicating which repository the row originates from.
• ORG_ID — operating unit identifier, populated from PA_PROJECTS_ALL for PA rows and from client information for ICM rows.

Common Use Cases and Queries

Typical uses include audit task listings for a given audit project, task manager workload reports, and integration extracts requiring a unified task feed across ICM and Oracle Projects. Because SOURCE_CODE separates the two origins, analysts commonly filter on it to isolate one repository.

List all tasks for an audit project:

SELECT TASK_ID, TASK_NUMBER, TASK_NAME, TASK_MANAGER_NAME, START_DATE, COMPLETION_DATE, SOURCE_CODE FROM APPS.AMW_AUDIT_TASKS_V WHERE AUDIT_PROJECT_ID = :p_audit_project_id ORDER BY WBS_LEVEL, TASK_NUMBER;

Report ICM-sourced tasks only:

SELECT AUDIT_PROJECT_ID, TASK_NUMBER, TASK_NAME, TASK_MANAGER_NAME FROM APPS.AMW_AUDIT_TASKS_V WHERE SOURCE_CODE = 'ICM';

Summarize task counts by source and operating unit:

SELECT SOURCE_CODE, ORG_ID, COUNT(*) TASK_COUNT FROM APPS.AMW_AUDIT_TASKS_V GROUP BY SOURCE_CODE, ORG_ID;

Queries should account for the UNION ALL-free UNION deduplication and for the fact that ORG_ID may be null on ICM rows when client information is not set. Access is governed by standard APPS schema privileges and any product-specific security applied to the underlying AMW tables.