Search Results start_per




Overview
Explore in AI Chat

Overview

APPS.GL_BUDGETS_AUTOCOPY_V is a reporting view in the Oracle E-Business Suite General Ledger module that consolidates budget header information with the resolved fiscal period boundaries for each budget. Its principal function is to support the budget autocopy process by presenting, for every eligible budget, the numeric period identifiers that delimit its first and last valid periods. The view expresses period boundaries as period numbers and period years rather than as period names, which is a requirement for the range-based processing performed during budget copy and roll-forward operations.

The view is owned by the APPS schema and is defined over synonyms for the underlying General Ledger tables. It is read-only in nature and does not itself perform the autocopy; rather, it supplies the structured input set that downstream autocopy logic consumes. Because it joins budget definitions to GL_PERIOD_STATUSES, it returns only budgets whose first and last valid period names correspond to actual, defined calendar periods in the ledger, thereby guarding against orphaned or inconsistent budget definitions.

Underlying Base Objects

The view is defined over three documented base objects, all exposed as synonyms owned by APPS:

  • GL_BUDGETS — the budget header table, supplying the budget name, ledger, status, first valid period name, last valid period name, and latest opened year.
  • GL_BUDGET_VERSIONS — the budget version table, supplying the BUDGET_VERSION_ID that uniquely identifies the version being copied.
  • GL_PERIOD_STATUSES — referenced twice under the aliases START_PER and END_PER to resolve the period number and period year of the first and last valid periods respectively.

The join between GL_BUDGETS and GL_BUDGET_VERSIONS is on both budget name and budget type, ensuring the version returned belongs to the correct budget definition. Both GL_PERIOD_STATUSES joins constrain APPLICATION_ID to 101, the General Ledger application identifier, and match on ledger and period name.

Key Columns

  • BUDGET_NAME — the name of the budget, carried from GL_BUDGETS.
  • BUDGET_VERSION_ID — the unique identifier of the budget version from GL_BUDGET_VERSIONS.
  • LEDGER_ID — the ledger to which the budget belongs.
  • START_PERIOD_NUM and START_PERIOD_YEAR — the numeric period and fiscal year of the budget's first valid period, resolved from START_PER.
  • END_PERIOD_NUM and END_PERIOD_YEAR — the numeric period and fiscal year of the budget's last valid period, resolved from END_PER.

These numeric boundaries are the operative values for autocopy, since copy ranges are expressed in period numbers and years. This is directly relevant to the search term "start_per," which corresponds to the START_PER alias used to derive START_PERIOD_NUM and START_PERIOD_YEAR.

Common Use Cases and Queries

The primary use case is identifying budgets eligible for autocopy and determining the exact period span to copy. Filtering conditions built into the view exclude budgets marked with status 'R' (reserved or otherwise not open for copy) and exclude any budget lacking a latest opened year. A typical query lists eligible budgets with their copy ranges:

  • SELECT budget_name, ledger_id, start_period_num, start_period_year, end_period_num, end_period_year FROM apps.gl_budgets_autocopy_v WHERE ledger_id = :p_ledger_id;
  • SELECT budget_name, budget_version_id, start_period_num, end_period_num FROM apps.gl_budgets_autocopy_v ORDER BY budget_name;

Integration scenarios include budget roll-forward utilities and period-to-period copy routines that require a bounded, validated range. Because the view resolves period names to numbers and years, callers avoid reimplementing the GL_PERIOD_STATUSES lookup logic. The view should be treated as a convenience layer over its base tables; performance depends on the availability of indexes on GL_PERIOD_STATUSES and GL_BUDGET_VERSIONS.