Search Results gl_budget

Overview

APPS.GLBV_GL_BUDGETS is a read-only Oracle E-Business Suite view that presents General Ledger budget definitions alongside their associated budget versions. It is a Business Intelligence (BI) style view, delivered in the APPS schema and exposed as a reporting and integration surface rather than as a transactional object. The view answers the recurring functional question of how a named budget in General Ledger maps to the versions maintained against it, since in EBS the budget header (GL_BUDGETS) and its individual versions (GL_BUDGET_VERSIONS) are stored separately but are logically linked by budget name and budget type.

Because the user search term "gl_budget_version" points directly at this association, the view is best understood as the join that surfaces a BUDGET_VERSION_ID together with the parent budget attributes. A defining characteristic, evident from the view text, is the predicate '_SEC:GL:GL_BUDGET.LEDGER_ID' IS NOT NULL, which enforces the GL ledger security model so that only budgets for ledgers accessible to the current responsibility or user are returned. The WITH READ ONLY clause confirms that the view cannot be used for DML.

Underlying Base Objects

The view is defined over two base tables in the GL schema:

• GL_BUDGETS (aliased GL_BUDGET) — the budget definition header, holding BUDGET_NAME, BUDGET_TYPE, LEDGER_ID, status, date and period range attributes.
• GL_BUDGET_VERSIONS (aliased GL_BUDGET_VERSION) — the version records, supplying BUDGET_VERSION_ID.

The join predicates are GL_BUDGET.BUDGET_NAME = GL_BUDGET_VERSION.BUDGET_NAME and GL_BUDGET.BUDGET_TYPE = GL_BUDGET_VERSION.BUDGET_TYPE. Notably, the documented metadata lists no referenced base objects, so the tables above are inferred from the view text itself. The join is on name and type rather than on a surrogate key, which reflects the EBS data model where a budget is uniquely identified by the pairing of name and type, and versions are children of that pairing.

Key Columns

• BUDGET_VERSION_ID — the version surrogate key from GL_BUDGET_VERSIONS; the primary identifier for a specific version, and the column most often sought when resolving "gl_budget_version".
• BUDGET_NAME — the name of the parent budget.
• LEDGER_ID — the ledger to which the budget belongs; also the column governed by ledger security.
• STATUS — presented as '_LA:GL_BUDGET.STATUS:GL_LOOKUPS:PLAN/VERSION STATUS:MEANING', a lookup-decoded label for the budget or version status (for example, current versus frozen), resolved through the PLAN/VERSION STATUS lookup type.
• DATE_CREATED / DATE_CLOSED — creation and closure dates of the budget definition.
• FIRST_VALID_PERIOD_NAME / LAST_VALID_PERIOD_NAME — the period range over which the budget is valid.
• LATEST_OPENED_YEAR — the most recent open budget year.
• REQUIRE_BUDGET_JOURNALS_FLAG — decoded via '_LA:GL_BUDGET.REQUIRE_BUDGET_JOURNALS_FLAG:GL_LOOKUPS:YES/NO:MEANING' to a YES/NO meaning, indicating whether budget journals are mandatory.
• DESCRIPTION — the free-text budget description.

Common Use Cases and Queries

The view supports budget-to-version reconciliation, duplicate-version detection, and downstream integration extracts where a stable BUDGET_VERSION_ID is required. A typical query lists all versions for a ledger:

• SELECT budget_version_id, budget_name, ledger_id, status, date_created FROM apps.glbv_gl_budgets WHERE ledger_id = :ledger_id ORDER BY budget_name;
• SELECT budget_name, COUNT(*) FROM apps.glbv_gl_budgets GROUP BY budget_name HAVING COUNT(*) > 1; — identifies budgets carrying multiple versions.
• SELECT budget_version_id, budget_name, first_valid_period_name, last_valid_period_name FROM apps.glbv_gl_budgets WHERE require_budget_journals_flag = 'Yes';

All queries are automatically filtered by GL ledger security; users without access to a ledger receive no rows for it. Because the view is read-only, any maintenance of budgets or versions must be performed through the corresponding GL forms or concurrent programs, not through this object.