Results for “fp_type_code”

20 results




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

Overview

The view PA_PMC_RESOURCE_LIST_V is an Oracle Applications (APPS) database object owned by the APPS schema and validated within the Oracle E-Business Suite. It belongs to the Projects (PA) product family and is documented as being used by WebConnect to retrieve all resource lists. In practical terms, the view consolidates resource list identifiers and names from multiple Projects planning and budgeting contexts into a single, uniformly structured result set that integration layers, such as WebConnect, can consume without needing to understand the underlying table relationships.

A resource list in Oracle Projects is a reusable grouping of resources — people, roles, and other planning entities — that drives financial planning, budgeting, and forecasting. By exposing both plan-type resource lists and budget-type resource lists through one interface, PA_PMC_RESOURCE_LIST_V abstracts the differences between the financial plan and budget schemas and presents a normalized shape with a consistent set of columns. This makes it well suited for reporting, LOV (list of values) population, and programmatic lookups where a caller needs the resource list name (RESOURCE_LIST_NAME) together with its identifier and originating context.

Underlying Base Objects

The documented base objects referenced by this view are:

The view text confirms the structure: it is a UNION ALL of two branches. The first branch joins PA_FP_OPTIONS_RESLISTS_V (aliased FP) to PA_RESOURCE_LISTS_ALL_BG (aliased BG) on FP_RESOURCE_LIST_ID = BG.RESOURCE_LIST_ID, returning the resource list identifier, the base resource list name, a financial plan type identifier, the literal 'PLAN_TYPE' as the type code, and a project identifier. The second branch selects directly from PA_PMC_RESOURCE_LISTS_V, returning resource list columns and the literal values -1 for FIN_PLAN_TYPE_ID and PROJECT_ID and 'BUDGET_TYPE' as the type code. The packages FND_PROFILE and PA_CROSS_BUSINESS_GRP support profile-option and cross-business-group security behavior that governs the rows visible to the calling session.

Key Columns

  • RESOURCE_LIST_ID — Unique identifier of the resource list. Sourced as FP_RESOURCE_LIST_ID in the plan-type branch and as RESOURCE_LIST_ID in the budget-type branch.
  • RESOURCE_LIST_NAME — The user-facing name of the resource list, obtained from PA_RESOURCE_LISTS_ALL_BG.NAME. This is the column most commonly searched (e.g., "resource_list_name").
  • FIN_PLAN_TYPE_ID — The financial plan type identifier for plan-type resource lists; set to -1 for budget-type rows.
  • FP_TYPE_CODE — Discriminator indicating the origin of the row: 'PLAN_TYPE' or 'BUDGET_TYPE'.
  • PROJECT_ID — The associated project identifier for plan-type rows; set to -1 for budget-type rows.

Common Use Cases and Queries

Typical uses include resolving a resource list name from an identifier, populating a selection list, and filtering resource lists by plan or budget context.

Resolve a name from an identifier:

SELECT resource_list_id, resource_list_name, fp_type_code
FROM   pa_pmc_resource_list_v
WHERE  resource_list_id = :p_resource_list_id;

Find resource lists by name pattern:

SELECT resource_list_id, resource_list_name, fp_type_code, project_id
FROM   pa_pmc_resource_list_v
WHERE  resource_list_name LIKE :p_name_pattern;

List only plan-type resource lists for a project:

SELECT resource_list_id, resource_list_name, fin_plan_type_id
FROM   pa_pmc_resource_list_v
WHERE  fp_type_code = 'PLAN_TYPE'
AND    project_id = :p_project_id;

Because the view is defined over planning and budgeting objects, results remain subject to the security and profile settings applied through FND_PROFILE and PA_CROSS_BUSINESS_GRP. Callers should therefore treat the returned set as context-sensitive rather than globally complete.