Search Results gms_encumbrance_items




Overview

GMS_ENCUMBRANCE_ITEMS is a reporting and integration view in the Oracle EBS Grants Accounting (GMS) module. It exposes encumbrance item records associated with grant-funded project transactions, allowing users and external processes to query encumbrance details without directly accessing the underlying transaction tables. In Oracle EBS 12.1.1 and 12.2.2, this view is primarily used for reporting on committed funds, budget checking, and grants-related expenditure tracking.

The view is defined over GMS_ENCUMBRANCE_ITEMS_ALL, applying an ORG_ID-based security predicate via USERENV('CLIENT_INFO'). This means the view returns only those encumbrance items visible to the current operating unit context established during a session. Organizations that query this view must ensure the correct client information is set; otherwise, records may appear missing or be filtered out entirely.

Underlying Base Objects

According to ETRM metadata, no base objects are documented for this view in the 12.2.2 repository. However, the view text explicitly references GMS_ENCUMBRANCE_ITEMS_ALL as its single source object. The view applies an ORG_ID filter using the standard multiorg security pattern found throughout Oracle EBS, comparing NVL(ORG_ID, -99) against the value derived from the session's CLIENT_INFO.

The documentation notes that the view is "Not implemented in this database," indicating it may not be present in every environment or may exist only in specific grants-enabled instances. Its columns correspond one-to-one with the underlying _ALL table, with the addition of the multiorg security predicate.

Key Columns

Common Use Cases and Queries

A frequent requirement is identifying encumbrances that use a particular project rate type, particularly when validating currency conversion setup. The following query returns encumbrance items filtered by PROJECT_RATE_TYPE:

  • SELECT encumbrance_item_id, encumbrance_id, project_rate_type, project_exchange_rate, amount FROM gms_encumbrance_items WHERE project_rate_type = 'Corporate';

Other common scenarios include reconciling distributed versus non-distributed encumbrances, reporting by GL date range, and linking encumbrance items to tasks or awards.

  • SELECT encumbrance_item_id, gl_date, encumbrance_type, amount FROM gms_encumbrance_items WHERE enc_distributed_flag = 'N' AND gl_date BETWEEN :start_date AND :end_date;
  • SELECT task_id, SUM(amount) total_encumbered FROM gms_encumbrance_items GROUP BY task_id;

Because the view enforces operating unit security, integration and reporting tools must set the CLIENT_INFO context correctly. When the view is unavailable in a given instance, equivalent reporting must target GMS_ENCUMBRANCE_ITEMS_ALL directly with an explicit ORG_ID filter.