Results for “effective_period_num”

50+ results




Overview
Explore in AI Chat

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

Overview

The APPS.GL_SRS_LEDGER_PERIOD_START view is a General Ledger reporting object in Oracle EBS 12.1.1 and 12.2.2 that consolidates the valid accounting periods available for each ledger across three distinct data categories: actuals, budgets, and encumbrances. Its documented purpose is to "review valid periods for actuals, budgets, and encumbrances," making it a foundational reference for period-driven reporting, period-list generation, and cross-validation of which ledger/period combinations contain transactional or budgetary data. The view is owned by the APPS schema and is marked VALID. Rather than storing data, it derives its result set entirely from General Ledger base tables, projecting a normalized set of period and ledger identifiers along with a flag that discriminates the record type. This design allows reporting tools and period-selection list-of-values components to query a single object instead of unioning multiple GL tables manually.

Underlying Base Objects

The view is defined over five documented GL base objects, accessed through APPS synonyms: GL_LEDGERS, GL_PERIODS, GL_PERIOD_STATUSES, GL_BUDGET_PERIOD_RANGES, and GL_LEDGER_SET_ASSIGNMENTS. The view text is a three-way UNION that maps directly to these objects:

The GL_LEDGER_SET_ASSIGNMENTS join is outer ((+)), and the ledger identifier resolves through NVL(LS.LEDGER_ID, LED.LEDGER_ID), accommodating both ledger-set and single-ledger configurations.

Key Columns

  • PERIOD_NUM — the numeric period within the accounting calendar, used for ordering and range filtering.
  • PERIOD_NAME — the user-facing period label (for example, JAN-24); the primary join key across the union branches and to GL_PERIOD_STATUSES.
  • PERIOD_YEAR — the fiscal/accounting year to which the period belongs.
  • EFFECTIVE_PERIOD_NUM — a derived sortable key computed as (PERIOD_YEAR * 10000) + PERIOD_NUM; in the budget branch this value is taken directly from GL_PERIOD_STATUSES.
  • LEDGER_ID — identifies the ledger for which the period is valid.
  • BUDGET_ENCUMBRANCE_ID — carries the BUDGET_VERSION_ID for budget rows and the sentinel value -1 for actuals and encumbrances.
  • ACTUAL_FLAG — discriminates record type: 'A' (actuals), 'B' (budgets), 'E' (encumbrances).

Common Use Cases and Queries

Typical uses include populating period selection lists in concurrent program parameters, identifying which periods hold actual versus budgetary activity per ledger, and validating period ranges before running GL reports or subledger transfers. A representative query lists all valid actual periods for a specific ledger:

SELECT period_name, period_year, effective_period_num FROM gl_srs_ledger_period_start WHERE ledger_id = :p_ledger_id AND actual_flag = 'A' ORDER BY effective_period_num;

To enumerate budget periods with their version identifiers:

SELECT period_name, period_year, budget_encumbrance_id FROM gl_srs_ledger_period_start WHERE ledger_id = :p_ledger_id AND actual_flag = 'B' ORDER BY effective_period_num;

To determine the earliest and latest valid encumbrance period per ledger:

SELECT ledger_id, MIN(effective_period_num), MAX(effective_period_num) FROM gl_srs_ledger_period_start WHERE actual_flag = 'E' GROUP BY ledger_id;

Because the view filters on GL_PERIOD_STATUSES closing status and encumbrance year, results inherently reflect periods open, closed, or permanently closed and should not be treated as a list of open periods alone.