Search Results budget_encumbrance_id




Overview
Explore in AI Chat

Overview

The view APPS.JG_ZZ_SRS_LEDGER_BUD_ENCUM_V is a reporting and integration utility view in Oracle E-Business Suite (available in both 12.1.1 and 12.2.2) that presents a unified, line-of-business "pick list" of Budget and Encumbrance identifiers used in General Ledger. It is defined in the APPS schema and is used primarily as a value source for concurrent program parameters, Oracle Reports parameter LOVs (List of Values), and integration extracts that must select either an actual ledger, a budget version, or an encumbrance type from a single source.

The view name follows the JG_ZZ_SRS convention, indicating it was created by Oracle's regional/localization and reporting solution (SRS) team rather than being part of the core seeded GL schema. As a result, it acts as a convenience abstraction rather than a transactional table. Its most prominent use case is supplying the BUDGET_ENCUMBRANCE_ID and related identifiers to standardized reports that need to operate uniformly across actuals, budgets, and encumbrances. The view was frequently targeted by users searching for the budget_encumbrance_id column because it exposes that identifier in a form suitable for a report parameter.

Underlying Base Objects

The view is a UNION ALL of three branches, each drawing from a distinct set of source objects. According to the ETRM 12.2.2 metadata, the referenced base objects are:

  • GL_BUDGETS (synonym) – Supplies the budget name used to match budget versions.
  • GL_BUDGET_VERSIONS (synonym) – Supplies the BUDGET_VERSION_ID used as the budget-side identifier.
  • GL_BUDGET_PERIOD_RANGES (synonym) – Filters budget versions so only those with period ranges (i.e., assignable budgets) appear.
  • GL_ENCUMBRANCE_TYPES (synonym) – Supplies enabled encumbrance types and their IDs.
  • GL_LOOKUPS (view) – Supplies a single literal "Actual" row via a lookup code of N/A with lookup type LITERAL.

The first branch produces the "Actual" pseudo-record, the second produces one row per budget version, and the third produces one row per enabled encumbrance type. The union therefore returns a combined, denormalized set of identifiers keyed by an ACTUAL_FLAG of A, B, or E.

Key Columns

  • BUDGET_ENCUMBRANCE_NAME – The display name. For the actual row it is the lookup meaning; for budgets it is GL_BUDGETS.BUDGET_NAME; for encumbrances it is GL_ENCUMBRANCE_TYPES.ENCUMBRANCE_TYPE.
  • BUDGET_ENCUMBRANCE_ID – The identifier. It is -100 for the actual row, GL_BUDGET_VERSIONS.BUDGET_VERSION_ID for budgets, and GL_ENCUMBRANCE_TYPES.ENCUMBRANCE_TYPE_ID for encumbrances.
  • LEDGER_ID – A character column. It is the literal 'Actual' for the actual row, the numeric GL_BUDGETS.LEDGER_ID converted to character for budgets, and the literal 'Encumbrance' for the encumbrance branch.
  • ACTUAL_FLAG – The discriminator: A = actual, B = budget, E = encumbrance.

Note that LEDGER_ID and ACTUAL_FLAG are context-dependent and not consistently typed or semantically aligned, which is important when consumers join or filter on them.

Common Use Cases and Queries

The view is typically used as a parameter value set source or as a simple lookup for populating report selectors. A representative query retrieves all entries for the budget/encumbrance parameter dropdown:

  • SELECT budget_encumbrance_name, budget_encumbrance_id, actual_flag FROM apps.jg_zz_srs_ledger_bud_encum_v ORDER BY actual_flag, budget_encumbrance_name;

A filtered query to return only enabled encumbrance types:

  • SELECT budget_encumbrance_name, budget_encumbrance_id FROM apps.jg_zz_srs_ledger_bud_encum_v WHERE actual_flag = 'E';

A query to list only budgets relevant to a specific ledger:

  • SELECT budget_encumbrance_name, budget_encumbrance_id FROM apps.jg_zz_srs_ledger_bud_encum_v WHERE actual_flag = 'B' AND ledger_id = TO_CHAR(&ledger_id);

Because the view references GL_BUDGET_PERIOD_RANGES, budget rows only appear when the budget version has a defined period range, meaning budgets without ranges (e.g., unpublished or unassigned versions) are intentionally excluded. This makes the view suitable for report parameters that require a valid, assignable budget context.