Search Results pa_status_proj_generic_v




Overview
Explore in AI Chat

Overview

PA_STATUS_PROJ_GENERIC_V is an APPS-owned view in the Oracle E-Business Suite Projects (PA) module that consolidates project status information across budget, revenue, cost, actuals, and commitments. The view is documented as a retrofit into CASE, indicating it exists to support project status reporting where a single generic structure is required rather than the more specialized underlying cost and revenue status views. In EBS 12.1.1 and 12.2.2, the view is VALID and is exposed as APPS.PA_STATUS_PROJ_GENERIC_V.

The view presents a project-level status snapshot, combining baseline and original budget values with inception-to-date (ITD), period-to-date (PTD), and total actual values. It also enforces project security by invoking the PA_SECURITY package, specifically PA_SECURITY.VIEW_LABOR_COSTS and PA_SECURITY.ALLOW_QUERY, so that users only see cost and project data they are authorized to access. This makes the view suitable for reporting layers, forms personalizations, and integration extracts where both financial and physical progress measures are needed at project granularity.

Underlying Base Objects

The documented view metadata lists the following referenced objects: PA_PROJECTS, PA_PROJECT_ACCUM_ACTUALS, PA_PROJECT_ACCUM_COMMITMENTS, PA_PROJECT_ACCUM_HEADERS, and DUAL as base tables/synonyms, plus the packages PA_SECURITY and PA_STATUS, and the views PA_STATUS_PROJ_BGT_COST_V and PA_STATUS_PROJ_BGT_REV_V. The view is therefore defined directly over project master data (PA_PROJECTS) joined to accumulation headers and actual/commitment accumulators.

Baseline and original budget amounts and quantities are sourced from PA_STATUS_PROJ_BGT_COST_V and PA_STATUS_PROJ_BGT_REV_V, while the current actuals come from PA_PROJECT_ACCUM_ACTUALS and commitment commitments from PA_PROJECT_ACCUM_COMMITMENTS. The join is driven by PROJECT_ID between PA_PROJECTS and PA_PROJECT_ACCUM_HEADERS, with project security applied through PA_SECURITY.ALLOW_QUERY. The use of SYNONYMs indicates the view resolves to the APPS schema objects at runtime.

Key Columns

The view exposes several important columns, including BUDGET_TYPE_CODE sourced from both the cost and revenue budget views. In the context of a user searching for cost_budget_type_code, this column identifies the cost budget type associated with the project's baseline figures, and it is one of the principal filtering attributes when distinguishing between approved cost budgets, original budgets, and other budget types maintained in PA.

Common Use Cases and Queries

Typical usage includes project status dashboards, budget-versus-actual reports, revenue and margin analysis, and extracts feeding external reporting or middleware. Because the view filters through PA_SECURITY, it is also appropriate for secured self-service reporting. The following sample selects cost budget type code and key cost measures for a single project:

SELECT project_id, segment1, name, budget_type_code, baseline_burdened_cost_itd, burdened_cost_itd, cmt_burdened_cost_ptd FROM apps.pa_status_proj_generic_v WHERE segment1 = :project_number;

To identify projects whose cost budget type falls within a specific classification and which are over budget:

SELECT project_id, name, budget_type_code, baseline_burdened_cost_tot, burdened_cost_itd FROM apps.pa_status_proj_generic_v WHERE budget_type_code = :cost_budget_type_code AND baseline_burdened_cost_tot < burdened_cost_itd;

For margin and revenue analysis, users select BASELINE_REVENUE_TOT minus BASELINE_BURDENED_COST_TOT alongside REVENUE_ITD minus BURDENED_COST_ITD. Note that the view joins both cost and revenue budget views, so multiple rows per project can occur depending on budget types; queries should aggregate or filter by BUDGET_TYPE_CODE where a single budget basis is required.