Search Results pa_structures_links_v




Overview
Explore in AI Chat

Overview

PA_STRUCTURES_LINKS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the Projects (PA) product family. It presents the links that connect project structures — specifically the relationships between a work breakdown structure (WBS) or structure element and its parent structure element across project versions. In ETRM terms, the view exposes the hierarchical and cross-project relationships recorded in the Projects structure model, together with the planned effort, baseline and scheduled dates, and project manager assignments associated with each structure element.

Its primary role is to support reporting and integration scenarios where the parent-to-child linkages between structure elements must be surfaced without consumers having to navigate the underlying relationship and version tables directly. The view is defined with a driving hint on PJI_FM_XBS_ACCUM_TMP1, indicating that it is tuned for accumulation and effort-rollup style queries rather than simple single-row lookups.

Underlying Base Objects

According to the documented ETRM metadata, the view is defined over the following base objects, all referenced through APPS synonyms except for the utility package:

  • PA_OBJECT_RELATIONSHIPS — supplies the relationship rows and relationship type linking structure versions to one another.
  • PA_PROJECTS_ALL — provides project number (SEGMENT1) and project name for both the linked and parent projects.
  • PA_PROJ_ELEMENTS — supplies the structure element identity, element number, and element name.
  • PA_PROJ_ELEMENT_VERSIONS — provides the structure version records for the linked and parent structures.
  • PA_PROJ_ELEM_VER_SCHEDULE — contributes scheduled start and finish dates for the element version.
  • PA_PROJ_ELEM_VER_STRUCTURE — links an element version to its parent structure version.
  • PJI_FM_XBS_ACCUM_TMP1 — a temporary accumulation object supplying planned labor and equipment hours and the calendar/plan version context.
  • PA_PROJECT_PARTIES_UTILS — a package whose functions resolve the project manager identity and name.

The joins connect PPV1 (parent structure versions) to PPV2 (linked structure versions) via PA_OBJECT_RELATIONSHIPS, with the relationship type constrained to 'LW' and 'LF'.

Key Columns

The view exposes identifier columns for both sides of the relationship, including PROJECT_ID, NAME, and SEGMENT1 for the parent (PPA1/PPV1) and linked (PPA2/PPV2) projects. Element-level columns include ELEMENT_VERSION_ID, PROJ_ELEMENT_ID, ELEMENT_NUMBER, and NAME. Relationship metadata is carried by RELATIONSHIP_TYPE, COMMENTS, OBJECT_RELATIONSHIP_ID, and RECORD_VERSION_NUMBER. Effort and schedule information is supplied through PLANNED_EFFORT (the sum of labor and equipment hours) and BASELINE_START_DATE, BASELINE_FINISH_DATE, SCHEDULED_START_DATE, and SCHEDULED_FINISH_DATE. Project manager details are returned via the PA_PROJECT_PARTIES_UTILS.GET_PROJECT_MANAGER and GET_PROJECT_MANAGER_NAME function calls.

Common Use Cases and Queries

Typical applications include structure hierarchy reporting, effort rollup analysis, and integration extracts that must reconcile linked project structures. A representative query retrieves the linked structures and planned effort for a given project:

  • SELECT project_id, name, segment1, relationship_type, planned_effort, scheduled_start_date, scheduled_finish_date FROM pa_structures_links_v WHERE project_id = :p_project_id;
  • SELECT project_id, element_number, relationship_type, planned_effort FROM pa_structures_links_v WHERE relationship_type IN ('LW','LF');
  • SELECT project_id, name, scheduled_finish_date FROM pa_structures_links_v ORDER BY project_id, scheduled_finish_date;

Because PLANNED_EFFORT is derived through NVL-based arithmetic against the accumulation temporary object, results depend on the availability of accumulation rows for the relevant plan version and calendar. Queries should therefore constrain by project or structure version where possible to limit the volume of accumulation data processed.