Results for “pa_rpt_cust_summary_base_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_RPT_CUST_SUMMARY_BASE_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Projects (PA) module. It serves as a foundational data source for the customer summary reporting layer, consolidating project cost, revenue, labor hour, and budget information at the customer level. The view is defined as a UNION ALL of multiple SELECT statements, each aligned to a distinct budget type, and is intended to feed higher-level report queries and concurrent programs rather than to be maintained directly by end users.

The view plays a supporting role in the PA reporting architecture, sitting between the accumulation views (PA_RPT_CUST_ACT_SUMMARY and PA_RPT_CUST_BGT_SUMMARY) and the report-specific presentation logic. Because it exposes both actual and budgeted figures, it allows report developers to present cost, revenue, and budget comparisons for a given project and customer without writing complex join logic.

Underlying Base Objects

The documented base objects referenced by PA_RPT_CUST_SUMMARY_BASE_V are:

• PA_RPT_CUST_ACT_SUMMARY (VIEW) – supplies the actual cost, revenue, and labor hour columns.
• PA_RPT_CUST_BGT_SUMMARY (VIEW) – supplies the budget columns.
• PA_BUDGET_TYPES (SYNONYM) – referenced four times (aliases B1, B2, B3, B4) to resolve budget type codes and descriptions.
• PA_RPT_UTILS (PACKAGE) – provides the PL/SQL function GET_RPT_BUDGET_TYPE, which returns the budget type code for a given category and position.

The view text shows that budget type codes are resolved dynamically through PA_RPT_UTILS.GET_RPT_BUDGET_TYPE, called with parameters such as ('C', 1), ('C', 2), ('R', 1), and ('R', 2). This design allows the view to adapt to the reporting budget type configuration without hard-coded values.

Key Columns

The view exposes identifying keys together with a large set of accumulated amount columns. Principal columns include:

• PROJECT_ID, PROJECT_ACCUM_ID, ACCUM_PERIOD, CUSTOMER_ID – the dimensional keys for each row.
• RAW_COST_ITD / YTD / PTD and their BILLABLE_ counterparts – raw cost accumulations.
• BURDENED_COST_ITD / YTD / PTD and BILLABLE_BURDENED_COST_* – burdened cost accumulations.
• REVENUE_ITD / YTD / PTD – revenue accumulations.
• LABOR_HOURS_ITD / YTD / PTD and BILLABLE_LABOR_HOURS_* – labor hour accumulations.
• BUDGET_TYPE_CODE and BUDGET_TYPE – repeated for each budget position (B1 through B4), linking rows to the reporting budget types.

The suffix conventions follow PA reporting standards: ITD (inception to date), YTD (year to date), and PTD (period to date).

Common Use Cases and Queries

Because the view is keyed on PROJECT_ID, CUSTOMER_ID, and ACCUM_PERIOD, it is commonly used for customer-level cost and revenue summaries, budget-versus-actual comparisons, and period-based reporting extracts. A typical query filtering on the budget type code is:

• SELECT project_id, customer_id, accum_period, budget_type_code, raw_cost_itd, revenue_itd
• FROM apps.pa_rpt_cust_summary_base_v
• WHERE budget_type_code = :p_budget_type_code
• AND accum_period BETWEEN :p_from_period AND :p_to_period;

When the user searches for budget_type_code, the relevant point is that this view derives the code through PA_RPT_UTILS.GET_RPT_BUDGET_TYPE rather than from a static column, so filtering requires the same reporting budget type configuration used by the underlying report. Understanding this dependency is essential when troubleshooting missing or unexpected budget rows.