Search Results gms_implementations




Overview
Explore in AI Chat

Overview

GMS_IMPLEMENTATIONS is a Grants Accounting (GMS) implementation-level view exposed in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a single row of configuration data that governs how award numbering and award distribution behave within a given operating unit. Unlike transactional award views, this object is a setup/parameter view: it carries the implementation choices that determine whether users may create awards manually, whether the system generates award numbers automatically, and how award distribution records are created and defaulted.

The view is defined as a secured query over the underlying GMS_IMPLEMENTATIONS_ALL table, filtered by the operating unit (ORG_ID) resolved from the session context. The WHERE clause uses USERENV('CLIENT_INFO') to extract the current ORG_ID and compares it against the row's ORG_ID, with a fallback of -99 when no organization context is present. This is the standard multi-org (MO) security pattern used throughout Oracle EBS, ensuring each operating unit sees only its own implementation row. Note that the ETRM metadata for this object states "Not implemented in this database" and documents no referenced base objects, meaning the view may not be present or populated in every environment.

Underlying Base Objects

The view text selects directly from GMS_IMPLEMENTATIONS_ALL, the multi-org base table that physically stores Grants Accounting implementation settings. The "_ALL" suffix indicates the table holds rows for every operating unit rather than a single organization, and each row is keyed by ORG_ID. The GMS_IMPLEMENTATIONS view is the org-secured presentation of that table: it applies the MO filter at query time so that application code and reports do not need to repeat the ORG_ID predicate. Because the ETRM record lists no referenced base objects separately, the only documented dependency is the GMS_IMPLEMENTATIONS_ALL source identified in the view text. The view columns are a direct projection of the base table columns with no joins, aggregations, or computed expressions other than the security predicate.

Key Columns

Common Use Cases and Queries

This view is primarily used to inspect and drive award numbering and distribution setup. Reporting on implementation settings, validating configuration during upgrades, and supporting integrations that must replicate award numbering logic are typical scenarios. A basic query retrieves the current operating unit's settings:

  • SELECT ORG_ID, MANUAL_AWARD_NUM_TYPE, NEXT_AUTOMATIC_AWARD_NUMBER, AWARD_DISTRIBUTION_OPTION, ENABLED FROM GMS_IMPLEMENTATIONS;
  • To check whether automatic numbering is active: SELECT ENABLED, NEXT_AUTOMATIC_AWARD_NUMBER FROM GMS_IMPLEMENTATIONS WHERE ENABLED = 'Y';
  • To review default distribution configuration: SELECT DEFAULT_DIST_AWARD_NUMBER, DEFAULT_DIST_AWARD_ID FROM GMS_IMPLEMENTATIONS;

Because the view is org-secured, results depend on the session's CLIENT_INFO context; in tools that do not initialize client info, the predicate may resolve to -99 and return no rows. Where the view is absent or unpopulated, administrators query GMS_IMPLEMENTATIONS_ALL directly with an explicit ORG_ID predicate. Standard WHO columns support auditing changes to implementation settings over time.