Results for “pa_resource_list_assignments_v”

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

Overview

The PA_RESOURCE_LIST_ASSIGNMENTS_V view is a Projects (PA) module reporting object owned by the APPS schema. It exposes the assignment of resource lists to a project specifically for use in Oracle E-Business Suite self-service budgeting and workplan functionality. Resource lists in Oracle Projects define groupings of resources — such as employees, jobs, or organizations — that can be planned and budgeted against. This view correlates each project with the resource lists configured against that project and, crucially, flags whether each list is used for workplan purposes or for financial plan (budget/forecast) purposes.

The view plays a supporting role in Project Financial Planning and Project Workplan integration. It abstracts the multi-column foreign-key relationship held on the project financial plan options record, presenting a simplified, de-normalized result set of one row per resource list per project. This makes it convenient for reporting, list-of-values population, and integration logic that must determine which resource lists apply to workplan versus financial plan contexts.

Underlying Base Objects

The view is defined over two documented objects plus a utility package:

• PA_PROJ_FP_OPTIONS (referenced via synonym) — the project-level financial plan options table. It stores the resource list identifiers associated with cost, revenue, and all-resource configurations through the columns COST_RESOURCE_LIST_ID, REVENUE_RESOURCE_LIST_ID, and ALL_RESOURCE_LIST_ID.
• PA_RESOURCE_LISTS_ALL_BG (referenced via synonym) — the resource list base table, providing the defined resource lists joined on RESOURCE_LIST_ID.
• PA_FIN_PLAN_UTILS (package) — a PL/SQL utility package invoked twice within the view's SELECT list to compute the workplan and financial plan usage flags via the functions IS_WP_RESOURCE_LIST and IS_FP_RESOURCE_LIST.

The join predicate matches a resource list where it appears in any of the three financial plan option columns, and the DISTINCT keyword collapses the result to unique project/resource list combinations.

Key Columns

• RESOURCE_LIST_ID — the identifier of the resource list assigned to the project.
• PROJECT_ID — the project to which the resource list assignment belongs.
• USE_FOR_WP_FLAG — a computed flag derived from PA_FIN_PLAN_UTILS.IS_WP_RESOURCE_LIST(PROJECT_ID, RESOURCE_LIST_ID), indicating whether the resource list is used for workplan purposes.
• USE_FOR_FP_FLAG — a computed flag derived from PA_FIN_PLAN_UTILS.IS_FP_RESOURCE_LIST(PROJECT_ID, RESOURCE_LIST_ID), indicating whether the resource list is used for financial plan purposes.

Note that the ETRM view text labels the workplan column USED_FOR_WP_FLAG, while the documented exposed column name is USE_FOR_WP_FLAG. The user's search term, use_for_wp_flag, corresponds directly to this workplan indicator column.

Common Use Cases and Queries

The primary use case is identifying which resource lists are valid for workplan versus financial plan entry on a given project. A typical query filters by project and inspects the workplan flag:

SELECT resource_list_id,
       project_id,
       use_for_wp_flag,
       use_for_fp_flag
FROM   apps.pa_resource_list_assignments_v
WHERE  project_id = :p_project_id
AND    use_for_wp_flag = 'Y';

Because the flag columns are populated by package functions rather than stored columns, the view is best suited to transactional lookups at the project level rather than large-scale bulk extraction. Typical consumers include self-service budget and workplan pages, list-of-values definitions, and integration routines that must validate whether a given resource list is permitted in a particular planning context. When only the financial plan flag is relevant, the same view is queried with a predicate on USE_FOR_FP_FLAG. Combining both flags allows a project to be profiled for the full set of resource lists available across planning modes.