Search Results contact_role_type




Overview
Explore in AI Chat

Overview

APPS.AST_ORG_CONTACT_ROLES_V is a reporting and integration view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes organization contact role assignments together with their decoded lookup meanings. The view is defined over HZ_ORG_CONTACT_ROLES, the base table that stores the relationship between an organization contact and the role that contact performs for a given organization, and it resolves two code columns into human-readable descriptions by outer-joining AR_LOOKUPS twice. The first join decodes ROLE_TYPE against lookup type CONTACT_ROLE_TYPE; the second decodes STATUS against lookup type REGISTRY_STATUS.

The view restricts its output to records whose STATUS is 'A' (active) or 'I' (inactive), which means logically deleted or otherwise excluded statuses are filtered out before the caller ever sees them. For users searching on the term "contact_role_type", this view is the standard access point: the ROLE_TYPE column is the foreign key to the CONTACT_ROLE_TYPE lookup, and the view surfaces the corresponding MEANING so that reports do not have to join the lookup table themselves.

Underlying Base Objects

The documented base objects for the view are:

  • HZ_ORG_CONTACT_ROLES (referenced through a synonym) — the primary driving object. It stores one row per organization contact role, including role type, role level, primary flag, status, audit columns, DFF attribute columns, and the object version number used for optimistic locking.
  • AR_LOOKUPS (view) — joined twice, aliased LKUP1 and LKUP2, to translate ROLE_TYPE and STATUS into their display meanings. Both joins are outer joins, so a contact role is still returned even if no matching lookup row exists.

Because HZ_ORG_CONTACT_ROLES is the TCA (Trading Community Architecture) store for contact roles, this view sits in the same family as other HZ_ORG_CONTACT* objects and is typically consumed alongside HZ_ORG_CONTACTS and HZ_PARTIES when a full contact picture is required.

Key Columns

Common Use Cases and Queries

Typical uses include contact-role reporting, identifying primary contacts by role for a party, and validating that role assignments carry a recognized CONTACT_ROLE_TYPE. A representative query listing all roles for a given organization contact is:

  • SELECT org_contact_id, role_type, meaning, primary_flag, status FROM apps.ast_org_contact_roles_v WHERE org_contact_id = :p_contact_id;

To retrieve only primary contacts per role type:

  • SELECT org_contact_id, role_type, meaning FROM apps.ast_org_contact_roles_v WHERE primary_contact_per_role_type = 'Y' AND status = 'A';

Because the view already decodes lookups, it is well suited to BI Publisher reports, OA Framework list-of-values, and integration extracts that must present readable role and status labels rather than raw codes.