Search Results pa_config_lists_project_v

Overview

PA_CONFIG_LISTS_PROJECT_V is a Projects (PA) module view in Oracle E-Business Suite 12.1.1 and 12.2.2 that presents project records alongside the configuration list elements to which they are associated. Its documented purpose is to "display all list elements" in the context of project data, making it a convenience view for reporting and integration scenarios where project attributes and their corresponding list element definitions must be presented together. The view is not implemented as a physical database object in every environment; the ETRM documentation explicitly states "Not implemented in this database," meaning that in some 12.1.1 or 12.2.2 instances the view does not exist at all, and in others it is created only when the relevant Projects configuration features are deployed. Because of this conditional deployment, developers and report authors should verify existence against ALL_VIEWS or DBA_VIEWS before referencing it in custom code.

Underlying Base Objects

The view text joins two documented sources: PA_XC_PROJECT_DETAILS_V (aliased PXP) and PA_CONFIG_LIST_ELEMENTS (aliased PCLE). PA_XC_PROJECT_DETAILS_V is itself a view that resolves project-level information, including project identity, organization, status, and the project manager attributes. PA_CONFIG_LIST_ELEMENTS is the table that stores individual entries belonging to configurable lists used by the Projects module. The join is defined as PXP.PROJECT_ID = PCLE.LIST_ELEMENT_ID (+), an outer join with the plus operator on the PA_CONFIG_LIST_ELEMENTS side. This means every project returned by PA_XC_PROJECT_DETAILS_V is preserved even when no matching list element exists, with the PCLE columns returned as null in those rows. The documented metadata lists no additional referenced base objects beyond these two, so the view is best understood as a single-purpose join whose cardinality is driven by the project side plus any matching configuration list elements.

Key Columns

The view exposes the following documented columns, grouped here by origin:

• Project identity and status from PA_XC_PROJECT_DETAILS_V: PROJECT_ID, PROJECT_NAME, PROJECT_NUMBER, PROGRESS_STATUS_CODE, PROGRESS_STATUS, TAG.
• Organization context: COMPANY_ID, COMPANY_NAME.
• Project manager attributes: PROJECT_MANAGER_ID, PROJECT_MANAGER_NAME, PROJECT_MANAGER_USER_ID, PROJECT_MANAGER_USER_NAME. The PROJECT_MANAGER_NAME column is the one most commonly targeted when users search for "project_manager_name," as it provides the display name of the assigned project manager directly from the view.
• Date attributes: START_DATE and END_DATE for the project.
• Configuration list element attributes from PA_CONFIG_LIST_ELEMENTS: LIST_ID, LIST_ELEMENT_ID, DISPLAY_ORDER, RECORD_VERSION_NUMBER, and the standard audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
• Descriptive flexfield columns: ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15, which carry the DFF context and segment values recorded against the list element.

Common Use Cases and Queries

Typical use cases include building project-level reports that must show the project manager alongside list membership, and integration extracts that need to reconcile project records with configurable list definitions. A simple query returns project and manager information for a given project number:

SELECT PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, PROJECT_MANAGER_NAME, START_DATE, END_DATE FROM PA_CONFIG_LISTS_PROJECT_V WHERE PROJECT_NUMBER = :project_number;

To restrict the result to projects that have at least one configuration list element associated, filter on the outer-joined column:

SELECT PROJECT_ID, PROJECT_NAME, PROJECT_MANAGER_NAME, LIST_ID, LIST_ELEMENT_ID, DISPLAY_ORDER FROM PA_CONFIG_LISTS_PROJECT_V WHERE LIST_ID IS NOT NULL ORDER BY PROJECT_ID, DISPLAY_ORDER;

Because PUBLISHED_NAME columns may differ between releases, verifying the view definition in DBA_VIEWS is recommended before deploying dependent code in either 12.1.1 or 12.2.2.