Search Results pm_parent_task_reference

Overview

APPS.PA_PROGRAM_LINKS_AMG_V is an Oracle EBS Projects (PA) reporting view that exposes the linkage between tasks and structures across project versions. It is defined over the core Projects tables that hold project definitions, project element versions, project element version structures, project elements, and object relationships. The view is significant because it surfaces both the source (child) and parent contexts of a program link in a single row, joining task-level details to their associated structure versions and projects. In the context of Oracle EBS 12.1.1 and 12.2.2, this view is typically used in reporting, integration, and diagnostics where program or project reference relationships must be traced between tasks and structures. The mention of pm_project_reference in the search reflects its role in surfacing project reference identifiers for both the parent and child project records, enabling cross-project reconciliation and lookup by external reference.

Because the view is owned by APPS and references public synonyms, it is intended to be queried from the APPS schema or through EBS reporting tools such as Oracle Reports, BI Publisher, and custom SQL integrations. It does not store data; it is a read-only projection of the underlying relationship and version data.

Underlying Base Objects

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

• PA_PROJECTS_ALL — the master project definition table, providing project name, project number (segment1), and the pm_project_reference attribute for both parent and child projects.
• PA_PROJ_ELEMENTS — the project element definitions, supplying the element number, name, and pm_source_reference.
• PA_PROJ_ELEMENT_VERSIONS — the versioned view of project elements, providing element_version_id, project_id, and parent_structure_version_id.
• PA_PROJ_ELEM_VER_STRUCTURE — the structure that links element versions to their parent structure version and project, establishing hierarchy.
• PA_OBJECT_RELATIONSHIPS — the generic relationship table that records the link between tasks and structures via object_id_from1, object_id_to1, and relationship_type.

The joins constrain object_type to 'PA_STRUCTURES' and relationship_type to 'LW' and 'LF', which represent the program link relationships between task and structure objects. Two aliases of PA_OBJECT_RELATIONSHIPS (por1 and por2) are used to bridge the child structure to the parent task and then to the parent structure version.

Key Columns

The view projects columns from both the child and parent sides of the relationship, which is what makes it useful for link analysis:

• PPV2.PROJECT_ID, PPA2.NAME, PPA2.PM_PROJECT_REFERENCE, PPA2.SEGMENT1 — the child (source) project context, including the pm_project_reference so records can be located by external project reference.
• PPV2.ELEMENT_VERSION_ID — the versioned structure element for the child side.
• POR1.RELATIONSHIP_TYPE and POR1.COMMENTS — the type of link (LW or LF) and any comments captured on the relationship records.
• PPV1.PROJECT_ID, PPA1.NAME, PPA1.PM_PROJECT_REFERENCE, PPA1.SEGMENT1 — the parent project context, again exposing pm_project_reference.
• PPV1.PARENT_STRUCTURE_VERSION_ID and PPV1.ELEMENT_VERSION_ID — parent structure version and element version identifiers.
• PPE1.PROJ_ELEMENT_ID, PPE1.ELEMENT_NUMBER, PPE1.NAME, PPE1.PM_SOURCE_REFERENCE — the project element details, including the source reference.
• POR1.OBJECT_RELATIONSHIP_ID — the unique identifier for the relationship row, useful for drill-down.

Common Use Cases and Queries

Typical scenarios include tracing which tasks a structure is linked to, reconciling project references across linked projects, and reporting on LW/LF relationship comments. A basic query filtering by project reference is shown below:

SELECT child_project_id, child_project_reference,
       parent_project_id, parent_project_reference,
       relationship_type, comments
FROM   apps.pa_program_links_amg_v
WHERE  child_project_reference = :pm_project_reference
   OR  parent_project_reference = :pm_project_reference;

Analysts also use the view to count links by relationship type, to identify orphaned or missing structure versions, and to feed integration extracts that must publish project linkage metadata to downstream systems. Because the view joins versioned structures and elements, queries should be filtered by project or element where possible to limit the volume of versioned rows returned.