Results for “gms_terms_conditions_v”

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

Overview

The GMS_TERMS_CONDITIONS_V view is a denormalized reporting and integration object owned by the APPS schema within the Oracle E-Business Suite Grants Accounting (GMS) module. Its documented status is VALID and it is shipped in both EBS 12.1.1 and 12.2.2. The view consolidates award-level terms and conditions into a single, readable row per award term, joining identifier information from the awarding transaction with descriptive attributes maintained on the term definition and its category.

Because grants awards carry many negotiated terms—reporting obligations, cost-share requirements, prior-approval thresholds, and sponsor-specific clauses—the raw transaction tables store these as numeric IDs and coded values. GMS_TERMS_CONDITIONS_V resolves those IDs into human-readable category descriptions and term names, which is precisely what makes it valuable for BI Publisher reports, OBIEE extracts, custom concurrent programs, and inbound/outbound interfaces. The user search term "term_name" corresponds to the view's TERM_NAME column, the primary descriptive field consumers filter and display against.

Underlying Base Objects

The documented view text defines GMS_TERMS_CONDITIONS_V over three base objects, all referenced through public synonyms owned by APPS:

• GMS_AWARDS_TERMS_CONDITIONS — the award-level transaction table (alias ATC) providing AWARD_ID, TERM_ID, CATEGORY_ID, OPERAND, VALUE, and WHO/date audit columns.
• GMS_TERMS_CONDITIONS — the term definition table (alias TC) supplying TC.NAME (TERM_NAME) and DESCRIPTION.
• GMS_TC_CATEGORIES — the term category table (alias TCC) supplying the category NAME (CATEGORY_DIS).

The join condition is ATC.TERM_ID = TC.TERM_ID AND ATC.CATEGORY_ID = TC.CATEGORY_ID AND TCC.CATEGORY_ID = TC.CATEGORY_ID. This is an inner join on all three objects, so only awards whose terms resolve to valid definitions and categories are returned. The view does not itself store data; it is a read-only projection and should always be queried rather than duplicated.

Key Columns

• AWARD_ID — Foreign key to the GMS award; the primary grouping key for reporting.
• TERM_ID — Identifier of the specific term within its category.
• CATEGORY_ID — Identifier of the term category to which the term belongs.
• CATEGORY_DIS — Human-readable category name, sourced from GMS_TC_CATEGORIES.NAME.
• TERM_NAME — The term's display name from GMS_TERMS_CONDITIONS.NAME; this is the column most commonly searched and reported.
• DESCRIPTION — Free-form descriptive text explaining the term.
• OPERAND — The comparison operator associated with the term's value (for example, equals, greater than, less than).
• VALUE — The award-specific value or threshold captured for that term.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns for change tracking.
• ROW_ID — The ROWID of the underlying ATC row, useful for identifying the source record.

Common Use Cases and Queries

Typical scenarios include listing all terms captured on an award for a terms-and-conditions report, driving approval notifications when specific thresholds are configured, and extracting award term data into a data warehouse. The following query returns all terms for a given award, ordered by category and term name:

SELECT award_id,
       category_dis,
       term_name,
       operand,
       value,
       last_update_date
FROM   apps.gms_terms_conditions_v
WHERE  award_id = :p_award_id
ORDER BY category_dis, term_name;

To locate every award affected by a particular term, filter directly on the search term column:

SELECT award_id, category_dis, term_name, value
FROM   apps.gms_terms_conditions_v
WHERE  UPPER(term_name) LIKE UPPER('%' || :p_term_name || '%');

Because the view performs three-way inner joins, filters on TERM_NAME and CATEGORY_DIS are applied against the definition tables and are not index-friendly on the ATC leading column; for large award populations, constrain first by AWARD_ID where possible. All queries should be executed against the APPS schema with the standard Grants Accounting responsibility grants in place.