Results for “award_status”

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

Overview

GMS_AWARD_STATUS_V is a lightweight dictionary-style view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMS – Grants Accounting product family. The view exposes the set of valid award status values used throughout the Grants Accounting module. Rather than storing operational award records or transactional data, it serves strictly as a reference (lookup) view that translates the internal lookup code list defined for the lookup type AWARD_STATUS into human-readable status meanings. Its status is documented as VALID in the ETRM repository for release 12.2.2, and the same definition applies under 12.1.1, where Grants Accounting shares the identical lookup-driven data model.

Because awards progress through a controlled lifecycle — from draft and submission through active, suspended, and finally closed or terminated — reporting tools, concurrent programs, and integration interfaces need a consistent, stable source for the permitted status values. GMS_AWARD_STATUS_V provides exactly that: a single, minimal projection over the lookup definitions, ensuring that any consumer querying the view retrieves only the status values that the application regards as valid for an award.

Underlying Base Objects

The view is defined over a single referenced base object: GMS_LOOKUPS, which itself is a view within the APPS schema rather than a physical table. GMS_LOOKUPS in turn draws on the underlying lookup infrastructure maintained by the Oracle Application Object Library (typically FND_LOOKUP_VALUES and its associated tables, which store lookup types, lookup codes, meanings, descriptions, enabled flags, and effective dates).

The defining query is deliberately simple. It selects the MEANING column with a DISTINCT qualifier, filtered by the predicate LOOKUP_TYPE = 'AWARD_STATUS'. Consequently the view returns one row per distinct award status meaning, with no joins to award headers, award funding, or transactional tables. It is therefore a pure code-to-meaning reference view with no dependency on award data itself, which makes it inexpensive to query and safe to use in validation and display logic across Grants Accounting.

Key Columns

• AWARD_STATUS — The sole documented column exposed by the view. Despite the name, the column carries the meaning (the descriptive, user-facing text) of each value defined under the AWARD_STATUS lookup type, such as Active, Closed, Suspended, or Terminated, depending on the values configured in the instance. All rows returned are distinct.

Because only the meaning is projected, the view does not expose the underlying lookup code, description, enabled flag, start or end dates, or tag. Consumers requiring those attributes must query GMS_LOOKUPS or FND_LOOKUP_VALUES directly and filter on the same lookup type. This design keeps the view narrow and purpose-specific: it answers the question "which award status descriptions exist?" rather than "what are the full attributes of each status?"

Common Use Cases and Queries

The principal use case is populating list-of-values (LOV) regions and validation lists in custom reports, forms, OAF pages, and concurrent programs that present or filter awards by status. It is equally useful in BI Publisher and Oracle Reports data models where a static set of permitted award statuses is needed.

• Retrieve all valid award statuses for an LOV: SELECT award_status FROM apps.gms_award_status_v ORDER BY award_status;
• Validate that a user-supplied status is legitimate: SELECT 1 FROM apps.gms_award_status_v WHERE award_status = :p_status;
• Drive a report parameter list of statuses: SELECT DISTINCT award_status FROM apps.gms_award_status_v;
• Cross-check against configured lookup values to confirm completeness: join or compare with GMS_LOOKUPS filtered on LOOKUP_TYPE = 'AWARD_STATUS'.

Because the view returns only distinct meanings, it should not be used to infer lookup codes, enabled/disabled state, or date-effective validity. For those requirements, reference the lookup tables directly. As with all APPS-owned objects, access should be granted through standard EBS responsibility and security conventions rather than direct schema grants.