Results for “base_labor_hours_tot”

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

Overview

The view APPS.PA_RPT_CUST_BGT_SUMMARY is a reporting object within the Oracle E-Business Suite Projects (PA) module. Its stated purpose, per the ETRM documentation, is to display project-level budgets broken down by customer. It is a reporting view only; it stores no data of its own and exists to simplify access to budget and cost accumulations distributed across customers.

In Oracle EBS 12.1.1 and 12.2.2, Projects maintains budget, cost, and revenue accumulations at the project level in the accumulations tables. When a project is associated with multiple customers and split billing arrangements, reporting budget figures per customer requires apportioning those accumulated amounts according to each customer's bill split percentage. The view performs exactly this apportionment, applying each customer's CUSTOMER_BILL_SPLIT percentage to the corresponding base and original cost, burdened cost, and revenue balances. This makes the view useful for customer-level budget versus cost analysis, revenue reporting, and for feeding downstream reporting tools such as Oracle Business Intelligence or custom concurrent programs, without requiring the report developer to reimplement the split-billing logic.

Underlying Base Objects

The documented view metadata identifies the following referenced base objects (all exposed as synonyms in the APPS schema):

• PA_PROJECT_ACCUM_BUDGETS — holds the accumulated budget amounts (raw and burdened cost, revenue) at the defined period granularity.
• PA_PROJECT_ACCUM_HEADERS — provides the accumulation header context, including the project accumulation identifier, period, and budget type.
• PA_PROJECT_CUSTOMERS — supplies the customer, bill split percentage, and bill split definition used to apportion the accumulated amounts.
• PA_PROJECTS_ALL — the project master, used to anchor the projection to the project.
• PA_PROJECT_TYPES — the project type definition associated with the project.
• PA_BUDGET_TYPES — the budget type definition, used to filter or describe the budget being reported.

The view joins the accumulation header and budget tables to the project customers table and multiplies each accumulated measure by the customer bill split percentage divided by 100, so that the sum across customers reconciles to the project-level accumulation.

Key Columns

• PROJECT_ACCUM_ID — the project accumulation identifier linking the row to the accumulation header and project.
• BUDGET_TYPE_CODE — identifies the budget type (for example, approved cost or revenue budget) to which the amounts belong.
• ACCUM_PERIOD — the period for which the accumulated amounts are reported.
• CUSTOMER_ID — the customer associated with the split portion of the budget.
• CUSTOMER_BILL_SPLIT — the percentage of the project allocated to that customer; drives the DECODE apportionment applied to every amount.
• Raw cost columns BASE_RAW_COST_* and ORIG_RAW_COST_* — inception-to-date (ITD), year-to-date (YTD), prior period (PP), and period-to-date (PTD) raw cost, apportioned to the customer.
• Burdened cost columns BASE_BURDENED_COST_* and ORIG_BURDENED_COST_* — the same four views for burdened cost.
• Revenue columns BASE_REVENUE_* — ITD, YTD, PP, and PTD revenue, apportioned where a split percentage exists.

Where CUSTOMER_BILL_SPLIT is zero, the view returns zero for the affected amount, avoiding division-by-zero or unallocated customer rows contributing to totals.

Common Use Cases and Queries

Typical usage includes customer-level profitability and budget consumption reporting, reconciliation of project budgets to customer allocations, and extraction feeds for custom reports or dashboards.

SELECT p.project_number,
       p.project_name,
       c.customer_id,
       v.budget_type_code,
       v.accum_period,
       v.customer_bill_split,
       SUM(v.base_burdened_cost_ytd) AS budget_burdened_ytd
  FROM apps.pa_rpt_cust_bgt_summary v,
       apps.pa_projects_all p,
       apps.pa_project_customers c
 WHERE v.project_accum_id = p.project_id
   AND v.customer_id = c.customer_id
   AND v.budget_type_code = 'COST'
 GROUP BY p.project_number, p.project_name, c.customer_id,
          v.budget_type_code, v.accum_period, v.customer_bill_split;

For reconciliation, compare the sum of base_burdened_cost_ptd across customers against the unapportioned project accumulation for the same accum_period; the totals should agree. Because the view applies split-billing logic, users must ensure that customer split percentages are fully maintained in PA_PROJECT_CUSTOMERS; unallocated percentage remains unreported. As with all APPS reporting views, queries should be run against the APPS schema synonyms and privileges granted appropriately, and performance is best served by filtering on PROJECT_ACCUM_ID or ACCUM_PERIOD.