Results for “pa_adw_top_tasks_b_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_ADW_TOP_TASKS_B_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Projects (PA) module. It is classified as a retrofitted object, indicating that it was re-engineered or re-pointed as part of the upgrade path shared between EBS 12.1.1 and 12.2.2. The view exposes a consolidated, denormalized presentation of top-level project tasks, filtered by the relationship between tasks and their parent projects as recorded in the Oracle Projects ADW (Application Data Warehouse) family of objects.

The "_B_V" naming convention suggests a "base" view variant that typically feeds an associated "_TL" (translated) or summary view, and the ADW prefix ties it to the Projects data warehouse extraction layer. Its primary role is to provide downstream reporting, analytics, and integration consumers with a stable, join-friendly projection of top task attributes without requiring direct access to the underlying transactional tables. Note that several user-defined columns (USER_COL1 through USER_COL10) are hard-coded to NULL, providing reserved placeholders for descriptive flexfield or extension attributes.

Underlying Base Objects

According to the ETRM metadata, the view is defined over two referenced objects:

• PA_ADW_PROJECTS_B_V (VIEW) — the ADW base project view, used here to restrict the result set to tasks whose parent project qualifies within the ADW project population.
• PA_TASKS (SYNONYM) — a synonym (typically resolving to PA_TASKS in the base application) holding the task-level transactional records.

The view text performs an inner join between PA_TASKS (aliased PTT) and PA_ADW_PROJECTS_B_V (aliased PP) on PROJECT_ID, with an additional self-referencing predicate PTT.TOP_TASK_ID = PTT.TASK_ID. This second condition is what filters the result to genuine top tasks: a task qualifies as a top task only when its TOP_TASK_ID equals its own TASK_ID, meaning it sits at the root of the task hierarchy and has no parent task above it.

Key Columns

• TOP_TASK_ID — identifier of the top-level task; per the join logic this equals the task's own TASK_ID.
• PROJECT_ID — the owning project, used to join back to project-level and ADW project views.
• TASK_NUMBER — the user-facing number of the top task.
• TASK_NAME — the descriptive name of the top task.
• DESCRIPTION — free-text description of the task.
• CARRYING_OUT_ORGANIZATION_ID — the organization responsible for carrying out the task.
• SERVICE_TYPE_CODE — classification of the service or task type.
• USER_COL1–USER_COL10 — reserved columns, returned as NULL, available for extending the view's shape.
• ADW_NOTIFY_FLAG — flag controlling ADW notification/extraction behaviour for the task.

Common Use Cases and Queries

This view is typically consumed in Projects reporting, data warehouse extraction, and integrations that need a clean list of top-level tasks per project without traversing the task hierarchy manually.

A basic listing follows:

• SELECT project_id, top_task_id, task_number, task_name, service_type_code FROM apps.pa_adw_top_tasks_b_v WHERE project_id = :p_project_id;

To join top tasks with their ADW project context:

• SELECT t.task_number, t.task_name, p.* FROM apps.pa_adw_top_tasks_b_v t, apps.pa_adw_projects_b_v p WHERE t.project_id = p.project_id;

To identify tasks flagged for ADW notification:

• SELECT task_number, task_name FROM apps.pa_adw_top_tasks_b_v WHERE adw_notify_flag = 'Y';

Because the view is retrofitted and stable across 12.1.1 and 12.2.2, it is suited for extraction scripts and custom reports that must remain portable across both releases.