Search Results as_sales_leads

Overview

The AS_SALES_LEADS table is a core transactional entity within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, residing in the OSM schema. As part of the Sales Foundation (AS) module, it serves as the central repository for storing all sales lead records. A sales lead represents a prospective sales opportunity, typically containing information about a potential customer, the product or service of interest, and the associated sales process. The table's primary role is to capture, track, and manage the lifecycle of these leads, from initial creation through qualification and conversion. Its extensive network of foreign key relationships, particularly with the Trading Community Architecture (TCA) foundation tables, underscores its integration with the broader EBS ecosystem for managing parties, contacts, and addresses.

Key Information Stored

The table's structure is defined by its primary and foreign keys, which indicate the critical data points it holds. The primary key, SALES_LEAD_ID, uniquely identifies each lead record. Essential foreign key columns define the lead's context and relationships: CUSTOMER_ID and PRIMARY_CNT_PERSON_PARTY_ID link to HZ_PARTIES to identify the lead's account and primary contact person. STATUS_CODE and LEAD_RANK_ID reference lookup tables (AS_STATUSES_B, AS_SALES_LEAD_RANKS_B) for the lead's current progression stage and priority ranking. The table also stores assignment information via ASSIGN_TO_SALESFORCE_ID (JTF_RS_RESOURCE_EXTNS) and ASSIGN_SALES_GROUP_ID (JTF_RS_GROUPS_B). Furthermore, it links to physical locations (ADDRESS_ID to HZ_PARTY_SITES), contact points (PRIMARY_CONTACT_PHONE_ID to HZ_CONTACT_POINTS), and associated marketing offers (OFFER_ID to AMS_ACT_OFFERS).

Common Use Cases and Queries

This table is central to lead management operations and reporting. Common use cases include generating lead pipeline reports, tracking lead conversion rates to opportunities, and managing sales team assignments. A typical query might join AS_SALES_LEADS with TCA and resource tables to create a comprehensive lead listing. For example:

• SELECT sl.SALES_LEAD_ID, hp.PARTY_NAME Customer, sl.STATUS_CODE, jre.RESOURCE_NAME Assigned_To FROM OSM.AS_SALES_LEADS sl, HZ_PARTIES hp, JTF_RS_RESOURCE_EXTNS jre WHERE sl.CUSTOMER_ID = hp.PARTY_ID AND sl.ASSIGN_TO_SALESFORCE_ID = jre.RESOURCE_ID(+);

Another critical pattern involves querying leads converted to opportunities by joining with the AS_SALES_LEAD_OPPORTUNITY table. Performance tuning for such queries is essential, given the volume of data and the number of joins involved.

Related Objects

AS_SALES_LEADS has a wide array of dependencies, as shown in the metadata. It is the parent table for numerous child entities that store supplemental lead data, including AS_SALES_LEAD_LINES (for line items), AS_SALES_LEAD_CONTACTS (for additional contacts), and AS_SALES_LEADS_LOG (for audit history). Key transactional relationships exist with AS_SALES_LEAD_OPPORTUNITY for tracking converted leads and AS_ACCESSES_ALL_ALL for security. It is also referenced by objects in other modules, such as IGR_I_APPL_ALL and IGS_RC_I_APPL_ALL in Grants/Recruiting, PV_REFERRALS_B in Partner Management, and ASO_QUOTE_RELATED_OBJECTS in Quoting, demonstrating its cross-functional importance. For programmatic access, developers should utilize the standard Oracle Sales APIs rather than direct DML on this table.