Results for “gl_budgets_control_budgets_v”

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

Overview

The GL_BUDGETS_CONTROL_BUDGETS_V view is an Oracle E-Business Suite General Ledger (GL) reporting object owned by the APPS schema. It is documented as "10SC ONLY," indicating that it is a specialized utility view rather than a general-purpose budgeting interface used across all operating units. The view exposes the association between a budget version and its controlling budget version, along with the descriptive name of that controlling (detail) budget. Its primary purpose is to resolve the parent/child relationship that governs budgetary control hierarchies, allowing reports and integrations to identify which budget version controls another without navigating the underlying version tables directly.

The presence of the DETAIL_BUDGET_NAME column makes the view particularly relevant to users searching for that identifier, since it surfaces the human-readable name of the controlling budget alongside the numeric keys required for programmatic joins.

Underlying Base Objects

The view is defined over three base sources, all referenced through APPS synonyms. The ETRM documentation lists GL_BUDGETS and GL_BUDGET_VERSIONS as the referenced base objects. The view text shows GL_BUDGET_VERSIONS referenced twice, aliased as BV1 and BV2:

• GL_BUDGETS BUD — supplies ledger, status, and period-range attributes through the join on BUD.BUDGET_NAME = BV1.BUDGET_NAME.
• GL_BUDGET_VERSIONS BV1 — the primary budget version, joined to the budget name.
• GL_BUDGET_VERSIONS BV2 — the controlling detail budget version, outer-joined via BV1.BUDGET_VERSION_ID = BV2.CONTROL_BUDGET_VERSION_ID (+). The outer join ensures budget versions that have no controlling parent are still returned.

Key Columns

• BUDGET_NAME — the name of the budget associated with the primary version.
• BUDGET_VERSION_ID — the unique identifier of the primary budget version (BV1).
• DETAIL_BUDGET_NAME — the name of the controlling/detail budget (BV2), the column of principal interest.
• DETAIL_BUDGET_VERSION_ID — the version identifier of the controlling detail budget.
• CONTROL_BUDGET_VERSION_ID — the control budget version key linking the two versions.
• LEDGER_ID — the ledger to which the budget belongs.
• STATUS — the budget status (for example, open or frozen).
• FIRST_VALID_PERIOD_NAME / LAST_VALID_PERIOD_NAME — the valid period boundaries of the budget.
• LATEST_OPENED_YEAR — the most recent open accounting year for the budget.

Common Use Cases and Queries

Typical uses include reconciling control budget hierarchies, verifying that a budget version points to the correct detail budget, and feeding downstream reporting that must display the controlling budget name. A representative query follows:

• Find all versions and their controlling detail budget names: SELECT budget_name, budget_version_id, detail_budget_name, detail_budget_version_id, ledger_id FROM apps.gl_budgets_control_budgets_v WHERE ledger_id = :p_ledger_id;
• Isolate versions with no controlling parent (the outer join returns NULLs): SELECT budget_name, budget_version_id FROM apps.gl_budgets_control_budgets_v WHERE detail_budget_version_id IS NULL;
• Search by the detail budget name: SELECT budget_name, detail_budget_name FROM apps.gl_budgets_control_budgets_v WHERE detail_budget_name = :p_detail_budget_name;

Because the view is flagged "10SC ONLY," it should be treated as a specialized or legacy object; new development should confirm availability for the target release before relying on it in production reporting.