Search Results gms_status_commitments_v




Overview
Explore in AI Chat

Overview

GMS_STATUS_COMMITMENTS_V is an Oracle E-Business Suite views owned by the APPS schema and delivered as part of the GMS – Grants Accounting product family. In the EBS 12.1.1 and 12.2.2 releases, the view exposes commitment (encumbrance) activity for grant-funded awards and projects in a reporting-ready format. Its defining purpose is to consolidate commitment documents — purchase orders and other encumbrance sources — with the project, task, award, expenditure type, and accounting period context required by grants administrators and principal investigators.

Because the view joins commitment burden data to project and task definitions, it allows encumbered quantities and costs to be reported against the same award and task hierarchy used by the Grants Accounting budget-to-actual reports. Querying by the COMMITMENT_NUMBER column, which the search term suggests is the primary driver of interest, returns the award/project context, the supplier, the expenditure category, and the raw and burdened cost for each commitment line, presented in the functional currency as rounded by the PA_CURRENCY package.

The object is grant-specific: it is not a general Payables or Purchasing commitments view. Its presence in grants reporting means it supports funds-checking and encumbrance visibility in a sponsored-award context where commitments must be associated with a valid award, project, and task combination.

Underlying Base Objects

The view is defined as an inline join of five base data sources. GMS_COMMITMENT_BURDEN_V supplies the commitment facts, including award, project, task, document type, expenditure type, commitment number, quantities, supplier, transaction source, and accounted raw and burdened costs. PA_PROJECTS_ALL provides the project number (SEGMENT1) and project name. PA_TASKS supplies the task number and task name. HR_ORGANIZATION_UNITS resolves the organization name for the expenditure organization. PA_PERIODS supplies the accounting period name, organization ID, and the period date range used to join the expenditure item date.

The documented referenced base objects extend beyond the immediate FROM clause: GMS_BUDGET_BALANCE, HR_GENERAL, HR_SECURITY, PA_CMT_UTILS, PA_CURRENCY, and PO_INTG_DOCUMENT_FUNDS_GRP are all registered dependencies. The HR_SECURITY and HR_GENERAL references reflect organization-based security applied to HR_ORGANIZATION_UNITS, meaning a user's organizational access can constrain the rows returned. PA_CURRENCY.ROUND_CURRENCY_AMT is applied to the raw and burdened cost columns to enforce currency precision. PO_INTG_DOCUMENT_FUNDS_GRP and PA_CMT_UTILS relate to funds checking and commitment utility logic used during commitment creation and reporting.

Key Columns

Common Use Cases and Queries

The typical use case is retrieving all commitments associated with a specific award, project, or commitment number, and reconciling encumbered values against budget balances. A representative query is:

SELECT award_id, project_number, task_number, commitment_number,
       supplier_name, expenditure_type, quantity, raw_cost, burdened_cost,
       pa_period, gl_date
FROM   apps.gms_status_commitments_v
WHERE  commitment_number = :commitment_number
ORDER BY pa_period, task_number;

Reporting variants aggregate by project and period, for example SUM(burdened_cost) GROUP BY project_number, pa_period, to present period-by-period encumbrance status. Because the view applies HR security and currency rounding, it should be treated as a reporting and inquiry layer rather than a maintenance interface; encumbrance transactions themselves are created and adjusted in Purchasing and Payables. Note that the view is documented as VALID in the APPS schema and is owned by Oracle, so custom code should reference it without modification.