Search Results begin_headcount

Overview

The PA_FP_VIEW_BY_COMP_V view is an Oracle Projects (PA) reporting object owned by the APPS schema. It presents forecast amounts organized by accounting period for a single amount type, exposing one row per amount subtype together with its per-period distribution. Its principal role is to support financial planning and forecasting inquiries in Oracle EBS 12.1.1 and 12.2.2, particularly where a user must analyze how a specific amount subtype — for example, HEADCOUNT_ADJUSTMENTS, BEGIN_HEADCOUNT, UTILIZATION_ADJUSTMENTS, or UTILIZATION_PERCENT — accumulates across a defined range of periods. Because the view derives several of its most important figures through calls to the PA_FP_ORG_FCST_UTILS package, it effectively pre-computes PA and GL forecast totals that would otherwise require custom PL/SQL logic. This makes the view a convenient integration and reporting surface for forecasts sourced from the Projects financial planning engine.

Underlying Base Objects

The view's documented dependencies are PA_AMOUNT_TYPES_VL, PA_FIN_PLAN_VIEW_GLOBAL, PA_FP_ORG_FCST_UTILS, PA_FP_PERIOD_VALUES_V, and PA_LOOKUPS. The visible view text references two aliases that map to these objects: PATL supplies the descriptive amount type through PA_AMOUNT_TYPES_VL (providing AMOUNT_TYPE_NAME, surfaced as AMOUNT_SUBTYPE_NAME), while PPPD provides the stored period values, likely sourced via PA_FP_PERIOD_VALUES_V. The columns PRECEDING_PERIODS_AMOUNT, SUCCEEDING_PERIODS_AMOUNT, PERIOD_AMOUNT1 through PERIOD_AMOUNT13, AMOUNT_SUBTYPE_CODE, and AMOUNT_SUBTYPE_ID originate from this period data. PA_FP_ORG_FCST_UTILS is invoked as the calculation engine for derived PA and GL amounts, and PA_LOOKUPS and PA_FIN_PLAN_VIEW_GLOBAL provide auxiliary lookups and plan context. The AMOUNT_SUBTYPE_CODE column is the key translation point: the view's DECODE logic branches on it to decide whether a derived calculation or a simple period sum is returned.

Key Columns

• AMOUNT_SUBTYPE_CODE — the indicator that drives the view's conditional logic; the searched term. Values such as HEADCOUNT_ADJUSTMENTS, BEGIN_HEADCOUNT, UTILIZATION_ADJUSTMENTS, and UTILIZATION_PERCENT trigger package-based calculations.
• AMOUNT_SUBTYPE_NAME — the descriptive name from PA_AMOUNT_TYPES_VL (aliased from AMOUNT_TYPE_NAME).
• AMOUNT_SYBTYPE_ID — the subtype identifier (note the documented spelling in the view text).
• PRECEDING_PERIODS_AMOUNT / SUCCEEDING_PERIODS_AMOUNT — cumulative forecasts before and after the modeled period window.
• PERIOD1 through PERIOD13 — the per-period forecast amounts.
• TOTAL_PA — a DECODE result: either a calculated PA amount for the four special subtypes, or the sum of PERIOD1..PERIOD13 with NVL defaulting to zero.
• Derived GL amounts — calculated via PA_FP_ORG_FCST_UTILS.CALCULATE_GL_AMOUNT for the same special subtypes, mirroring the TOTAL_PA logic.

Common Use Cases and Queries

A typical query isolates one amount subtype and reports its period distribution and totals.

SELECT amount_subtype_code, amount_subtype_name, preceding_periods_amount, succeeding_periods_amount, period1, period2, total_pa FROM apps.pa_fp_view_by_comp_v WHERE amount_subtype_code = 'HEADCOUNT_ADJUSTMENTS';

Because the view returns one row per subtype, filtering on AMOUNT_SUBTYPE_CODE is the standard access path. Analysts also aggregate the period columns to reconcile forecast totals, or compare TOTAL_PA against the sum of PERIOD1..13 for ordinary subtypes, since the NVL-wrapped addition prevents null propagation. The view is appropriate for ad hoc reporting, custom concurrent programs, and integration extracts where forecast-by-component detail is required.