Search Results quantity_ptd_base




Overview
Explore in AI Chat

Overview

APPS.PA_TODATE_BASE_BUDGET_V is a PL/SQL-based reporting view in the Oracle E-Business Suite Projects (PA) module, residing in the APPS schema and registered under FND Design Data as PA.PA_TODATE_BASE_BUDGET_V. It presents budget amounts and quantities aggregated across standard Oracle Projects time-phased horizons — period-to-date (PTD), prior period (PP), year-to-date (YTD), and inception-to-date (ITD) — all expressed in the project's base currency and base unit of measure where applicable. The view is classified as an Oracle internal object: Oracle Corporation does not support direct access to applications data through it except from standard Oracle Applications programs. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2.

The view is of particular interest to developers and report authors searching on quantity_ptd_base, since that column exposes the period-to-date budgeted quantity in the base unit of measure for a given project, task, budget type, and resource combination. It is the quantity counterpart to RAW_COST_PTD_BASE and BURDENED_COST_PTD_BASE, enabling quantity-versus-cost comparisons on the same time horizon.

Underlying Base Objects

The view is documented as being defined over the following objects:

  • PA_BUDGET_LINES (synonym) — the primary source of budgeted cost, revenue, and quantity lines.
  • PA_BUDGET_VERSIONS (synonym) — supplies the budget type designation and version context.
  • PA_RESOURCE_ASSIGNMENTS (synonym) — links budget lines to the resources and resource list members assigned to the project.
  • PA_RESOURCE_LIST_MEMBERS (synonym) — provides the resource alias and resource list identity used to qualify budget amounts.
  • PA_ACCUM_UTILS (package) — the accumulator utility package that performs the PTD/PP/YTD/ITD rollups driving the _PTD_BASE, _PP_BASE, _YTD_BASE, and _ITD_BASE column families.

Because PA_ACCUM_UTILS is a package rather than a table, the view performs cumulative calculations at query time rather than reading a single pre-aggregated table, which explains the presence of the RESOURCE_ACCUMULATED_FLAG column indicating whether the underlying budget version has already been accumulated.

Key Columns

The view's keying columns are PROJECT_ID, TASK_ID, BUDGET_TYPE_CODE, RESOURCE_LIST_MEMBER_ID, RESOURCE_LIST_ID, and RESOURCE_ID, with START_DATE and END_DATE delimiting each budget line. Measure columns include RAW_COST, BURDENED_COST, REVENUE, QUANTITY, and LABOR_QUANTITY. The cumulative families repeat these measures per horizon: RAW_COST_PTD_BASE, BURDENED_COST_PTD_BASE, REVENUE_PTD_BASE, QUANTITY_PTD_BASE, and LABOR_QUANTITY_PTD_BASE for period-to-date; the _PP_BASE, _YTD_BASE, and _ITD_BASE variants for prior period, year-to-date, and inception-to-date respectively. UNIT_OF_MEASURE_BASE identifies the unit of measure applicable to the budget in the PA period, which is essential when interpreting QUANTITY_PTD_BASE and its sibling quantity columns.

Common Use Cases and Queries

Typical scenarios include budget-versus-actual quantity reporting, period budget consumption analysis, and extract feeds into project cost or performance reporting. Because the object is internal, supported usage flows through standard Oracle Programs such as the Project Status Inquiry and budget reports; direct SQL should be treated as diagnostic or read-only.

SELECT project_id,
       task_id,
       budget_type_code,
       resource_list_member_id,
       unit_of_measure_base,
       quantity_ptd_base,
       labor_quantity_ptd_base,
       raw_cost_ptd_base,
       burdened_cost_ptd_base
  FROM apps.pa_todate_base_budget_v
 WHERE project_id = :p_project_id
   AND budget_type_code = 'APPROVED_COST_BUDGET'
 ORDER BY task_id, resource_list_member_id;

Aggregate queries follow the same pattern, for example summarizing QUANTITY_PTD_BASE by task to compare budgeted quantity against actuals for a reporting period. All access remains subject to the Oracle internal-use restriction.