Search Results as_sales_lead_ranks_b




Overview
Explore in AI Chat

Overview

The AS_SALES_LEAD_RANKS_B table is a core reference data table within the Oracle E-Business Suite (EBS) Sales Foundation module (AS). It serves as the base table for defining and storing the distinct ranking classifications that can be assigned to sales leads throughout the lead management lifecycle. These ranks are typically used to qualify and prioritize leads based on their perceived sales potential, likelihood of conversion, or other business-defined criteria. The table's role is to provide a centralized, master list of valid rank codes that can be consistently applied across all sales leads in the system, ensuring data integrity and standardized reporting on lead quality and pipeline health.

Key Information Stored

The primary data stored in this table is the unique identifier and definition for each lead rank. While the full column list is not detailed in the provided metadata, the structure can be inferred from standard EBS patterns and the documented keys. The critical column is RANK_ID, which serves as the primary key and is a numeric or alphanumeric code uniquely identifying each rank. The table likely contains additional columns to control the rank's configuration and lifecycle, such as an ENABLED_FLAG to activate or deactivate the rank for use, a START_DATE_ACTIVE and END_DATE_ACTIVE for date-effective control, and a SEEDED_FLAG indicating if the row is a pre-delivered Oracle seed data record. Descriptive, user-facing names and descriptions for each rank are stored not in this base table, but in the corresponding translation table, AS_SALES_LEAD_RANKS_TL.

Common Use Cases and Queries

This table is primarily referenced for validation, reporting, and data maintenance. A common operational use case is when a sales representative updates the qualification status of a lead, selecting a rank from a validated list sourced from this table. For reporting, analysts frequently join this table to lead data to segment and analyze pipeline value by lead quality. Common SQL patterns include querying for all active ranks or joining to the leads table for analysis.

  • Listing all active lead ranks: SELECT RANK_ID FROM AS_SALES_LEAD_RANKS_B WHERE ENABLED_FLAG = 'Y' AND SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);
  • Reporting lead counts by rank: SELECT b.RANK_ID, tl.NAME, COUNT(l.LEAD_ID) FROM AS_SALES_LEADS l, AS_SALES_LEAD_RANKS_B b, AS_SALES_LEAD_RANKS_TL tl WHERE l.LEAD_RANK_ID = b.RANK_ID AND b.RANK_ID = tl.RANK_ID AND tl.LANGUAGE = USERENV('LANG') GROUP BY b.RANK_ID, tl.NAME;

Related Objects

The AS_SALES_LEAD_RANKS_B table is central to a small hierarchy of objects within the Sales Foundation module. Its primary relationship is with the AS_SALES_LEADS table, which holds the individual lead records. The foreign key constraint on AS_SALES_LEADS.LEAD_RANK_ID ensures that every rank assigned to a lead exists in AS_SALES_LEAD_RANKS_B. For multilingual deployments, the AS_SALES_LEAD_RANKS_TL (Translation) table is dependent on this base table, storing the translated name and description for each RANK_ID across different languages. Administrators typically maintain rank definitions via the Oracle Applications GUI, which leverages underlying APIs and forms that ultimately interact with this table.