Search Results gms_commitment_encumbered_v




Overview
Explore in AI Chat

Overview

GMS_COMMITMENT_ENCUMBERED_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMS – Grants Accounting product family. It presents commitment and encumbrance activity associated with sponsored awards, consolidating requisition and purchase order funding lines against award distributions. The view is registered as VALID in ETRM for both 12.1.1 and 12.2.2 and is intended primarily for reporting, inquiry, and downstream integration rather than transactional data entry.

The view conforms to the standard Oracle Grants Accounting requirement that award-level commitments be reconciled with encumbered requisition and purchasing documents. It materializes document type, commitment number, award identifiers, expenditure classification, organization, period name, and encumbered amounts by unioning rows sourced from the purchasing requisition path and the purchase order path. The result is a single presentation layer through which grant administrators, principal investigators, and reporting engines can query outstanding commitments by award.

Underlying Base Objects

The documented base objects reveal a composite definition spanning Purchasing, Payables, Grants Accounting, and Projects. Purchasing objects include PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, PO_REQ_DISTRIBUTIONS_ALL, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, PO_LINE_TYPES, and PO_VENDORS. Award and encumbrance data derive from GMS_AWARD_DISTRIBUTIONS, GMS_ENCUMBRANCES_ALL, and GMS_ENCUMBRANCE_ITEMS_ALL. Period and source context come from PA_PERIODS, PA_TRANSACTION_SOURCES, and GL_LEDGERS.

Two packages are referenced in the view text and metadata: PO_INTG_DOCUMENT_FUNDS_GRP, which supplies the active encumbrance function for requisition distributions, and GMS_BUDGET_BALANCE, which supports award budget reconciliation. PA_CMT_UTILS is also referenced for commitment utility logic. The view text confirms a UNION ALL structure joining requisition and purchase order legs, with ADL.DOCUMENT_TYPE driving the document classification (for example 'REQ' for requisitions and PO equivalents for purchase orders). Filter predicates include NVL(RL.MODIFIED_BY_AGENT_FLAG,'N') = 'N', RL.SOURCE_TYPE_CODE = 'VENDOR', NVL(RD.ENCUMBERED_FLAG,'N') = 'Y', and status constraints ADL.ADL_STATUS = 'A' and ADL.FC_STATUS = 'A'.

Key Columns

Common Use Cases and Queries

Typical uses include award commitment inquiries, encumbrance reconciliation reports, and extracts feeding grants reporting. A representative query filters encumbrances for a specific award:

  • SELECT cmt_number, document_type, project_id, task_id, expenditure_type, acct_raw_cost FROM apps.gms_commitment_encumbered_v WHERE award_id = :p_award_id ORDER BY gl_date;
  • SELECT pa_period, SUM(acct_raw_cost) FROM apps.gms_commitment_encumbered_v WHERE award_id = :p_award_id GROUP BY pa_period;
  • SELECT document_type, COUNT(*) FROM apps.gms_commitment_encumbered_v WHERE award_id = :p_award_id GROUP BY document_type;

Because the view depends on Purchasing and Grants Accounting base tables, query performance is sensitive to the volume of open requisitions and POs for the award, and joins to PO_DISTRIBUTIONS_ALL and GMS_AWARD_DISTRIBUTIONS should be constrained by award or period where possible.