Results for “labor_quantity”

50+ results




Overview
Explore in AI Chat

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

Overview

The PA_BASE_BUDGET_BY_RESOURCE_V view is a Projects (PA) module database object owned by the APPS schema. It provides a summarized, resource-level projection of project budget data, aggregating budget line amounts and quantities across budget versions, projects, tasks, and resource list members. The view is documented in Oracle E-Business Suite R12.1.1 and 12.2.2 as valid, with the ETRM description noting that it is "10Sc Only" — that is, it is intended primarily to support Oracle Projects' integration with the Oracle Project Manufacturing / Standard Costing (10Sc) resource budgeting model rather than as a general-purpose reporting view.

Functionally, the view exposes one row per combination of budget version, project, task, budget type, and resource list member, with cost and quantity measures rolled up via SUM aggregation. Because it filters on CURRENT_FLAG = 'Y', only the current budget version is returned, making the view a convenient source for "latest baseline" resource budget reporting. Its role is therefore to bridge the normalized transactional tables (budget lines, resource assignments, resource lists) and consumers requiring denormalized, aggregated budget figures.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over four base objects, all referenced as synonyms owned by APPS:

Joins are established on RESOURCE_LIST_MEMBER_ID, RESOURCE_ASSIGNMENT_ID, and BUDGET_VERSION_ID. A filter excludes rows where NVL(M.MIGRATION_CODE, '-99') <> 'N', omitting migrated resource list members.

Key Columns

  • BUDGET_VERSION_ID, PROJECT_ID, TASK_ID, BUDGET_TYPE_CODE — the primary grouping dimensions identifying the budget context.
  • RESOURCE_LIST_MEMBER_ID, RESOURCE_LIST_ID, RESOURCE_ID — identify the specific resource being budgeted.
  • RESOURCE_ACCUMULATED_FLAG — indicates whether resources are accumulated.
  • RAW_COST, BURDENED_COST, REVENUE, QUANTITY — aggregated (SUM) financial and volumetric measures from budget lines.
  • LABOR_QUANTITY — derived via TO_NUMBER(DECODE(A.TRACK_AS_LABOR_FLAG,'N',NULL,SUM(NVL(L.QUANTITY,0)))), populating only when the assignment is tracked as labor.
  • UNIT_OF_MEASURE — the unit associated with the resource quantity.

Common Use Cases and Queries

Typical uses include resource budget vs. actual comparisons, current-version budget extracts for cost, and feeding 10Sc related processes. A representative query follows:

  • SELECT PROJECT_ID, TASK_ID, RESOURCE_ID, RAW_COST, BURDENED_COST, QUANTITY, LABOR_QUANTITY FROM APPS.PA_BASE_BUDGET_BY_RESOURCE_V WHERE PROJECT_ID = :p_project_id;
  • Filter by BUDGET_TYPE_CODE to isolate approved versus baseline budgets.
  • Aggregate further by RESOURCE_ID or TASK_ID for summarized resource reporting.

Because the view returns only the current budget version and aggregates at the resource level, consumers requiring historical versions or detail-line granularity must query the underlying PA_BUDGET_LINES and PA_BUDGET_VERSIONS tables directly.