Search Results task_manager_person_id

Overview

AMW_AUDIT_TASKS_VL is a multilingual (VL) view owned by the APPS schema within the AMW – Internal Controls Manager product of Oracle E-Business Suite. It exposes audit task records used to plan, track, and report on the individual work items that make up an audit project or engagement. Because Internal Controls Manager (ICM) straddles the audit and compliance domains, task records carry scheduling attributes (start and completion dates), hierarchical relationships (top and parent tasks, level identifier), and ownership attributes such as the task manager.

The view's principal purpose is to join the transactional base table to its translation table so that the task name and description are returned in the session's active language. It is the natural reporting and integration surface for any query that needs the human-readable name of an audit task alongside its operational data. The column TASK_MANAGER_PERSON_ID identifies the person accountable for the task and is frequently used as a search predicate when building dashboards, workload reports, or workflow routing logic. The view is listed as VALID in the ETRM repository and exposes a ROW_ID pseudocolumn derived from the base table's physical rowid.

Underlying Base Objects

Documented base objects for this view are not enumerated in the ETRM metadata, but the view text reveals its two constituent tables:

• AMW_AUDIT_TASKS_B — the base (non-translated) table holding all operational columns: identifiers, hierarchy, dates, manager assignment, who-columns, descriptive flexfield attributes (ATTRIBUTE_CATEGORY through ATTRIBUTE10), security group, and the OBJECT_VERSION_NUMBER used for optimistic locking.
• AMW_AUDIT_TASKS_TL — the translation table supplying TASK_NAME and DESCRIPTION for the language returned by USERENV('LANG').

The two are joined on TASK_ID, with the language predicate restricting the result set to a single translated row per task. Each base table supplies columns prefixed B or TL respectively in the view definition.

Key Columns

• ROW_ID — rowid of the underlying base record; useful for direct row addressing.
• TASK_ID — primary key of the audit task and the join key to both base tables.
• AUDIT_PROJECT_ID — the audit project or engagement to which the task belongs.
• TASK_NUMBER — user-facing task identifier within the project.
• TOP_TASK_ID / PARENT_TASK_ID / LEVEL_ID — define the task hierarchy, supporting multi-level work breakdown structures and roll-up reporting.
• START_DATE / COMPLETION_DATE — planned or actual scheduling boundaries for the task.
• TASK_MANAGER_PERSON_ID — the person responsible for the task; the primary column sought when searching by manager.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit trail columns.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–10 — descriptive flexfield segments for customer-specific extensions.
• SECURITY_GROUP_ID — supports multi-organization / security group filtering.
• OBJECT_VERSION_NUMBER — concurrency control for updates through the base table.
• TASK_NAME, DESCRIPTION — translated descriptive text sourced from AMW_AUDIT_TASKS_TL.

Common Use Cases and Queries

Typical scenarios include task workload reports by manager, audit status dashboards, hierarchy roll-ups, and integration extracts feeding external GRC or reporting tools. Because the view resolves translation automatically, it is preferred over querying the base and translation tables separately.

• Tasks assigned to a specific manager: SELECT task_id, task_number, task_name, start_date, completion_date FROM amw_audit_tasks_vl WHERE task_manager_person_id = :person_id ORDER BY start_date;
• All tasks for an audit project: SELECT task_id, task_number, task_name, level_id FROM amw_audit_tasks_vl WHERE audit_project_id = :project_id ORDER BY task_number;
• Incomplete tasks past their start date: SELECT task_id, task_name, start_date FROM amw_audit_tasks_vl WHERE completion_date IS NULL AND start_date < SYSDATE;
• Resolving the manager name: join TASK_MANAGER_PERSON_ID to PER_ALL_PEOPLE_F (PERSON_ID) with an effective date predicate to return the manager's display name.
• Hierarchy roll-up: use TOP_TASK_ID and PARENT_TASK_ID in a self-join or CONNECT BY query to present parent and child tasks in a tree.

Because the view filters on USERENV('LANG'), callers should ensure the session language is initialized; otherwise translated columns may return no rows for tasks whose translation row is absent in that language.