Search Results pa_struct_proj_lov_v




Overview

PA_STRUCT_PROJ_LOV_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined within the Projects (PA) product module. Its name indicates its primary function: it supplies the data set behind the Project Structure list of values (LOV) used throughout the Projects application. Rather than storing data, the view assembles a filtered, denormalized projection of project header information joined to the structure-type definitions assigned to each project.

Because the view is exposed in the APPS schema without a package wrapper, it serves two purposes. First, it drives the seeded LOV windows that allow users to select a valid project carrying an associated project structure. Second, it acts as a lightweight integration and reporting surface, allowing custom concurrent programs, Oracle Reports, OAF pages, and BI Publisher data models to enumerate projects and their structure types without reconstructing the multi-table join manually. The view is documented as VALID and present in both 12.1.1 and 12.2.2, and its definition is stable across those releases in the ETRM metadata.

Underlying Base Objects

The ETRM metadata records the following referenced base objects: PA_PROJECTS_ALL, PA_PROJ_ELEMENTS, PA_PROJ_STRUCTURE_TYPES, PA_STRUCTURE_TYPES, all exposed through APPS synonyms, together with the PA_PROJECT_PARTIES_UTILS package. The view text confirms the join path:

PA_PROJECT_PARTIES_UTILS is listed as referenced metadata, typically reflecting security or party-related logic applied in related LOV constructs rather than in the visible SELECT text. The effective grain of the view is one row per project per assigned structure type.

Key Columns

  • PROJECT_ID — the unique project identifier from PA_PROJECTS_ALL; the primary join key for downstream queries.
  • PROJECT_NAME — the project name (PA_PROJECTS_ALL.NAME), the descriptive value normally displayed in the LOV.
  • PROJECT_NUMBER — the project number (PA_PROJECTS_ALL.SEGMENT1), the user-facing project identifier.
  • STRUCTURE_TYPE — the structure type assigned to the project, derived from PA_STRUCTURE_TYPES; commonly values such as Work Breakdown Structure, Organization, or Cost Breakdown Structure.

Common Use Cases and Queries

The view is most frequently used to validate that a project has an associated structure before enabling structure-dependent functionality, and to populate selection lists in custom extensions.

  • Listing all projects by structure type:
    SELECT project_id, project_number, project_name, structure_type
    FROM   apps.pa_struct_proj_lov_v
    WHERE  structure_type = 'WORK BREAKDOWN STRUCTURE'
    ORDER BY project_number;
  • Resolving a project number to its ID and structure:
    SELECT project_id, project_name, structure_type
    FROM   apps.pa_struct_proj_lov_v
    WHERE  project_number = :p_project_number;
  • Counting structures per project to detect projects with multiple or missing structures:
    SELECT project_id, COUNT(*) structure_count
    FROM   apps.pa_struct_proj_lov_v
    GROUP BY project_id
    HAVING COUNT(*) <> 1;

Note that the LOV variant returns no rows for project templates and no rows for projects lacking a structure element. Because the view contains no organization or operating-unit filter, callers requiring MOAC or project security must apply additional predicates against PA_PROJECTS_ALL or use the standard security-enabled LOV constructs.