Results for “used_for_wp_flag”

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

Overview

APPS.PA_RESOURCE_LIST_ASSIGNMENTS_V is a reporting view in the Oracle E-Business Suite Projects (PA) module that exposes the association between project resource lists and the financial plan options configured for a given project. Its central purpose is to answer the question implied by the search term "resource_list_id": for a specific resource list, which project is it attached to, and is that list consumed as a working plan (WP) resource list, a financial plan (FP) resource list, or both.

In Oracle EBS 12.1.1 and 12.2.2 the view is owned by APPS and is defined with a DISTINCT projection over the intersection of resource lists and financial plan options. Because the underlying join is expressed as an OR across three foreign keys, a single row in PA_PROJ_FP_OPTIONS may match the same resource list through more than one column; the DISTINCT clause collapses those duplicates so that each unique (resource_list_id, project_id) combination appears once. The view therefore behaves as a derived, de-duplicated assignment matrix rather than a base transactional table.

Underlying Base Objects

The view is constructed from two referenced base objects and one database package:

• PA_PROJ_FP_OPTIONS (SYNONYM) — Stores the financial plan option configuration for each project, including three resource list foreign keys: COST_RESOURCE_LIST_ID, REVENUE_RESOURCE_LIST_ID, and ALL_RESOURCE_LIST_ID. These are the columns joined in the WHERE clause.
• PA_RESOURCE_LISTS_ALL_BG (SYNONYM) — The resource list definition table in the Projects module. Its RESOURCE_LIST_ID equates to any of the three option columns, establishing that a resource list is genuinely assigned.
• PA_FIN_PLAN_UTILS (PACKAGE) — A PL/SQL utility package supplying two Boolean-returning functions used inline in the SELECT list: IS_WP_RESOURCE_LIST and IS_FP_RESOURCE_LIST. Because these are PL/SQL calls, the view cannot be used in all contexts (for example, certain parallel query or index-only scenarios) without care.

No base table is joined for project master data; PROJECT_ID is carried straight from PA_PROJ_FP_OPTIONS.

Key Columns

• RESOURCE_LIST_ID — Identifier of the resource list assigned to the project; the primary lookup key users search on.
• PROJECT_ID — The project that owns the financial plan options referencing the resource list.
• USED_FOR_WP_FLAG — Result of PA_FIN_PLAN_UTILS.IS_WP_RESOURCE_LIST(PROJECT_ID, RESOURCE_LIST_ID); indicates whether the list is used for the working plan.
• USED_FOR_FP_FLAG — Result of PA_FIN_PLAN_UTILS.IS_FP_RESOURCE_LIST(PROJECT_ID, RESOURCE_LIST_ID); indicates whether the list is used for the financial plan.

The two flag columns are computed at query time and return the package's Boolean representation, so consumers should not assume a simple Y/N character domain.

Common Use Cases and Queries

Typical scenarios include finding every project that references a given resource list, validating which plan a list drives, and auditing resource list usage prior to changes.

• Locate assignments for a specific list:

SELECT project_id, resource_list_id, used_for_wp_flag, used_for_fp_flag FROM apps.pa_resource_list_assignments_v WHERE resource_list_id = :p_resource_list_id;

• Enumerate all resource lists for a project and classify their plan usage by filtering on the flag columns.
• Feed integration or reconciliation extracts that must confirm a resource list is actually linked to financial plan options before processing.

Because of the inline package calls and DISTINCT processing, queries should filter on RESOURCE_LIST_ID or PROJECT_ID where possible, and avoid treating the view as a source of counts without accounting for de-duplication.