Results for “pa_budget_resources_v”

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

Overview

PA_BUDGET_RESOURCES_V is a Projects (PA) module view owned by the APPS schema. The ETRM documentation describes its scope succinctly as "10Sc Only," indicating this is a legacy 10SC (Oracle Projects 10SC) compatibility construct retained in the E-Business Suite 12.1.1 and 12.2.2 data model primarily for backward compatibility rather than for new development. The view exposes a hierarchical, flattened representation of resource list members drawn from the PA_RESOURCE_LIST_MEMBERS table, augmented with a derived resource name resolved at runtime through the PA_RESOURCES_PKG package. Its principal consumers are reports, concurrent programs, and integration extracts that historically needed a denormalized, indented view of the resource list hierarchy for budgeting and planning purposes.

Users searching for the TRACK_AS_LABOR_FLAG column arrive at this view because it is one of the projected columns, reflecting the labor-tracking attribute associated with each resource list member. That attribute is significant in Oracle Projects budgeting, where resources marked as labor participate in labor cost and burdening calculations differently from non-labor resources such as expense or equipment items.

Underlying Base Objects

The view is defined directly over one documented base object, PA_RESOURCE_LIST_MEMBERS (exposed in the APPS schema as a synonym), and functionally depends on two additional constructs:

• PA_RESOURCE_LIST_MEMBERS — the driving table containing resource list membership rows, parent-child relationships, enable/display flags, resource identifiers, and the TRACK_AS_LABOR_FLAG and MIGRATION_CODE attributes.
• PA_RESOURCES_PKG — a PL/SQL package referenced through the GET_RESOURCE_NAME function, which resolves RESOURCE_ID and RESOURCE_TYPE_ID into a human-readable, 30-character resource name. This dependency means the view executes PL/SQL per row and is not a pure SQL projection.

The view applies a CONNECT BY hierarchical filter, starting from members with a null PARENT_MEMBER_ID and descending through PRIOR RESOURCE_LIST_MEMBER_ID = PARENT_MEMBER_ID. Only rows with DISPLAY_FLAG = 'Y' and ENABLED_FLAG = 'Y' are returned, so disabled or hidden members are excluded entirely from the hierarchy.

Key Columns

• ALIAS — the resource list member alias, indented by two spaces per hierarchy level using LPAD and LEVEL, producing a visual tree effect in report output.
• ALIAS2 — the unindented alias value, provided for join and comparison purposes.
• RESOURCE_LIST_ID / RESOURCE_LIST_MEMBER_ID — identifiers for the parent resource list and the individual membership row.
• RESOURCE_ID — the identifier of the underlying resource, passed to PA_RESOURCES_PKG.GET_RESOURCE_NAME.
• TRACK_AS_LABOR_FLAG — indicates whether the resource is treated as labor for budgeting and cost purposes; this is the column most frequently queried against this view.
• PARENT_MEMBER_ID — the parent membership identifier, coalesced to zero via NVL when null, supporting hierarchy traversal.
• RESOURCE_NAME — the derived 30-character resource name returned by the package function.
• MIGRATION_CODE — a migration-related attribute carried through from the base table.

Common Use Cases and Queries

Typical uses include validating which members of a resource list are flagged as labor, reconstructing the hierarchy of a specific resource list, and feeding legacy budgeting reports that expect an indented alias column.

To isolate labor-tracked members of a given list:

• SELECT resource_list_member_id, alias2, resource_name, track_as_labor_flag FROM pa_budget_resources_v WHERE resource_list_id = :p_list_id AND track_as_labor_flag = 'Y';

To reproduce the full indented hierarchy for reporting:

• SELECT alias, resource_name, nvl(parent_member_id,0) parent_member_id FROM pa_budget_resources_v WHERE resource_list_id = :p_list_id ORDER BY resource_list_member_id;

Because the view invokes PA_RESOURCES_PKG.GET_RESOURCE_NAME per row, query performance degrades on large resource lists; filtering by RESOURCE_LIST_ID is strongly recommended. Given its 10SC-only designation, new development should prefer direct queries against PA_RESOURCE_LIST_MEMBERS unless compatibility with legacy reporting is required.