Search Results pa_projects_sec_v




Overview
Explore in AI Chat

Overview

PA_PROJECTS_SEC_V is a security-constrained view owned by the APPS schema within the Oracle E-Business Suite Projects (PA) module. It exposes a filtered projection of project records from PA_PROJECTS, applying Oracle EBS row-level security semantics so that a querying user sees only those projects to which they have been granted access. The view is defined over PA_PROJECTS joined conceptually with the current FND_USER session context, and is intended for reporting, integration, and inquiry purposes where security enforcement is required without embedding custom access logic.

Non-template projects only are returned, since the view text filters on TEMPLATE_FLAG = 'N'. A project qualifies when at least one of the following holds: its security level is 1 (public) and the user is internal; the user appears as a project party (employee resource, RESOURCE_TYPE_ID 101, or customer contact, RESOURCE_TYPE_ID 112); or the user holds an active FND_GRANTS instance grant over the carrying-out organization. Because inclusion of LONG_NAME was central to the search that surfaced this object, the view is frequently used where a full descriptive project label is preferred over the short NAME.

Underlying Base Objects

The view is defined over the following documented base objects: PA_PROJECTS (synonym), PA_PROJECT_PARTIES (synonym), FND_USER (synonym), FND_GRANTS (synonym), FND_OBJECTS (synonym), FND_GLOBAL (package), and PA_SECURITY_PVT (package). PA_PROJECTS supplies the primary project attributes. PA_PROJECT_PARTIES is used in the EXISTS clause to identify party-based access. FND_USER resolves the session user and whether that user is external. FND_GRANTS and FND_OBJECTS validate organization-instance grants within their active date range. FND_GLOBAL supplies USER_ID and EMPLOYEE_ID; PA_SECURITY_PVT.GET_GRANTEE_KEY returns the current grantee key used to match grants.

Key Columns

  • PROJECT_ID — Primary identifier of the project; the join key for downstream queries.
  • NAME — Short project name.
  • LONG_NAME — Extended descriptive project name, the column most commonly searched.
  • SEGMENT1 — Project number used in code combinations and reporting.
  • DESCRIPTION — Free-text project description.
  • PROJECT_TYPE — Classification of the project.
  • CARRYING_OUT_ORGANIZATION_ID — Organization responsible for executing the project; also the grant instance target.
  • PROJECT_STATUS_CODE — Current lifecycle status of the project.
  • TEMPLATE_FLAG — Always 'N' in this view, excluding templates.
  • ORG_ID — Operating unit identifier, useful for multi-org filtering.
  • PROJECT_CURRENCY_CODE — Currency in which the project is denominated.

Common Use Cases and Queries

The view is typically used in place of a direct PA_PROJECTS query when the requirement is to honor user security automatically. Typical scenarios include secured LOV-style lookups, custom concurrent reports, and integration extracts that must not leak unauthorized project data. A basic search on LONG_NAME is straightforward:

  • SELECT project_id, name, long_name, segment1 FROM pa_projects_sec_v WHERE long_name LIKE :search_term;
  • SELECT project_id, long_name, project_status_code FROM pa_projects_sec_v WHERE org_id = :org_id AND project_status_code = 'APPROVED';
  • SELECT v.project_id, v.long_name FROM pa_projects_sec_v v WHERE v.carrying_out_organization_id = :org_id;

Queries against this view automatically inherit the party, organization-grant, and public-security conditions, so no additional security predicates are required by the caller. The view is read-only and should not be treated as a substitute for API-based project maintenance. Oracle Proprietary, Confidential Information — Legal Notices apply to its use and distribution.