Search Results source_task_version_id

Overview

APPS.PA_DEPENDENCIES_V is a validation-level Oracle EBS view owned by the APPS schema and registered under FND Design Data as PA.PA_DEPENDENCIES_V. It exposes dependency relationships that exist between project elements—typically tasks and other schedulable structures—within Oracle Project Management and Oracle Projects scheduling. The view consolidates relationship data from the underlying PA_OBJECT_RELATIONSHIPS table and enriches it with project, element, version, schedule, and resource-owner (task manager) attributes drawn from several other Projects and HR objects. Its documented status is VALID, and its usage type is classified as Internal.

Because the object is marked "Oracle Internal Use Only," Oracle does not support direct customer access to the underlying data except through standard Oracle Applications programs. The view is therefore primarily intended for internal scheduling and dependency-resolution logic within Oracle Projects, though it is frequently encountered by technical consultants during reporting and integration work.

Underlying Base Objects

The view is defined over the following documented referenced objects:

• PA_OBJECT_RELATIONSHIPS — the principal source of dependency rows, capturing the relationship records that link source and target project elements.
• PA_PROJECTS_ALL — supplies project identifying and descriptive attributes such as PROJECT_ID, PROJECT_NUMBER, and PROJECT_NAME.
• PA_PROJ_ELEMENTS — provides element-level detail (ELEMENT_NUMBER, ELEMENT_NAME, PROJ_ELEMENT_ID).
• PA_PROJ_ELEMENT_VERSIONS — supplies version identifiers (ELEMENT_VERSION_ID, SOURCE_TASK_VERSION_ID, PARENT_STRUCTURE_VERSION_ID) used in scheduling versioning.
• PA_PROJ_ELEM_VER_SCHEDULE — contributes scheduled and actual date information for the elements.
• PER_ALL_PEOPLE_F — resolves the task manager (TASK_MANAGER_ID and TASK_MANAGER) into a person name, using the effective-dated HR people table.
• PA_PROJ_ELEMENTS_UTILS — a PL/SQL package referenced in the view definition, used for element utility logic.

The view joins these objects to present dependencies in a single, denormalized result set in which the relationship record from PA_OBJECT_RELATIONSHIPS is expanded with project, element, version, schedule, and person context.

Key Columns

• DEPENDENCY_TYPE / DEPENDENCY_TYPE_CODE — the classification of the dependency relationship.
• PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME — project identification for the dependency.
• PROJ_ELEMENT_ID, ELEMENT_NUMBER, ELEMENT_NAME, ELEMENT_VERSION_ID — the element (task) and its version on which the dependency is defined.
• SOURCE_TASK_ID, SOURCE_TASK_VERSION_ID, SOURCE_PROJECT_ID — the predecessor (source) task and project driving the dependency.
• TASK_MANAGER_ID / TASK_MANAGER — the user identifier and name of the manager responsible for the task, resolved via PER_ALL_PEOPLE_F. This column is directly relevant to queries searching on task_manager_id.
• LAG_DAY — lag in days associated with the dependency.
• SCHEDULED_START_DATE, SCHEDULED_FINISH_DATE, ACTUAL_START_DATE, ACTUAL_FINISH_DATE — scheduling and actual dates for the element.
• OBJECT_RELATIONSHIP_ID, RECORD_VERSION_NUMBER, PARENT_STRUCTURE_VERSION_ID — internal identifiers supporting the relationship and version model.

Common Use Cases and Queries

Typical technical scenarios include resolving which tasks depend on other tasks, identifying managers responsible for dependent tasks, and reconciling scheduled versus actual dates across a dependency network. The following query retrieves all dependencies whose task manager matches a given person, using the documented TASK_MANAGER_ID column:

SELECT PROJECT_NUMBER,
       PROJECT_NAME,
       ELEMENT_NUMBER,
       ELEMENT_NAME,
       SOURCE_TASK_ID,
       DEPENDENCY_TYPE,
       LAG_DAY,
       TASK_MANAGER_ID,
       TASK_MANAGER
  FROM APPS.PA_DEPENDENCIES_V
 WHERE TASK_MANAGER_ID = :person_id;

Because the view references effective-dated tables (notably PER_ALL_PEOPLE_F), queries should account for date-effective joins only where the view does not already resolve them. Consultants integrating with this object should also note the Internal use restriction and validate any custom reporting against Oracle's support guidelines.