Search Results gms_installments_u2
Overview
GMS.GMS_INSTALLMENTS is a transactional table in the Oracle E-Business Suite Grants Management (GMS) schema that stores information about the installments, supplements, and amendments associated with a particular award. The Type column determines the semantic meaning of each row: an Award row represents a funding installment, a Supplement represents an extension of an existing installment that carries additional funding capability, and an Amendment is documentation-only with no funding capability. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and it is documented as VALID in both the 12.1.1 and 12.2.2 ETRM repositories, with 35 columns in the 12.2.2 physical schema.
From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is standalone. The table nevertheless exhibits hub-like characteristics through its surrogate key INSTALLMENT_ID, and its AWARD_ID reference to IGF_AW_AWARD_ALL suggests it could be modeled as a link or satellite dependent on the award hub. This is offered as a modeling suggestion only; the table's own physical design is a conventional EBS transactional entity with standard WHO columns and a descriptive flexfield.
Key Information Stored
The most operationally significant columns are:
- INSTALLMENT_ID — Surrogate primary key, NUMBER(15), enforced by unique index GMS_INSTALLMENTS_U1.
- AWARD_ID — Identifier of the award to which the installment belongs; foreign key to IGF_AW_AWARD_ALL.
- INSTALLMENT_NUM — User-entered installment number, VARCHAR2(15). Together with AWARD_ID it forms the business-key candidate enforced by unique index GMS_INSTALLMENTS_U2.
- TYPE — Installment type; documented values are Award, Amendment, or Supplement.
- ACTIVE_FLAG — Status flag where Immediate indicates Active and Deferred indicates Inactive.
- START_DATE_ACTIVE / END_DATE_ACTIVE — First and last effective dates of the installment.
- CLOSE_DATE / ISSUE_DATE — Close date and issue date for the installment.
- DIRECT_COST / INDIRECT_COST — Direct and indirect cost amounts funded by the installment.
- BILLABLE_FLAG — Indicates billability of the installment.
- PROPOSAL_ID — Reference to the originating proposal.
- DESCRIPTION — Free-text description, VARCHAR2(250).
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield structure-defining and segment columns.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.
Common Use Cases and Queries
Typical reporting scenarios include listing all active funding installments for an award, reconciling direct and indirect cost funding against the award budget, and distinguishing funding rows from documentation-only amendments. A representative query is:
SELECT i.installment_num, i.type, i.active_flag, i.start_date_active, i.end_date_active, i.direct_cost, i.indirect_cost FROM gms.gms_installments i WHERE i.award_id = :award_id AND i.active_flag = 'Immediate' ORDER BY i.installment_num;- Aggregation by award:
SELECT award_id, SUM(direct_cost) direct_total, SUM(indirect_cost) indirect_total FROM gms.gms_installments WHERE type = 'Award' GROUP BY award_id; - Documentation audit:
SELECT installment_num, issue_date, description FROM gms.gms_installments WHERE award_id = :award_id AND type = 'Amendment'; - Proposal traceability:
SELECT award_id, installment_num, proposal_id FROM gms.gms_installments WHERE proposal_id IS NOT NULL;
Because the unique business key is (AWARD_ID, INSTALLMENT_NUM), joins to award master data should be driven through AWARD_ID, and lookups by user-facing installment number must always be qualified by award. The GMS_INSTALLMENTS_U2 index supports this access path directly.
Related Objects
The following objects are the most significant dependencies on GMS_INSTALLMENTS, based on the documented foreign key relationships:
- IGF_AW_AWARD_ALL — Referenced by GMS_INSTALLMENTS.AWARD_ID; the principal parent for award-level joins.
- IGS_FI_PP_INSTLMNTS — Referenced by GMS_INSTALLMENTS.INSTALLMENT_ID; links the GMS installment to the financials installment record.
- GMS_INSTALLMENTS_U1 — Unique index on INSTALLMENT_ID (primary key enforcement).
- GMS_INSTALLMENTS_U2 — Unique index on (AWARD_ID, INSTALLMENT_NUM); the business-key candidate most often queried by users searching for gms_installments_u2.
- GMS_AWARD_BUDGETS / GMS_AWARD_HEADERS (GMS schema) — Award-level entities against which installment funding is reconciled in standard Grants Management reporting.
- IGF proposal entities — Accessed through the PROPOSAL_ID column for proposal-to-award traceability.
No additional FK relationships beyond the two documented references are asserted here; the table is classified as standalone in the Data Vault heuristic, and the indexes and columns listed above constitute the complete documented physical footprint for release 12.2.2.
-
INDEX: GMS.GMS_INSTALLMENTS_U2
12.2.2
owner:GMS, object_type:INDEX, object_name:GMS_INSTALLMENTS_U2, status:VALID,
-
INDEX: GMS.GMS_INSTALLMENTS_U2
12.1.1
owner:GMS, object_type:INDEX, object_name:GMS_INSTALLMENTS_U2, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
TABLE: GMS.GMS_INSTALLMENTS
12.2.2
owner:GMS, object_type:TABLE, fnd_design_data:GMS.GMS_INSTALLMENTS, object_name:GMS_INSTALLMENTS, status:VALID,
-
TABLE: GMS.GMS_INSTALLMENTS
12.1.1
owner:GMS, object_type:TABLE, fnd_design_data:GMS.GMS_INSTALLMENTS, object_name:GMS_INSTALLMENTS, status:VALID,
-
eTRM - GMS Tables and Views
12.1.1
description: Versions of award and budget workflows. There can be many workflows for an award or budget. ,
-
eTRM - GMS Tables and Views
12.2.2
description: Versions of award and budget workflows. There can be many workflows for an award or budget. ,