Results for “billable_labor_hours_itd”

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

Overview

PA_RPT_CUST_ACT_SUMMARY is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Projects (PA) product family. Its documented purpose is to display project-level actuals distributed by customer. Rather than storing data itself, the view consolidates accumulated project actual amounts held at the project accumulation level and allocates each measure across the customers associated with the project, based on the customer bill split percentage defined on PA_PROJECT_CUSTOMERS.

The view is intended primarily for operational and management reporting rather than for transaction processing. It presents period-based and cumulative cost and labor figures — raw cost, billable raw cost, burdened cost, billable burdened cost, and labor hours — at the intersection of project accumulation header, accumulation period, and customer. This makes it a convenient source for reports that must show how total project actuals break down across multiple funding or billing customers, a common requirement in government contracting, capital projects, and shared-services engagements where a single project serves more than one customer. In EBS 12.1.1 and 12.2.2 the object remains a database view in the APPS schema with a VALID status, and no online form or concurrent program is documented as its exclusive consumer; it is exposed for ad hoc query, custom reporting, and integration extracts.

Underlying Base Objects

The ETRM metadata for 12.2.2 lists the following referenced base objects, each accessed through an APPS synonym: PA_PROJECTS, PA_PROJECT_ACCUM_ACTUALS, PA_PROJECT_ACCUM_HEADERS, PA_PROJECT_CUSTOMERS, and PA_PROJECT_TYPES. In the view text, PA_PROJECT_ACCUM_HEADERS supplies the project accumulation identifier and accumulation period (PAH.PROJECT_ACCUM_ID, PAH.ACCUM_PERIOD), PA_PROJECT_ACCUM_ACTUALS supplies the underlying cost and hour buckets (for example PAA.RAW_COST_ITD, PAA.BURDENED_COST_PTD, PAA.LABOR_HOURS_YTD), and PA_PROJECT_CUSTOMERS supplies customer identity and the bill split percentage (PC.CUSTOMER_ID, PC.CUSTOMER_BILL_SPLIT). PA_PROJECTS and PA_PROJECT_TYPES provide the project and project-type context used to join and qualify accumulation rows. The accumulation tables are the same structures that drive project performance reporting in Oracle Projects, so the view inherits their period-by-period and inception-to-date semantics.

Key Columns

• PROJECT_ACCUM_ID / ACCUM_PERIOD — the accumulation header identifier and the GL or PA period for which actuals are summarized. These form the primary grouping keys.
• CUSTOMER_ID / CUSTOMER_BILL_SPLIT — the customer receiving an allocated share of the project actuals and that customer's bill split percentage from PA_PROJECT_CUSTOMERS.
• Raw cost measures — RAW_COST_ITD, RAW_COST_YTD, RAW_COST_PP, and RAW_COST_PTD, each scaled by the bill split percentage.
• Billable raw cost measures — BILLABLE_RAW_COST_ITD, YTD, PP, and PTD, scaled identically.
• Burdened cost measures — BURDENED_COST_ITD, YTD, PP, and PTD.
• Billable burdened cost measures — BILLABLE_BURDENED_COST_ITD, YTD, PP, and PTD.
• Labor hours measures — LABOR_HOURS_ITD, YTD, and PP.

The suffix conventions are significant: ITD denotes inception-to-date, YTD year-to-date, PTD period-to-date, and PP prior period. Each amount column is wrapped in a DECODE that returns zero when CUSTOMER_BILL_SPLIT is zero, preventing division-by-zero behavior and ensuring that customers with no bill split contribute no allocated amounts. When bill split is non-zero, the underlying actual is multiplied by the split and divided by 100.

Common Use Cases and Queries

Typical uses include reporting project cost by customer for revenue recognition support, preparing customer-facing cost statements, reconciling billable versus burdened cost at the customer level, and feeding downstream extracts. A representative query filters to a single project and accumulation period:

• SELECT customer_id, customer_bill_split, raw_cost_ptd, billable_burdened_cost_ptd, labor_hours_ptd FROM apps.pa_rpt_cust_act_summary WHERE project_accum_id = :p_accum_id;
• SELECT customer_id, SUM(billable_burdened_cost_itd) FROM apps.pa_rpt_cust_act_summary WHERE accum_period BETWEEN :p_from AND :p_to GROUP BY customer_id;

Because the view depends on accumulation data, results reflect the most recent PRC: Update Project Summary Amounts process run (or its equivalents in 12.2). Reports should therefore be scheduled after accumulation is refreshed. Access is read-only, and organizations commonly wrap the view in custom views or BI Publisher data models rather than granting direct privileges to end users.