Results for “gl_srs_glrtb2_abe_start_period”

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

Overview

The GL_SRS_GLRTB2_ABE_START_PERIOD view is a General Ledger reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a presentation-layer construct used by Oracle's seeded General Ledger standard reports and related integration logic, functioning as an interface view that supplies a row-oriented result set of period information to reporting engines. Its name indicates its role as a start-period selector for a standard report maintained under the GL standard reporting product family (SRS/GLRTB2). The view normalizes a literal seed row with a fully expanded period cross-reference so downstream report parameters can be resolved against a consistent structure.

A user searching for end_period_name arrives here because this view explicitly exposes an END_PERIOD_NAME column. That column, together with PERIOD_NAME, forms the bounded period range the view projects from the ledger and budget period ranges.

Underlying Base Objects

The view is defined over three referenced base objects, all resolved through the APPS schema:

• GL_PERIOD_STATUSES (SYNONYM) — the ledger period calendar and status table, joined twice in the view: once as the driving period (GLPS) and once as the terminating period (GLPSEND).
• GL_BUDGET_PERIOD_RANGES (SYNONYM) — supplies the budget version identifier and the start/end period number boundaries that constrain the join.
• GL_LOOKUPS (VIEW) — source of the seed row, drawn from a lookup type of LITERAL with lookup code N/A, supplying placeholder values and the literal label.

The join enforces APPLICATION_ID = 101 (General Ledger) on both period status aliases, requires matching LEDGER_ID, and matches PERIOD_YEAR to the budget range while requiring GLPS.PERIOD_NUM to fall between the range's START_PERIOD_NUM and END_PERIOD_NUM. The additional predicate GLPS.EFFECTIVE_PERIOD_NUM <= GLPSEND.EFFECTIVE_PERIOD_NUM restricts the driving period to at or before the terminating period.

Key Columns

• PERIOD_NUM — the period number; seeded as -1 in the header row, otherwise drawn from GL_PERIOD_STATUSES.
• PERIOD_NAME — the period label delivered to the report, sourced from GL_PERIOD_STATUSES.PERIOD_NAME.
• PERIOD_YEAR — the fiscal/calendar year of the period, seeded as -1 in the header row.
• LEDGER_ID — the ledger identifier associated with the period and terminating period.
• BUDGET_ENCUMBRANCE_ID — populated from GL_BUDGET_PERIOD_RANGES.BUDGET_VERSION_ID, identifying the budget version whose range frames the query.
• ACTUAL_FLAG — a discriminator, 'A' for the seed/literal row and 'B' for budget-related rows, separating the placeholder from operational data.
• END_PERIOD_NAME — the period name of the terminating period (GLPSEND.PERIOD_NAME); 'X' in the seed row. This is the column most directly relevant to an end_period_name search.

Common Use Cases and Queries

The view is typically used to resolve the valid period range for a given ledger and budget version, or to present a selectable period list to a report parameter form. It supports reporting that must reconcile a start period against a known end period name.

SELECT period_name, period_year, ledger_id,
       budget_encumbrance_id, end_period_name
FROM   apps.gl_srs_glrtb2_abe_start_period
WHERE  actual_flag = 'B'
AND    ledger_id = :p_ledger_id
ORDER BY period_year, period_num;

To isolate rows terminating in a specific period name:

SELECT DISTINCT end_period_name
FROM   apps.gl_srs_glrtb2_abe_start_period
WHERE  end_period_name = :p_end_period_name;

Because the seed row returns PERIOD_NUM = -1, LEDGER_ID = -1, and ACTUAL_FLAG = 'A', filter on ACTUAL_FLAG = 'B' to exclude the placeholder when consuming real period data. Where query performance matters, ensure GL_PERIOD_STATUSES and GL_BUDGET_PERIOD_RANGES are correctly indexed on LEDGER_ID, PERIOD_YEAR, and PERIOD_NUM.