Results for “fv_budgets_with_dates_v”

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

Overview

The FV_BUDGETS_WITH_DATES_V view is a Federal Financials (FV) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes budget definition information from General Ledger alongside derived start and end dates, allowing budget records to be reported against actual calendar periods rather than only against period names. The view joins budget headers and budget versions to GL_PERIOD_STATUSES twice: once to resolve the first valid period name into a START_DATE, and once to resolve the last valid period name into an END_DATE. As a result, consumers obtain a date-bounded view of each budget/version combination, which is essential for time-sensitive reporting, audit trails, and integration extracts where period names alone are insufficient. The view is especially relevant to Federal Financials implementations, where budget control, budget journals, and period-level validity are audited closely.

Underlying Base Objects

The view is defined over three base objects, all referenced through APPS synonyms: GL_BUDGETS, GL_BUDGET_VERSIONS, and GL_PERIOD_STATUSES. GL_BUDGETS provides the budget header attributes (name, type, ledger, first and last valid periods, latest opened year, the require budget journals flag, and status). GL_BUDGET_VERSIONS supplies BUDGET_VERSION_ID and is joined to GL_BUDGETS on both BUDGET_NAME and BUDGET_TYPE, producing one row per budget version. GL_PERIOD_STATUSES is joined for application 101 (General Ledger) and the budget's ledger, using the first and last valid period names as the join keys, to return period start and end dates. The view therefore inherits the referential relationship between budget definitions, their versions, and accounting period calendars defined in GL.

Key Columns

• BUDGET_NAME and BUDGET_TYPE — identify the budget definition within General Ledger.
• BUDGET_VERSION_ID — the specific budget version associated with the budget.
• SET_OF_BOOKS_ID — the ledger identifier, aliased from B.LEDGER_ID.
• FIRST_VALID_PERIOD_NAME and LAST_VALID_PERIOD_NAME — the period name boundaries defined on the budget header.
• LATEST_OPENED_YEAR — the most recent opened fiscal year for the budget.
• REQUIRE_BUDGET_JOURNALS_FLAG — indicates whether budget journals are required for this budget; this column is the field most commonly queried against when users search for require_budget_journals_flag.
• STATUS — the budget status (for example, open or frozen).
• START_DATE and END_DATE — the period start and end dates derived from the first and last valid period names via GL_PERIOD_STATUSES.

Common Use Cases and Queries

Typical uses include identifying budgets that require budget journals, generating date-bounded budget validity reports, and feeding downstream extracts that need ledger and period date context.

• Locating budgets that enforce budget journals:

  SELECT BUDGET_NAME, BUDGET_TYPE, SET_OF_BOOKS_ID, STATUS
  FROM   FV_BUDGETS_WITH_DATES_V
  WHERE  REQUIRE_BUDGET_JOURNALS_FLAG = 'Y';

• Producing a validity window for each budget version:

  SELECT BUDGET_NAME, BUDGET_VERSION_ID, START_DATE, END_DATE
  FROM   FV_BUDGETS_WITH_DATES_V
  WHERE  SET_OF_BOOKS_ID = :ledger_id
  ORDER  BY BUDGET_NAME, BUDGET_VERSION_ID;

• Listing active budgets whose validity window contains a reporting date:

  SELECT BUDGET_NAME, BUDGET_VERSION_ID, START_DATE, END_DATE
  FROM   FV_BUDGETS_WITH_DATES_V
  WHERE  :report_date BETWEEN START_DATE AND END_DATE;

Because the view encapsulates the period-name-to-date resolution, reporting and integration logic avoids repeating the GL_PERIOD_STATUSES joins. Organizations should confirm that the required first and last valid period names exist in GL_PERIOD_STATUSES, since missing period status rows can exclude a budget/version combination from the results.