Search Results primary_customer_name




Overview
Explore in AI Chat

Overview

APPS.PA_REP_PROJ_SP_PA_V is a reporting view in the Oracle E-Business Suite Projects (PA) module, owned by the APPS schema and registered under FND Design Data as PA.PA_REP_PROJ_SP_PA_V. Its status is VALID. The view consolidates project-level attributes — classification, status, period distribution, financial values, and customer identification — into a single denormalized row per project/organization combination, which makes it suitable for reporting and downstream integration scenarios where project master and period data must be joined without navigating the full PA schema.

The view is explicitly flagged as Oracle Internal Use Only. Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. Developers who query it do so at their own risk; the supported alternative is to build custom extracts on the documented base tables, or to rely on the same base objects the view uses.

Underlying Base Objects

The documented dependency list shows that PA_REP_PROJ_SP_PA_V is defined over the following objects:

PA_PROJECTS_ALL supplies the core project record (project id, number, name, org id, type). PA_PERIODS_V supplies the PA period name, period start date, and the fiscal year and quarter derivations. PA_PROJECT_CLASSES provides the class category and class code pairs, while PA_PROBABILITY_MEMBERS contributes the win probability. PA_PROJECT_PLAYERS and PA_PROJECT_STATUSES resolve the project player role, player person id, and the status description. PA_IMPLEMENTATIONS is the multi-org anchor, and PA_PROJECTS_MAINT_UTILS is the maintenance utility package referenced for internal derivation logic. Note that because PA_PROJECTS_MAINT_UTILS is a package and not a table, the view may not be fully resolvable in a read-only reporting extract that lacks execute grants on that package.

Key Columns

The view exposes 21 columns. The most frequently referenced are:

PRIMARY_CUSTOMER_NAME is the column most likely to be the search target for users looking to identify projects by customer. Because it is a long character field, filtering with equality comparisons can be inefficient; an UPPER() or LIKE predicate on a substring is generally preferable.

Common Use Cases and Queries

Typical scenarios include customer-centric project listings, pipeline and probability reporting, and period-based project value summaries. A simple customer lookup is shown below:

SELECT project_number, project_name, status, total_value, net_value
FROM apps.pa_rep_proj_sp_pa_v
WHERE UPPER(primary_customer_name) LIKE UPPER('%ACME%');

A period-based summary grouping by quarter and PA period provides a pipeline view:

SELECT year, quarter, pa_period, COUNT(*), SUM(total_value)
FROM apps.pa_rep_proj_sp_pa_v
WHERE org_id = :p_org_id
GROUP BY year, quarter, pa_period;

Because the view is Oracle Internal Use Only and depends on a maintenance package, production use should be restricted to standard Oracle Applications programs. Custom reports requiring primary customer information are better aligned to PA_PROJECTS_ALL joined to PA_CUSTOMERS or the relevant customer table for the installed release.