Search Results gms_commitments_override_v




Overview
Explore in AI Chat

Overview

APPS.GMS_COMMITMENTS_OVERRIDE_V is a Grants Accounting (GMS) view in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes commitment (encumbrance) records for sponsored projects and awards, drawing predominantly from Oracle Purchasing requisition distributions. The view is named "OVERRIDE" because it supplies commitment data that Grants Accounting uses to override or supplement the standard project commitment streams maintained by the Projects module. It is part of the integration surface between Oracle Purchasing, Oracle Projects, and GMS, allowing sponsored-project burdening rules and award-level compiled set identifiers to be applied to requisition-based commitments.

Records returned by the view represent purchasing requisitions that have not yet been converted into purchase orders or invoices. This makes the view a reporting source for outstanding requisition commitments against grant-funded tasks. It also supports funds checking and award budget consumption reporting within Grants Accounting.

Underlying Base Objects

The view is defined over a set of documented base objects that the ETRM metadata lists for 12.2.2. The primary fact source is the view PA_PROJ_REQ_DISTRIBUTIONS, aliased in the view text as PPRD, which supplies project, task, requisition, distribution, item, date, vendor, and amount attributes.

Surrounding the main source are several supporting objects and packages:

The view therefore sits atop the Projects commitment infrastructure, with GMS-specific extension logic applied through GMS_COST_PLUS_EXTN.

Key Columns

Common Use Cases and Queries

Typical uses include reporting outstanding requisition commitments by award, verifying burdened commitment amounts for sponsored projects, and reconciling GMS award budget consumption against purchasing activity.

A simple query filtering by project and task:

  • SELECT project_id, task_id, req_number, req_line, amount, burdended_cost FROM apps.gms_commitments_override_v WHERE project_id = :p_project_id AND task_id = :p_task_id;

Reporting by expenditure type and organization:

  • SELECT expenditure_type, expenditure_organization_id, SUM(amount) FROM apps.gms_commitments_override_v WHERE project_id = :p_project_id GROUP BY expenditure_type, expenditure_organization_id;

Because the view invokes PL/SQL functions per row (burdening, compiled set lookup, period retrieval), queries against large requisition volumes can be expensive. Restricting by PROJECT_ID, TASK_ID, or date range is recommended to limit function execution and improve response time.