Search Results fin_plan_end_date

Overview

The APPS.PA_FP_OPTIONS_RESLISTS_V view is an Oracle E-Business Suite internal database object residing in the APPS schema. It exposes financial plan option data associated with resource lists, serving as a denormalized read layer over the underlying configuration stored for Project Management financial plans. The view is registered within the FND Design Data repository under the identifier PA.PA_FP_OPTIONS_RESLISTS_V and carries a VALID status in the ETRM metadata for EBS 12.1.1 and 12.2.2.

The view type is documented as Internal, accompanied by the standard Oracle warning that Oracle Corporation does not support direct access to applications data through this object except from standard Oracle Applications programs. Its primary role is therefore to supply data to Oracle-delivered PL/SQL utilities and other views within the Project Costing and financial planning subsystem rather than to act as a public reporting interface. The object is particularly relevant to inquiries concerning financial plan effective dates, because it exposes the FIN_PLAN_START_DATE and FIN_PLAN_END_DATE columns directly at the resource-list level.

Underlying Base Objects

The documented dependency for this view is the base object APPS.PA_PROJ_FP_OPTIONS, accessed through a synonym. PA_PROJ_FP_OPTIONS stores the financial plan options defined for a project, including plan type, resource list assignment, and the effective date range of the plan configuration. PA_FP_OPTIONS_RESLISTS_V projects a focused subset of these columns, joining or filtering the base records so that each row represents a financial plan type and resource list combination for a given project.

The view is referenced by the Oracle package PA_FIN_PLAN_UTILS2 and by APPS.PA_PMC_RESOURCE_LIST_V. This dependency chain confirms that the view functions as a shared access point for financial plan resource list data used internally by Project Management utilities and by higher-level resource list views.

Key Columns

• PROJECT_ID (NUMBER, length 15) — The unique identifier of the project to which the financial plan options and resource list belong.
• FIN_PLAN_TYPE_ID (NUMBER, length 15) — The identifier of the financial plan type associated with the option record.
• FP_RESOURCE_LIST_ID (NUMBER, length 15) — The identifier of the financial plan resource list linked to the project and plan type.
• FP_RESOURCE_LIST_TYPE (VARCHAR2, length 30) — A descriptive code indicating the classification of the resource list, such as the resource source or list category used within the financial plan.
• FIN_PLAN_START_DATE (DATE) — The effective start date for the financial plan option and resource list configuration.
• FIN_PLAN_END_DATE (DATE) — The effective end date for the configuration. This column is the field most commonly targeted when users search on "fin_plan_end_date," and it defines the termination of the plan option's applicability.

Common Use Cases and Queries

Typical usage centers on identifying the effective window of a project's financial plan resource list configuration. A developer or administrator performing diagnostics may query the view to determine which resource list was active for a project on a given date, or to locate configurations whose end date has passed or is approaching.

A representative query retrieving all plan option records with their effective dates is shown below:

SELECT PROJECT_ID
     , FIN_PLAN_TYPE_ID
     , FP_RESOURCE_LIST_ID
     , FP_RESOURCE_LIST_TYPE
     , FIN_PLAN_START_DATE
     , FIN_PLAN_END_DATE
FROM APPS.PA_FP_OPTIONS_RESLISTS_V;

To inspect the end date specifically for a single project, a filter on PROJECT_ID and FIN_PLAN_END_DATE is applied:

SELECT PROJECT_ID
     , FIN_PLAN_TYPE_ID
     , FP_RESOURCE_LIST_ID
     , FIN_PLAN_END_DATE
FROM APPS.PA_FP_OPTIONS_RESLISTS_V
WHERE PROJECT_ID = :p_project_id
ORDER BY FIN_PLAN_END_DATE;

Because the object is designated Internal, direct SQL access should be limited to diagnostic or integration scenarios where no supported public API or view provides equivalent information. Where the data is required for user-facing reporting, the supported Oracle-delivered interfaces built on PA_FIN_PLAN_UTILS2 or PA_PMC_RESOURCE_LIST_V should be preferred.