Results for “preceding_periods_amount”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.PA_FIN_PLAN_ADJ_TOTAL_V view is a reporting object within the Oracle Projects (PA) module of Oracle E-Business Suite, available in both release 12.1.1 and 12.2.2. It presents the total adjusted financial plan amounts, broken down by accounting period, for a single adjustment reason. The view is defined with a status of VALID and is owned by the APPS schema.

Its primary role is to support the Financial Plan adjustment reporting and integration layer. Rather than exposing isolated adjustment line details, the view aggregates period-level adjusted amounts and rolls them into subtotal and grand total columns, enabling reporting tools, concurrent programs, and downstream integrations to consume pre-summarized adjustment figures. The view is inherently context-driven: its definition invokes PA_FIN_PLAN_VIEW_GLOBAL.GET_VERSION_ID(), meaning it returns data scoped to the budget version currently selected in the Financial Plan global package context. This design makes it a session-dependent reporting view rather than a standalone persistent dataset.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects for PA_FIN_PLAN_ADJ_TOTAL_V:

• PA_FP_PERIOD_VALUES_V (VIEW) — Supplies the period-level amounts. Aliased as A in the view text, it contributes the PRECEDING_PERIODS_AMOUNT, SUCCEEDING_PERIODS_AMOUNT, and PERIOD_AMOUNT1 through PERIOD_AMOUNT13 columns.
• PA_AMOUNT_TYPES_VL (VIEW) — Referenced twice, as aliases B and D. The B instance provides the primary amount type attributes and filters on PLAN_ADJUSTABLE_FLAG = 'Y'; the D instance resolves the adjustment subtype code and filters on PLAN_ADJ_AMOUNT_FLAG = 'Y'.
• PA_FIN_PLAN_VIEW_GLOBAL (PACKAGE) — Not a data source but a controlling package. The view joins on GET_VERSION_ID() to constrain rows to the active budget version.
• PA_RESOURCE_ASSIGNMENTS (SYNONYM) — Aliased as E, it anchors the assignment context, filtered to RESOURCE_ASSIGNMENT_TYPE = 'PROJECT'.

The joins bind A.BUDGET_VERSION_ID and E.BUDGET_VERSION_ID to the package context and link amount types by AMOUNT_TYPE_CODE, with the second amount type lookup keyed on AMOUNT_TYPE_CODE||'_ADJ' as AMOUNT_SUBTYPE_CODE.

Key Columns

• AMOUNT_TYPE_ID, AMOUNT_TYPE_NAME, AMOUNT_TYPE_CODE — Identity and descriptive attributes of the base amount type.
• AMOUNT_SUBTYPE_CODE — Derived as AMOUNT_TYPE_CODE concatenated with '_ADJ', marking the adjustment variant.
• PRECEDING_PERIODS_AMOUNT, SUCCEEDING_PERIODS_AMOUNT — Adjusted amounts attributed to periods outside the current plan horizon.
• PERIOD_AMOUNT1 … PERIOD_AMOUNT13 — Period-by-period adjusted amounts, each wrapped in NVL(...,0) to guarantee non-null numeric output.
• TOTAL — The sum of PERIOD_AMOUNT1 through PERIOD_AMOUNT6, providing a first-half subtotal.
• TOTAL_PA — The sum of all thirteen period amounts, representing the full periodic total.

Common Use Cases and Queries

Typical scenarios include reconciling financial plan adjustments, feeding period-based adjustment totals into custom reports, and validating that adjustment amounts tie to plan amounts.

• Retrieve all adjustment totals for the active plan version:
  SELECT amount_type_code, amount_subtype_code, total, total_pa FROM apps.pa_fin_plan_adj_total_v;
• List detailed period amounts for a single adjustment reason:
  SELECT amount_type_code, period_amount1, period_amount2, period_amount3, total_pa FROM apps.pa_fin_plan_adj_total_v WHERE amount_type_code = :p_amount_type;
• Identify adjustment reasons carrying non-zero totals:
  SELECT amount_type_name, total_pa FROM apps.pa_fin_plan_adj_total_v WHERE total_pa <> 0 ORDER BY total_pa DESC;

Because results depend on PA_FIN_PLAN_VIEW_GLOBAL.GET_VERSION_ID(), queries should be executed within a session where the intended budget version context has already been established, ensuring the returned adjustment totals correspond to the correct financial plan version.