Results for “resource_accumulated_flag”

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

Overview

PA_ORIG_BUDGET_BY_RESOURCE_V is a reporting view owned by the APPS schema in Oracle EBS Projects (PA). Per the ETRM metadata it is documented as "10Sc Only," indicating its behavior and column semantics are tied to the 10Sc (11i-era) data model conventions rather than the newer budget rearchitecture. The view presents the original budget, aggregated by resource, for the current original budget version of a project. It returns summarized cost, revenue, and quantity figures at the intersection of project, task, budget type, and resource list member.

Its defining characteristic is the CURRENT_ORIGINAL_FLAG = 'Y' filter on PA_BUDGET_VERSIONS, which restricts output to the single budget version designated as the current original baseline. This makes the view suitable for baseline-versus-actual comparisons, funding analysis, and resource-level budget distribution reporting without requiring the caller to resolve the correct budget version manually.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through APPS synonyms:

• PA_BUDGET_VERSIONS — supplies BUDGET_VERSION_ID, PROJECT_ID, BUDGET_TYPE_CODE, RESOURCE_ACCUMULATED_FLAG, and the CURRENT_ORIGINAL_FLAG driving the filter.
• PA_RESOURCE_LIST_MEMBERS — supplies RESOURCE_LIST_ID and RESOURCE_ID, and joins to resource assignments via RESOURCE_LIST_MEMBER_ID. The join applies NVL(M.MIGRATION_CODE,'-99') <> 'N' to exclude migrated-away members.
• PA_RESOURCE_ASSIGNMENTS — supplies TASK_ID, TRACK_AS_LABOR_FLAG, and UNIT_OF_MEASURE, and links budget lines to resources.
• PA_BUDGET_LINES — the fact source for RAW_COST, BURDENED_COST, REVENUE, and QUANTITY amounts.

All measures are aggregated with SUM over NVL defaults of zero, so projects without lines still yield deterministic zero-valued rows rather than nulls. This inner-join structure means a row is produced only where a budget line exists for a resource assignment on the current original version.

Key Columns

• BUDGET_VERSION_ID / PROJECT_ID / TASK_ID — the primary structural keys identifying the budget baseline, project, and task.
• BUDGET_TYPE_CODE — distinguishes approved vs. submitted vs. other budget categories carried on the version.
• RESOURCE_LIST_MEMBER_ID / RESOURCE_LIST_ID / RESOURCE_ID — the resource identity and its parent list, enabling rollup from member to list to resource.
• RAW_COST / BURDENED_COST / REVENUE / QUANTITY — summed budget measures in project currency and the assignment unit of measure.
• LABOR_QUANTITY — conditionally derived: equal to aggregated quantity when TRACK_AS_LABOR_FLAG is not 'N', otherwise null. Use this column to isolate labor-tracked quantities.
• RESOURCE_ACCUMULATED_FLAG — indicates whether the resource was accumulated in the budget version.
• UNIT_OF_MEASURE — the assignment's unit, relevant when comparing QUANTITY across resources.

Common Use Cases and Queries

Typical scenarios include original-baseline extraction for project reporting, resource-level budget distribution analysis, and integration feeds into external reporting or costing systems. The following sample returns the original budget by resource for a project:

• SELECT project_id, task_id, resource_id, resource_list_id, raw_cost, burdened_cost, revenue, quantity, labor_quantity, unit_of_measure FROM apps.pa_orig_budget_by_resource_v WHERE project_id = :p_project_id ORDER BY task_id, resource_id;
• SELECT resource_id, SUM(raw_cost) raw_cost, SUM(burdened_cost) burdened_cost FROM apps.pa_orig_budget_by_resource_v WHERE project_id = :p_project_id GROUP BY resource_id;
• SELECT task_id, SUM(labor_quantity) labor_qty FROM apps.pa_orig_budget_by_resource_v WHERE project_id = :p_project_id GROUP BY task_id;

Because the view already restricts to the current original version, queries should not additionally filter BUDGET_VERSION_ID unless reviewing a specific baseline. Join to PA_PROJECTS or PA_TASKS for descriptive attributes, and note that cost figures are budget amounts, not actuals.