Search Results gms_encumbrance_items_v




Overview
Explore in AI Chat

Overview

The APPS.GMS_ENCUMBRANCE_ITEMS_V view is a denormalized reporting object within the Oracle E-Business Suite Grants Accounting (GMS) module. It presents encumbrance line detail together with the descriptive context required to interpret those lines, joining project, task, expenditure type, transaction source, and lookup information into a single flat structure. The view is owned by the APPS schema and is documented as VALID in the ETRM repository for release 12.2.2, with equivalent behavior in 12.1.1.

Encumbrances in Grants Accounting represent commitments against sponsored awards and internal projects — amounts reserved for anticipated costs that have not yet been realized as expenditures. The view surfaces those commitments at the individual encumbrance item level, which is the granularity at which encumbrance amounts are held in the underlying detail table. Because it resolves surrogate identifiers into user-recognizable values, the view is well suited to operational reporting, reconciliation extracts, and integration interfaces that must present encumbrance data in a consumable form.

Underlying Base Objects

The view is defined over seven documented objects. The primary fact source is GMS_ENCUMBRANCE_ITEMS_ALL, which supplies the encumbrance item rows, identifiers, dates, currency attributes, and descriptive flexfield columns. GMS_ENCUMBRANCES provides the encumbrance header attributes, including encumbrance group, status, incurred-by person and organization, and ORG_ID. Project and task descriptors come from PA_PROJECTS_ALL and PA_TASKS, joined on PROJECT_ID and TASK_ID respectively. PA_EXPENDITURE_TYPES supplies the cost rate flag through the encumbrance type join, PA_TRANSACTION_SOURCES supplies the user-facing transaction source and reversal flag, and PA_LOOKUPS is used to translate the unit of measure lookup code into the L.MEANING value exposed as UNIT_OF_MEASURE_M.

With the exception of PA_LOOKUPS, which is itself a view, the referenced objects are consumed through APPS synonyms. The join to PA_TRANSACTION_SOURCES is an outer join, so encumbrance items without a matching transaction source are retained.

Key Columns

Identification columns include ROW_ID, ENCUMBRANCE_ITEM_ID, ENCUMBRANCE_ID, PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, TASK_ID, TASK_NUMBER, and TASK_NAME. Financial and currency columns include DENOM_CURRENCY_CODE, DENOM_RAW_AMOUNT, ACCT_CURRENCY_CODE, ACCT_RAW_COST, ACCT_EXCHANGE_RATE, and the parallel PROJECT_* currency attributes, together with AMOUNT and ACCT_EXCHANGE_ROUNDING_LIMIT. Date columns include ENCUMBRANCE_ITEM_DATE, PA_DATE, and GL_DATE.

The UNIT_OF_MEASURE_M column, which is directly relevant to the search that led to this object, is the translated meaning of the expenditure type's unit of measure. It is derived from the PA_LOOKUPS join on LOOKUP_TYPE = 'UNIT', so it returns the descriptive unit label rather than the internal lookup code. Status and control columns encompass ENCUMBRANCE_GROUP, ENCUMBRANCE_STATUS_CODE, ENC_DISTRIBUTED_FLAG, and NET_ZERO_ADJUSTMENT_FLAG. Audit columns include CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include award-level encumbrance reporting by unit of measure, reconciliation of distributed encumbrances to the general ledger, and extracts feeding downstream commitments reporting.

  • Listing open encumbrances with their unit of measure: SELECT project_number, task_number, encumbrance_status_code, unit_of_measure_m, amount FROM apps.gms_encumbrance_items_v WHERE encumbrance_status_code = 'OPEN' ORDER BY project_number, task_number;
  • Aggregating committed amounts per project and UOM: SELECT project_number, unit_of_measure_m, SUM(amount) total_committed FROM apps.gms_encumbrance_items_v GROUP BY project_number, unit_of_measure_m;
  • Currency and exchange detail extract: SELECT encumbrance_id, denom_currency_code, denom_raw_amount, acct_currency_code, acct_raw_cost, acct_exchange_rate FROM apps.gms_encumbrance_items_v WHERE acct_rate_date >= :p_from_date;
  • Tracking late encumbrance items by date: SELECT encumbrance_item_id, project_number, gl_date, pa_date, amount FROM apps.gms_encumbrance_items_v WHERE gl_date IS NULL;

Because the view joins several project and grants tables, queries should constrain on PROJECT_ID, ENCUMBRANCE_ID, or date ranges to avoid full scans of the underlying encumbrance detail.