Search Results pa_status_proj_v




Overview
Explore in AI Chat

Overview

PA_STATUS_PROJ_V is an Oracle EBS Projects (PA) reporting view owned by the APPS schema. Its documented description is "10SC Only," which indicates it was originally developed to support the Oracle Projects Status Reporting (10SC) functionality set. In the ETRM metadata for release 12.2.2 the object is listed as a VALID VIEW, meaning it remains deployed in the current schema even though its origin predates the multiorg and subledger architecture refinements of R12.

The view consolidates project identifiers with a wide set of accumulated actual, commitment, and baseline budget metrics, all expressed across four reporting time windows: inception-to-date (ITD), year-to-date (YTD), prior period (PP), and period-to-date (PTD). Its role is to present a single denormalized row per project, budget-type combination, so that status reports, project performance inquiries, and third-party integrations can retrieve summarized cost, revenue, and labor-hour figures without joining the underlying accumulation tables directly.

Underlying Base Objects

The ETRM documentation records the following referenced base objects for PA_STATUS_PROJ_V:

  • PA_PROJECTS (SYNONYM) — supplies PROJECT_ID, SEGMENT1, and NAME, the project identification attributes.
  • PA_PROJECT_ACCUM_ACTUALS (SYNONYM) — alias PAA; the source of accumulated actual raw cost, billable raw cost, burdened cost, billable burdened cost, labor hours, billable labor hours, and revenue figures.
  • PA_PROJECT_ACCUM_COMMITMENTS (SYNONYM) — alias PAC; provides committed cost (CMT) raw and burdened amounts.
  • PA_PROJECT_ACCUM_HEADERS (SYNONYM) — the accumulation control/header table underpinning the accumulation rows.
  • PA_STATUS (PACKAGE) — the status processing package associated with the 10SC reporting logic.
  • PA_STATUS_PROJ_BGT_COST_V (VIEW) — alias SPBC; supplies baseline raw cost and baseline burdened cost amounts and the cost budget type code.
  • PA_STATUS_PROJ_BGT_REV_V (VIEW) — alias SPBR; supplies the revenue budget type code.

Each accumulation and commitment amount is wrapped in NVL(...,0) so that projects lacking a particular measure still return a numeric zero rather than a null, simplifying downstream arithmetic.

Key Columns

The SELECT list exposes the following groups of columns:

  • Project keys: PROJECT_ID, SEGMENT1 (project number), and NAME.
  • Budget type codes: BUDGET_TYPE_CODE from both SPBC and SPBR, distinguishing cost and revenue budget versions.
  • Actual cost and revenue (PAA): RAW_COST_*, BILLABLE_RAW_COST_*, BURDENED_COST_*, BILLABLE_BURDENED_COST_*, LABOR_HOURS_*, BILLABLE_LABOR_HOURS_*, and REVENUE_*, each in ITD, YTD, PP, and PTD variants.
  • Commitments (PAC): CMT_RAW_COST_* and CMT_BURDENED_COST_* for the same four time windows.
  • Baseline budget (SPBC): BASELINE_RAW_COST_* and BASELINE_BURDENED_COST_* across ITD, YTD, PP, and PTD.

Common Use Cases and Queries

Typical usage includes project status reporting, cost-versus-baseline variance analysis, and data extraction for external reporting tools. A representative query retrieving consolidated cost and commitment data for a project is:

  • SELECT project_id, segment1, name, raw_cost_itd, burdened_cost_itd, cmt_raw_cost_itd, baseline_raw_cost_itd FROM apps.pa_status_proj_v WHERE segment1 = :project_number;
  • SELECT segment1, name, revenue_itd, raw_cost_itd, (revenue_itd - raw_cost_itd) margin FROM apps.pa_status_proj_v ORDER BY segment1;
  • SELECT project_id, labor_hours_ptd, billable_labor_hours_ptd, raw_cost_ptd FROM apps.pa_status_proj_v WHERE project_id = :project_id;

Because the view is documented as "10SC Only" and depends on legacy accumulation structures, implementers should confirm its continued suitability against current Projects reporting views before relying on it in new customizations.