Search Results prior_forecast_quantity




Overview
Explore in AI Chat

Overview

PA_FP_WEBADI_NP_CUSTOM_V is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) module, classified as VALID in the ETRM repository. Its documented purpose is to support Financial Planning by providing a customizable data source for the non-periodic budget and forecast download to Microsoft Excel through the WebADI (Web Applications Desktop Integrator) interface. The view is a customization layer built on top of the seeded non-periodic download view PA_FP_WEBADI_NON_PERIODIC_V. It exists so that implementers can tailor the columns and content delivered to the spreadsheet without modifying Oracle's seeded definition, which would be overwritten during patching. Because it exposes both the underlying budget line attributes and computed rate and cost elements, it acts as the reporting and integration surface for non-periodic plan data, including the project cost rate types referenced by financial plan calculations. This behavior is consistent across the EBS 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The view's View Text defines a direct projection from PA_FP_WEBADI_NON_PERIODIC_V, preserving the column ordering and applying an ORDER BY clause on TASK_DISPLAY_SEQUENCE, RESOURCE_NAME, UOM, and CURRENCY. The documented base objects for the view and its dependency chain are:

The view therefore inherits the business logic, security filtering, and rate derivation implemented in these packages rather than re-implementing them.

Key Columns

The projection exposes planning identifiers, descriptive attributes, quantities, amounts, and rate information. Notable columns include BUDGET_VERSION_ID (the plan version), FIN_PLAN_PREFERENCE_CODE, PLAN_CLASS_CODE, and PROJECT_ID, PROJECT_NUMBER, and PROJECT_NAME for project context. TASK_NUMBER, TASK_NAME, and TASK_DISPLAY_SEQUENCE provide the task hierarchy, while RESOURCE_NAME and RESOURCE_LIST_MEMBER_ID identify the resource. FIN_PLAN_PREFERENCE_CODE, START_DATE, END_DATE, CURRENCY, and UOM frame the plan line, with QUANTITY, ACTUAL_QUANTITY, ETC_QUANTITY, CURRENT_QUANTITY, ORIGINAL_QUANTITY, and PRIOR_FORECAST_QUANTITY representing the quantity measures. Cost columns such as RAW_COST, BURDENED_COST, REVENUE, and their ACTUAL, ETC, CURRENT, ORIGINAL, and PRIOR_FORECAST variants provide the amount measures.

The rate-related columns directly address the user's search for project_cost_rate_type. These include PROJFUNC_COST_RATE_TYPE, PROJFUNC_COST_RATE_DATE_TYPE, PROJECT_COST_RATE_TYPE, and PROJECT_COST_RATE_DATE_TYPE for cost, plus the corresponding PROJFUNC_REV_* and PROJECT_REV_* columns for revenue. Derived rate values are exposed as RAW_COST_RATE, BURDENED_COST_RATE, BILL_RATE, PROJFUNC_COST_RATE, PROJECT_COST_RATE, PROJFUNC_REV_RATE, and PROJECT_REV_RATE, with companion date columns such as PROJECT_COST_RATE_DATE and PROJECT_REV_RATE_DATE.

Common Use Cases and Queries

The primary scenario is customizing the non-periodic budget/forecast Excel download so that additional processing-specific columns, such as the project cost rate type or rate date type, are available to planners. Analysts also query the view directly for ad-hoc reporting on plan quantities, costs, and rates.

  • Retrieve project cost rate type information for a plan version.
  • Compare projected versus actual cost and revenue quantities.
  • Export plan lines ordered by task, resource, UOM, and currency.
  • Review rate values alongside their applicable rate types and dates.

A representative query is:

SELECT BUDGET_VERSION_ID, PROJECT_NUMBER, PROJECT_NAME, TASK_NUMBER, RESOURCE_NAME, CURRENCY, UOM, PROJECT_COST_RATE_TYPE, PROJECT_COST_RATE_DATE_TYPE, PROJECT_COST_RATE, PROJECT_COST_RATE_DATE, RAW_COST, BURDENED_COST FROM APPS.PA_FP_WEBADI_NP_CUSTOM_V WHERE BUDGET_VERSION_ID = :p_budget_version_id ORDER BY TASK_DISPLAY_SEQUENCE, RESOURCE_NAME;

Because the view is ordered and extends a seeded WebADI view, changes should be implemented as a custom copy applied to the download layout, preserving the APPS schema ownership and the underlying package logic.