Results for “direct_cost”

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

Overview

GMS_INSTALLMENTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Grants Accounting (GMS) product family. Its purpose is to present installment records for awards in a decoded, presentation-ready form. An installment in Grants Accounting represents a scheduled or event-driven request for payment against an award, characterized by amounts for direct and indirect cost, an active period, a billing status, and a classification type. The view exposes the transactional installment data together with a translated installment type description, removing the need for downstream consumers—reports, concurrent programs, integrations, and ad hoc queries—to perform their own lookup join. The object carries a VALID status in both the 12.1.1 and 12.2.2 releases and is documented in the ETRM repository with identical owner and referenced-object metadata. Because it is a view rather than a table, it holds no data of its own and imposes minimal storage overhead, but it inherits the read consistency and performance characteristics of the underlying base objects.

Underlying Base Objects

The view is defined over two referenced objects: the synonym GMS_INSTALLMENTS, which resolves to the base installment table holding the authoritative installment records, and the view GMS_LOOKUPS, which supplies lookup code translations. The join condition is a foreign-key-style lookup rather than a relational constraint:

FROM GMS_INSTALLMENTS I, GMS_LOOKUPS LP WHERE LP.LOOKUP_TYPE = 'INSTALLMENT_TYPE' AND LP.LOOKUP_CODE = I.TYPE

In practical terms, GMS_INSTALLMENTS is the driving object and contributes every substantive attribute, while GMS_LOOKUPS contributes a single derived column, the lookup meaning presented as TYPE_DIS. Because the join is an inner join on the lookup type INSTALLMENT_TYPE, an installment whose TYPE value has no matching lookup code in that lookup type will be excluded from the result set. Consumers relying on row counts should account for this behavior and, where completeness matters, query the base table directly. The view is created and owned by APPS, so it is normally queried without a schema prefix by application users and with the APPS prefix in DBA and technical documentation.

Key Columns

The column list mirrors the base table's structure, with the addition of the decoded type description. The primary identifier is INSTALLMENT_ID, with INSTALLMENT_NUM providing the user-facing sequence number and AWARD_ID linking each installment to its parent award. The DIRECT_COST and INDIRECT_COST columns carry the monetary amounts associated with the installment and are the attributes most frequently targeted by searches such as "direct_cost." The active period is bounded by START_DATE_ACTIVE and END_DATE_ACTIVE, while CLOSE_DATE records the date an installment was closed. ACTIVE_FLAG and BILLABLE_FLAG are status indicators controlling whether the installment is currently in force and whether it may be billed. TYPE holds the lookup code, and TYPE_DIS exposes the corresponding lookup meaning from GMS_LOOKUPS. ISSUE_DATE and DESCRIPTION provide the issuance date and free-text narrative. Fifteen descriptive flexfield columns, ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15, support customer-specific extensions. Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and ROWID complete the projection.

Common Use Cases and Queries

Typical uses include award funding reports, billing schedules, and integration extracts that load installment data into external financial or reporting systems. The following query retrieves active, billable installments with direct cost amounts for a given award:

• SELECT installment_id, installment_num, direct_cost, indirect_cost, type_dis, start_date_active, end_date_active FROM gms_installments_v WHERE award_id = :p_award_id AND active_flag = 'Y' ORDER BY installment_num;
• SELECT type_dis, SUM(direct_cost) direct_total, SUM(indirect_cost) indirect_total FROM gms_installments_v WHERE award_id = :p_award_id GROUP BY type_dis;
• SELECT installment_id, direct_cost, indirect_cost FROM gms_installments_v WHERE billable_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

Queries should filter by AWARD_ID wherever possible to keep result sets bounded, and developers requiring absolute completeness should be aware of the inner join to GMS_LOOKUPS described above.