Search Results dest_per




Overview
Explore in AI Chat

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

Overview

APPS.GL_BUDGETS_WITH_DATES_V is a reporting view in the Oracle E-Business Suite General Ledger module that enriches budget definitions with the calendar start and end dates corresponding to their valid period ranges. Budget records in the GL_BUDGETS table identify only the first and last valid period names (for example, "JAN-2013" and "DEC-2013"); the view resolves those period names into actual GL calendar dates by joining to GL_PERIOD_STATUSES twice — once for the beginning of the budget range and once for the end.

The view is a critical asset for reporting and integration because it bridges a common usability gap: users and downstream systems typically need to know when a budget window begins and ends in absolute dates rather than EBS period names. It preserves the original budget identity columns while appending START_DATE and END_DATE, making it convenient for BI Publisher reports, Discoverer worksheets, and custom concurrent programs. Because it exposes a stable, denormalized shape, it is also suitable for interfaces feeding planning tools or data warehouses.

Underlying Base Objects

The view is defined over three synonyms that resolve to the core GL base tables:

  • GL_BUDGETS — The primary driver, holding budget_name, budget_type, ledger_id, first_valid_period_name, last_valid_period_name, and status for each budget definition.
  • GL_BUDGET_VERSIONS — Joined on budget_name and budget_type to supply budget_version_id, which uniquely identifies a specific version of a budget.
  • GL_PERIOD_STATUSES — Joined twice (aliased START_PER and DEST_PER), each filtered with application_id = 101 (General Ledger) and ledger_id = b.ledger_id, and matched on the first and last valid period names respectively. The first instance provides START_DATE; the second provides END_DATE.

Because the joins rely on exact period name matches within the same ledger and application, the view only returns budgets whose first and last valid periods exist as open or defined period statuses for that ledger.

Key Columns

  • BUDGET_NAME — The user-defined name of the budget.
  • BUDGET_TYPE — Classifies the budget as a standard GL budget type; combined with budget_name it identifies a logical budget.
  • BUDGET_VERSION_ID — Surrogate key of the specific budget version, sourced from GL_BUDGET_VERSIONS.
  • SET_OF_BOOKS_ID — The ledger_id of the budget (aliased for backward compatibility with set-of-books terminology).
  • FIRST_VALID_PERIOD_NAME / LAST_VALID_PERIOD_NAME — The original period boundaries from GL_BUDGETS.
  • STATUS — The current lifecycle status of the budget (for example, open or frozen).
  • START_DATE / END_DATE — Resolved calendar dates from GL_PERIOD_STATUSES for the first and last valid periods.

Common Use Cases and Queries

The most frequent usage is presenting budget windows with tangible dates for reconciliation and audit reporting. A typical query lists all budgets for a ledger:

  • SELECT budget_name, budget_type, start_date, end_date, status FROM apps.gl_budgets_with_dates_v WHERE set_of_books_id = :ledger_id ORDER BY start_date;

Another common pattern validates that a budget covers a specific period before loading actuals comparison reports:

  • SELECT budget_name, budget_version_id FROM apps.gl_budgets_with_dates_v WHERE start_date <= :report_date AND end_date >= :report_date;

Integration scenarios use the view to populate date attributes in budgeting dashboards or to drive extract programs that need period-independent date ranges. Because it already performs the period-to-date resolution, it removes the need for custom PL/SQL date lookups in calling code, reducing duplication and ensuring consistent results across reporting tools.