Search Results sub_project_id




Overview
Explore in AI Chat

Overview

APPS.PA_STRUCTURES_LINKS_V is an Oracle E-Business Suite internal view owned by the APPS schema that exposes the structural and scheduling relationships between parent and sub-project elements in Oracle Projects. It is delivered as part of the PA (Projects) product family and carries FND Design Data reference PA.PA_STRUCTURES_LINKS_V. The view flattens the relationship records held in the Projects object-relationship model into a single denormalized result set, pairing each sub-project/task (the "from" side of a structure link) with its parent project, parent task, and the associated scheduling attributes.

Its primary role is to support the Structured Project / work-breakdown reporting in Oracle Projects, and in particular to resolve a parent element's identity — including PARENT_TASK_NUMBER — for any given child record. Because it exposes both descriptive identifiers (project and task numbers and names) and financial/scheduling measures (planned effort, baseline and scheduled dates, project manager), it is commonly encountered in project structure inquiries, integration extracts, and custom reports. Oracle marks the object "Internal — Oracle Internal Use Only", so supported access is expected only through standard Oracle Applications programs and not through direct customer SQL in a production, supported sense.

Underlying Base Objects

The view is defined over the following documented base objects, all resolved through synonyms in the APPS schema:

These objects are joined so that a single row represents one structure link, with sub-element columns drawn from the child side and parent columns resolved from the parent element version.

Key Columns

Common Use Cases and Queries

The view is typically used to resolve the parent task for a child element, to report project structure hierarchies, or to extract scheduling and effort data for integration. A representative query retrieves the parent task number for a given sub-project:

  • SELECT sub_project_number, parent_project_number, parent_task_number, parent_task_name FROM apps.pa_structures_links_v WHERE parent_task_number IS NOT NULL;
  • Filter to a specific child: ... WHERE sub_project_id = :p_sub_project_id;
  • Report link type: ... WHERE relationship_type = :p_relationship_type;
  • Extract scheduling: SELECT parent_task_number, scheduled_start_date, scheduled_finish_date, planned_effort FROM apps.pa_structures_links_v;

Consumers should treat the view as read-only and prefer standard Oracle Projects APIs where available, since direct querying of internal views is unsupported.