Search Results gms_installments




Overview
Explore in AI Chat

Overview

GMS_INSTALLMENTS is a transactional table owned by the GMS schema, the Grants Accounting module of Oracle E-Business Suite. It stores information about award installments — the scheduled or actual disbursement events associated with a grant or award. In EBS releases 12.1.1 and 12.2.2, the table is documented as VALID with 35 columns. Each row represents a single installment belonging to a specific award, identified through the award foreign key and an installment sequence number. The table carries both financial attributes (direct and indirect cost amounts), lifecycle attributes (active dates, close date, issue date), and descriptive attributes.

The ETRM metadata records a heuristic Data Vault classification of standalone for this object. As a modeling suggestion, this indicates the table is not a pure hub, link, or satellite in the Data Vault sense; it holds a mixture of transactional facts, lifecycle state, and descriptive attributes keyed to its own surrogate identifier and to an external award reference. Consumers should therefore treat it as an integrated transaction entity rather than a strict dimensional construct.

Key Information Stored

The table's surrogate primary key is INSTALLMENT_ID, enforced by the unique index GMS_INSTALLMENTS_U1. A second unique index, GMS_INSTALLMENTS_U2, covers (AWARD_ID, INSTALLMENT_NUM) and serves as the principal business-key candidate — no award may repeat an installment number.

  • INSTALLMENT_ID — surrogate primary key; also the FK to IGS_FI_PP_INSTLMNTS, tying the installment to the underlying payment-plan installment definition.
  • AWARD_ID — foreign key to IGF_AW_AWARD_ALL; the parent award to which this installment belongs.
  • INSTALLMENT_NUM — sequence number of the installment within the award; half of the business key.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — effective date range during which the installment is active.
  • CLOSE_DATE — date the installment was closed.
  • DIRECT_COST / INDIRECT_COST — the direct and indirect cost amounts associated with the installment.
  • ACTIVE_FLAG — indicates whether the installment is currently active.
  • BILLABLE_FLAG — indicates whether the installment is billable.
  • TYPE — classification of the installment.
  • ISSUE_DATE — date the installment was issued.
  • DESCRIPTION — free-text description of the installment.
  • PROPOSAL_ID — reference to the originating proposal.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns present on every row.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard EBS descriptive flexfield (DFF) columns, available for client-specific extensions.

Common Use Cases and Queries

Typical reporting needs include listing all installments for an award, reconciling active versus closed installments, and summarizing direct and indirect cost by award or period. A representative query retrieves installments for a given award ordered by sequence:

  • SELECT installment_id, installment_num, start_date_active, end_date_active, direct_cost, indirect_cost, active_flag FROM gms_installments WHERE award_id = :award_id ORDER BY installment_num;
  • Active-installment reports filter on active_flag = 'Y' combined with the date range between START_DATE_ACTIVE and END_DATE_ACTIVE.
  • Cost aggregation joins to IGF_AW_AWARD_ALL on AWARD_ID to group direct and indirect cost totals per award.
  • Non-billable installment reviews filter on billable_flag = 'N'.

Because the table is transactional, queries should generally be scoped by AWARD_ID or by the active date window to avoid full-table scans on large grant volumes.

Related Objects

The documented foreign keys establish the primary dependencies for this object:

  • IGF_AW_AWARD_ALL — joined via GMS_INSTALLMENTS.AWARD_ID; the parent award header providing award context.
  • IGS_FI_PP_INSTLMNTS — joined via GMS_INSTALLMENTS.INSTALLMENT_ID; the underlying payment-plan installment definition.

Downstream, other GMS Grants Accounting transactions that reference AWARD_ID — such as award budget, award cost, and billing/receipt records — commonly join through the award key to relate financial activity to specific installments. Reporting views and concurrent programs in the Grants Accounting module that summarize award funding and payment schedules read from GMS_INSTALLMENTS as the source of installment-level detail. Where the DFF columns are enabled, the attribute category and ATTRIBUTE1–15 are typically surfaced through descriptive flexfield views in the same application context.

Because the metadata classifies this object as standalone, no additional child tables are documented as directly foreign-keying GMS_INSTALLMENTS; integrators should confirm dependencies in their target instance before assuming referential relationships beyond the two documented foreign keys.