Search Results pa_structures




Overview
Explore in AI Chat

Overview

PA_STRUC_TASK_SEARCH_V is an Oracle Projects (PA) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a consolidated, search-oriented projection of the Project Work Breakdown Structure (WBS) hierarchy, merging structure versions and task elements into a single denormalized result set. The view's central design principle is the DECODE on PPE.OBJECT_TYPE: when the underlying project element is a task ('PA_TASKS'), the view surfaces the task element number and name; when it is a structure ('PA_STRUCTURES'), it substitutes the structure version number and version name. This makes the view suitable for generic WBS browsers, task search pages, and integration extracts that must present both structural nodes and tasks without branching program logic.

The view also carries scheduling, progress, status, and relationship information, positioning it as a broad read-model for project element enquiries rather than a narrow lookup.

Underlying Base Objects

The view is defined over the following documented base objects:

The join graph anchors on element version identifiers, ensuring one consistent row per element-version projection.

Key Columns

Common Use Cases and Queries

Typical uses include WBS/task search screens, progress dashboards, milestone tracking extracts, and integration feeds requiring both structures and tasks in one stream.

  • Locate tasks by name or number within a project.
  • List critical or milestone elements with dates.
  • Report schedule variance against baseline.
  • Resolve manager and organization names for an element.

Sample query:

SELECT project_id, wbs_number, wbs_level, element_version_id,
       name, object_type, scheduled_start_date, scheduled_finish_date,
       milestone_flag, completed_percentage, full_name
FROM   apps.pa_struc_task_search_v
WHERE  project_id = :p_project_id
AND    object_type = 'PA_TASKS'
ORDER BY wbs_number;

Because the view is a join of versioned and scheduled data across multiple Projects tables, queries should filter by PROJECT_ID or ELEMENT_VERSION_ID to avoid full scans on large implementations.