Results for “role_res”

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

Overview

APPS.AR_CONTACT_ROLES_V is a reporting and integration view in the Oracle E-Business Suite Receivables (AR) module. It exposes role-responsibility assignments associated with trading community contacts, joining the underlying role-responsibility records to Receivables lookup values in order to resolve a human-readable meaning for each responsibility type. The view is defined as a non-ANSI outer join between HZ_ROLE_RESPONSIBILITY and AR_LOOKUPS, allowing rows to be returned even when no matching lookup value exists.

Because it presents denormalized, decoded data across the two objects, the view is commonly consumed by forms, concurrent programs, and custom SQL that need to relate a contact or customer account role to its descriptive responsibility classification without writing the join manually. The ROWID column preserved from the base record also makes the view usable in certain update-through-view patterns within Oracle Forms.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, AR_CONTACT_ROLES_V references two objects:

• HZ_ROLE_RESPONSIBILITY — referenced through the synonym ROLE_RES; the primary source of role-responsibility rows, including responsibility type, primary flag, and descriptive flexfield attributes.
• AR_LOOKUPS — referenced as ARLKP1; supplies the decoded MEANING for the responsibility type via an outer join on RESPONSIBILITY_TYPE = LOOKUP_CODE and LOOKUP_TYPE = 'SITE_USE_CODE'.

Both objects are documented in ETRM as a SYNONYM (HZ_ROLE_RESPONSIBILITY) and a VIEW (AR_LOOKUPS) respectively. The outer join (+) notation confirms that responsibility rows are preserved even where the SITE_USE_CODE lookup does not resolve.

Key Columns

• ROWID — row identifier of the underlying HZ_ROLE_RESPONSIBILITY record.
• RESPONSIBILITY_ID — unique identifier of the role-responsibility assignment.
• RESPONSIBILITY_TYPE — code classifying the responsibility; joined to the SITE_USE_CODE lookup set.
• CUST_ACCOUNT_ROLE_ID — foreign key to the customer account role.
• ORIG_SYSTEM_REFERENCE — source-system identifier for the record.
• PRIMARY_FLAG — indicates whether this responsibility is the primary one.
• MEANING — decoded description of RESPONSIBILITY_TYPE from AR_LOOKUPS.
• Object version columns — OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield context and segment values.

Common Use Cases and Queries

The view is typically queried to list decoded responsibility types for a customer account role or contact, or to troubleshoot responsibility-type mappings.

• List all responsibilities with their decoded meanings:
  SELECT responsibility_id, responsibility_type, meaning, primary_flag FROM apps.ar_contact_roles_v;
• Retrieve responsibilities for a specific customer account role:
  SELECT responsibility_id, responsibility_type, meaning FROM apps.ar_contact_roles_v WHERE cust_account_role_id = :role_id;
• Identify responsibility types lacking a valid lookup mapping:
  SELECT responsibility_id, responsibility_type FROM apps.ar_contact_roles_v WHERE meaning IS NULL;
• Inspect flexfield data captured on role responsibilities:
  SELECT responsibility_id, attribute_category, attribute1 FROM apps.ar_contact_roles_v WHERE attribute_category IS NOT NULL;

As a view, AR_CONTACT_ROLES_V carries no independent storage; all reads resolve against the two underlying objects, and performance depends on indexing on HZ_ROLE_RESPONSIBILITY and the AR_LOOKUPS lookup code.