Search Results pa_fin_plan_amount_sets




Overview
Explore in AI Chat

Overview

The PA_FIN_PLAN_AMOUNT_SETS table is a core reference table within the Oracle E-Business Suite Projects module (PA). It serves as a master repository for defining the distinct sets of financial amounts that can be utilized in project financial planning. In the context of Oracle EBS 12.1.1 and 12.2.2, financial plans are a critical component for budgeting and forecasting project costs and revenue. This table enables the configuration and segregation of different financial data categories, allowing organizations to maintain separate amount sets for costs, revenue, and combined totals. Its primary role is to provide a controlled list of valid amount sets that are linked to project-level financial plan options, thereby enforcing data integrity and structure in the planning process.

Key Information Stored

While the provided ETRM metadata does not list specific columns beyond the primary key, the table's structure is defined by its purpose and relationships. The central column is FIN_PLAN_AMOUNT_SET_ID, which is the unique identifier (Primary Key) for each amount set record. Typically, this table would also contain a column for the amount set name or code (e.g., AMOUNT_SET_NAME) to provide a meaningful description, such as 'Cost Plan Amounts', 'Revenue Plan Amounts', or 'All Plan Amounts'. Additional columns may include creation date, last update date, and descriptive flexfield attributes for customization. The data stored is static configuration data, defined during implementation and referenced by transactional planning data.

Common Use Cases and Queries

The primary use case is to query the valid amount sets available for assignment to a project's financial plan options. This is essential for setup validation, reporting, and integration tasks. A common reporting need is to list all projects and their associated financial amount set configurations. A sample SQL pattern to achieve this, joining with the related PA_PROJ_FP_OPTIONS table, would be:

SELECT p.segment1 project_number,
       a_set_all.amount_set_name all_amount_set,
       a_set_cost.amount_set_name cost_amount_set,
       a_set_rev.amount_set_name revenue_amount_set
FROM pa_proj_fp_options opt,
     pa_projects_all p,
     pa_fin_plan_amount_sets a_set_all,
     pa_fin_plan_amount_sets a_set_cost,
     pa_fin_plan_amount_sets a_set_rev
WHERE opt.project_id = p.project_id
  AND opt.all_amount_set_id = a_set_all.fin_plan_amount_set_id(+)
  AND opt.cost_amount_set_id = a_set_cost.fin_plan_amount_set_id(+)
  AND opt.revenue_amount_set_id = a_set_rev.fin_plan_amount_set_id(+);

This query demonstrates how the table is used to translate the ID references stored in transaction tables into human-readable names for reports and interfaces.

Related Objects

The PA_FIN_PLAN_AMOUNT_SETS table has a direct and exclusive relationship with the PA_PROJ_FP_OPTIONS table, which stores financial planning options at the project level. As documented in the ETRM metadata, three separate foreign key relationships exist:

  • PA_PROJ_FP_OPTIONS.ALL_AMOUNT_SET_ID references PA_FIN_PLAN_AMOUNT_SETS.FIN_PLAN_AMOUNT_SET_ID
  • PA_PROJ_FP_OPTIONS.COST_AMOUNT_SET_ID references PA_FIN_PLAN_AMOUNT_SETS.FIN_PLAN_AMOUNT_SET_ID
  • PA_PROJ_FP_OPTIONS.REVENUE_AMOUNT_SET_ID references PA_FIN_PLAN_AMOUNT_SETS.FIN_PLAN_AMOUNT_SET_ID

These relationships allow a single project's financial plan to be configured with different amount sets for total, cost-only, and revenue-only planning views. The table is referenced by these foreign keys but does not itself contain foreign keys to other tables, positioning it as a standalone reference entity.