Search Results as_sales_lead_contacts




Overview
Explore in AI Chat

Overview

The AS_SALES_LEAD_CONTACTS table is a core data object within the Oracle E-Business Suite (EBS) Sales Foundation module (AS). It functions as a junction table that establishes and manages the relationships between sales leads and their associated contact parties. Its primary role is to enable the storage of multiple contact points for a single sales lead, a critical requirement for managing complex business opportunities. The table is owned by the OSM schema and is valid for both EBS releases 12.1.1 and 12.2.2. As indicated by its description, records in this table are transient and can be deleted, reflecting the dynamic nature of contact associations throughout the lead management lifecycle.

Key Information Stored

The table's structure is defined by its primary and unique keys, which dictate its data integrity rules. The primary key (AS_SALES_LEAD_CONTACTS_PK) is the system-generated LEAD_CONTACT_ID, serving as a unique identifier for each contact association record. A unique key constraint (AS_SALES_LEAD_CONTACTS_UK) enforces that the combination of SALES_LEAD_ID and CONTACT_ID is unique, preventing duplicate contact assignments for the same lead. The most critical foreign key columns store references to related entities: SALES_LEAD_ID links to the parent lead in AS_SALES_LEADS, CONTACT_ID and CUSTOMER_ID link to party information in HZ_PARTIES, ADDRESS_ID links to HZ_PARTY_SITES, and PHONE_ID links to HZ_CONTACT_POINTS. These columns collectively form the relational bridge between the sales lead and the Trading Community Architecture (TCA) registry.

Common Use Cases and Queries

This table is central to operations involving lead contact management. A primary use case is retrieving all contacts for a specific sales lead for communication or reporting purposes. For instance, a common query would join AS_SALES_LEAD_CONTACTS with HZ_PARTIES to fetch contact names and details. Another critical scenario is validating or de-duplicating contact assignments before inserting a new record, leveraging the unique key constraint. In reporting, this table enables analyses such as counting the number of contacts per lead or listing all leads associated with a particular contact person. Since records can be deleted, the table also supports workflows where contact roles change, requiring the disassociation and reassociation of parties to a lead.

Related Objects

The AS_SALES_LEAD_CONTACTS table has defined foreign key relationships with several key EBS tables, primarily within the Trading Community Architecture (TCA) and Sales Foundation modules. The documented relationships are as follows:

  • AS_SALES_LEADS: Linked via AS_SALES_LEAD_CONTACTS.SALES_LEAD_ID. This is the primary parent table for the sales lead header information.
  • HZ_PARTIES: Linked via AS_SALES_LEAD_CONTACTS.CONTACT_ID (for the contact person) and AS_SALES_LEAD_CONTACTS.CUSTOMER_ID (for the customer organization). This provides access to the TCA party details.
  • HZ_PARTY_SITES: Linked via AS_SALES_LEAD_CONTACTS.ADDRESS_ID. This stores the physical or mailing address for the contact.
  • HZ_CONTACT_POINTS: Linked via AS_SALES_LEAD_CONTACTS.PHONE_ID. This stores communication details such as phone numbers, email addresses, or fax numbers for the contact.

These relationships ensure data consistency and enable comprehensive joins for extracting complete lead and contact information from the system.