Search Results pa_projects_basic_v

Overview

PA_PROJECTS_BASIC_V is a predefined Oracle E-Business Suite view owned by the APPS schema and validated in both release 12.1.1 and 12.2.2. It belongs to the Projects (PA) product family and is classified in ETRM as "10SC Only - Retrofitted," indicating that it originated in an earlier Oracle Projects release and was carried forward for backward compatibility rather than introduced as new functionality. Its purpose is to present a lightweight, security-filtered projection of project header information suitable for list-of-values screens, concurrent reporting, and external integrations that do not require the full column set of PA_PROJECTS_ALL. The view deliberately omits heavy descriptive and setup attributes, exposing only identification, classification, currency, and funding-related flags. Access is mediated through PA_SECURITY.ALLOW_QUERY, so rows are returned only when the invoking user holds the appropriate project security profile permissions.

Underlying Base Objects

The view joins three primary sources: PA_PROJECTS_ALL (aliased P, the project header table and the source of most columns), PA_PROJECT_TYPES (aliased PT, supplying the project type class code and the CC provider flag), and PA_OPERATING_UNITS_V (aliased POU, supplying the operating unit name). The join predicate matches project type and operating unit organization across P, PT, and POU, and explicitly excludes project types equal to AWARD_PROJECT. The security predicate embeds a scalar subquery against SYS.DUAL that calls PA_SECURITY.ALLOW_QUERY for each project identifier. ETRM also documents indirect dependencies on HR_GENERAL, HR_ORGANIZATION_UNITS, HR_SECURITY, and MO_GLOBAL, which are invoked transitively through the operating unit view and the PA security package rather than joined directly.

Key Columns

• ORG_ID — Operating unit identifier used for multi-org partitioning; joins to HR_OPERATING_UNITS.
• PROJECT_ID — Primary key of the project, used to link to tasks, budgets, expenditures, and awards.
• PROJECT_NUMBER and PROJECT_NAME — The user-visible project number (SEGMENT1) and short name; the view text also aliases SEGMENT1 to PROJECT_NUMBER_SORT_ORDER.
• LONG_NAME — The extended project description.
• OPERATING_UNIT — Name of the owning operating unit, drawn from PA_OPERATING_UNITS_V.
• PROJECT_TYPE_CLASS_CODE — Classifies the project as, for example, indirect, contract, or capital.
• PROJECT_STATUS_CODE — Current lifecycle status such as approved, active, or closed.
• TEMPLATE_FLAG — Defaulted to N via NVL when null; identifies project templates.
• PM_PROJECT_REFERENCE — External reference used for Project Management integration.
• PROJECT_CURRENCY_CODE — Functional currency of the project.
• CC_PRVDR_FLAG, BASELINE_FUNDING_FLAG, REVALUATE_FUNDING_FLAG — Funding and cross-charge configuration indicators inherited from the project type and project header.

Common Use Cases and Queries

The view is typically used where a secure, minimal project list is required. A standard lookup restricted to one operating unit might read:

SELECT project_id, project_number, project_name, project_status_code FROM apps.pa_projects_basic_v WHERE org_id = :p_org_id AND project_status_code = 'APPROVED' ORDER BY project_number;

For funding analysis, the flags can be filtered directly:

SELECT project_number, project_name, baseline_funding_flag, revaluate_funding_flag FROM apps.pa_projects_basic_v WHERE cc_prvdr_flag = 'Y';

Because the view already applies PA_SECURITY.ALLOW_QUERY, developers should not add redundant security predicates; instead they should confirm that the reporting user has a valid project security profile, since a restrictive profile will silently reduce the row set. Joins back to PA_PROJECTS_ALL on PROJECT_ID are required to obtain attributes not exposed here, such as start and end dates, manager, or customer. The view is not a substitute for the Projects reporting schemas (for example, the PA_*_SUMMARY tables), and its "10SC Only - Retrofitted" status means it should be treated as a compatibility object rather than a strategic integration point.