Search Results allow_update

Overview

PA_MU_PROJECTS_LOV_V is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) module, classified as VALID and identified in the ETRM repository as "Retrofitted." Its purpose is to expose a security-filtered list of active projects that the currently authenticated user is permitted to query. The view is designed as a List of Values (LOV) source, meaning it is intended to drive Oracle Forms LOVs and similar selection mechanisms where a user must pick a project from a constrained, authorized list rather than from the full population of PA_PROJECTS rows.

Two characteristics distinguish this view. First, it filters out closed projects by calling PA_PROJECT_STUS_UTILS.IS_PROJECT_STATUS_CLOSED and requiring the result to be 'N'. Second, it enforces function security by invoking PA_SECURITY.ALLOW_QUERY for each project, returning a row only when that function yields 'Y'. The view therefore combines status filtering with row-level access control, ensuring that only projects the user can legitimately see are presented. The PROJECT_ID, PROJECT_NAME, PROJECT_NUMBER, ORGANIZATION, ORGANIZATION_ID, PROJECT_ORGANIZATION_NAME, and PROJECT_ORGANIZATION_ID columns constitute the descriptive LOV payload.

Underlying Base Objects

The documented base objects referenced by the view are HR_GENERAL (PACKAGE), HR_ORGANIZATION_UNITS (VIEW), HR_SECURITY (PACKAGE), PA_PROJECTS (SYNONYM), PA_PROJECT_STUS_UTILS (PACKAGE), PA_SECURITY (PACKAGE), and DUAL (TABLE). PA_PROJECTS is the primary driving table, joined to HR_ORGANIZATION_UNITS on CARRYING_OUT_ORGANIZATION_ID = ORGANIZATION_ID to resolve the carrying-out organization. DUAL appears in the scalar subquery that evaluates PA_SECURITY.ALLOW_QUERY. The security and status packages supply the PL/SQL functions that gate row visibility. Because the view depends on session-sensitive functions, its result set is not deterministic across users or sessions and is not suitable for materialization.

Key Columns

• PROJECT_ID — Surrogate key of the project from PA_PROJECTS; the value typically returned by the LOV.
• PROJECT_NAME — Project name (P.NAME), the user-facing description.
• PROJECT_NUMBER — Project number (P.SEGMENT1), the human-readable identifier.
• ORGANIZATION and ORGANIZATION_ID — Name and character-form organization identifier of the carrying-out organization.
• PROJECT_ORGANIZATION_NAME and PROJECT_ORGANIZATION_ID — Name and identifier of the project organization, derived from the same HR organization join.
• ALLOW_UPDATE — Result of PA_SECURITY.ALLOW_UPDATE(P.PROJECT_ID), indicating whether the current user may update the project.

Common Use Cases and Queries

The view supports LOV population, project-selection validation, and security-aware reporting. The ALLOW_UPDATE column in particular answers the common requirement of determining, for a given user session, which visible projects are also writable. A representative query follows:

• SELECT project_id, project_name, project_number, allow_update FROM apps.pa_mu_projects_lov_v ORDER BY project_name;
• SELECT project_id FROM apps.pa_mu_projects_lov_v WHERE allow_update = 'Y';
• SELECT project_number, organization FROM apps.pa_mu_projects_lov_v WHERE project_name LIKE :search;

Because ALLOW_QUERY and ALLOW_UPDATE are evaluated against the current session, queries must be issued under the correct APPS responsibility and user context; invoking the view from a background or concurrent job without an initialized security profile may return no rows. The ALLOW_UPDATE column distinguishes this view from the query-only LOV views and makes it useful where update privilege must be established before allowing a user to proceed.