Results for “tot_quantity”

50+ results




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

Overview

PA_ALLOC_TXN_ACCUM_RBS_V is an APPS-owned database view within the Oracle E-Business Suite Projects (PA) product family. It exposes accumulated project transaction data mapped to Resource Breakdown Structure (RBS) elements, providing a pre-joined, aggregated reporting layer over the raw PJI (Project Intelligence) transaction accumulation tables. The view is delivered in a VALID state in both EBS 12.1.1 and 12.2.2 and is referenced primarily by Project Intelligence reporting and any custom integration requiring revenue, cost, and quantity rollups by RBS element.

The view presents a unified aggregation in which cost, revenue, burdened cost, billable amounts, and labor hours are summed and grouped by project, project element, PA period, GL period, RBS version, and RBS element. Because so many downstream BI and cost analysis queries target RBS-level accumulations, the column RBS_ELEMENT_ID — returned via NVL(RBS.ELEMENT_ID, -1) — is one of the most frequently searched identifiers associated with this view.

Underlying Base Objects

The documented base objects referenced by this view are:

The joins tie each transaction to its header, expenditure type, project RBS assignment, RBS element map, organization extraction info, and calendar period. The inner query filters RECVR_PERIOD_TYPE = 'PA' and INVENTORY_ITEM_ID = -1, and the outer query aggregates the union of those rows, tagging the result with the literal RECORD_SOURCE = 'PJI'.

Key Columns

  • PROJECT_ID / PROJECT_ELEMENT_ID — project and task (element) owning the accumulation.
  • RBS_VERSION_ID — the RBS structure version, defaulted to -1 when unmapped.
  • RBS_ELEMENT_ID — the RBS resource element; returned as NVL(...,-1) so unmapped rows never surface NULL.
  • PA_PERIOD / GL_PERIOD — accounting period names; GL_PERIOD is cast as a null string in the source.
  • TOT_REVENUE, TOT_RAW_COST, TOT_BURDENED_COST — aggregated revenue and cost measures.
  • TOT_QUANTITY / TOT_LABOR_HOURS — aggregated labor hours accumulated from QUANTITY.
  • TOT_BILLABLE_* — parallel billable cost, quantity, and hour totals.
  • I_* columns — reserved "invoice" style counterparts, currently summed to zero.

Common Use Cases and Queries

Typical use cases include RBS-level cost and revenue reporting, burdened cost rollups, labor hour analysis, and reconciliation with Project Intelligence dashboards. Because the view aggregates internally, consumers can filter directly on RBS element without re-aggregating base facts.

Example: retrieve cost and hours for a project by RBS element.

  • SELECT project_id, rbs_version_id, rbs_element_id, pa_period, SUM(tot_burdened_cost) cost, SUM(tot_labor_hours) hrs FROM pa_alloc_txn_accum_rbs_v WHERE project_id = :p_project_id AND rbs_element_id <> -1 GROUP BY project_id, rbs_version_id, rbs_element_id, pa_period;

A second pattern isolates the RBS mapping dimension for a given version.

  • SELECT rbs_element_id, SUM(tot_revenue), SUM(tot_billable_burdened_cost) FROM pa_alloc_txn_accum_rbs_v WHERE rbs_version_id = :p_version GROUP BY rbs_element_id;