Results for “ar_contact_roles_v”

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

Overview

AR_CONTACT_ROLES_V is an Oracle Applications (APPS) view in the Receivables (AR) product family that exposes contact role information associated with customers and their site uses. The view is documented as a Release 11.5-only construct, and its structure is preserved in ETRM metadata for Oracle EBS 12.1.1 and 12.2.2 to support legacy reporting, migration, and integration compatibility analysis. It presents the assignment of a responsibility (role) to a contact record, joined against Receivables lookup values to resolve the coded responsibility type into a human-readable meaning.

Functionally, the view answers the question of which roles a contact holds and whether that role assignment is primary. This makes it relevant in customer master reporting, contact management dashboards, and data conversion routines that need to reconcile role assignments between legacy and current data models. Because the view carries an object version column, it is also relevant to optimistic concurrency patterns used by the underlying Oracle Customers (HZ) data model.

Underlying Base Objects

The ETRM metadata documents two referenced base objects:

• HZ_ROLE_RESPONSIBILITY (SYNONYM) — the primary driver of the view, supplying role assignment rows, responsibility identifiers, primary flag, descriptive flexfield attributes, and the object version number.
• AR_LOOKUPS (VIEW) — an outer-joined lookup source that maps RESPONSIBILITY_TYPE to a translated meaning. The join is defined on LOOKUP_CODE with LOOKUP_TYPE fixed to the value 'SITE_USE_CODE'.

In the underlying view text, the ROLE_RES alias refers to HZ_ROLE_RESPONSIBILITY and ARLKP1 refers to AR_LOOKUPS. The join to AR_LOOKUPS is a (+) outer join, meaning role rows without a matching site use code are still returned, with MEANING null. This construction is characteristic of lookups resolution used throughout Oracle Receivables.

Key Columns

The view exposes identity, audit, flexfield, and control columns. Principal columns include:

• ROW_ID — the underlying row identifier from HZ_ROLE_RESPONSIBILITY, exposed for row addressing.
• RESPONSIBILITY_ID / CONTACT_ROLE_ID — identifiers for the responsibility and the resulting contact role assignment.
• RESPONSIBILITY_TYPE / USAGE_CODE — the coded role type, joined to SITE_USE_CODE lookup values.
• PRIMARY_FLAG — indicates whether the role is the primary role for the contact.
• MEANING / USAGE_MEANING — the translated display value of the role code.
• OBJECT_VERSION_NUMBER / OBJECT_VERSION — the optimistic locking version used by the HZ data model; the user's search for "object_version" maps directly to this column.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments.

Common Use Cases and Queries

Typical uses include reporting contact role coverage, verifying primary role designations, and migrating role data by leveraging audit and flexfield columns. A representative query is:

• SELECT ROW_ID, RESPONSIBILITY_ID, RESPONSIBILITY_TYPE, MEANING, PRIMARY_FLAG, OBJECT_VERSION FROM APPS.AR_CONTACT_ROLES_V WHERE PRIMARY_FLAG = 'Y';
• SELECT RESPONSIBILITY_TYPE, COUNT(*) FROM APPS.AR_CONTACT_ROLES_V GROUP BY RESPONSIBILITY_TYPE;
• SELECT ROW_ID, OBJECT_VERSION FROM APPS.AR_CONTACT_ROLES_V WHERE RESPONSIBILITY_TYPE = :p_type AND PRIMARY_FLAG = 'Y';

Because the view is documented as Release 11.5 only, adopters on 12.1.1 and 12.2.2 should confirm availability and column presence against the customer's actual schema before relying on it in production interfaces.