Search Results unit_of_measure_m




Overview
Explore in AI Chat

Overview

The APPS.GMS_ENCUMBRANCE_ITEMS_V view is a reporting and integration object within the Oracle EBS Grants Management (GMS) module. It presents a denormalized, read-only projection of encumbrance item data that is otherwise scattered across several transaction and setup tables. Encumbrance items represent the individual lines against which funds are reserved for a project or award activity, and this view assembles the identifying information (project, task, encumbrance group, transaction source) together with the financial attributes (amounts, currency, exchange rates, dates, and accounting flags) required for reporting.

The object is owned by the APPS schema and is exposed as a view rather than as a base table. In the Oracle EBS architecture, APPS-owned views on synonymous base objects are the standard mechanism for presenting joins to external consumers — including Discoverer workbooks, BI Publisher reports, and custom interfaces — while masking the underlying normalization. Unlike the base table, which stores surrogate identifiers only, this view resolves those identifiers into human-readable values such as PROJECT_NUMBER, PROJECT_NAME, TASK_NUMBER, and the decoded unit of measure, substantially reducing the effort required to build ad hoc reports.

Underlying Base Objects

The view is defined over seven documented base objects. GMS_ENCUMBRANCE_ITEMS_ALL is the primary driving table, supplying the item-level records and materializing all ATTRIBUTE columns and financial/accounting fields. GMS_ENCUMBRANCES is joined on ENCUMBRANCE_ID to supply group-level attributes including ENCUMBRANCE_GROUP, ENCUMBRANCE_STATUS_CODE, INCURRED_BY_PERSON_ID, the operating ORG_ID, and INCURRED_BY_ORGANIZATION_ID.

PA_PROJECTS_ALL and PA_TASKS, accessed through their APPS synonyms, provide the project and task descriptive columns. PA_EXPENDITURE_TYPES is joined on EXPENDITURE_TYPE to obtain the cost rate flag and, critically, the UNIT_OF_MEASURE code. That code is resolved against the PA_LOOKUPS view, filtered to LOOKUP_TYPE = 'UNIT', to yield the L.MEANING value exposed as UNIT_OF_MEASURE_M. PA_TRANSACTION_SOURCES supplies the USER_TRANSACTION_SOURCE and ALLOW_REVERSAL_FLAG; this join is outer (indicated by the (+) operator), so items without a matching transaction source are not excluded from the result set.

Key Columns

  • UNIT_OF_MEASURE_M — the decoded meaning of the unit of measure, resolved from PA_LOOKUPS where LOOKUP_TYPE = 'UNIT'. This is the column most commonly referenced by report authors filtering on a specific UOM, since it returns the descriptive value rather than the internal code.
  • ENCUMBRANCE_ITEM_ID / ENCUMBRANCE_ID — primary and foreign key identifiers linking each item to its parent encumbrance.
  • PROJECT_NUMBER, PROJECT_NAME, TASK_NUMBER, TASK_NAME — resolved descriptive attributes of the project and task.
  • ENCUMBRANCE_GROUP, ENCUMBRANCE_STATUS_CODE, INCURRED_BY_PERSON_ID — group-level control attributes from GMS_ENCUMBRANCES.
  • AMOUNT, DENOM_RAW_AMOUNT, ACCT_RAW_COST — the primary monetary values, alongside DENOM_CURRENCY_CODE, ACCT_CURRENCY_CODE, and PROJECT_CURRENCY_CODE and their associated rate, rate type, and rate date columns.
  • ENCUMBRANCE_ITEM_DATE, PA_DATE, GL_DATE — transactional, project accounting, and general ledger dates used in period-based reporting.
  • TRANSACTION_SOURCE, USER_TRANSACTION_SOURCE, SYSTEM_LINKAGE_FUNCTION — identify the originating subsystem and linkage behaviour.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE10 — the descriptive flexfield columns, inheriting the DFF context from the base item table.

Common Use Cases and Queries

Typical scenarios include auditing open encumbrances by award, reconciling encumbrance amounts against expenditure, and producing UOM-based analysis of committed quantities. Because the view exposes decoded values, it is frequently used directly as a report data source.

A representative query filtering on the unit of measure would be:

  • SELECT project_number, task_number, encumbrance_item_id, unit_of_measure_m, amount, denom_currency_code, encumbrance_item_date FROM apps.gms_encumbrance_items_v WHERE unit_of_measure_m = :p_uom AND encumbrance_status_code = 'A';

More commonly, the view is used without a UOM predicate to list items for a project or transaction source:

  • SELECT project_number, encumbrance_group, user_transaction_source, amount, gl_date FROM apps.gms_encumbrance_items_v WHERE project_number = :p_project ORDER BY encumbrance_item_date;

Reports that must distinguish unreserved UOM values should note that UNIT_OF_MEASURE_M derives from an inner join to PA_LOOKUPS; items whose expenditure type carries no UOM code will render the column as null.