Results for “budget_type_code2”

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

Overview

PA_RPT_CUST_SUMMARY is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2, delivered as part of the Projects (PA) product family. Its documented purpose is to display summary project-level actuals and budgets organized by customer. Rather than presenting transactional detail, the view aggregates cost, revenue, and labor-hour figures across defined accumulation periods, giving project managers, billing analysts, and financial reporters a consolidated picture of project performance segmented by the customer associated with each project.

The view is read-only in nature and is intended for reporting and integration consumption. Because it pre-joins and pre-aggregates transactional data from Projects and Grants accounting structures, it removes the burden of reconstructing period-to-date (PTD), year-to-date (YTD), and inception-to-date (ITD) rollups at query time. Its presence in the APPS schema means it is accessible to standard EBS responsibility-based reporting, custom concurrent programs, Oracle Business Intelligence Publisher (BI Publisher) data templates, and external extract processes.

Underlying Base Objects

The ETRM 12.2.2 metadata documents two referenced base objects for this view: PA_RPT_CUST_SUMMARY_BASE_V (a view) and PA_RPT_UTILS (a package). The dependency on PA_RPT_CUST_SUMMARY_BASE_V indicates that the summary view is a layered construct — the base view supplies the underlying columnar data and joins, while PA_RPT_CUST_SUMMARY applies column selection and aggregation via SUM functions. The dependency on PA_RPT_UTILS signals that some part of the definition, most likely parameter or lookup resolution logic, is driven by a PL/SQL package rather than being fully static SQL. This layered design is common in Projects reporting views, allowing EBS to centralize reusable logic and simplify maintenance across releases.

Key Columns

The view exposes identifying columns including PROJECT_ID, PROJECT_ACCUM_ID, ACCUM_PERIOD, and CUSTOMER_ID. These keys define the grain of each aggregated row — a project's accumulated amounts for a given period, reported against a specific customer.

• Cost actuals: RAW_COST_ITD/YTD/PTD and their billable counterparts, plus BURDENED_COST_ITD/YTD/PTD and BILLABLE_BURDENED_COST_ITD/YTD/PTD, covering both raw and burdened cost perspectives.
• Revenue: REVENUE_ITD, REVENUE_YTD, and REVENUE_PTD.
• Labor: LABOR_HOURS_ITD/YTD/PTD and BILLABLE_LABOR_HOURS_ITD/YTD/PTD.
• Budget columns: The view supports two budget slots, each carrying BUDGET_TYPE_CODE1/BUDGET_TYPE_CODE2 and BUDGET_TYPE1/BUDGET_TYPE2 paired with BASE and ORIG raw cost, burdened cost, and labor-hour measures (ITD, YTD, PTD, and TOT). This is the area most relevant to the user search term budget_type_code1, which identifies the budget type assigned to the first budget slot.

Common Use Cases and Queries

Typical usage includes project cost-versus-budget reporting by customer, revenue and margin analysis per accumulation period, and extracts feeding BI Publisher or data warehouse loads. Because BUDGET_TYPE_CODE1 distinguishes the budget version (for example, approved versus original), analysts commonly filter on it to isolate a specific baseline.

A representative query:

• SELECT project_id, customer_id, accum_period, budget_type_code1, SUM(base_raw_cost_itd1), SUM(orig_raw_cost_itd1) FROM apps.pa_rpt_cust_summary WHERE budget_type_code1 = :budget_type GROUP BY project_id, customer_id, accum_period, budget_type_code1;

This pattern lets report authors compare base and original budgeted raw cost by project and customer for the budget version identified through budget_type_code1.