Results for “pa_fp_of_webadi_v”

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

Overview

PA_FP_OF_WEBADI_V is a read-only Oracle EBS Projects (PA) view owned by the APPS schema. It exposes financial plan forecast data structured for consumption by the WebADI (Web Applications Desktop Integrator) interface, presenting organisation-level forecast elements together with period-by-period amounts. The view joins the denormalised project period amounts table with HR organisation units, forecast elements, projects, resources and amount types, producing a flattened row set in which the same organisation and forecast element combination is repeated for each of the 52 period amount columns. This structure supports the upload and download of forecast plan data through the WebADI spreadsheet interface, and is equally suitable for ad-hoc reporting on project forecast revenue and cost across periods.

Underlying Base Objects

The view is defined over the following documented objects. PA_PROJ_PERIODS_DENORM supplies the period amount columns (PERIOD_AMOUNT1 through PERIOD_AMOUNT52) and the amount subtype identifier. PA_ORG_FCST_ELEMENTS supplies organisation forecast element attributes including ORG_ID, ORGANIZATION_ID, OTHER_ORG_ID and OTHER_ORGANIZATION_ID. Four aliased instances of HR_ALL_ORGANIZATION_UNITS (HRORG1 to HRORG4) resolve the names for the owning organisation, the organisation, the other organisation and the other organisation identifier respectively. PA_PROJECTS_ALL provides the project name, while PA_AMOUNT_TYPES_VL supplies the amount type name, PA_WORK_TYPES_B contributes work type context, and PA_RESOURCES plus PA_PROJECT_ASSIGNMENTS resolve the resource or assignment name via a DECODE on RESOURCE_ID. The package PA_FIN_PLAN_VIEW_GLOBAL is called through GET_VERSION_ID to determine the budget version used for filtering, and PA_BUDGET_VERSIONS and PA_RESOURCE_ASSIGNMENTS are referenced in the broader join logic.

Key Columns

AMOUNT_SUBTYPE_ID and AMOUNT_TYPE_NAME identify the forecast amount subtype and its descriptive type. ORG_ID, ORGANIZATION_ID, OTHER_ORG_ID and OTHER_ORGANIZATION_ID carry the organisation keys, with the adjacent HRORG1.NAME through HRORG4.NAME columns providing their names — the user searched term other_organization_name corresponds directly to the HRORG3 or HRORG4 name value resolved for the other organisation. PP.NAME holds the project name, and the DECODE on RESOURCE_ID returns either PPA.ASSIGNMENT_NAME (when RESOURCE_ID equals -1) or PR.NAME, giving a consistent resource label. PERIOD_AMOUNT1 to PERIOD_AMOUNT52 hold the amounts for each forecast period, arranged according to the period offset defined by the underlying denormalised structure.

Common Use Cases and Queries

Typical usage includes retrieving forecast amounts by other organisation name, extracting data for WebADI template population, and validating forecast element setup. The following example selects the key descriptive columns and the first three period amounts, filtering on the other organisation name.

• SELECT organization_id, other_organization_name, name, period_amount1, period_amount2, period_amount3 FROM pa_fp_webadi_v WHERE other_organization_name = 'My Org';

• SELECT project_name, amount_type_name, SUM(period_amount1) FROM pa_fp_webadi_v GROUP BY project_name, amount_type_name;

• SELECT * FROM pa_fp_webadi_v WHERE org_id = :p_org_id AND amount_subtype_id = :p_subtype_id;

Because the view depends on PA_FIN_PLAN_VIEW_GLOBAL.GET_VERSION_ID(), results are scoped to the budget version held in the package session context, so callers should ensure the correct version is initialised before querying. No DML should be issued against the view.