Search Results pa_structure_type_class




Overview
Explore in AI Chat

Overview

APPS.PA_FIN_WP_TASKS_V is a reporting view in Oracle EBS Projects (PA) that exposes the tasks belonging to a project's financial workplan structure. It is defined as a UNION of two nearly identical SELECT statements that resolve the set of parent project elements acting as workplan task containers, then joins each to its child elements to return the tasks themselves. The view is primarily consumed by Project Management and financial reporting components that must distinguish workplan task-level detail from higher project structures.

The name and column projection confirm its purpose: it filters project elements to those whose owning structure is a single-instance structure (first branch) or a WORKPLAN-class structure (second branch), and that has reached the STRUCTURE_PUBLISHED status in pa_proj_elem_ver_structure. In this way only published, valid workplan task hierarchies are surfaced, which is essential for downstream cost, budget, and progress reporting where unpublished or draft structures must be excluded.

Underlying Base Objects

The view is defined over five documented objects: PA_PROJ_ELEMENTS, PA_PROJ_ELEM_VER_STRUCTURE, PA_PROJ_STRUCTURE_TYPES, PA_STRUCTURE_TYPES, and PA_LOOKUPS. PA_PROJ_ELEMENTS is referenced twice (aliased ppe for the child/task rows and ppe2 for the parent structure elements), joined on parent_structure_id = ppe2.proj_element_id and matching project_id. PA_PROJ_STRUCTURE_TYPES links each structure element to its structure_type_id, which in turn joins to PA_STRUCTURE_TYPES for classification. PA_LOOKUPS supplies the structure-type class description via lookup_type = 'PA_STRUCTURE_TYPE_CLASS'. PA_PROJ_ELEM_VER_STRUCTURE provides the version/status control, where the EXISTS clause restricts output to structures with status_code = 'STRUCTURE_PUBLISHED'.

The first UNION branch restricts ppe2.proj_element_id to elements appearing exactly once in pa_proj_structure_types; the second branch restricts to elements appearing exactly twice and additionally requires structure_type_class_code = 'WORKPLAN'. This dual-branch design accommodates differing structural cardinality conventions across project templates.

Key Columns

The view returns seven columns. NAME and ELEMENT_NUMBER carry the task's descriptive label and sequence identifier from pa_proj_elements. PROJ_ELEMENT_ID is the primary identifier of the task row and is the column most frequently searched by users, since many PA APIs and interface tables key on proj_element_id. PROJECT_ID identifies the owning project. STRUCTURE_TYPE_ID and STRUCTURE_TYPE_CLASS_CODE tie the row to its structure definition and classification (for example WORKPLAN). MEANING provides the decoded lookup description for the structure-type class, offering a human-readable label for reporting.

Common Use Cases and Queries

Typical uses include validating that a task has been published before loading transactions, resolving proj_element_id values to task names for reports, and locating all workplan tasks under a project. A representative query follows:

  • SELECT proj_element_id, name, element_number, project_id, structure_type_class_code, meaning FROM apps.pa_fin_wp_tasks_v WHERE project_id = :p_project_id;
  • SELECT * FROM apps.pa_fin_wp_tasks_v WHERE proj_element_id = :p_element_id; — to resolve a task by its element identifier.
  • SELECT proj_element_id, name FROM apps.pa_fin_wp_tasks_v WHERE structure_type_class_code = 'WORKPLAN' AND meaning = :p_meaning; — to filter by the decoded class label.

Because the view enforces the STRUCTURE_PUBLISHED condition, it should be preferred over direct queries against pa_proj_elements when only current, published workplan tasks are relevant. Note that the UNION can theoretically return a row from each branch; consumers should apply DISTINCT where uniqueness is critical.