Results for “installment_type”

13 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.GMS_INSTALLMENTS_V is a reporting view in the Oracle E-Business Suite Grants Management (GMS) module, exposed under the APPS schema in both release 12.1.1 and 12.2.2. It presents award installment records together with the decoded meaning of each installment's type code, so that consumers receive a human-readable description rather than a raw lookup code. The view is defined over the transactional installment table GMS_INSTALLMENTS and joins it to GMS_LOOKUPS on the INSTALLMENT_TYPE lookup type. Because it is a view rather than a synonym to a base table, it is read-only in practice and is intended for reporting, inquiry, and integration extraction rather than for direct DML.

The view is particularly relevant when a user searches on "installment_type". The column TYPE holds the stored lookup code on each installment row, while the joined MEANING column supplies the translated display value from the INSTALLMENT_TYPE lookup. This pairing is the primary reason the view exists: it removes the requirement for downstream reporting tools to perform their own decode against GMS_LOOKUPS.

Underlying Base Objects

The view is documented as referencing two base objects:

  • GMS_INSTALLMENTS (SYNONYM) — the primary source of installment rows, aliased as I. This provides the identifier, award linkage, dates, cost amounts, flags, descriptive fields, the standard WHO audit columns, and the fifteen descriptive flexfield attribute columns.
  • GMS_LOOKUPS (VIEW) — aliased as LP, joined on LOOKUP_TYPE = 'INSTALLMENT_TYPE' and LOOKUP_CODE = I.TYPE. GMS_LOOKUPS is itself a view over the Oracle Applications lookup infrastructure, which means the returned MEANING value respects the application's lookup configuration.

The join is an inner join by construction: an installment row whose TYPE value has no corresponding INSTALLMENT_TYPE lookup code will not be returned by this view. Because the join is on lookup code rather than on a primary key, no row duplication occurs provided the lookup code is unique within the lookup type. Note also that GMS_LOOKUPS resolves MEANING according to session language settings, so the value returned can vary by user environment.

Key Columns

  • INSTALLMENT_ID — the unique identifier of the installment record.
  • INSTALLMENT_NUM — the user-visible installment number.
  • AWARD_ID — the award to which the installment belongs; the standard join key to award-level reporting.
  • TYPE — the installment type lookup code stored on GMS_INSTALLMENTS.
  • MEANING — the decoded description of the installment type from the INSTALLMENT_TYPE lookup. This is the column most consumers want when searching on "installment_type".
  • START_DATE_ACTIVE, END_DATE_ACTIVE, CLOSE_DATE, ISSUE_DATE — the lifecycle dates governing the installment's validity and issuance.
  • ACTIVE_FLAG, BILLABLE_FLAG — status indicators for active and billable installments.
  • DIRECT_COST, INDIRECT_COST — the cost amounts associated with the installment.
  • DESCRIPTION — free-text description of the installment.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield context and segment values.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, ROWID — audit and row-identity columns supporting incremental extraction and tool-level row addressing.

Common Use Cases and Queries

Typical uses include award installment inquiries, billing and invoicing validation, and interface extraction where the readable installment type is required.

List installments for a single award with decoded type:

  • SELECT INSTALLMENT_NUM, MEANING, START_DATE_ACTIVE, END_DATE_ACTIVE, DIRECT_COST, INDIRECT_COST FROM APPS.GMS_INSTALLMENTS_V WHERE AWARD_ID = :p_award_id ORDER BY INSTALLMENT_NUM;

Filter by installment type meaning:

  • SELECT AWARD_ID, INSTALLMENT_NUM, TYPE, MEANING FROM APPS.GMS_INSTALLMENTS_V WHERE MEANING = 'Invoice';

Activity report over a date range:

  • SELECT AWARD_ID, INSTALLMENT_NUM, MEANING, ISSUE_DATE FROM APPS.GMS_INSTALLMENTS_V WHERE ACTIVE_FLAG = 'Y' AND ISSUE_DATE BETWEEN :from_date AND :to_date;

Incremental extraction using the audit column:

  • SELECT INSTALLMENT_ID, AWARD_ID, TYPE, MEANING, LAST_UPDATE_DATE FROM APPS.GMS_INSTALLMENTS_V WHERE LAST_UPDATE_DATE > :last_run;