Search Results total_pa




Overview
Explore in AI Chat

Overview

APPS.PA_FINPLAN_VIEW_BY_COMP_V is a reporting view within the Oracle E-Business Suite Projects (PA) module that presents financial plan amounts organized by amount subtype, distributed horizontally across a defined set of accounting periods. It is a filtered derivative of the lower-level view PA_FP_VIEW_BY_COMP_V, inheriting its period-bucketed column structure while restricting the result set to a curated subset of amount subtypes. Rather than exposing raw transaction-level financial plan data, the view aggregates balances into period1 through period13 columns and augments each row with cumulative "preceding" and "succeeding" period amounts.

The name of the view — "BY_COMP" — reflects that it is designed for comparison-oriented reporting, where each amount subtype row can be evaluated across a period range and against the totals that precede or follow the displayed window. This makes it well suited to budget-versus-actual analysis, forecast run-rate reporting, and any integration that consumes period-spread financial plan figures in a tabular form. The view is owned by the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2.

Underlying Base Objects

Per the ETRM metadata, the documented base objects referenced by this view are:

  • PA_FP_VIEW_BY_COMP_V (VIEW) — the immediate parent view from which all columns are projected. PA_FINPLAN_VIEW_BY_COMP_V adds no joins of its own; it is a thin projection and filter layer.
  • PA_FIN_PLAN_VIEW_GLOBAL (PACKAGE) — the package supplying the core financial plan retrieval and period-distribution logic consumed by the underlying view chain.
  • PA_FP_ORG_FCST_UTILS (PACKAGE) — utility package providing organizational and forecast-related helper logic used in constructing the period-based results.

The view therefore does not query base tables such as PA_BUDGET_VERSIONS directly. Its behavior is a function of the parent view and the two packages, which together resolve amount subtype definitions, period ranges, and the derivation of preceding and succeeding period totals.

Key Columns

  • AMOUNT_SUBTYPE_ID / AMOUNT_SUBTYPE_CODE / AMOUNT_SUBTYPE_NAME — identify the financial plan amount subtype (for example, cost, revenue, or burden categories). The view is ordered by AMOUNT_SUBTYPE_ID.
  • PRECEDING_PERIODS_AMOUNT — the summed amount for periods occurring before the reporting window. Wrapped in NVL(...,0) so that absent values are returned as zero. This is the column the user searched for and is central to cumulative and comparative analysis.
  • SUCCEEDING_PERIODS_AMOUNT — the summed amount for periods after the reporting window, likewise defaulted to zero.
  • PERIOD1 … PERIOD13 — the horizontal spread of amounts across up to thirteen accounting periods, each NVL-protected.
  • TOTAL_PA — the Projects-application total for the amount subtype row.
  • TOTAL — the overall total for the amount subtype row.

The WHERE clause excludes AMOUNT_SUBTYPE_CODE values of 'CAPACITY' and 'UTILIZATION_HOURS', ensuring that only monetary or otherwise comparable subtypes are returned. This filtering distinguishes PA_FINPLAN_VIEW_BY_COMP_V from its parent view.

Common Use Cases and Queries

Typical uses include generating period-spread financial plan reports, reconciling budget versus forecast by subtype, and feeding downstream integrations or extracts that require a fixed-width period layout.

Retrieving all subtypes with their preceding-period opening balance:

  • SELECT amount_subtype_name, preceding_periods_amount, succeeding_periods_amount, total_pa, total FROM apps.pa_finplan_view_by_comp_v ORDER BY amount_subtype_id;

Isolating a single subtype and its period distribution:

  • SELECT amount_subtype_code, period1, period2, period3, total FROM apps.pa_finplan_view_by_comp_v WHERE amount_subtype_code = 'COST';

Comparing the opening and closing cumulative positions:

  • SELECT amount_subtype_name, preceding_periods_amount, total, succeeding_periods_amount FROM apps.pa_finplan_view_by_comp_v WHERE preceding_periods_amount > 0;

Because the view applies NVL defaults, consumers can safely aggregate the period columns without null handling. Access should be granted through the APPS schema or an appropriate synonym, and reporting responsibility security should be observed when exposing results.