Results for “ra_contact_roles”

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

Overview

RA_CONTACT_ROLES is an Oracle Receivables (AR) table that stores the roles or usages assigned to contacts within the E-Business Suite. Each row represents a specific role that a contact plays in a business context, such as billing contact, statement recipient, dunning contact, or correspondence recipient. Because a single contact can serve multiple roles, the table provides a many-to-many bridge between individual contacts and the functional purposes they fulfill, and it is central to how Receivables selects the correct party when generating invoices, statements, dunning letters, and collections correspondence.

The object resides in the AR schema and is marked VALID across Oracle EBS 12.1.1 and 12.2.2. The documented primary key is controlled by the RA_CONTACT_ROLES_PK constraint on CONTACT_ROLE_ID. From a Data Vault modeling perspective, the mined relationship structure suggests a satellite-leaning classification: the table depends closely on a parent contact entity and carries descriptive role attributes rather than acting as a pure hub or a link. Analysts designing an integration layer or data warehouse should treat RA_CONTACT_ROLES as descriptive detail that hangs off the contact subject area, with role semantics carried in attributes rather than in independent keys.

Key Information Stored

The table is documented with 30 columns. The most consequential are:

• CONTACT_ROLE_ID — The surrogate primary key, enforced by RA_CONTACT_ROLES_PK and backed by the unique index RA_CONTACT_ROLES_U1. This is the technical identifier for a single role assignment.
• CONTACT_ID — Foreign key to the contact parent, identifying which contact holds the role. Together with USAGE_CODE, it forms the unique index RA_CONTACT_ROLES_U2, making (CONTACT_ID, USAGE_CODE) a business-key candidate and confirming that a contact may hold each usage code only once.
• USAGE_CODE — The functional role or usage assigned to the contact, such as billing, statement, dunning, or correspondence recipient. This code is the primary filtering and lookup attribute for role resolution.
• PRIMARY_FLAG — Indicates whether the role is the primary designation for the contact, used to disambiguate when multiple contacts could serve a purpose.
• ORIG_SYSTEM_REFERENCE — Holds the identifier of the originating system when contact roles are imported or synchronized from an external source.
• Attribute columns (ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15) — The standard Oracle EBS flexfield segment set, available for descriptor, reference, or global attribute extensions.
• Audit and concurrency columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide who/when auditing and optimistic locking.
• Concurrent program columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE record which request and program created or last updated the row.

Common Use Cases and Queries

Typical scenarios include identifying all roles assigned to a contact, locating the billing or statement contact for a customer, resolving which contact should receive dunning or collections correspondence, and synchronizing role data with external CRM or master data systems. A representative query to list every role for a contact is:

• SELECT r.contact_role_id, r.contact_id, r.usage_code, r.primary_flag, r.last_update_date FROM ra_contact_roles r WHERE r.contact_id = :p_contact_id ORDER BY r.primary_flag DESC, r.usage_code;

To find the primary billing contact, filter on the usage code and the primary flag:

• SELECT r.contact_id FROM ra_contact_roles r WHERE r.usage_code = :p_usage_code AND r.primary_flag = 'Y';

Because RA_CONTACT_ROLES_U2 guarantees one row per contact/usage combination, reporting joins can rely on that uniqueness instead of aggregating. The ORIG_SYSTEM_REFERENCE column should be used during reconciliation when roles are loaded from external sources. The attribute columns support client-specific descriptor flexfields for reporting extensions.

Related Objects

The table’s relationship structure is centered on the contact parent referenced by CONTACT_ID. Significant related objects include:

• Parent contact table — joined through RA_CONTACT_ROLES.CONTACT_ID, supplying party/contact name and context for each role row.
• RA_CONTACTS — the Receivables contact entity that anchors the relationship and is the natural join partner for role queries.
• HZ_CONTACT_ROLE context objects — the Trading Community Architecture layer that stores contact role assignments at the party model level and is commonly synchronized with RA_CONTACT_ROLES.
• RA_CUSTOMERS — customer records linked to the contacts that hold these roles, used when deriving recipient information for billing and collections.
• RA_DUNNING_LETTERS / collection correspondence objects — consume the usage and primary flags to determine letter recipients.
• RA_STATEMENTS and statement cycle objects — rely on statement usage codes to select statement recipients.

All joins should use CONTACT_ID, and the (CONTACT_ID, USAGE_CODE) unique index guarantees deterministic joins for role-specific lookups.