Search Results funding_name




Overview
Explore in AI Chat

Overview

The APPS.GMS_FUNDING_PATTERNS_V view is a reporting and integration object within the Oracle E-Business Suite Grants Accounting (GMS) module. It exposes funding pattern definitions maintained against sponsored projects and tasks, allowing reporting layers, concurrent programs, and external integrations to read funding allocation rules without directly querying the underlying base table. In the context of Oracle EBS 12.1.1 and 12.2.2, this view is registered in the ETRM as a VALID object owned by the APPS schema and is treated as a read-only projection of funding pattern data. Its principal value lies in presenting the distribution sequence, effective dates, and status indicators — including FUNDS_STATUS — that govern how award funding is allocated across project and task combinations.

Underlying Base Objects

The view is defined over a single documented base object: the synonym GMS_FUNDING_PATTERNS, which resolves to the corresponding GMS funding patterns table in the APPS schema. The view text is a straightforward SELECT with no joins, unions, or aggregations; it projects the full set of parent columns in a fixed order. As a result, the view carries no independent storage and reflects the parent table's rows in real time. Data integrity, concurrency, and validation behavior are inherited entirely from the base table, and no row-level security predicates are added at the view level. Because the definition is a direct projection, the view is safe for query-only consumption and should not be treated as a DML target.

Key Columns

  • FUNDING_PATTERN_ID — Primary identifier for the funding pattern record.
  • FUNDING_SEQUENCE — Order in which funding sources are applied within the pattern.
  • FUNDING_NAME — Descriptive name of the funding pattern.
  • RETROACTIVE_FLAG — Indicates whether the pattern applies retroactively to prior transactions.
  • PROJECT_ID / TASK_ID — Project and task to which the funding pattern is attached.
  • STATUS — Lifecycle status of the pattern record itself.
  • FUNDS_STATUS — Status of the funds associated with the pattern; frequently queried to determine whether funding is active, on hold, or otherwise restricted for allocation.
  • START_DATE / END_DATE — Effective date range during which the pattern is valid.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN.
  • ORG_ID — Operating unit identifier supporting multi-org filtering.

Common Use Cases and Queries

The most frequent query pattern involves filtering by FUNDS_STATUS together with project and date criteria, as reflected in the originating search term. A representative query is:

SELECT funding_pattern_id, funding_name, funding_sequence, funds_status, start_date, end_date FROM apps.gms_funding_patterns_v WHERE project_id = :p_project_id AND funds_status = :p_funds_status AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));

Additional scenarios include reconciling active funding patterns per operating unit using ORG_ID, auditing retroactive adjustments via RETROACTIVE_FLAG, and feeding downstream allocation logic by ordering on FUNDING_SEQUENCE. Because the view performs no filtering, callers must apply STATUS and effective-date predicates explicitly to avoid returning inactive patterns. Standard EBS best practice applies: qualify the APPS schema, use bind variables for project and status values, and avoid DML against the view, directing maintenance to the base funding patterns maintenance forms instead.