Results for “contact_name”

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

Overview

AR_CONTACTS_ACTIVE_V is a seeded Oracle Receivables view owned by the APPS schema and defined over Oracle Trading Community Architecture (TCA) and Receivables base tables. It presents a flattened, denormalized list of active customer contacts — that is, parties holding a CONTACT role on a customer account with a status of A (Active). The view answers the recurring EBS question of "who are the active contacts for a given customer or customer site?" without requiring the caller to traverse the multi-table TCA relationship model directly.

Because the "org_cont" root reflects a search over customer contact assignments, this view is the canonical integration point for that requirement. It joins the account role assignment (HZ_CUST_ACCOUNT_ROLES), the party master record (HZ_PARTIES), the directional relationship linking subject to object parties (HZ_RELATIONSHIPS), and the organization contact detail where the job title is stored (HZ_ORG_CONTACTS). The result is a single row per active contact/account-role combination, ideal for reporting, LOVs, and downstream interfaces.

Underlying Base Objects

The view is defined over four documented base objects, all accessed through APPS synonyms:

• HZ_CUST_ACCOUNT_ROLES (alias ACCT_ROLE) — supplies the contact role assignment, the CUST_ACCOUNT_ROLE_ID, the owning customer account and site, and the role type/status filters.
• HZ_PARTIES (alias PARTY) — supplies the contact's party name.
• HZ_RELATIONSHIPS (alias REL) — links the contact party to the organization via a forward directional relationship.
• HZ_ORG_CONTACTS (alias ORG_CONT)) — supplies the job title held by the contact within the organization.

The join predicates are: ACCT_ROLE.PARTY_ID = REL.PARTY_ID, ORG_CONT.PARTY_RELATIONSHIP_ID = REL.RELATIONSHIP_ID, and REL.SUBJECT_ID = PARTY.PARTY_ID. The relationship is further constrained by SUBJECT_TABLE_NAME = 'HZ_PARTIES', OBJECT_TABLE_NAME = 'HZ_PARTIES', and DIRECTIONAL_FLAG = 'F'. Role filtering enforces ROLE_TYPE = 'CONTACT' and STATUS = 'A'.

Key Columns

• CONTACT_ID — sourced from ACCT_ROLE.CUST_ACCOUNT_ROLE_ID. This is the customer account role identifier, not the party ID.
• CONTACT_NAME — the party name from HZ_PARTIES.PARTY_NAME.
• JOB_TITLE — from HZ_ORG_CONTACTS.JOB_TITLE, the contact's role/title within the organization.
• CUSTOMER_ID — the owning customer account (CUST_ACCOUNT_ID).
• ADDRESS_ID — the customer account site (CUST_ACCT_SITE_ID) at which the contact is registered.

Common Use Cases and Queries

Typical uses include customer contact reports, site-level contact LOVs, and interfaces that need a flat contact feed. The following returns all active contacts for a specific customer account:

SELECT contact_id, contact_name, job_title, customer_id, address_id
FROM apps.ar_contacts_active_v
WHERE customer_id = :p_customer_id;

To retrieve contacts for a specific site:

SELECT contact_name, job_title
FROM apps.ar_contacts_active_v
WHERE address_id = :p_site_id
ORDER BY contact_name;

Because the view already filters ROLE_TYPE = 'CONTACT' and STATUS = 'A', no additional status predicate is normally required. Note that CONTACT_ID is the role ID, so joins to party-level data must be performed through HZ_CUST_ACCOUNT_ROLES rather than directly to HZ_PARTIES.