Results for “glfv_gl_budgets”

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

Overview

GLFV_GL_BUDGETS is a General Ledger (GL) view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes budget definition and version information. In Oracle GL, a budget is a collection of estimated amounts spanning a defined range of accounting periods for a specific ledger. The view presents one row per budget-version combination, joining the parent budget definition (GL_BUDGETS) to its versions (GL_BUDGET_VERSIONS) and the owning ledger (GL_LEDGERS).

The "F" in the view name follows Oracle's convention for a Foreign or Form-based view, and the name is significant for users who search for "gl_budget_version" terminology: the view is the primary reporting surface where budget definitions and their associated version identifiers are reconciled together. It is commonly consumed by budget inquiry, budget transfer, and reconciliation reporting, and by integration routines that need a consolidated picture of budget status, validity windows, and journal-control flags without navigating the normalized base tables directly.

Underlying Base Objects

The view is defined over three base objects joined on ledger and budget identifiers:

• GL_BUDGETS (GL_BUDGET) — the budget definition, supplying BUDGET_NAME, LEDGER_ID, BUDGET_TYPE, status, description, date created, date closed, first/last valid period names, latest opened year, and the require-budget-journals flag. Joins to GL_LEDGERS on LEDGER_ID, and to GL_BUDGET_VERSIONS on BUDGET_NAME and BUDGET_TYPE.
• GL_LEDGERS (GL_LEDGERS) — the ledger master, supplying the ledger name. Joined on GL_BUDGET.LEDGER_ID = GL_LEDGERS.LEDGER_ID.
• GL_BUDGET_VERSIONS (GL_BUDGET_VERSION) — the budget version header, supplying BUDGET_VERSION_ID. Joined on matching budget name and budget type.

The documented view text applies row security through the ledger clause ('_SEC:GL:GL_BUDGET.LEDGER_ID' IS NOT NULL) and is declared WITH READ ONLY, so it cannot be used for DML. The ETRM metadata notes that this view is not implemented in the search database and documents no referenced base objects, but the extracted view text confirms the dependency set above.

Key Columns

• BUDGET_VERSION_ID — the unique identifier of the budget version; the primary key column returned by the view.
• BUDGET_NAME — the name of the budget, shared between the budget and version records.
• LEDGER_ID / LEDGER_NAME — the ledger that owns the budget and its display name.
• "_LA:STATUS" — the decoded status meaning, resolved from the GL_LOOKUPS lookup type "PLAN/VERSION STATUS".
• DATE_CREATED / DATE_FROZEN — creation date of the budget and the date the budget (or a version) was frozen.
• FIRST_BUDGET_PERIOD / LAST_BUDGET_PERIOD — the first and last accounting period for which the budget is valid.
• LATEST_OPENED_YEAR — the most recent year still open for the budget.
• "_LA:REQUIRE_BUDGET_JE_FLAG" — the decoded YES/NO flag indicating whether budget journals are required before balances can change.
• DESCRIPTION — free-text description of the budget.
• _DF — a descriptive flexfield column carrying the budget's DFF segment values.

Common Use Cases and Queries

The view is typically used to enumerate budget versions per ledger, to check status and journal-control behavior before posting, and to confirm the valid period range for budget entry. A representative query follows:

SELECT budget_version_id, budget_name, ledger_name,
       "_LA:STATUS" AS status_meaning,
       first_budget_period, last_budget_period,
       latest_opened_year, "_LA:REQUIRE_BUDGET_JE_FLAG" AS require_je
FROM   glfv_gl_budgets
WHERE  ledger_id = :p_ledger_id
ORDER  BY budget_name;

Typical scenarios include: (1) validating that a version exists before budgeting, since a budget must have at least one version; (2) filtering to only open versions for budget entry; and (3) identifying budgets whose require-journals flag is set for posting control. Because the join uses budget name and type, duplicates can appear if multiple versions share the same name; adding version-specific predicates, or joining to GL_BUDGET_PERIODS for amounts, refines the result. The read-only nature and ledger-based row security make the view safe for reporting, though write operations must target the base tables.