Results for “gl_budgets_name_v”

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

Overview

GL_BUDGETS_NAME_V is a General Ledger (GL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Per the ETRM documentation, it carries a status of VALID and is annotated with the restriction 10SC ONLY. The view presents budget definition and budget version information in a single, denormalized result set, joining the budget header definition to its associated budget versions. Its principal role is to provide reporting and integration consumers with a stable, readable projection of budget metadata — budget name, ledger assignment, budget status, description, the latest opened accounting year, and the REQUIRE_BUDGET_JOURNALS_FLAG attribute that controls whether budget journals are mandatory for that budget.

The search term associated with this object, require_budget_journals_flag, identifies the view column that is most frequently queried by implementers auditing budget journal control settings. Rather than joining GL_BUDGETS to GL_BUDGET_VERSIONS directly, the view allows a single SELECT against a pre-joined object.

Underlying Base Objects

The view is defined over two documented base objects, both exposed as APPS synonyms:

• GL_BUDGETS — the budget definition (header) table, aliased as B in the view text.
• GL_BUDGET_VERSIONS — the budget version table, aliased as BV in the view text.

The view text is:

• SELECT B.BUDGET_NAME BUDGET_NAME, BV.BUDGET_VERSION_ID BUDGET_VERSION_ID, B.LEDGER_ID LEDGER_ID, B.STATUS STATUS, B.REQUIRE_BUDGET_JOURNALS_FLAG REQUIRE_BUDGET_JOURNALS_FLAG, B.DESCRIPTION DESCRIPTION, B.LATEST_OPENED_YEAR LATEST_OPENED_YEAR FROM GL_BUDGETS B, GL_BUDGET_VERSIONS BV WHERE BV.BUDGET_NAME = B.BUDGET_NAME

The join condition is BV.BUDGET_NAME = B.BUDGET_NAME. This means the view produces one row for each budget version belonging to a budget name. Because the join is expressed only on BUDGET_NAME, all columns sourced from B (LEDGER_ID, STATUS, REQUIRE_BUDGET_JOURNALS_FLAG, DESCRIPTION, LATEST_OPENED_YEAR) repeat for each matching budget version row.

Key Columns

• BUDGET_NAME — the unique name assigned to the budget definition; also the join key to GL_BUDGET_VERSIONS.
• BUDGET_VERSION_ID — the surrogate identifier of the budget version row in GL_BUDGET_VERSIONS.
• LEDGER_ID — the ledger (formerly set of books) to which the budget is assigned.
• STATUS — the budget status, typically reflecting whether the budget is open, frozen, or otherwise inactive.
• REQUIRE_BUDGET_JOURNALS_FLAG — the flag indicating whether budget journals are required for entries to this budget. When enabled, budget amounts cannot be entered directly and must be posted through budget journals.
• DESCRIPTION — the free-text description defined on the budget.
• LATEST_OPENED_YEAR — the most recent accounting year that has been opened for the budget.

Common Use Cases and Queries

The primary scenario is auditing budget journal control across ledgers. The following query lists budgets that require budget journals:

• SELECT BUDGET_NAME, LEDGER_ID, STATUS, REQUIRE_BUDGET_JOURNALS_FLAG, LATEST_OPENED_YEAR FROM APPS.GL_BUDGETS_NAME_V WHERE REQUIRE_BUDGET_JOURNALS_FLAG = 'Y' ORDER BY BUDGET_NAME;

A second scenario retrieves version-level detail for a specific budget:

• SELECT BUDGET_NAME, BUDGET_VERSION_ID, DESCRIPTION, STATUS FROM APPS.GL_BUDGETS_NAME_V WHERE BUDGET_NAME = :p_budget_name;

Because the view exposes LEDGER_ID, it also supports ledger-scoped reporting, for example listing all budgets and their latest opened year for a given ledger. When consuming the view, note that the 10SC ONLY annotation indicates the object is restricted in scope, and results repeat header-level attributes across budget versions.