Search Results project_organization_name




Overview
Explore in AI Chat

Overview

APPS.AP_WEB_PA_PROJECTS_V is an Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 reporting view owned by the APPS schema. It presents a trimmed, query-optimized projection of Oracle Projects master data intended for consumption by Oracle Payables web (expense) functionality and similar integration points, where a project must be resolved together with the name of its carrying-out (project) organization. The view exposes core project attributes and, critically, derives the human-readable organization name by joining the project's carrying-out organization identifier to the HR organization units view.

The object is documented in ETRM with a straightforward definition: a SELECT from PA_PROJECTS_EXPEND_V aliased P, joined to HR_ORGANIZATION_UNITS aliased O on P.CARRYING_OUT_ORGANIZATION_ID = O.ORGANIZATION_ID. Its role is to provide a stable, security-aware read surface for applications and custom reports that need project number, name, dates, type, and the associated organization name without navigating the underlying Projects schema directly.

Underlying Base Objects

The documented referenced base objects are:

  • PA_PROJECTS_EXPEND_V (VIEW) — the primary source of project rows; supplies project identifiers, descriptive fields, dates, project type, carrying-out organization ID, and project type class code.
  • HR_ORGANIZATION_UNITS (VIEW) — resolves the carrying-out organization ID to its name (O.NAME).
  • HR_SECURITY (PACKAGE), HR_GENERAL (PACKAGE), PA_PROJECT_UTILS (PACKAGE), PA_CROSS_BUSINESS_GRP (PACKAGE), and FND_PROFILE (PACKAGE) — supporting PL/SQL objects referenced transitively through the underlying views to enforce organization security, business-group (operating unit) scoping, and profile-option-driven filtering.

The view therefore inherits the security and business-group behavior of PA_PROJECTS_EXPEND_V and HR_ORGANIZATION_UNITS rather than defining its own filtering. Access is effectively governed by the HR security model and the MO (Operating Unit) profile context active in the session.

Key Columns

  • PROJECT_ID — surrogate primary key of the project; the standard foreign key used throughout Projects and Payables.
  • PROJECT_NUMBER — the user-visible project number, typically the value entered or searched in Payables and Projects forms.
  • PROJECT_NAME — descriptive title of the project.
  • PROJECT_DESCRIPTION — free-form description text.
  • START_DATE / COMPLETION_DATE — project scheduling boundaries.
  • PROJECT_TYPE — classification of the project (for example, billable or capital).
  • PROJECT_ORGANIZATION_ID — alias for CARRYING_OUT_ORGANIZATION_ID, the organization responsible for carrying out the project.
  • PROJECT_ORGANIZATION_NAME — the resolved O.NAME value from HR_ORGANIZATION_UNITS; this is the column of primary interest when users search on "project_organization_name."
  • PROJECT_TYPE_CLASS_CODE — the class code associated with the project type, used for grouping and filtering.

Common Use Cases and Queries

The view is typically used in expense or invoice reporting where a project must be displayed alongside its owning organization, and in ad-hoc queries that filter or group by organization name. A representative query returning projects for a specific organization name is:

SELECT PROJECT_ID,
       PROJECT_NUMBER,
       PROJECT_NAME,
       PROJECT_ORGANIZATION_NAME,
       PROJECT_TYPE_CLASS_CODE
  FROM APPS.AP_WEB_PA_PROJECTS_V
 WHERE PROJECT_ORGANIZATION_NAME = :p_org_name
 ORDER BY PROJECT_NUMBER;

Because HR security is inherited, the set of rows returned depends on the HR security profile of the connected user and the operating unit context; reports intended to run across business groups should be reviewed against PA_CROSS_BUSINESS_GRP behavior. For validation-style lookups, PROJECT_ID and PROJECT_NUMBER are the appropriate keys to join back to AP or PA transaction tables.