Results for “outline_number”

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

Overview

PA_DELIVERABLES_TASKS_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. According to the documented ETRM metadata, the view "selects all tasks and the deliverables associated to it," presenting task-level project structure records together with their associated deliverable context. It is a reporting and integration convenience layer: rather than joining the underlying project element and project element version tables directly, consumers — including concurrent programs, Oracle Reports, OBIEE/BI Publisher extracts, and custom extensions — can query a single object that already filters for task-type structure elements and exposes the outline (WBS) hierarchy information required to render project schedules.

The view is defined as a simple inner join with an equality predicate on PROJECT_ID and PROJ_ELEMENT_ID, plus a restrictive predicate fixing OBJECT_TYPE to 'PA_TASKS'. It is therefore a narrow, read-only projection of task records, not a full deliverables entity. In ETRM the view carries a VALID status, indicating that it compiles cleanly against the shipped 12.2.2 schema and is safe to reference in custom code.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• PA_PROJ_ELEMENTS (alias PPE) — the project element master table holding tasks, deliverables, and other structure elements. It supplies PROJ_ELEMENT_ID, NAME, ELEMENT_NUMBER, PROJECT_ID, RECORD_VERSION_NUMBER, and the OBJECT_TYPE discriminator.
• PA_PROJ_ELEMENT_VERSIONS (alias PEV) — the versioned structure table supplying the WBS/outline hierarchy, including WBS_NUMBER and PARENT_STRUCTURE_VERSION_ID.

The join conditions are PPE.PROJ_ELEMENT_ID = PEV.PROJ_ELEMENT_ID and PPE.PROJECT_ID = PEV.PROJECT_ID. The filter PPE.OBJECT_TYPE = 'PA_TASKS' limits the result set to tasks, so deliverable rows (which also reside in PA_PROJ_ELEMENTS under a different OBJECT_TYPE) are represented only insofar as they relate to the task structure. Because the join is inner and unqualified by structure version, multiple rows may be returned for a task that has several element versions, and consumers should constrain on version or parent structure where a single current row is required.

Key Columns

• TASK_ID — the PROJ_ELEMENT_ID of the task; the primary join key to other project structure views and to task-level facts.
• TASK_NAME — the descriptive task name from PA_PROJ_ELEMENTS.NAME.
• TASK_NUMBER — the user-visible element number of the task.
• OUTLINE_NUMBER — the WBS/outline number sourced from PA_PROJ_ELEMENT_VERSIONS.WBS_NUMBER. This is the column most frequently searched for in relation to this view, and it corresponds to the concatenated outline path (for example, 1.2.3) that positions the task within the project work breakdown structure. It is the field used for sorting and displaying task hierarchy in reports.
• PROJECT_ID — the owning project, required for every project-scoped query and for joins to PA_PROJECTS.
• PARENT_STRUCTURE_VERSION_ID — identifies the structure version to which the task's outline position belongs, enabling version-aware hierarchy queries.
• RECORD_VERSION_NUMBER — optimistic locking / change-tracking value from the element record.

Common Use Cases and Queries

Typical uses include validating task outline numbering for a project, feeding task-level LOVs, and joining tasks to deliverables or expenditure items. A standard current-project task listing follows:

• SELECT task_id, task_number, task_name, outline_number, project_id FROM apps.pa_deliverables_tasks_v WHERE project_id = :p_project_id ORDER BY outline_number;
• Hierarchy validation: SELECT task_number, outline_number FROM apps.pa_deliverables_tasks_v WHERE project_id = :p_project_id AND outline_number LIKE :p_prefix || '%' ORDER BY outline_number;
• Join to project master for reporting: SELECT v.outline_number, v.task_name, p.project_number, p.name FROM apps.pa_deliverables_tasks_v v, apps.pa_projects_all p WHERE v.project_id = p.project_id;

Because the view exposes no deliverable-specific columns beyond the task structure, teams needing deliverable detail should join TASK_ID to the deliverable tables in the PA schema. Queries should always be project-filtered to avoid full scans across all tasks in the instance.