Search Results as_sales_lead_lines




Overview
Explore in AI Chat

Overview

The AS_SALES_LEAD_LINES table is a core transactional entity within the Oracle E-Business Suite (EBS) Sales Foundation module (AS). It functions as the detailed line-level repository for sales lead information. While the parent table, AS_SALES_LEADS, stores the header-level attributes of a sales lead, this table captures the specific products, services, or areas of interest that constitute the lead. Its primary role is to enable the tracking and qualification of multiple potential opportunities within a single lead, providing the granular data necessary for sales analysis, forecasting, and the eventual conversion of leads into opportunities and quotes.

Key Information Stored

The table's structure is defined by its primary and foreign keys, which dictate the critical data relationships. The primary key, SALES_LEAD_LINE_ID, uniquely identifies each line. The SALES_LEAD_ID column is a foreign key linking the line to its parent record in AS_SALES_LEADS. Core business data is stored through foreign key references to other master tables: INTEREST_TYPE_ID, PRIMARY_INTEREST_CODE_ID, and SECONDARY_INTEREST_CODE_ID link to AS_INTEREST_TYPES_B and AS_INTEREST_CODES_B for classifying the customer's interest. For product-specific leads, the INVENTORY_ITEM_ID and ORGANIZATION_ID columns reference MTL_SYSTEM_ITEMS_B to identify the exact item from inventory. Additional columns track marketing and sales context, such as SOURCE_PROMOTION_ID (linked to AMS_SOURCE_CODES) and OFFER_ID (linked to AMS_ACT_OFFERS).

Common Use Cases and Queries

A primary use case is generating reports on lead line distribution by product or interest code to analyze sales pipeline quality. Another critical process is the conversion of qualified lead lines into opportunity lines, facilitated by the relationship with AS_SALES_LEAD_OPP_LINES. Common queries involve joining to parent and descriptive tables. For example, to list all lead lines with their product information:

  • SELECT asll.SALES_LEAD_LINE_ID, asl.LEAD_NUMBER, msib.SEGMENT1 ITEM_CODE, asll.CREATION_DATE FROM OSM.AS_SALES_LEAD_LINES asll JOIN OSM.AS_SALES_LEADS asl ON asll.SALES_LEAD_ID = asl.SALES_LEAD_ID LEFT JOIN INV.MTL_SYSTEM_ITEMS_B msib ON asll.INVENTORY_ITEM_ID = msib.INVENTORY_ITEM_ID AND asll.ORGANIZATION_ID = msib.ORGANIZATION_ID WHERE asl.STATUS_CODE = 'QUALIFIED';

Integration with other modules, such as the IGS (iGrants) module, is evidenced by the foreign key from IGS_RC_I_A_LINES, indicating this table supports cross-module processes like grant or application tracking related to a sales lead.

Related Objects

The table maintains extensive relationships within the EBS schema. Its primary parent is AS_SALES_LEADS. Key child tables that consume its data include AS_SALES_LEAD_OPP_LINES for opportunity conversion and ASO_QUOTE_RELATED_OBJECTS for quotation linkage. It is also referenced by tables from other modules, notably IGR_I_A_LINES and IGS_RC_I_A_LINES, highlighting its integration beyond core Sales. The table's descriptive data is sourced from master tables: AS_INTEREST_TYPES_B, AS_INTEREST_CODES_B, MTL_SYSTEM_ITEMS_B, AMS_SOURCE_CODES, and AMS_ACT_OFFERS. The existence of a dedicated primary key constraint, AS_SALES_LEAD_LINES_PK, enforces data integrity for this central entity.