Results for “proj_element_id”

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

Overview

PA_FIN_WP_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. As documented in the ETRM metadata, the view "selects the tasks in the workplan structure, financial structure, or a shared structure." It therefore provides a unified, read-only representation of project task elements that belong to either the financial structure, the workplan (execution) structure, or a structure serving both purposes simultaneously. This makes it a valuable reporting and integration object, since consumers do not need to know in advance which structural class a given task belongs to. The view normalizes these cases and exposes a consistent column set, allowing reporting tools, concurrent programs, and custom interfaces to retrieve task-level records across structure types with a single query against the APPS schema.

Underlying Base Objects

The view is defined over five referenced objects, all resolved through APPS: PA_PROJ_ELEMENTS (SYNONYM), PA_PROJ_STRUCTURE_TYPES (SYNONYM), PA_PROJ_ELEM_VER_STRUCTURE (SYNONYM), PA_STRUCTURE_TYPES (SYNONYM), and PA_LOOKUPS (VIEW). PA_PROJ_ELEMENTS supplies the task rows, joined twice (aliased PPE and PPE2) so that each child task is linked to its parent structure element. PA_PROJ_STRUCTURE_TYPES relates structure elements to their structure types, while PA_STRUCTURE_TYPES identifies the structural class code. PA_LOOKUPS (via LOOKUP_TYPE = 'PA_STRUCTURE_TYPE_CLASS') resolves the class into a user-facing meaning. PA_PROJ_ELEM_VER_STRUCTURE provides the published version context, and the view is restricted to records with STATUS_CODE = 'STRUCTURE_PUBLISHED'. The definition is a UNION of two nearly identical branches: the first handles structures whose PROJ_ELEMENT_ID appears exactly once in PA_PROJ_STRUCTURE_TYPES, and the second handles those appearing exactly twice, additionally filtered to STRUCTURE_TYPE_CLASS_CODE = 'WORKPLAN'. Together these branches capture financial, workplan, and shared structures.

Key Columns

The view exposes a focused projection of task attributes. Because the user's search term was "proj_element_id," note that PROJ_ELEMENT_ID is a central column, representing the unique identifier of the project element (task) in PA_PROJ_ELEMENTS and forming the join key throughout the definition. Other documented columns include NAME (the task name), ELEMENT_NUMBER (the task's element number), PROJECT_ID (the owning project), STRUCTURE_TYPE_ID (identifier of the associated structure type), STRUCTURE_TYPE_CLASS_CODE (the structural classification, such as WORKPLAN or financial), and MEANING (the decoded lookup meaning for the structure type class). The ETRM column listing references ELEMENT_NAM, which corresponds to element naming derived from these base attributes. These columns enable consumers to identify each task, its parent project, and the structural context in which it participates.

Common Use Cases and Queries

Typical uses include validating that tasks are assigned to published structures, generating workplan versus financial task listings, and feeding downstream interfaces that need task identity independent of structure class.

• List all tasks for a project with their structure classification: SELECT proj_element_id, element_number, name, structure_type_class_code, meaning FROM apps.pa_fin_wp_tasks_v WHERE project_id = :project_id;
• Retrieve only workplan tasks: SELECT proj_element_id, name FROM apps.pa_fin_wp_tasks_v WHERE structure_type_class_code = 'WORKPLAN';
• Join to other task-level views to enrich reporting: SELECT v.proj_element_id, v.name, t.task_number FROM apps.pa_fin_wp_tasks_v v, apps.pa_tasks t WHERE v.proj_element_id = t.task_id;

Because the view is limited to published structures, it is well suited to reporting against stable, released project definitions in both 12.1.1 and 12.2.2 environments.