Results for “gms_awards_contacts_u1”

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

Overview

GMS.GMS_AWARDS_CONTACTS is a transactional table within the Oracle E-Business Suite Grants Management (GMS) schema. It stores the association between an award and the external or internal contacts tied to that award, such as customer representatives, principal investigators, or administrative points of contact. The table is owned by the GMS schema and is registered in FND Design Data as GMS.GMS_AWARDS_CONTACTS, with a status of VALID across Oracle EBS 12.1.1 and 12.2.2. Physically, the table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, reflecting standard transactional data storage conventions.

In a heuristic Data Vault classification, this object behaves as a link table. It does not function as a standalone hub because its primary business attributes are composite references; instead it resolves the many-to-many relationship between awards and contacts, qualified by customer and usage context. Practitioners modeling GMS award data in a dimensional or Data Vault warehouse should treat GMS_AWARDS_CONTACTS as a link between an award hub and a contact hub, with PRIMARY_FLAG and USAGE_CODE acting as descriptive link attributes.

Key Information Stored

The table contains ten documented columns. The most significant are the four that participate in the unique business key, defined by the unique index GMS_AWARDS_CONTACTS_U1 in the APPS_TS_TX_IDX tablespace:

• AWARD_ID (NUMBER, 15) — Award identifier; the foreign key linking to IGF_AW_AWARD_ALL. This is the primary relationship column for the link.
• CONTACT_ID (NUMBER, 15) — Contact identifier, referencing the contact or party associated with the award.
• CUSTOMER_ID (NUMBER, 15) — Unique identifier of the customer that issued the award.
• USAGE_CODE (VARCHAR2, 30) — Contact usage type, qualifying the role or purpose of the contact in the context of the award.
• PRIMARY_FLAG (VARCHAR2) — Indicates whether the contact is the primary contact for the given usage.

Because the object definition does not document a single-column surrogate primary key, the composite of AWARD_ID, CONTACT_ID, CUSTOMER_ID, and USAGE_CODE serves as the business-key candidate enforced by GMS_AWARDS_CONTACTS_U1. The remaining columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — are standard Who columns maintained by the EBS audit framework, and should not be treated as business identifiers. Notably, the record is identified by its four-part business key rather than a system-generated sequence.

Common Use Cases and Queries

Typical reporting scenarios include listing all contacts on an award, identifying the primary contact per usage type, and reconciling award ownership by customer. A representative query joins the table to IGF_AW_AWARD_ALL to retrieve meaningful award descriptors:

• Retrieve contacts for a specific award: SELECT AWARD_ID, CONTACT_ID, CUSTOMER_ID, PRIMARY_FLAG, USAGE_CODE FROM GMS.GMS_AWARDS_CONTACTS WHERE AWARD_ID = :award_id;
• Locate primary contacts: filter on PRIMARY_FLAG = 'Y' combined with a specific USAGE_CODE.
• Aggregate contacts per award or per customer for contact-load reporting.
• Audit recent modifications using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Because the four-key uniqueness is enforced, any insert or update must respect GMS_AWARDS_CONTACTS_U1 to avoid a duplicate-key error. Downstream grants processing and award contact validation routines rely on this constraint to prevent duplicate role assignments.

Related Objects

The documented dependency information lists a single foreign key from GMS_AWARDS_CONTACTS to the award definition table. The most significant related objects are:

• IGF_AW_AWARD_ALL — joined via AWARD_ID; the parent award record supplying award-level attributes.
• GMS_AWARDS_CONTACTS# — the companion object referenced in the ETRM dependency listing, typically the shadow/interface counterpart used during concurrent processing or distribution.

No additional foreign keys are documented, so joins to contact or customer masters should be validated against the CONTACT_ID and CUSTOMER_ID values at implementation time. The single documented inbound dependency confirms that this table is a dependent child of the award entity rather than a parent of other stored objects.