Search Results gl_dss_encumbrance_type




Overview

APPS.RG_SRS_DSS_BUD_ENC_V is a reporting view in the Oracle E-Business Suite (12.1.1 and 12.2.2) that presents a consolidated list of budget and encumbrance identifiers used by Oracle Enterprise Planning and Budgeting / Enterprise Performance Foundation (EPB/EPF) and the ETRM (Enterprise Territory and Resource Management, formerly Enterprise Resource Management) slice-definition framework. The view belongs to the RG (Resource Management / Slice) family of DSS objects, whose names follow the pattern RG_SRS_DSS_* — "SRS" denoting the subsidiarity of the object within the Slice Reporting System, "DSS" denoting the Decision Support System layer. The view unifies the budget and encumbrance dimension into a single, uniform lookup set that reports and dashboards can join against when resolving a BUDGET_ENCUMBRANCE_ID to a human-readable name and to the correct slice context (ledger and system identifier). It is primarily consumed by the Graph/BI (Obiee) or Discoverer-based slice reporting that drives budgetary and encumbrance analysis.

Underlying Base Objects

The view is a UNION of four query branches defined over the following documented base objects:

Each UNION branch supplies a fixed ACTUAL_FLAG value — 'A' (a placeholder for the literal row), 'B' for budget rows, and 'E' for encumbrance rows — and a synthetic BUDGET_ENCUMBRANCE_ID such as -100, -1 or -2 for the reserved "not-applicable" and aggregate rows.

Key Columns

  • BUDGET_ENCUMBRANCE_NAME — the display label: the budget name from GL_BUDGET_VERSIONS, the encumbrance type from GL_ENCUMBRANCE_TYPES, or the lookup meaning for the aggregate/literal entries.
  • BUDGET_ENCUMBRANCE_ID — the identifier of the budget version or encumbrance type; reserved negative values (−100, −1, −2) denote the "not applicable" and "total/all" pseudo-entries.
  • LEDGER_ID — the ledger (set of books) to which the variable belongs. It is set to −1 for the literal placeholder branch.
  • SYSTEM_ID — the slice system identifier from RG_DSS_SYSTEM_VARIABLES, used by the ETRM slice engine to determine which runtime context the row applies to. This is the column most commonly searched for by practitioners.
  • ACTUAL_FLAG — discriminates the row source: 'A' (actual/literal), 'B' (budget), 'E' (encumbrance).

Common Use Cases and Queries

Typical usages include populating budget-vs-encumbrance LOVs in slice administration, resolving a stored BUDGET_ENCUMBRANCE_ID to a name for display, and restricting a report to a specific slice system. A simple lookup by the searched column is:

  • SELECT BUDGET_ENCUMBRANCE_NAME, BUDGET_ENCUMBRANCE_ID, LEDGER_ID, ACTUAL_FLAG FROM APPS.RG_SRS_DSS_BUD_ENC_V WHERE SYSTEM_ID = :p_system_id AND ACTUAL_FLAG = 'B';
  • SELECT BUDGET_ENCUMBRANCE_NAME, ACTUAL_FLAG FROM APPS.RG_SRS_DSS_BUD_ENC_V WHERE BUDGET_ENCUMBRANCE_ID = :p_id;

Because the join against RG_DSS_VARIABLES/RG_DSS_SYSTEM_VARIABLES uses +0 arithmetic rather than an indexed equijoin, queries filtering by SYSTEM_ID can be slow on large slice definitions; adding a predicate on ACTUAL_FLAG helps the optimizer prune branches. The view is read-only and should be used only for reporting/LOV purposes, never as a target of DML.