Search Results gl_budget_dependent_amts_v




Overview
Explore in AI Chat

Overview

GL_BUDGET_DEPENDENT_AMTS_V is an Oracle EBS General Ledger view owned by the APPS schema. Per its ETRM documentation, its stated description is "10SC ONLY," and the header comment embedded in the view text ($HEADER: GLGVWREG.LDT 120.29.12020000.1 2012/06/27) identifies its originating library file and the source version from which it was generated. The view is reported as VALID in the ETRM metadata for both 12.1.1 and 12.2.2.

The view presents budget balances at the detail level of a dependent (child) budget version, aggregated across the code combination, currency, and period dimensions, and then translated into the "detail" amount format used by Oracle's budget inquiry screens. It accomplishes this by self-joining GL_BALANCES: one alias (B1) supplies master budget version context, and the second alias (B2) supplies the actual measure columns. Its primary role is to support budget inquiry forms and any reporting that needs PTD, QTD, YTD, and project-to-date derived amounts for a budget version linked to a master budget version.

Underlying Base Objects

  • GL_BALANCES (via synonym) — joined twice as B1 and B2. B1 provides the master budget version identifier, period, code combination, and currency used as the aggregation key. B2 provides the raw balance amounts (PERIOD_NET_DR/CR, QUARTER_TO_DATE_DR/CR, BEGIN_BALANCE_DR/CR, PROJECT_TO_DATE_DR/CR). Both aliases are restricted to ACTUAL_FLAG = 'B', which is the budget balance flag in GL_BALANCES.
  • GL_BUDGET_VERSIONS (via synonym) — provides the mapping between a budget version and its control (master) budget version. The join B1.BUDGET_VERSION_ID = BV.CONTROL_BUDGET_VERSION_ID and BV.BUDGET_VERSION_ID = B2.BUDGET_VERSION_ID is what establishes the master/dependent relationship the view exposes.
  • BUDGET_INQUIRY_PKG (package) — supplies the function GET_FACTOR, invoked in every measure expression to normalize the derived amounts for inquiry presentation.

Key Columns

  • MASTER_BUDGET_VERSION_ID — the control budget version identifier from B1, identifying the master version against which the dependent amounts are reported.
  • LEDGER_ID, PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM — the ledger and accounting period context for the balances.
  • CODE_COMBINATION_ID — the accounting flexfield combination to which the amounts apply.
  • CURRENCY_CODE — the currency of the reported amounts; B1 and B2 must agree on currency for the join to succeed.
  • TEMPLATE_ID — the budget template associated with the balance row.
  • PTD_DETAIL_AMOUNT — net period activity: (PERIOD_NET_DR − PERIOD_NET_CR) / GET_FACTOR.
  • QTD_DETAIL_AMOUNT — quarter-to-date: QUARTER_TO_DATE_DR − QUARTER_TO_DATE_CR + PERIOD_NET_DR − PERIOD_NET_CR, divided by the factor.
  • YTD_DETAIL_AMOUNT — year-to-date: BEGIN_BALANCE_DR − BEGIN_BALANCE_CR + PERIOD_NET_DR − PERIOD_NET_CR, divided by the factor. This is the derived measure most closely associated with the search term begin_balance_dr: the BEGIN_BALANCE_DR column in GL_BALANCES feeds the YTD calculation, while BEGIN_BALANCE_CR is subtracted, and the net period activity is added before dividing by GET_FACTOR.
  • PJTD_DETAIL_AMOUNT — project-to-date: PROJECT_TO_DATE_DR − PROJECT_TO_DATE_CR + PERIOD_NET_DR − PERIOD_NET_CR, divided by the factor.

All measure columns are wrapped in NVL(..., 0) to treat missing balance components as zero, and the view aggregates using SUM with a GROUP BY over the non-measure columns.

Common Use Cases and Queries

The view is typically queried when a report or inquiry needs budget-versus-dependent-version detail amounts in the standard PTD/QTD/YTD/PJTD layout, expressed through the same factor normalization used by the Budget Inquiry form.

SELECT master_budget_version_id, ledger_id, period_name,
       code_combination_id, ptd_detail_amount, ytd_detail_amount
FROM   gl_budget_dependent_amts_v
WHERE  ledger_id = :ledger_id
AND    period_name = :period_name
AND    code_combination_id = :ccid;

Because YTD_DETAIL_AMOUNT derives from BEGIN_BALANCE_DR less BEGIN_BALANCE_CR plus net period activity, a typical reconciliation query compares the view's YTD output with the corresponding GL_BALANCES rows for the same budget version:

SELECT b.code_combination_id, b.period_name,
       (NVL(b.begin_balance_dr,0) - NVL(b.begin_balance_cr,0)
        + NVL(b.period_net_dr,0) - NVL(b.period_net_cr,0)) raw_ytd,
       v.ytd_detail_amount view_ytd
FROM   gl_balances b, gl_budget_dependent_amts_v v
WHERE  b.code_combination_id = v.code_combination_id
AND    b.period_name = v.period_name
AND    b.actual_flag = 'B';

Differences between raw_ytd and view_ytd reflect the division applied by BUDGET_INQUIRY_PKG.GET_FACTOR, which is expected behavior and should be accounted for in any reconciliation logic.