Search Results gms_funding_patterns




Overview
Explore in AI Chat

Overview

GMS_FUNDING_PATTERNS is a reporting view within the Oracle E-Business Suite Grants Accounting (GMS) module. It exposes the organization-secured funding pattern definitions maintained in the Grants Accounting application, presenting the sequence, name, and effective dating of each funding pattern configured for sponsored projects and tasks. A funding pattern in GMS defines the order and proportion in which award or sponsored project funding sources are consumed, and it is a foundational control for burdening, revenue recognition, and invoice generation against awards.

Functionally, the view is a filtered pass-through over the multi-organization table that stores funding pattern headers. Its purpose is to present only those rows that belong to the operating unit (organization) of the current session, using the standard Oracle multi-organization security model. The view itself stores no data, and the ETRM documentation notes it is not implemented as a database object in this instance; its definition is documented for reference, custom reporting, and integration design. In Oracle EBS 12.1.1 and 12.2.2, views of this pattern are typically queried by reporting tools (Oracle Reports, BI Publisher, Discoverer), by concurrent programs, and by custom extensions that need to read award funding configuration without touching the secured base table directly.

Underlying Base Objects

The view is defined over GMS_FUNDING_PATTERNS_ALL, which is the multi-organization base table holding funding pattern definitions for all operating units. The ETRM metadata documents no other referenced base objects, so the view is a single-table projection with a row-level security predicate rather than a join.

The security predicate restricts results by comparing the organization identifier stored in each row (ORG_ID) against the organization context carried in the session's CLIENT_INFO. The value in ORG_ID is compared to the numeric value derived from the first ten characters of CLIENT_INFO, with a leading blank character treated as NULL. When both the row's ORG_ID and the session value are null, the row is treated as matching the sentinel value of -99. This is the conventional Oracle multi-org policy: a user operating in a given operating unit sees only funding patterns created in that operating unit, and records without an organization assignment are exposed only in an unsecured context. Because the underlying table is the _ALL variant, the view provides the organization-filtered equivalent that applications use at runtime.

Key Columns

  • FUNDING_PATTERN_ID — Primary identifier for the funding pattern; the join key to dependent funding pattern lines and to award and project associations.
  • FUNDING_SEQUENCE — Ordinal position of the pattern in a defined series, controlling the order in which the pattern is applied.
  • FUNDING_NAME — Descriptive name of the funding pattern as entered by the user.
  • RETROACTIVE_FLAG — Indicates whether the pattern may be applied retroactively to transactions dated before its effective start.
  • PROJECT_ID and TASK_ID — Foreign keys to the project and task to which the pattern applies, enabling pattern lookup by sponsored project structure.
  • STATUS — Lifecycle state of the pattern header (for example, active or inactive).
  • FUNDS_STATUS — Funding-side status used to control whether the pattern participates in funds checking and consumption.
  • START_DATE and END_DATE — Effective dating window during which the pattern is valid.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — Standard Oracle WHO columns for audit and change tracking.

Common Use Cases and Queries

Typical uses include validating the funding order applied to a sponsored project, reconciling pattern configurations between environments, and driving custom award or invoice reports. A basic query lists all patterns visible to the current operating unit:

  • SELECT funding_pattern_id, funding_sequence, funding_name, project_id, task_id, status, funds_status, start_date, end_date FROM gms_funding_patterns ORDER BY project_id, funding_sequence;
  • SELECT funding_pattern_id, funding_name, retroactive_flag, start_date, end_date FROM gms_funding_patterns WHERE project_id = :project_id AND status = 'A' ORDER BY funding_sequence;
  • SELECT funding_pattern_id, funding_name, start_date, end_date FROM gms_funding_patterns WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));

Because the view enforces operating unit security through CLIENT_INFO, ad hoc queries executed outside the EBS session context may return no rows unless the client information is initialized, for example via initialization of ORG_ID through the standard multi-org APIs. In integrated environments, custom code should set the organization context before querying, or query the _ALL base table with an explicit ORG_ID predicate when cross-organization reporting is intended and authorized.