Search Results audit_project_id




Overview
Explore in AI Chat

Overview

APPS.AMW_AUDIT_TASKS_V is a read-only database view owned by the APPS schema within Oracle E-Business Suite, documented under FND Design Data metadata as AMW.AMW_AUDIT_TASKS_V. It forms part of the Audit Management Workbench (AMW) family of objects, which supports Oracle's internal audit and engagement tracking functionality. The view presents a denormalized, reporting-friendly projection of audit task records, joining task header data, task translations, audit project context, associated Oracle Projects task definitions, and the person records of assigned task managers.

The object is flagged Oracle Internal Use Only. Oracle Corporation does not support direct data access through this view except when invoked by standard Oracle Applications programs. The view type is classified as Internal, meaning it is not intended as a public, supported interface for external extraction, integration, or custom reporting. Consumers should treat the view as part of the application's internal API surface, referenced by PL/SQL packages such as AMW_AUDIT_ENGAGEMENT_PVT, AMW_SCOPE_PVT, AMW_EXPORT_AUDIT_PROCEDURE_V, and AMW_LOAD_AUDIT_PROCEDURE_DATA. Because of this status, its columns, joins, and semantics may change without notice across patches or releases, including 12.1.1 and 12.2.2.

Underlying Base Objects

According to the documented dependency information, AMW_AUDIT_TASKS_V is defined over the following objects: AMW_AUDIT_PROJECTS, AMW_AUDIT_TASKS_B (the base table holding task definitions), AMW_AUDIT_TASKS_TL (the translation table containing language-specific task attributes such as name and description), PA_PROJECTS_ALL (the Oracle Projects project repository), PA_TASKS (the Oracle Projects task repository), and PER_ALL_PEOPLE_F (the effective-dated person/employee table used to resolve task manager identity).

The join structure therefore marries AMW audit-specific task metadata with the broader Oracle Projects foundation, which supplies project and task identifiers, and with HR person records, which supply the task manager name. The base AMW_AUDIT_TASKS_B and AMW_AUDIT_TASKS_TL tables provide the audit-specific layer, while PA_PROJECTS_ALL and PA_TASKS anchor the records to standard Projects entities through PROJECT_ID and TASK_ID. The inclusion of PER_ALL_PEOPLE_F indicates that task manager names are resolved at query time from the effective-dated person records, which is a common EBS pattern.

Key Columns

The view exposes sixteen columns. The AUDIT_PROJECT_ID column is the user's search term and functions as the audit-side project identifier, distinct from the standard Oracle Projects PROJECT_ID. The PROJECT_ID and TASK_ID columns are the Projects-related foreign keys that link audit records to PA_PROJECTS_ALL and PA_TASKS respectively. TASK_NUMBER, TASK_NAME, and DESCRIPTION carry the human-readable task attributes, with DESCRIPTION at 250 characters. TOP_TASK_ID, LEVEL_ID, and PARENT_TASK_ID express the task hierarchy, enabling reconstruction of WBS-style task trees. TASK_MANAGER_PERSON_ID and TASK_MANAGER_NAME identify the assigned manager, the latter resolved to 240 characters via PER_ALL_PEOPLE_F. START_DATE and COMPLETION_DATE provide scheduling and status milestones, while SOURCE_CODE records the origin of the task record. ORG_ID supports multi-organization (operating unit) partitioning, which is essential for secure and correct filtering in any query.

Common Use Cases and Queries

Because the view consolidates audit tasks with project and person context, typical use is diagnostic or reporting-oriented: enumerating tasks under a given audit project, listing tasks with assigned managers, or exporting audit engagement data via the AMW export procedures. A representative query using the searched column is:

  • SELECT AUDIT_PROJECT_ID, PROJECT_ID, TASK_ID, TASK_NUMBER, TASK_NAME, TASK_MANAGER_NAME, START_DATE, COMPLETION_DATE FROM APPS.AMW_AUDIT_TASKS_V WHERE AUDIT_PROJECT_ID = :p_audit_project_id AND ORG_ID = :p_org_id;
  • Hierarchical retrieval: SELECT LEVEL_ID, TASK_ID, PARENT_TASK_ID, TOP_TASK_ID, TASK_NAME FROM APPS.AMW_AUDIT_TASKS_V WHERE AUDIT_PROJECT_ID = :p_audit_project_id ORDER BY LEVEL_ID, TASK_NUMBER;
  • Manager workload: SELECT TASK_MANAGER_PERSON_ID, TASK_MANAGER_NAME, COUNT(*) FROM APPS.AMW_AUDIT_TASKS_V GROUP BY TASK_MANAGER_PERSON_ID, TASK_MANAGER_NAME;

Given the Internal Use Only designation, these queries should be confined to diagnostic contexts, and any production integration should instead rely on supported Oracle Projects or HR interfaces. Always constrain by ORG_ID and, where applicable, by effective dates to avoid duplicate or cross-organization results.