Results for “system_id”

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

Overview

RG_SRS_DSS_BUD_ENC_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, catalogued under the RG – Application Report Generator product. The ETRM documentation annotates the object with the description "10SC ONLY," indicating it is scoped to a specific configuration rather than being a general-purpose reporting interface. The view exposes a consolidated list of budget and encumbrance references drawn from General Ledger, presenting each entry with a display name, a surrogate identifier, ledger and system context, and an indicator flag that distinguishes budget, encumbrance, and literal rows. Within the RG reporting framework, the view functions as a value-set source: RG_DSS_VARIABLES and RG_DSS_SYSTEM_VARIABLES hold the runtime selections that drive the rows returned, allowing a report definition to resolve budget version names and encumbrance type meanings for presentation and parameter validation. Its dependency chain reaches the GL_LOOKUPS view, which is significant for implementers who search on "gl_lookups," since lookup-driven decoding of encumbrance types is central to the view's behavior.

Underlying Base Objects

Documented metadata lists five referenced objects: GL_BUDGET_VERSIONS, GL_ENCUMBRANCE_TYPES, GL_LOOKUPS, RG_DSS_SYSTEM_VARIABLES, and RG_DSS_VARIABLES, all referenced through synonyms except GL_LOOKUPS, which is itself a view. The view body comprises four UNION branches:

• A pseudo-row from GL_LOOKUPS where LOOKUP_TYPE = 'LITERAL' and LOOKUP_CODE = 'N/A', yielding a name of "N/A" with identifiers fixed at -100 and ledger/system values of -1 and an ACTUAL_FLAG of 'A'.
• Budget rows joining GL_BUDGET_VERSIONS to RG_DSS_VARIABLES and RG_DSS_SYSTEM_VARIABLES on VARIABLE_ID, restricted to BALANCE_TYPE = 'B', tagged ACTUAL_FLAG 'B'.
• Encumbrance rows joining GL_ENCUMBRANCE_TYPES to RG_DSS_VARIABLES and RG_DSS_SYSTEM_VARIABLES, restricted to BALANCE_TYPE = 'E', tagged 'E'. The encumbrance name is decoded so that ENCUMBRANCE_TYPE_ID of -1 resolves through GL_LOOKUPS using LOOKUP_TYPE = 'GL_DSS_ENCUMBRANCE_TYPE' and LOOKUP_CODE = 'TOTAL'.
• A second literal branch returning the meaning of the 'GL_DSS_ENCUMBRANCE_TYPE' / 'ALL' lookup with BUDGET_ENCUMBRANCE_ID fixed at -2 and ACTUAL_FLAG 'E'.

The outer joins on GL_ENCUMBRANCE_TYPES (denoted by the (+) operator) preserve encumbrance rows whose type does not exist in the base table, which is how the 'TOTAL' placeholder is accommodated.

Key Columns

• BUDGET_ENCUMBRANCE_NAME — the display value: a budget version name, an encumbrance type name or lookup meaning, or the literal "N/A".
• BUDGET_ENCUMBRANCE_ID — the surrogate identifier: GL_BUDGET_VERSIONS.BUDGET_VERSION_ID, RG_DSS_VARIABLES.ENCUMBRANCE_TYPE_ID, or the reserved literals -100 and -2 for the "N/A" and "ALL" rows respectively.
• LEDGER_ID — the ledger from RG_DSS_VARIABLES, or -1 for literal rows.
• SYSTEM_ID — the system identifier from RG_DSS_SYSTEM_VARIABLES, or -1 for literal rows.
• ACTUAL_FLAG — a single-character discriminator: 'A' for the "N/A" literal, 'B' for budget, 'E' for encumbrance and the "ALL" literal.

Common Use Cases and Queries

The view is typically consumed as a validation or LOV source for report parameters, and for resolving stored encumbrance identifiers into readable names. A representative query filtering to active runtime selections is:

• SELECT BUDGET_ENCUMBRANCE_ID, BUDGET_ENCUMBRANCE_NAME, ACTUAL_FLAG FROM APPS.RG_SRS_DSS_BUD_ENC_V WHERE ACTUAL_FLAG IN ('B','E') ORDER BY ACTUAL_FLAG, BUDGET_ENCUMBRANCE_NAME;
• SELECT BUDGET_ENCUMBRANCE_NAME FROM APPS.RG_SRS_DSS_BUD_ENC_V WHERE BUDGET_ENCUMBRANCE_ID = :p_id AND LEDGER_ID = :p_ledger;

Because rows derive from RG_DSS_VARIABLES and RG_DSS_SYSTEM_VARIABLES, results reflect the variable context established by the running report rather than a static master list; queries issued outside that context may return only the literal branches. Direct DML against the view is not supported, and tuning attention should focus on the joins to GL_BUDGET_VERSIONS and GL_LOOKUPS.