Search Results gl_ledger_set_assignments

Overview

JG_ZZ_SRS_LEDGER_PER_START_V is a reporting view owned by the APPS schema within the JG (Regional Localizations) product family of Oracle E-Business Suite, and it is documented as VALID in ETRM for releases 12.1.1 and 12.2.2. The view presents a consolidated, period-oriented projection of ledger activity across three distinct data domains, distinguished by the ACTUAL_FLAG column: actual balances ('A'), budget balances ('B'), and encumbrance balances ('E'). Its name reflects its intended role as a supporting structure for a regional (ZZ) Statutory Reporting Solution (SRS) process that requires a single, uniform list of ledger and period combinations before downstream reporting or extraction logic is applied.

The view does not store data. It derives every row at runtime by joining GL ledger definitions to GL period definitions and period statuses. Because it exposes LEDGER_ID directly on every row, it is frequently located by users and developers searching for objects that carry ledger context, and it is particularly useful when a report must iterate ledgers and periods without writing three separate queries for actual, budget, and encumbrance data.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects, all accessed through APPS synonyms: GL_BUDGET_PERIOD_RANGES, GL_LEDGERS, GL_LEDGER_SET_ASSIGNMENTS, GL_PERIODS, and GL_PERIOD_STATUSES. The view definition is a UNION ALL of three SELECT branches:

• The actual branch joins GL_LEDGERS to GL_PERIODS on PERIOD_SET_NAME and ACCOUNTED_PERIOD_TYPE, and requires an existence check against GL_LEDGERS, GL_LEDGER_SET_ASSIGNMENTS, and GL_PERIOD_STATUSES where the application is 101 (General Ledger) and the closing status is Open, Closed, or Permanently Closed ('O','C','P').
• The budget branch joins GL_PERIOD_STATUSES to GL_BUDGET_PERIOD_RANGES on period number and year ranges for application 101, returning the budget version as BUDGET_ENCUMBRANCE_ID.
• The encumbrance branch mirrors the actual branch structure but tests GL_LEDGERS.LATEST_ENCUMBRANCE_YEAR against the period year to determine whether encumbrance data can exist.

The outer joins on GL_LEDGER_SET_ASSIGNMENTS and the NVL on ledger set membership mean that both standalone ledgers and ledgers belonging to a ledger set are represented.

Key Columns

• LEDGER_ID — The unique identifier of the ledger or ledger set member contributing the row; the primary join key for downstream ledger-aware queries.
• PERIOD_NUM, PERIOD_NAME, PERIOD_YEAR — The accounting period identity, aligned to the ledger's period set and accounted period type.
• EFFECTIVE_PERIOD_NUM — A derived sortable key computed as (PERIOD_YEAR * 10000) + PERIOD_NUM, enabling chronological ordering across fiscal years.
• ACTUAL_FLAG — Domain discriminator: 'A' for actual, 'B' for budget, 'E' for encumbrance.
• BUDGET_ENCUMBRANCE_ID — Carries BUDGET_VERSION_ID for budget rows; set to -1 for actual and encumbrance rows.

Common Use Cases and Queries

Typical usage includes driving period-by-period reporting loops, seeding concurrent program parameters, and validating that a ledger has open or closed periods before extraction. A common query filters by ledger and domain:

• SELECT ledger_id, period_name, period_year, effective_period_num FROM apps.jg_zz_srs_ledger_per_start_v WHERE actual_flag = 'A' AND ledger_id = :ledger_id ORDER BY effective_period_num;
• SELECT DISTINCT ledger_id FROM apps.jg_zz_srs_ledger_per_start_v WHERE actual_flag = 'B';

Because the view returns only ledger and period combinations that satisfy the existence tests, it can safely be used as the driving set for statutory reporting extracts without additional filtering on GL_PERIOD_STATUSES.