Search Results parent_task_name




Overview
Explore in AI Chat

Overview

PA_PROGRAM_LINKS_AMG_V is an Oracle E-Business Suite view owned by the APPS schema and shipped as part of the Projects (PA) product. Its documented purpose is to provide program links information — that is, the parent/child relationships that connect a sub-project (a "program" element) to the higher-level project and task to which it is linked through Oracle Projects' object relationship model. In releases 12.1.1 and 12.2.2, the view is registered as VALID and is exposed through the APPS synonym layer, making it available to reporting tools, concurrent programs, and custom integrations without requiring callers to hold privileges on the underlying PA base tables directly.

The view is primarily a read-only reporting and integration construct. It is not an entity that is maintained by the application; all maintenance occurs on the base tables, and the view resolves the current state of program links at query time.

Underlying Base Objects

The view is defined over the following base objects, all accessed through the APPS synonyms:

  • PA_PROJ_ELEMENT_VERSIONS (aliased PPV1 and PPV2) — element version records for the parent and the program element respectively.
  • PA_PROJ_ELEM_VER_STRUCTURE (PPEVS1) — the structure version linkage that ties an element version to its parent structure version.
  • PA_PROJ_ELEMENTS (PPE1) — the project element (task) master rows.
  • PA_PROJECTS_ALL (PPA1 and PPA2) — project master rows for the parent project and the sub-project.
  • PA_OBJECT_RELATIONSHIPS (POR1 and POR2) — the relationship records that define the link between a program and its associated element version.

The join path is driven by object relationships: POR1 connects the program's element version (PPV2.ELEMENT_VERSION_ID) as its OBJECT_ID_TO1, restricted to OBJECT_TYPE = 'PA_STRUCTURES' and RELATIONSHIP_TYPE IN ('LW','LF'). POR1's OBJECT_ID_FROM1 is then matched to POR2's OBJECT_ID_TO1, and POR2's OBJECT_ID_FROM1 resolves to the parent element version (PPV1.ELEMENT_VERSION_ID). The structure-version linkage, the element master row, and both project master rows complete the projection.

Key Columns

Common Use Cases and Queries

Typical uses include reporting on program hierarchies, validating that a sub-project is correctly linked to its parent project and task, and feeding downstream integrations that need the parent/sub-project mapping.

List all program links for a given parent project:

SELECT sub_project_number,
       sub_project_name,
       parent_project_number,
       parent_task_number,
       relationship_type
FROM   apps.pa_program_links_amg_v
WHERE  parent_project_number = 'PRJ-1001';

Identify orphaned or missing links by comparing program projects against the view:

SELECT p.segment1, p.name
FROM   apps.pa_projects_all p
WHERE  p.project_type = 'PROGRAM'
AND    NOT EXISTS (SELECT 1
                   FROM   apps.pa_program_links_amg_v v
                   WHERE  v.sub_project_id = p.project_id);

Because the view joins multiple versioned tables and both project masters, queries should be scoped by project number or ID wherever possible to limit the volume of element-version rows evaluated.