Search Results contact_row_id




Overview
Explore in AI Chat

Overview

AS_SALES_LEAD_CONTACTS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and defined in the AS (Sales Foundation) product family. It exposes sales lead contact details by denormalizing the association between a sales lead and the parties, relationships, and contact points that describe the individuals attached to that lead. The view is documented in ETRM as having a status of VALID and is delivered as part of the Sales Foundation data model underpinning Oracle Sales, TeleSales, and related lead-management flows in Release 12.1.1 and 12.2.2.

Because the view joins the lead-contact intersection table to the Trading Community Architecture (TCA) party and contact-point model, it presents human-readable contact attributes—names, titles, e-mail addresses, phone numbers, relationship codes, and lookup meanings—alongside the lead-contact key and descriptive flexfield columns. This makes it the natural reporting and integration surface for lead contact data, where consumers would otherwise need to reproduce several joins across HZ and AS tables.

Underlying Base Objects

The view text is defined over AS_SALES_LEAD_CONTACTS (the lead-contact base table, referenced by synonym) joined to the following TCA objects, also referenced by synonym: HZ_PARTIES, HZ_RELATIONSHIPS, and HZ_CONTACT_POINTS. Two lookup views complete the definition: AR_LOOKUPS and AS_LOOKUPS. AR_LOOKUPS supplies the translated meaning of the phone line type, while AS_LOOKUPS is joined in the predicate structure for lead-specific lookup values.

The joins are driven from the lead-contact row: HZ_RELATIONSHIPS is matched on REL.PARTY_ID = LEAD_CONTACT.CONTACT_PARTY_ID, HZ_PARTIES (aliased PARTY_CONTACTS) supplies the contact person's name attributes, and a second HZ_PARTIES instance (aliased REL_PARTY) supplies the related party's e-mail address. HZ_CONTACT_POINTS supplies phone attributes, and HZ_RELATIONSHIPS additionally contributes the relationship code and subject/object party identifiers. The view therefore sits directly on top of the AS lead-interaction tables and the HZ registry, with the lookup views providing decoded values.

Key Columns

Common Use Cases and Queries

Typical scenarios include listing all contacts for a lead with their decoded phone types, retrieving the primary contact for a lead, and feeding lead contact details into external CRM or campaign systems. A representative query selects the lead, contact name, e-mail, and primary phone:

SELECT sales_lead_id, first_name, last_name, email_address, phone_number, phone_type
FROM apps.as_sales_lead_contacts_v
WHERE sales_lead_id = :p_lead_id
AND primary_contact_flag = 'Y';

To join contact details back to a lead master query, use LEAD_CONTACT_ID or CONTACT_PARTY_ID as the correlation key. When the requirement involves the TCA party row itself—for example, to update a party attribute—CONTACT_ROW_ID from this view provides the party ROWID. Consumers should note that the view is a reporting construct: DML against it is not supported, and updates should target AS_SALES_LEAD_CONTACTS or the HZ base tables through the supported APIs.