Search Results project_manager_name




Overview
Explore in AI Chat

Overview

APPS.PA_STRUCT_PROJ_LOV_V is a database view owned by the APPS schema in Oracle E-Business Suite, documented as VALID in both Release 12.1.1 and 12.2.2. It is registered in FND Design Data as PA.PA_STRUCT_PROJ_LOV_V and is classified as an internal, Oracle-only object. Oracle explicitly warns that this object is for internal use and is not supported for direct access except from standard Oracle Applications programs. Consequently, it should be treated as a read-only, non-API dependent view.

The view serves as the backing query for project-related List of Values (LOV) mechanisms within Oracle Projects. Its column set — PROJECT_ID, PROJECT_NAME, PROJECT_NUMBER, STRUCTURE_TYPE, PROJECT_MANAGER_ID, and PROJECT_MANAGER_NAME — indicates that it presents a project selection list enriched with work breakdown structure (WBS) information and the project manager identity. This explains why it surfaces in searches for the "project_manager_id" attribute, a value that end users and reporting tools frequently need to resolve from a project name.

Underlying Base Objects

The view is defined over five documented objects:

  • PA_PROJECTS_ALL — the central project master table, supplying PROJECT_ID, PROJECT_NAME, and PROJECT_NUMBER.
  • PA_PROJ_ELEMENTS — the project elements table, which stores structure elements and supplies structure-related context.
  • PA_PROJ_STRUCTURE_TYPES — associates project structures with structure type definitions.
  • PA_STRUCTURE_TYPES — defines the structure type classifications, feeding the STRUCTURE_TYPE column.
  • PA_PROJECT_PARTIES_UTILS — a PL/SQL package that resolves project party roles and is used to derive PROJECT_MANAGER_ID and PROJECT_MANAGER_NAME.

Because PM identity is resolved through PA_PROJECT_PARTIES_UTILS rather than a static join to a party table, PROJECT_MANAGER_ID is effectively a derived runtime value tied to the party/role model assigned by the package. This explains why PROJECT_MANAGER_NAME carries a large VARCHAR2(4000) length. The view is not referenced by any other database object, so it sits at the top of its dependency chain.

Key Columns

  • PROJECT_ID (NUMBER, 15) — primary key of the project; the join key to PA_PROJECTS_ALL and most project transaction tables.
  • PROJECT_NAME (VARCHAR2, 30) — user-facing project name displayed in LOVs.
  • PROJECT_NUMBER (VARCHAR2, 25) — the project's alternate key used for reporting reconciliation.
  • STRUCTURE_TYPE (VARCHAR2, 150) — the structure type name associated with the project's project structure definition.
  • PROJECT_MANAGER_ID (NUMBER) — identifier of the person assigned the project manager role, resolved via PA_PROJECT_PARTIES_UTILS.
  • PROJECT_MANAGER_NAME (VARCHAR2, 4000) — display name of the project manager, stored wide to accommodate concatenated name formats.

Common Use Cases and Queries

The view supports LOV-driven project selection and is frequently joined when reports must display both project and manager identity. A straightforward lookup by manager is:

SELECT project_id,
       project_name,
       project_number,
       structure_type,
       project_manager_id,
       project_manager_name
FROM   apps.pa_struct_proj_lov_v
WHERE  project_manager_id = :p_manager_id;

To resolve a project name to its manager, filter on the project number:

SELECT project_name, project_manager_name
FROM   apps.pa_struct_proj_lov_v
WHERE  project_number = :p_number;

Because the view has no downstream dependents and its manager columns are derived, it should be used for read-only reference rather than as a persistent integration surface. Where a stable, supported interface is required, developers should prefer the Oracle Projects public APIs. For 12.1.1 and 12.2.2 the column layout is consistent, making queries portable across both releases.