Search Results preceding_period




Overview
Explore in AI Chat

Overview

PA_FP_WEBADI_P_CUSTOM_V is an Oracle EBS Projects (PA) view owned by the APPS schema. It is a customization view used within the Financial Planning module to drive the periodic budget and forecast download to an Excel spreadsheet. The view exposes a single flat row per planning resource assignment, task, amount type, and currency combination, with the associated planning dates and a 52-column periodic spread (preceding period, PRD1 through PRD52, and succeeding period). Applications and extensions can modify this view to add, remove, or rename columns and thereby control exactly which data elements appear in the downloaded spreadsheet, without altering the underlying planning engine tables.

The view is relevant to the search term planning_end_date: the PLANNING_END_DATE column is exposed here and represents the end date of the planning window for the resource assignment line, complementing PLANNING_START_DATE. Both dates frame the periods over which the PRD1 through PRD52 amounts are spread. In EBS 12.1.1 and 12.2.2, the object remains a standard, VALID APPS view defined against the periodic planning view lineage.

Underlying Base Objects

Per the documented ETRM metadata, PA_FP_WEBADI_P_CUSTOM_V is defined over a single referenced base object: the view PA_FP_WEBADI_PERIODIC_V. The custom view is therefore a projection and re-ordering layer, not a direct table reader. Its defining text selects the columns listed above from PA_FP_WEBADI_PERIODIC_V and applies an ORDER BY clause on TASK_DISPLAY_SEQUENCE, RESOURCE_NAME, UNIT_OF_MEASURE, TXN_CURRENCY_CODE, and AMOUNT_TYPE_NAME, so the exported spreadsheet is presented in a stable, human-readable sequence. Because the customization is applied at this view level, the underlying periodic view and its own base tables can be upgraded by Oracle without disturbing customer-specific spreadsheet layouts.

Key Columns

Common Use Cases and Queries

Typical usage is to validate or troubleshoot the data that will populate the Excel download, or to build a custom query that mirrors the download output. For example, to inspect the planning window and a representative period amount:

  • SELECT project_name, task_number, resource_name, planning_start_date, planning_end_date, amount_type_name, txn_currency_code, prd1, prd2 FROM apps.pa_fp_webadi_p_custom_v WHERE planning_end_date >= SYSDATE ORDER BY task_display_sequence, resource_name;
  • Filter by version to review a specific download: WHERE budget_version_id = :p_version_id AND fin_plan_preference_code = :p_pref;
  • Reconcile deleted lines: WHERE delete_flag = 'Y';

Because the ORDER BY is embedded in the view definition, custom queries generally return rows pre-sorted by task, resource, UOM, currency, and amount type, matching the spreadsheet layout expected by planners.