Search Results pa_project_lists_user_v




Overview
Explore in AI Chat

Overview

PA_PROJECT_LISTS_USER_V is an Oracle Applications (APPS) schema view in the Oracle E-Business Suite Projects (PA) module. It exposes project header information filtered and enriched for user-facing project list functionality, most notably the "My Projects" and project search/list pages within the Projects module. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the presentation-layer data source for project list regions, driving form-based and OAF (Oracle Application Framework) list displays.

The view's defining characteristic is its integration of a security check: it calls PA_SECURITY_PVT.CHECK_USER_PRIVILEGE to determine whether the current user has access to a given project, translating the internal 'T'/'F' privilege result into a 'Y'/'N' flag. This makes the view a convenient, security-aware source for reporting and integration scenarios where only user-accessible projects should be returned. Status is reported as VALID in the documented environment.

Underlying Base Objects

PA_PROJECT_LISTS_USER_V is defined over a substantial set of base tables, views, synonyms, and packages. Its central data source is PA_PROJECTS_ALL (the primary project definition table), augmented by PA_PROJECT_OPP_ATTRS, PA_PROJECT_PARTIES, PA_PROBABILITY_MEMBERS, PA_PROJECT_TYPES_ALL, PA_PROJECT_STATUSES, and PA_LOCATIONS.

Descriptive and reference data are joined from HR_ALL_ORGANIZATION_UNITS, PER_ALL_PEOPLE_F, FND_TERRITORIES_VL, FND_LOOKUPS, FND_USER, and FND_GRANTS. The view also incorporates two subordinate project views, PA_PROJ_CURR_STATUS_REP_V and PA_STATUS_PROJ_LIST_V, and calls several PL/SQL packages: PA_SECURITY_PVT (privilege checking), PA_PROJECTS_MAINT_UTILS (primary customer name derivation via GET_PRIMARY_CUSTOMER_NAME), PA_PROJECT_DATES_UTILS, and FND_GLOBAL (session and user context). Because security logic executes at query time, performance depends on the underlying base objects and joins being properly indexed.

Key Columns

Common Use Cases and Queries

The view is typically queried by reports, concurrent programs, and integrations requiring a security-filtered list of projects with descriptive and status attributes already resolved.

SELECT project_id, name, segment1, project_status_name, start_date
FROM   apps.pa_project_lists_user_v
WHERE  org_id = :org_id

To list only projects the current user may access, filter on the security-derived indicator:

SELECT project_id, name, project_status_name, primary_customer_name
FROM   apps.pa_project_lists_user_v
WHERE  enabled_flag = 'Y'
AND     = 'Y'

Other frequent applications include populating LOV-style project pickers, feeding customer-facing project summaries, extracting active project rosters for downstream systems, and pulling DFF segment values (PSI.COLUMN4–COLUMN33) into custom reports. Because the view already resolves lookups, statuses, currency, and the primary customer name, it reduces the need for downstream joins in reporting logic.