Search Results pa_online_projects_v




Overview
Explore in AI Chat

Overview

PA_ONLINE_PROJECTS_V is a customizable view owned by the APPS schema within the Oracle E-Business Suite Projects (PA) module. It is validated and available in both EBS 12.1.1 and 12.2.2. Its purpose is to expose a curated, security-filtered list of projects for consumption by the Self Service Time application, allowing employees to select chargeable projects when entering time and expense information. Because the view is explicitly described as customizable, Oracle permits implementers to modify its definition without invalidating standard functionality, which makes it a frequent extension point in Projects and Time implementations. Note that the actual runtime behavior of the view depends on referenced base objects such as FND_PROFILE, HR_GENERAL, HR_SECURITY, and PA_CROSS_BUSINESS_GRP, which supply profile option values, HR organizational context, and cross-business-group security rules respectively.

Underlying Base Objects

The view is defined primarily over PA_PROJECTS_EXPEND_V, itself a view in the Projects schema that resolves expenditure-related project attributes. PA_ONLINE_PROJECTS_V selects a DISTINCT projection of that source, and additionally resolves the carrying-out organization name via a correlated subquery against HR_ORGANIZATION_UNITS. The documented referenced base objects also include the packages FND_PROFILE, HR_GENERAL, HR_SECURITY, PA_CROSS_BUSINESS_GRP, and PA_PROJECT_UTILS. These are not directly present in the view text excerpt but are invoked indirectly through PA_PROJECTS_EXPEND_V, which uses them to enforce security and derive profile-driven behavior. HR_SECURITY, for example, applies organization-based security so that a user only sees projects belonging to organizations they are authorized to access. FND_PROFILE supplies values for relevant profile options, PA_CROSS_BUSINESS_GRP enforces cross-business-group filtering, and PA_PROJECT_UTILS provides project-related utility logic.

Key Columns

  • PROJECT_ID — Unique numeric identifier for the project; used as the primary key in downstream joins and pickers.
  • PROJECT_NUMBER — The user-facing project number, typically displayed first in Self Service Time project lists.
  • PROJECT_NAME — Descriptive name of the project.
  • PROJECT_TYPE — Classification of the project (for example, billable or internal), useful for grouping and defaulting behavior.
  • START_DATE and COMPLETION_DATE — Effective date range of the project; used to filter selectable projects to those active during the entered time period.
  • CARRYING_OUT_ORGANIZATION_ID — Identifier of the organization responsible for carrying out the project.
  • CARRYING_OUT_ORGANIZATION_NAME — Resolved name of that organization, obtained via the correlated subquery against HR_ORGANIZATION_UNITS.

Common Use Cases and Queries

Typical uses include driving project LOVs in Self Service Time, validating chargeable project selections, and building custom time-entry validations or reports. Because the view is expected to be customized, many implementations add attributes such as project manager, customer, or task references. A basic query to retrieve visible projects is:

SELECT project_number, project_name, project_id, project_type, start_date, completion_date, carrying_out_organization_name FROM apps.pa_online_projects_v WHERE sysdate BETWEEN start_date AND NVL(completion_date, sysdate);

A query filtering by organization is:

SELECT project_number, project_name FROM apps.pa_online_projects_v WHERE carrying_out_organization_id = :org_id;

Because HR_SECURITY and profile-driven logic are applied within the underlying views and packages, results are automatically restricted to projects the querying user is authorized to see, so the view is generally safe to expose in custom self-service pages without additional security predicates.