Search Results element_number




Overview
Explore in AI Chat

Overview

APPS.PA_STRUC_PREDECESSORS_V is a seeded Oracle E-Business Suite view that exposes the dependency (predecessor/successor) relationships defined between project structure elements, primarily tasks and structures within Oracle Projects. The view consolidates the object-relationship records stored in PA_OBJECT_RELATIONSHIPS and joins them to the project element, element version, and structure-version tables so that each row presents a fully resolved predecessor relationship, including both the "from" (predecessor) element and the "to" (successor) element.

The view restricts its output to relationships of type 'D' (dependency) where the successor object type is 'PA_TASKS' and the predecessor object type is either 'PA_TASKS' or 'PA_STRUCTURES'. It is implemented as a UNION of two branches: the first handles task-to-task and structure-to-task dependencies resolved through the element version structure, and the second handles structure-level dependencies. The view is read-only and is intended for reporting and integration rather than direct maintenance.

Because the user searched for "element_number," it is significant that the view exposes element_number columns for both the predecessor (pe1.element_number) and, in the first branch, the successor (pe2.element_number). This allows consumers to identify dependencies using the business-visible element number rather than internal surrogate keys.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects, all resolved through APPS synonyms:

  • PA_OBJECT_RELATIONSHIPS — stores the actual relationship records (rel), including object_type_from, object_type_to, relationship_type, lag_day, priority and record version.
  • PA_PROJECTS_ALL — the project master (pp1/pp2), supplying project_id, segment1 and name.
  • PA_PROJ_ELEMENTS — the project element definitions (pe1, pe2), supplying proj_element_id, element_number and name.
  • PA_PROJ_ELEMENT_VERSIONS — element version records (pv1, pv2), supplying element_version_id.
  • PA_PROJ_ELEM_VER_STRUCTURE — the structure-version hierarchy (evs), supplying version_number and name.

The joins link relationship records to element versions, then to elements, projects and structure versions, reconstructing both ends of each dependency.

Key Columns

  • object_relationship_id — unique identifier for the dependency record.
  • project_id, segment1, name — the project owning the successor/predecessor element.
  • pe1.proj_element_id, pe1.element_number, pe1.name — the predecessor (from) element identity.
  • pv1.element_version_id, evs.version_number, evs.name — the predecessor element version and structure version details.
  • pe2.element_number, pe2.name — the successor element number/name (null in the structure branch).
  • object_id_from1 — the originating object id of the relationship.
  • relationship_type, relationship_subtype, lag_day, imported_lag, priority — scheduling and dependency attributes.
  • pm_product_code, record_version_number — product ownership and optimistic-lock version.

Common Use Cases and Queries

Typical uses include dependency reporting, schedule integration, and predecessor validation in project planning. A representative query filtering by element_number follows:

  • SELECT project_id, segment1, element_number, name, lag_day, priority FROM ap_pppa_struc_predecessors_v WHERE element_number = :p_element_number;
  • SELECT * FROM apps.pa_struc_predecessors_v WHERE project_id = :p_project_id ORDER BY element_number;

Because the view is read-only and pre-joins five base objects, it is convenient for ad-hoc reporting and downstream integrations that need resolved predecessor information without reconstructing the relationship model.