Results for “pa_fp_options_reslists_v_r”

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

Overview

PA_FP_OPTIONS_RESLISTS_V_R is a Projects (PA) module view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes the resource lists associated with financial plan options at the project and plan type level. Its name follows the standard Oracle convention for a read-only reporting view (_V) defined against a table whose rows are secured or filtered (_R). The view consolidates three logically distinct resource list assignments—cost resource lists, revenue resource lists, and combined cost-and-revenue resource lists—into a single result set using a UNION ALL construct, tagging each row with a descriptive type literal.

For users and integrators searching on plan_type, this view is directly relevant: all three branches of the view filter PA_PROJ_FP_OPTIONS.FIN_PLAN_OPTION_LEVEL_CODE = 'PLAN_TYPE', meaning the resource list assignments returned apply at the financial plan type level rather than at the project or project-level plan option level. This makes the view the canonical source for determining which resource list was nominated for cost, revenue, or combined planning under a given plan type.

Underlying Base Objects

The view is defined over a single base table: PA_PROJ_FP_OPTIONS. No other documented base objects are referenced, and the ETRM metadata lists no additional referenced base objects. The view aggregates three SELECT blocks joined by UNION ALL:

• The first block selects cost resource lists (COST_RESOURCE_LIST_ID) where the preference code is COST_ONLY or COST_AND_REV_SEP and the option level is PLAN_TYPE.
• The second block selects revenue resource lists (REVENUE_RESOURCE_LIST_ID) where the preference code is REVENUE_ONLY or COST_AND_REV_SEP.
• The third block selects combined resource lists (ALL_RESOURCE_LIST_ID) where the preference code is COST_AND_REV_SAME.

Each block enforces non-null constraints on PROJECT_ID, FIN_PLAN_TYPE_ID, and the respective resource list identifier, ensuring that only fully qualified option records are surfaced.

Key Columns

• PROJECT_ID — Identifier of the project to which the financial plan option belongs.
• FIN_PLAN_TYPE_ID — Identifier of the financial plan type; this is the plan_type context that drives the view's filtering.
• FP_RESOURCE_LIST_ID — The resource list identifier, drawn from any of the three source columns depending on the branch.
• FP_RESOURCE_LIST_TYPE — A descriptive literal: 'COST RESOURCE LIST', 'REVENUE RESOURCE LIST', or 'COST AND REVENUE RESOURCE LIST', derived in the view as RESLISTTYPE.
• FIN_PLAN_START_DATE — Effective start date of the financial plan option assignment.
• FIN_PLAN_END_DATE — Effective end date of the financial plan option assignment.

Note that the documented column list presents the identifiers with the FP_ prefix, whereas the view text aliases the underlying columns without it. The view is documented as not implemented in the database extracted for the ETRM reference, so column naming should be confirmed against the target instance.

Common Use Cases and Queries

Typical uses include reporting the resource list configuration for a plan type, validating plan option setup prior to plan generation, and joining resource list assignments to plan type definitions.

Retrieve all resource list assignments for a specific plan type:

SELECT project_id,
       fin_plan_type_id,
       fp_resource_list_id,
       fp_resource_list_type,
       fin_plan_start_date,
       fin_plan_end_date
FROM   pa_fp_options_reslists_v_r
WHERE  fin_plan_type_id = :plan_type_id
ORDER BY project_id, fp_resource_list_type;

Enumerate all plan types using a combined (cost and revenue) resource list:

SELECT DISTINCT fin_plan_type_id, fp_resource_list_id
FROM   pa_fp_options_reslists_v_r
WHERE  fp_resource_list_type = 'COST AND REVENUE RESOURCE LIST';

Join to plan type definitions to produce a human-readable inventory of resource list assignments per plan type, filtered by project. Because the view performs a UNION ALL across three branches, duplicate resource list identifiers can appear when the same list is referenced under multiple preference codes; DISTINCT should be applied where uniqueness is required.