Search Results fixed_date




Overview
Explore in AI Chat

Overview

PA_FP_WEBADI_CONTENTS_V is an APPS-owned view within the Oracle E-Business Suite Projects (PA) module. Its documented purpose is to supply the dataset that is downloaded into an Excel worksheet for Financial Planning through the WebADI (Web Application Desktop Integrator) framework. In other words, it is the read-side extract that populates the integrated spreadsheet a planner uses to review and maintain project financial plan amounts.

The view is delivered with a VALID status in both 12.1.1 and 12.2.2, and its definition is identical across those releases from a functional standpoint. It resides in the APPS schema and, as is standard for EBS views of this class, is exposed to end users through grants and synonyms rather than being referenced by fully qualified name. The WebADI integrator defined for Financial Planning calls this view, applies its own column mapping, and renders the result set into the desktop Excel layout.

The data model reflects the periodic nature of project financial planning. Rather than storing a variable number of periods as rows, the view projects a fixed, wide block of period amount columns (PERIOD_AMOUNT1 through PERIOD_AMOUNT52), which aligns with the calendar structure configured for the plan and allows the WebADI template to map each spreadsheet column to a stable database column.

Underlying Base Objects

The documented base objects underlying PA_FP_WEBADI_CONTENTS_V span the budget, resource, task, and lookup areas of the Projects schema, together with several PL/SQL packages and a profile dependency.

Because so many of the referenced objects are synonyms, the view is sensitive to the standard EBS synonym and grant setup; customizations that alter those synonyms or revoke privileges on the underlying plan tables will surface as errors when the WebADI download runs.

Key Columns

Several trailing expressions in the view text are explicitly typed NULL placeholders (TO_DATE(NULL), TO_NUMBER(NULL), NULL), which reserve column positions for the WebADI template without carrying data.

Common Use Cases and Queries

The view is used almost exclusively as the WebADI download source for Financial Planning, but it can also be queried directly for troubleshooting, for building custom extracts, or for validating what a planner will see in the spreadsheet.

  • Diagnosing why a plan downloads incorrectly, by inspecting row counts and amount values for a specific plan version.
  • Building ad hoc reporting on planned periodic amounts beyond the standard WebADI template.
  • Comparing amounts held in the plan against the assignment and task context columns.

A representative query:

SELECT budget_version_id, name, task_number, amount_type_code, currency_code, period_amount1, period_amount2 FROM apps.pa_fp_webadi_contents_v WHERE budget_version_id = :p_version_id;

To examine amount types and units for one plan line:

SELECT resource_assignment_id, amount_type_name, amount_subtype_code FROM apps.pa_fp_webadi_contents_v WHERE budget_version_id = :p_version_id ORDER BY amount_type_name;

Because the view performs DECODE-based derivations and reads from denormalized plan tables, it is best treated as a read-only reporting surface. Direct DML against the view is neither supported nor advisable; changes to plan amounts should flow through the supported Financial Planning WebADI upload path, which uses the corresponding integrator and API rather than this view.