Results for “ra_hcontact_roles”

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

Overview

RA_HCONTACT_ROLES is a Receivables (AR) module view that exposes contact role information in Oracle EBS 12.1.1 and 12.2.2. Its documented description is simply "Contact roles." The view presents a denormalized, backward-compatible projection of contact-role assignments, mapping legacy column names to the columns physically stored in the underlying HZ (Trading Community Architecture) table. It serves reporting, integration, and upgrade-stabilization purposes: reports and interfaces historically written against the legacy AR contact-role model can continue to query familiar column names such as USAGE_CODE and CONTACT_ID while the physical data resides in the HZ schema.

In the supplied ETRM 12.2.2 metadata, the view is recorded as "Not implemented in this database," and no base objects are separately documented. Nevertheless, the view text clearly identifies HZ_ROLE_RESPONSIBILITY (aliased ROLE_RES) as its sole source object. The view is therefore a lightweight wrapper rather than a stored, materialized structure.

Underlying Base Objects

The view is defined exclusively over HZ_ROLE_RESPONSIBILITY. Each row of that table represents a role or responsibility associated with a contact, customer account, or party. The view performs no joins, aggregations, or filters; it is a straight column projection with aliasing. Several columns are renamed during projection to preserve legacy naming conventions:

• ROLE_RES.RESPONSIBILITY_TYPE is exposed as USAGE_CODE.
• ROLE_RES.CUST_ACCOUNT_ROLE_ID is exposed as CONTACT_ID.
• ROLE_RES.RESPONSIBILITY_ID is exposed under the column name CONTACT_ROLE_ID in the documented column list.

Because the definition is a simple projection, the view inherits the row cardinality, partitioning, and indexing behavior of HZ_ROLE_RESPONSIBILITY. No other AR, HZ, or FND tables are referenced in the view text provided.

Key Columns

• CONTACT_ROLE_ID — sourced from RESPONSIBILITY_ID; the unique identifier for the contact-role assignment.
• USAGE_CODE — sourced from RESPONSIBILITY_TYPE; indicates the role type or usage of the contact (for example, the business function the contact serves). This is the column most frequently referenced in searches and queries against this view.
• CONTACT_ID — sourced from CUST_ACCOUNT_ROLE_ID; identifies the contact or account-role record to which the role applies.
• PRIMARY_FLAG — indicates whether the role is the primary one for the contact.
• ORIG_SYSTEM_REFERENCE — the originating system's key, supporting data migration and multi-source integration.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• Concurrent program columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield (DFF) context and segment values.
• OBJECT_VERSION_NUMBER — optimistic locking version for the row.

Common Use Cases and Queries

Typical scenarios include auditing which roles a contact holds, filtering role assignments by usage, and feeding downstream extracts. The following sample selects active role usages for a given contact:

• SELECT contact_role_id, usage_code, contact_id, primary_flag FROM ra_hcontact_roles WHERE contact_id = :p_contact_id;
• SELECT usage_code, COUNT(*) FROM ra_hcontact_roles GROUP BY usage_code ORDER BY 2 DESC;
• SELECT r.contact_role_id, r.usage_code, r.orig_system_reference FROM ra_hcontact_roles r WHERE r.primary_flag = 'Y' AND r.last_update_date >= :p_since;

Because the view lacks filters, appropriate predicates on CONTACT_ID, USAGE_CODE, or the audit columns should be applied to limit result sets. In 12.2.2 environments where the view is not implemented, equivalent queries should target HZ_ROLE_RESPONSIBILITY directly, substituting RESPONSIBILITY_TYPE for USAGE_CODE and CUST_ACCOUNT_ROLE_ID for CONTACT_ID.