Results for “gl_encumbrance_types_current_v”

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

Overview

The GL_ENCUMBRANCE_TYPES_CURRENT_V view is a General Ledger (GL) database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As documented in the ETRM metadata, its description is limited to the notation "10SC ONLY," and its status is VALID. The view presents a filtered, current-state list of encumbrance types defined in the General Ledger application. Encumbrance types are the user-defined classifications that control how encumbrances — commitments and obligations recorded against budget funds — are tracked and reported within budgetary control.

The view's principal role is to expose only those encumbrance types that are currently active. This makes it well suited for reporting, list-of-values (LOV) definitions, and integration logic where disabled or obsolete encumbrance types must be excluded. Because it filters on the enabled flag, any consumer of the view automatically receives a clean set of values valid for current use, without needing to apply an additional predicate.

Underlying Base Objects

Per the documented metadata, the view is defined over the base object GL_ENCUMBRANCE_TYPES, which is referenced as a SYNONYM in the APPS schema. GL_ENCUMBRANCE_TYPES is the GL table that stores the master list of encumbrance type codes and descriptions used across budgetary control.

The view text documented in the ETRM excerpt confirms the relationship:

• SELECT ENC.ENCUMBRANCE_TYPE_ID ENCUMBRANCE_TYPE_ID, ENC.ENCUMBRANCE_TYPE ENCUMBRANCE_TYPE FROM GL_ENCUMBRANCE_TYPES ENC WHERE ENC.ENABLED_FLAG = 'Y'

The view therefore acts as a thin projection of the base table, returning only the identifier and name columns and restricting output to rows where ENABLED_FLAG = 'Y'. No joins to other tables are present, so the view carries no additional dependency beyond GL_ENCUMBRANCE_TYPES.

Key Columns

The view exposes a deliberately narrow column set, which is consistent with its purpose as a value-list source:

• ENCUMBRANCE_TYPE_ID — The unique identifier for the encumbrance type. This is the primary key inherited from GL_ENCUMBRANCE_TYPES and is the value most commonly sought by users who search for "encumbrance_type_id." It is used as a foreign key by other encumbrance and budgetary control objects.
• ENCUMBRANCE_TYPE — The descriptive name or code of the encumbrance type. This is the human-readable value displayed in forms, reports, and LOVs, and it is what users select when entering encumbrances.

Columns such as ENABLED_FLAG, creation and update audit columns, and other descriptive attributes that exist on the base table are not exposed, since the view has already filtered and projected to the two attributes of primary interest.

Common Use Cases and Queries

The view is most often used to resolve an encumbrance type ID to its name, or to present a filtered list of active encumbrance types. The following query retrieves the identifier and name for all active encumbrance types:

• SELECT encumbrance_type_id, encumbrance_type FROM apps.gl_encumbrance_types_current_v ORDER BY encumbrance_type;

To look up a specific encumbrance type by its identifier, a common integration or troubleshooting pattern is:

• SELECT encumbrance_type, encumbrance_type_id FROM apps.gl_encumbrance_types_current_v WHERE encumbrance_type_id = :p_encumbrance_type_id;

Because the view filters out disabled encumbrance types, it is appropriate for populating selection lists in custom forms, for validating IDs supplied by external interfaces, and for reconciliation reports that must reflect only currently enabled budgetary classifications. When a full historical or administrative view is required, including disabled types, the base table GL_ENCUMBRANCE_TYPES should be queried directly instead.