Results for “pa_struct_tasks_amg_v”

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

Overview

PA_STRUCT_TASKS_AMG_V is a PL/SQL-based view owned by the APPS schema in Oracle E-Business Suite, belonging to the Projects (PA) product family. It is available in both 12.1.1 and 12.2.2 releases and holds a VALID status in the ETRM repository. As documented, the view provides a list of structure versions, exposing the union of project element version records and their corresponding task definitions in a single flattened result set.

The view is intended for reporting and integration scenarios where consumers need visibility into the WBS hierarchy together with task-level attributes such as billing flags, rate schedules, and descriptive flexfield values. Because the view joins project elements, their versions, and tasks, it removes the burden of reconstructing those joins in custom reports, Discoverer workbooks, BI Publisher data templates, or interface programs. It is not a transactional entity; it is a read-only presentation layer over the underlying Projects structures.

Underlying Base Objects

The documented base objects referenced by this view span project element, task, and structure metadata:

• PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEM_VER_SCHEDULE — the project element and version scheduling tables that supply the WBS elements and their versions.
• PA_TASKS, PA_TASK_UTILS, PA_TASK_TYPES — task definitions and utilities used to derive task attributes.
• PA_PROJ_STRUCTURE_TYPES, PA_STRUCTURE_TYPES, PA_PROJ_TASK_STRUC_PUB, PA_PROJ_STRUC_MAPPING_UTILS, PA_PROJ_ELEMENTS_UTILS — structure type and mapping metadata plus the PL/SQL packages invoked during view execution.
• PA_PROGRESS_ROLLUP — progress rollup data for structure elements.
• PER_ALL_PEOPLE_F — the person table used to resolve manager or task manager person identifiers.
• PA_WORK_TYPES_VL and PJI_XBS_PLANS_PRJ_V — supporting views for work types and cross-business plan data.

Because the view text uses NVL over PE (PA_PROJ_ELEMENTS) and TASK (PA_TASKS) columns, it effectively unifies element-level and task-level attributes, falling back to the task table when the element column is null.

Key Columns

• PROJ_ELEMENT_ID, PROJECT_ID, ELEMENT_NUMBER — identity of the project element and its owning project.
• ROWID — carried from the element version record, enabling direct row-level reference during updates or drill-downs.
• NAME / LONG_TASK_NAME — resolved via NVL(PE.NAME, TASK.TASK_NAME), giving the display name of either the element or task.
• TOP_TASK_ID, PARENT_STRUCTURE_ID / PARENT_TASK_ID, WBS_LEVEL — hierarchy navigation columns for reconstructing the WBS tree.
• READY_TO_BILL_FLAG, READY_TO_DISTRIBUTE_FLAG, CHARGEABLE_FLAG, BILLABLE_FLAG, LIMIT_TO_TXN_CONTROLS_FLAG — billing and transaction control indicators.
• START_DATE, COMPLETION_DATE — task schedule dates.
• LABOR_BILL_RATE_ORG_ID, LABOR_STD_BILL_RATE_SCHDL, NON_LABOR_BILL_RATE_ORG_ID, NON_LABOR_STD_BILL_RATE_SCHDL — rate schedule attributes for labor and non-labor billing.
• LABOR_SCHEDULE_FIXED_DATE, LABOR_SCHEDULE_DISCOUNT and the non-labor equivalents — rate schedule control values.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE10 — descriptive flexfield columns resolved from the element version.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include building WBS/task hierarchy reports, validating billing readiness, and extracting rate schedule assignments. A simple listing of tasks for a project can be produced as follows:

• SELECT proj_element_id, element_number, name, wbs_level, chargeable_flag, billable_flag FROM pa_struct_tasks_amg_v WHERE project_id = :project_id ORDER BY wbs_level, element_number;
• SELECT element_number, name, labor_std_bill_rate_schdl, non_labor_std_bill_rate_schdl FROM pa_struct_tasks_amg_v WHERE ready_to_bill_flag = 'Y' AND project_id = :project_id;
• SELECT proj_element_id, parent_structure_id, top_task_id, wbs_level FROM pa_struct_tasks_amg_v WHERE project_id = :project_id CONNECT BY PRIOR proj_element_id = parent_structure_id START WITH parent_structure_id IS NULL;

Because the view invokes PL/SQL packages (PA_TASK_UTILS, PA_PROJ_ELEM_UTILS, PA_PROJ_TASK_STRUC_PUB), performance is sensitive to the WHERE predicates supplied; filtering by PROJECT_ID or PROJ_ELEMENT_ID is strongly recommended when the view is queried directly from custom SQL.