Search Results pa_dependencies_v




Overview
Explore in AI Chat

Overview

PA_DEPENDENCIES_V is a Projects (PA) module view owned by the APPS schema. It presents task-to-task dependency relationships defined within Oracle Projects, exposing predecessor and successor task elements together with their scheduling dates, relationship attributes, and owning project context. The view is a consolidation layer over the dependency records stored in PA_OBJECT_RELATIONSHIPS, joined to project elements, element versions, schedules, and project headers. Its principal role is to support reporting and integration scenarios where dependency network data — predecessors, successors, lag, and dependency type — must be retrieved without navigating the normalized relationship model directly.

The dependency type is central to this view. Two lookup-derived columns carry that meaning: the column named RELATIONSHIP_SUBTYPE, resolved through the lookup type PA_OBJECT_DEPENDENCY_TYPES, and a display-type column resolved through PA_DEPEND_DISP_TYPE. A user searching for dependency_type_code is typically seeking the value that identifies Finish-to-Start, Start-to-Start, Finish-to-Finish, or Start-to-Finish relationships; in this view that semantic is delivered by RELATIONSHIP_SUBTYPE and its decoded lookup meaning rather than by a column literally named dependency_type_code.

Underlying Base Objects

The documented base objects referenced by the view are:

The join chain is anchored on REL.OBJECT_ID_TO1 and REL.OBJECT_ID_FROM1 against ELEMENT_VERSION_ID, with OBJECT_TYPE_TO and OBJECT_TYPE_FROM constrained to 'PA_TASKS'. A subquery restricts the successor side to the maximum ELEMENT_VERSION_ID per project and element, ensuring only the current version is reported. A UNION with a mirrored branch supports the reciprocal direction of the relationship.

Key Columns

  • RELATIONSHIP_SUBTYPE — the dependency type code (e.g. the value decoded through PA_OBJECT_DEPENDENCY_TYPES); the closest analogue to dependency_type_code.
  • RELATIONSHIP_SUBTYPE (decoded) — the lookup meaning, returned via PA_PROJ_ELEMENTS_UTILS.GET_PA_LOOKUP_MEANING.
  • PROJECT_ID, SEGMENT1, NAME — project identity from PA_PROJECTS_ALL.
  • ELEMENT_NUMBER, NAME, PROJ_ELEMENT_ID — predecessor/successor task identifiers.
  • ELEMENT_VERSION_ID, PARENT_STRUCTURE_VERSION_ID — version context for the task elements.
  • LAG_DAY, COMMENTS — lag expressed in days and free-text relationship notes from PA_OBJECT_RELATIONSHIPS.
  • SCHEDULED_START_DATE, SCHEDULED_FINISH_DATE, ACTUAL_START_DATE, ACTUAL_FINISH_DATE — schedule data from PA_PROJ_ELEM_VER_SCHEDULE.
  • MANAGER_PERSON_ID, FULL_NAME — task manager identity.
  • OBJECT_RELATIONSHIP_ID, RECORD_VERSION_NUMBER — relationship surrogate key and concurrency token.

Common Use Cases and Queries

Typical uses include dependency network reporting, schedule impact analysis, and data extracts feeding external planning tools. The following query lists all published task dependencies with their decoded type, lag, and successor dates:

  • SELECT PROJECT_ID, SEGMENT1, NAME, ELEMENT_NUMBER, RELATIONSHIP_SUBTYPE, LAG_DAY, SCHEDULED_START_DATE FROM APPS.PA_DEPENDENCIES_V WHERE PROJECT_ID = :p_project_id;

To isolate a specific dependency type, filter on the subtype code using the PA_OBJECT_DEPENDENCY_TYPES lookup values:

  • SELECT ELEMENT_NUMBER, RELATIONSHIP_SUBTYPE, LAG_DAY FROM APPS.PA_DEPENDENCIES_V WHERE PROJECT_ID = :p_project_id AND RELATIONSHIP_SUBTYPE = 'FS';

Because the view exposes both predecessor and successor identifiers, it also supports self-join style analysis of critical path and lag accumulation, and it can be joined back to PA_PROJECTS_ALL or PER_ALL_PEOPLE_F for owner-based reporting. Note that only PUBLISHED dependencies are returned, so draft or working relationships are excluded by design.