Search Results object_id_from2




Overview
Explore in AI Chat

Overview

The APPS.PA_FIN_STRUCTURES_LINKS_V view is a reporting and integration object within the Oracle E-Business Suite Projects (PA) module. It exposes the financial structure hierarchy linkages that exist between a parent project structure version and its subordinate (sub) project structure version, together with the associated task-level detail and the relationship metadata recorded in the object relationships model. In Oracle Projects, financial structures are the containers that organize a project's budgeting and costing elements, and the links between them define roll-up and association behavior. This view surfaces those links in a denormalized, human-readable form by joining version records back to the owning projects and project elements so that names, numbers, and identifiers are returned together.

Because the object is a view rather than a table, it presents no independent storage. Its role is to simplify access to the otherwise opaque PA_OBJECT_RELATIONSHIPS structure, in which links are stored as generic relationship rows keyed by object type and direction. Report developers, extensions, and integration interfaces query this view when they need to reconcile which sub-financial-structure versions are attached to the latest financial structure version of a parent project.

Underlying Base Objects

The view is defined over several Projects tables and supporting objects, all accessed through APPS synonyms:

The join predicates tie PPV2 (the sub-side financial structure version) to POR1 via OBJECT_ID_TO1 and to PPA2/PPE2, while PPV1 (the parent side) is reached through POR2 and constrained so that its PARENT_STRUCTURE_VERSION_ID equals the latest financial structure version of its project. Only relationships of type 'LF' qualify.

Key Columns

The exposed columns align to the aliases used in the view text. The documented output includes:

Common Use Cases and Queries

Typical scenarios include validating that every active parent financial structure is linked to its intended sub-structures, generating hierarchy reports for project accounting review, and driving integration extracts that must carry project and element naming along with the raw relationship identifiers.

A straightforward retrieval of all links for a given parent project:

  • SELECT sub_project_number, sub_project_name, parent_project_number, relationship_type, object_relationship_id FROM apps.pa_fin_structures_links_v WHERE parent_project_number = :project_number;

To audit links carrying comments, or to confirm the latest-version constraint is applied, query by RELATIONSHIP_TYPE and inspect SUB_STRUCTURE_VER_ID against the expected version. Because the view already restricts the parent side to the latest financial structure version, results represent the current structure topology rather than historical versions. Joins back to PA_PROJECTS_ALL or PA_PROJ_ELEMENTS should therefore use the exposed identifiers (SUB_PROJECT_ID, PARENT_PROJECT_ID, PARENT_TASK_ID) rather than re-deriving them. Queries should be schema-qualified with APPS and run under a responsibility with Projects inquiry privileges.