Search Results etc_source




Overview

APPS.PA_FP_WEBADI_PERIODIC_V is an Oracle E-Business Suite view in the Projects (PA) module that exposes the staging interface used by Oracle WebADI to load periodic (time-phased) financial plan data into Oracle Projects. It is a thin wrapper view defined over a single base object, PA_FP_WEBADI_XFACE_TMP, and its purpose is to present the interim rows uploaded through a WebADI spreadsheet in a format usable by the Financial Plan periodic upload process, validation logic, and reporting. In Oracle EBS 12.1.1 and 12.2.2 the view retains the same structure, exposing budget version and resource-assignment identifiers, plan-class context, estimate-to-complete (ETC) attributes, rate and currency mapping columns, a preceding-period and succeeding-period amount, and 52 period amount columns (PRD1 through PRD52) that correspond to the accounting periods of a project's financial plan.

Underlying Base Objects

The only documented base object referenced by this view is PA_FP_WEBADI_XFACE_TMP, itself a temporary/interface table where WebADI writes uploaded rows before the Financial Plan periodic loader consumes them. Because the view selects directly from that table without joins, it provides no additional transformation, filtering, or aggregation; it functions as a column-surfacing view. At the synonym level, ETRM records PA_FP_WEBADI_XFACE_TMP as a synonym referenced by the view, meaning the physical table normally resides in the PA schema while the APPS synonym provides the namespace through which the view and concurrent processes access it. Consequently, any row visible through the view corresponds one-to-one with a row currently present in the interface table for the WebADI session or batch being processed.

Key Columns

Common Use Cases and Queries

Typical uses include diagnosing WebADI periodic upload failures, verifying ETC method/source values before loading, and auditing loader input rows before the interface table is purged. A representative query filtering on the ETC source is:

  • SELECT project_number, resource_alias, etc_method, etc_source, preceding_period_amount, succeeding_period_amount FROM apps.pa_fp_webadi_periodic_v WHERE etc_source = :p_source;
  • SELECT budget_version_id, plan_class_code, SUM(prd1 + prd2 + prd3) FROM apps.pa_fp_webadi_periodic_v GROUP BY budget_version_id, plan_class_code;
  • SELECT project_id, resource_assignment_id, delete_flag FROM apps.pa_fp_webadi_periodic_v WHERE delete_flag = 'Y';

Because the view offers no filtering of its own, all restriction and aggregation logic must be applied by the caller, and results always reflect the current contents of the underlying temporary interface table.