Results for “usage_code”

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

Overview

GMS_LOC_CONTACTS_V is an APPS-owned database view in the Oracle E-Business Suite Grants Accounting (GMS) module. It presents a denormalized, reporting-friendly projection of award contacts associated with grant awards, joining award header data, customer account contact roles, party person details, organization contact attributes, and site-level usage information. The view resolves several foreign key codes to their human-readable meaning values, notably the contact title (via AR_LOOKUPS on lookup type CONTACT_TITLE) and the site usage code (via AR_LOOKUPS on lookup type SITE_USE_CODE). This is precisely the reason a search for "usage_meaning" surfaces this object: the USAGE_MEANING column exposes the translated description of the contact's usage code rather than the raw code value. The view is read-only and is intended for inquiry, reporting, and integration extraction rather than direct DML. Because it encapsulates complex multi-table relationships in People/HR (HZ) and Receivables (AR) schemas, it is commonly used by grant administrators developing custom reports and by technologists building outbound interfaces that require award contact information in a flattened form.

Underlying Base Objects

The view is defined over a mix of synonyms and a view, all resolved within the APPS schema. The documented referenced base objects are: AR_LOOKUPS (a view on lookup values), GMS_AWARDS (synonym), GMS_AWARDS_CONTACTS (synonym), HZ_CUST_ACCOUNT_ROLES (synonym), HZ_CUST_ACCT_SITES_ALL (synonym), HZ_ORG_CONTACTS (synonym), HZ_PARTIES (synonym), and HZ_RELATIONSHIPS (synonym). GMS_AWARDS supplies the award identifier and links to the bill-to customer; GMS_AWARDS_CONTACTS is the primary driving table that associates awards with customer account contacts and carries the USAGE_CODE, PRIMARY_FLAG, and audit columns; HZ_CUST_ACCOUNT_ROLES stores the role definition (restricted to ROLE_TYPE = 'CONTACT' and STATUS = 'A'); HZ_PARTIES and HZ_RELATIONSHIPS resolve the person identity through a self-referencing relationship between subject and object parties; HZ_ORG_CONTACTS adds organizational contact attributes such as JOB_TITLE and MAIL_STOP; HZ_CUST_ACCT_SITES_ALL provides the site identifier; and AR_LOOKUPS is joined twice in outer-join fashion to translate the title and site usage meanings. Oracle assigns synonyms to the application tables to permit cross-schema access from APPS.

Key Columns

The view exposes the following documented columns:

• AWARD_ID — Identifier of the parent award in GMS_AWARDS.
• CONTACT_ID — Surrogate identifier of the contact, derived from the customer account role.
• TITLE_MEANING — Translated contact title, resolved from AR_LOOKUPS where LOOKUP_TYPE = 'CONTACT_TITLE'.
• FIRST_NAME / LAST_NAME — Person name values truncated to 40 and 50 bytes respectively via SUBSTRB.
• STATUS — Contact role status; the view restricts returned rows to 'A' (active).
• JOB_TITLE / MAIL_STOP — Organizational contact attributes sourced from HZ_ORG_CONTACTS.
• ORIG_SYSTEM_REFERENCE — Originating system key for the contact record, useful in integration mapping.
• ADDRESS_ID — Customer account site identifier.
• CUSTOMER_ID — Trading community customer identifier from GMS_AWARDS_CONTACTS.
• USAGE_CODE — The raw site usage code assigned to the contact.
• USAGE_MEANING — Translated meaning of the usage code, resolved from AR_LOOKUPS where LOOKUP_TYPE = 'SITE_USE_CODE'. This is the column that answers the "usage_meaning" search.
• PRIMARY_FLAG — Indicates whether the contact is the primary contact for the award.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and ROW_ID.

Common Use Cases and Queries

Typical scenarios include listing all active contacts for a given award with their translated usage meaning, building grant contact directories, and extracting contact data for downstream systems. Note that the CONTACT_ID alias in the view actually maps to CUST_ACCOUNT_ROLE_ID, so joins and filters should account for this naming convention.

Sample query returning contacts and usage meanings for a specific award:

SELECT award_id, contact_id, first_name, last_name,
       title_meaning, usage_code, usage_meaning, primary_flag
FROM   apps.gms_loc_contacts_v
WHERE  award_id = :p_award_id
ORDER  BY primary_flag DESC, last_name;

A second query filters by usage meaning to identify contacts of a particular usage type across awards:

SELECT award_id, last_name, job_title, mail_stop, usage_meaning
FROM   apps.gms_loc_contacts_v
WHERE  usage_meaning IN ('BILL TO', 'SHIP TO')
AND    status = 'A';

Because AR_LOOKUPS is outer-joined, USAGE_MEANING may be null where no lookup row exists; reports should therefore coalesce this column to the raw USAGE_CODE as a fallback. As with all Oracle EBS seeded views, the definition is subject to change across releases, so dependent customizations should be regression-tested during upgrades.