Results for “gl_budgets_with_dates_v”

20 results




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

Overview

GL_BUDGETS_WITH_DATES_V is an APPS-owned database view in the Oracle E-Business Suite General Ledger (GL) module. It is documented in ETRM as valid and marked with the description "10SC ONLY," indicating it was introduced or reserved for a specific 10SC (ten-segment chart / operating unit configuration) implementation context rather than as a broadly published, customer-facing object. The view extends the base budget definitions stored in GL_BUDGETS by resolving the first and last valid period names of each budget into concrete calendar dates.

Its role in reporting and integration is to provide a date-enriched, denormalized rendering of budget version metadata. Consumers who need the effective start and end dates of a budget — for example, when reconciling budget-to-actual reports over a date range, or when feeding budget metadata into downstream extracts — can query this view instead of joining GL_BUDGETS to GL_PERIOD_STATUSES twice themselves. The view abstracts away the two-period join and the fixed APPLICATION_ID = 101 filter that identifies General Ledger period status rows.

Underlying Base Objects

The view is defined over three referenced base objects, all exposed to APPS as synonyms:

The view therefore flattens a four-way relational structure (budgets, versions, and two period-status lookups) into a single row per budget version.

Key Columns

  • BUDGET_NAME — the name of the budget definition, carried from GL_BUDGETS.
  • BUDGET_TYPE — the budget type classification, carried from GL_BUDGETS.
  • BUDGET_VERSION_ID — the surrogate identifier of the budget version, from GL_BUDGET_VERSIONS.
  • SET_OF_BOOKS_ID — the ledger identifier, aliased from B.LEDGER_ID. Note that in 12.1.1/12.2.2 this aligns with the LEDGER_ID concept.
  • FIRST_VALID_PERIOD_NAME — the earliest period in which the budget is valid.
  • LAST_VALID_PERIOD_NAME — the latest period in which the budget is valid.
  • STATUS — the budget status flag.
  • START_DATE — the start date of the first valid period, derived via START_PER.
  • END_DATE — the end date of the last valid period, derived via DEST_PER.

The "dest_per" token in the user's search corresponds directly to the DEST_PER alias in the view text, which is the join that produces the END_DATE value.

Common Use Cases and Queries

Typical uses include identifying budgets active within a user-supplied date window, validating that a budget version's effective range covers a reporting period, and producing extracts of budget metadata with human-readable dates rather than period names.

Sample query returning active budgets overlapping a date range:

  • SELECT budget_name, budget_type, set_of_books_id, start_date, end_date FROM apps.gl_budgets_with_dates_v WHERE start_date <= :p_end_date AND end_date >= :p_start_date ORDER BY set_of_books_id, budget_name;

Sample query listing budgets for a specific ledger:

  • SELECT budget_name, first_valid_period_name, last_valid_period_name, start_date, end_date FROM apps.gl_budgets_with_dates_v WHERE set_of_books_id = :p_ledger_id;

Because the view is documented as 10SC ONLY, its availability and support may be restricted to that configuration; implementers should confirm the object exists in their environment before relying on it in custom code or reports.