Search Results gms_funding_patterns_all_n1

Overview

GMS.GMS_FUNDING_PATTERNS_ALL is a transactional table in the Oracle E-Business Suite Grants Management (GMS) application, owned by the GMS schema and registered under FND Design Data as GMS.GMS_FUNDING_PATTERNS_ALL. It stores the rule definitions used to charge transactions belonging to a sponsored project against one or more funding awards. For any given sponsored project, multiple funding pattern definitions may coexist, each identified by a system-generated funding pattern identifier and sequenced to control the order in which awards absorb sponsored costs. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its indexes are housed in APPS_TS_TX_IDX. Under a heuristic Data Vault classification mined from its foreign-key structure, the object is hub-leaning: it functions as a central referenced entity whose surrogate key is consumed by numerous downstream distribution and interface tables.

Key Information Stored

The table is defined with sixteen documented columns. The most significant include:

• FUNDING_PATTERN_ID — the system-generated primary key surrogate (NUMBER(15)); this is the single-column unique index GMS_FUNDING_PATTERNS_ALL_U1, making it the primary business-key candidate and the parent key for all downstream references. This column corresponds to the user's search term "gms_funding_patterns_all_u1".
• ORG_ID — the multi-organization operating unit that owns the funding pattern.
• FUNDING_SEQUENCE — the sequence number governing the order in which each entry within a funding pattern is applied.
• FUNDING_NAME — a user-defined name describing the funding pattern.
• RETROACTIVE_FLAG — indicates whether the pattern is designated for retroactive adjustments.
• PROJECT_ID and TASK_ID — the sponsored project and task for which the pattern is defined; both are covered by the non-unique index GMS_FUNDING_PATTERNS_ALL_N1.
• STATUS — the active/inactive state of the funding pattern.
• FUNDS_STATUS — the funds-availability status of the pattern.
• START_DATE and END_DATE — the effective date range during which the pattern is active.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Who columns for audit tracking.

The primary key constraint is GMS_FUNDING_PATTERN_PK, defined on FUNDING_PATTERN_ID.

Common Use Cases and Queries

The table is typically queried to resolve the funding rules applicable to a sponsored project, task, and date range, or to trace distributions back to the governing pattern. A common query retrieves active funding patterns for a project:

• SELECT FUNDING_PATTERN_ID, FUNDING_NAME, FUNDING_SEQUENCE, STATUS, START_DATE, END_DATE FROM GMS.GMS_FUNDING_PATTERNS_ALL WHERE PROJECT_ID = :project_id AND ORG_ID = :org_id ORDER BY FUNDING_SEQUENCE;
• Joining to GMS_FP_DISTRIBUTIONS on FUNDING_PATTERN_ID to report the distribution of charged amounts per pattern.
• Filtering by RETROACTIVE_FLAG and date range to identify patterns eligible for retroactive adjustment processing.

Reporting use cases include sponsored-project funding audits, funds-availability reconciliation using FUNDS_STATUS, and sequence-order validation of funding allocation rules.

Related Objects

The following documented objects reference GMS_FUNDING_PATTERNS_ALL via the FUNDING_PATTERN_ID foreign key:

• GMS_FP_DISTRIBUTIONS.FUNDING_PATTERN_ID — funding pattern distribution lines.
• GMS_BC_PACKETS.FUNDING_PATTERN_ID — burden cost packets associated with the pattern.
• GMS_DISTRIBUTION_DETAILS.FUNDING_PATTERN_ID — detailed distribution records.
• GMS_TRANSACTION_INTERFACE_ALL.FUNDING_PATTERN_ID — transaction interface rows staged for processing.
• GMS_AWARD_DISTRIBUTIONS.FUNDING_PATTERN_ID — award-level distribution records.

These relationships establish GMS_FUNDING_PATTERNS_ALL as the hub entity that downstream GMS distribution, packet, and interface tables depend upon.