Search Results pa_structures




Overview
Explore in AI Chat

Overview

APPS.PA_STRUC_TASK_SEARCH_V is a consolidated Oracle EBS Projects (PA) reporting view that exposes both project structures (PA_STRUCTURES) and project tasks (PA_TASKS) as a single searchable row set. It is defined over the project element and project element version model, blending element definitions, versioned scheduling data, percent-complete information, status, manager, and relationship data into a wide, denormalized result. The view's most distinctive feature is its use of DECODE logic keyed on PPE.OBJECT_TYPE: for PA_TASKS it returns the element number and name, while for PA_STRUCTURES it substitutes the structure version number and version name. A second DECODE returns 'Y' for structures and calls PA_PROJ_ELEMENTS_UTILS.is_summary_task_or_structure for tasks to indicate whether a row is a summary node. Because it joins current and versioned project element data with schedule, status, and relationship tables, the view serves as a practical foundation for structure/task lookups, hierarchical reporting, progress tracking, and integration extracts in EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is documented over the following objects, all accessed in the APPS schema:

Key Columns

Columns are largely exposed with the same names as their underlying sources. Important examples include:

Common Use Cases and Queries

The view is typically used to list structures and tasks under a project, to search by number/name, or to pull schedule and progress status together. A basic query restricted to structures is:

SELECT element_number, name, wbs_level, project_status_name FROM apps.pa_struc_task_search_v WHERE project_id = :p_project_id AND object_type = 'PA_STRUCTURES' ORDER BY display_sequence;

A task-focused search using the summary flag and progress is:

SELECT element_number, name, scheduled_start_date, scheduled_finish_date, completed_percentage FROM apps.pa_struc_task_search_v WHERE object_type = 'PA_TASKS' AND project_id = :p_project_id AND name LIKE :p_contains AND carry_out_summary_flag = 'N';

Additional scenarios include feeding an integration or extract with published structures (filter on LATEST_EFF_PUBLISHED_FLAG), reporting task dependencies via RELATIONSHIP_TYPE and OBJECT_TYPE_FROM, and comparing baseline versus scheduled dates through the pre-computed variance columns. Because the view performs multiple joins and DECODE branches, queries should always filter on PROJECT_ID or ELEMENT_VERSION_ID and avoid unrestricted full scans.