Results for “type_dis”

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

Overview

GMS_REFERENCE_NUMBERS_V is a reporting view owned by the APPS schema in Oracle EBS Release 12.1.1 and 12.2.2. It belongs to the GMS – Grants Accounting product family and exposes reference number records associated with awards so that they can be consumed directly by reports, concurrent programs, forms, and integration interfaces without requiring joins to the lookup tables. Reference numbers in Grants Accounting are the externally assigned identifiers that funders, sponsors, and agencies use to track a sponsored project; they are distinct from the internal AWARD_ID primary key. The view joins each reference number row to its corresponding lookup definition so that a decoded meaning for the reference number type is returned alongside the raw stored value.

The view is documented as VALID in ETRM and is intended as a read-only presentation layer. Because decoding of the TYPE column is performed inside the view, consumers avoid re-implementing the GMS_LOOKUPS join, which reduces the risk of inconsistent type descriptions across reports and interfaces.

Underlying Base Objects

The view is defined over two documented objects:

• GMS_REFERENCE_NUMBERS (documented as a SYNONYM): the transaction table that stores the reference number rows. It supplies AWARD_ID, TYPE, VALUE, REQUIRED_FLAG, and the standard WHO audit columns.
• GMS_LOOKUPS (documented as a VIEW): the lookup presentation object used for decoding. The join is constrained to LOOKUP_TYPE = 'REFERENCE_NUMBER' and LOOKUP_CODE = R.TYPE.

The documented view text performs an inner join between the two objects, meaning rows in GMS_REFERENCE_NUMBERS whose TYPE has no active lookup row of type REFERENCE_NUMBER are excluded from the result set. The GMS_LOOKUPS object is itself a view over the Oracle Applications lookup infrastructure, so the decoded MEANING reflects the currently defined lookup meaning rather than a value stored on the transaction row. Standard WHO columns are carried through unchanged from the base table.

Key Columns

• AWARD_ID: the award identifier that the reference number belongs to; the primary correlation key back to the award.
• TYPE: the lookup code identifying the kind of reference number (for example, a sponsor reference or agency identifier).
• VALUE: the actual reference number or identifier value as entered.
• TYPE_DIS (also exposed as MEANING in the view text): the decoded description of the TYPE, sourced from GMS_LOOKUPS.MEANING.
• REQUIRED_FLAG: indicates whether the reference number is mandatory for the associated award or type.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN: standard audit columns tracking who created or last modified the row and when.
• ROWID: the physical row identifier of the underlying GMS_REFERENCE_NUMBERS row.

Common Use Cases and Queries

This view is typically used in award reporting, sponsor-facing extracts, and validation queries that need reference numbers with human-readable type descriptions. A straightforward listing for a single award:

• SELECT award_id, type, type_dis, value, required_flag FROM apps.gms_reference_numbers_v WHERE award_id = :p_award_id;

To identify awards carrying a particular type of reference number, filter on TYPE, which is indexed in the base table more predictably than the decoded description:

• SELECT award_id, value FROM apps.gms_reference_numbers_v WHERE type = :p_lookup_code;

Because the decode is embedded, the view is also convenient for concurrent program extracts and BI Publisher data templates where lookup joins are undesirable. Note that the inner join to GMS_LOOKUPS means any integration expecting to see rows with retired or missing lookup codes should query GMS_REFERENCE_NUMBERS directly instead.