Results for “project_description”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PJM_PROJECTS_MTLL_PV is a project-only security view owned by the APPS schema within the Project Manufacturing (PJM) module of Oracle E-Business Suite. Its documented purpose is to serve as the "Project only view for Project Locators," meaning it exposes a filtered list of projects that are valid for use as project locators within a manufacturing organization. In the Project Manufacturing model, inventory and work-in-process transactions must be associated with a project and task, and the set of projects available for such transactions is governed by organization-level enablement parameters. This view encapsulates that filtering logic so that Oracle Forms, concurrent programs, and reporting tools do not need to re-implement it.

The view is particularly relevant in implementations where multiple manufacturing organizations share a single project repository. Rather than presenting every project defined in Oracle Projects, PJM_PROJECTS_MTLL_PV restricts the result set based on the current manufacturing organization context, as determined by the MFG_ORGANIZATION_ID profile option. This makes it a key component of the Project Locators LOV (list of values) used during material transactions, move orders, and other PJM-enabled flows.

Underlying Base Objects

According to the ETRM 12.2.2 metadata, the view is defined over PA_PROJECTS_ALL_BASIC_V, a Projects view that supplies the core project attributes. Supporting objects referenced by the view definition include FND_PROFILE (to retrieve the MFG_ORGANIZATION_ID profile value), PJM_ORG_PARAMETERS and PJM_PROJECT_PARAMETERS (synonyms to the organization- and project-level PJM setup tables), and indirectly PA_SECURITY, PA_PROJECT_UTILS, and PA_CROSS_BUSINESS_GRP through the underlying Projects view. The driving query selects project information from PA_PROJECTS_ALL_BASIC_V and applies an EXISTS clause that validates the project against PJM_PROJECT_PARAMETERS for the organization where PROJECT_REFERENCE_ENABLED is set to 'Y'. If no manufacturing organization is set in the profile, the restriction is effectively bypassed, and all projects are returned.

Key Columns

• PROJECT_ID — The unique internal identifier of the project; used as the foreign key in PJM transaction tables and as the value returned by the LOV.
• PROJECT_NUMBER — The user-visible project number, typically the primary search key in project locator fields.
• PROJECT_NAME — The descriptive name of the project, displayed alongside the number in selection lists.
• PROJECT_DESCRIPTION — Free-text description associated with the project.
• PROJECT_NUMBER_SORT_ORDER — A sortable representation of the project number, allowing consistent alphanumeric ordering in LOVs and reports.
• START_DATE — The project's start date, useful for date-range filtering or validation of transaction timing.
• COMPLETION_DATE — The project's scheduled or actual completion date.

Common Use Cases and Queries

The primary use case is populating the Project Locator field in PJM-enabled inventory and manufacturing windows. Reporting users also query it to determine which projects are enabled for a given organization. A typical query to list all locatable projects is:

SELECT project_number, project_name, start_date, completion_date FROM apps.pjm_projects_mtll_pv ORDER BY project_number_sort_order;

Because the view depends on FND_PROFILE.VALUE('MFG_ORGANIZATION_ID'), the result set varies with the session's organization context. To retrieve projects for a specific organization, the profile must first be set, for example via FND_PROFILE.PUT, or the query must be executed within a responsibility whose organization context is already established. A common diagnostic query is to join the view to PJM_PROJECT_PARAMETERS to confirm which projects are explicitly enabled:

SELECT v.project_number, v.project_name FROM apps.pjm_projects_mtll_pv v, apps.pjm_project_parameters p WHERE p.project_id = v.project_id ORDER BY v.project_number;

The term "montana energie" in the user's search does not correspond to any documented feature of this view; the object is unrelated to energy-sector terminology and should be understood strictly in the Project Manufacturing context described above.