Search Results lead_rank_code
Overview
AST_LS_SALES_LEADS_V is an APPS-owned reporting view in the Oracle EBS TeleSales (AST) module. It consolidates sales lead header, contact, lookup, customer, and resource information into a single, denormalized result set intended for inquiry screens, concurrent report programs, and outbound integrations that need lead data without joining the underlying transactional tables directly. The view draws primarily from the AS_SALES_LEADS synonym (aliased LDH) and its related contact table, decorating raw coded values with their translated meanings from the lookup and translation views.
The user search term source_promotion_code resolves to one specific column in this view. That column is derived from CMP.SOURCE_CODE, where CMP is the AMS_P_SOURCE_CODES_V view joined through the SOURCE_PROMOTION_ID column on the lead header. In other words, SOURCE_PROMOTION_CODE is the human-readable marketing source or promotion code associated with the lead, while SOURCE_PROMOTION_ID carries the internal key.
Underlying Base Objects
The documented base objects for this view span TeleSales, Marketing, Receivables, Order Management, and Trading Community Architecture:
- AS_SALES_LEADS (SYNONYM) — primary lead header table (LDH).
- AS_SALES_LEAD_CONTACTS (SYNONYM) — lead contact detail (LDC).
- AS_SALES_LEAD_RANKS_TL (SYNONYM) — translated lead rank meanings (RNK).
- AS_STATUSES_TL (SYNONYM) and AS_LOOKUPS (VIEW) — status and other lookup translations (AL1, AL3, AL4, AL5).
- AMS_SOURCE_CODES (SYNONYM) via AMS_P_SOURCE_CODES_V (VIEW) — marketing source/promotion definitions (CMP).
- AR_LOOKUPS (VIEW) — close reason and party-name meanings (CLOSE, AR1).
- OE_LOOKUPS (VIEW) — order-entry style lookup meanings.
- HZ_PARTIES (SYNONYM) and HZ_RELATIONSHIPS (SYNONYM) — customer/party attributes (CUS).
- JTF_RS_RESOURCE_EXTNS (SYNONYM) — assigned resource names (PER).
Because the view sits on top of these synonyms and views, it inherits their security and translation behavior while sparing report authors from re-implementing the joins.
Key Columns
- SALES_LEAD_ID, LEAD_NUMBER — unique identifier and user-facing lead number.
- CUSTOMER_ID, ADDRESS_ID, CUSTOMER_NAME, PARTY_TYPE — customer and party context from HZ_PARTIES.
- STATUS_CODE and STATUS — raw status code and its translated meaning.
- SOURCE_PROMOTION_ID / SOURCE_PROMOTION_CODE — marketing source key and its descriptive code, the column of interest for the searched term.
- LEAD_RANK_CODE and LEAD_RANK — ranking code and translated ranking.
- CHANNEL_CODE and SALES_CHANNEL — channel code and meaning.
- BUDGET_AMOUNT, BUDGET_STATUS_CODE, BUDGET_STATUS, CURRENCY_CODE — lead value/qualification data.
- QUALIFIED_FLAG, URGENT_FLAG, ACCEPT_FLAG, KEEP_FLAG, DELETED_FLAG — status indicator flags.
- ASSIGN_TO_PERSON_ID, ASSIGN_SALES_GROUP_ID, ASSIGNED_NAME — assignment information.
- LEAD_CONTACT_ID, CONTACT_ROLE, CONTACT_ID, CONTACT_FULL_NAME — contact details.
- ATTRIBUTE1 through ATTRIBUTE20 — descriptive flexfield segments.
- CREATION_DATE, UPDATE_DATE — audit columns.
Common Use Cases and Queries
The view is frequently used to list open, qualified leads by promotion source, to reconcile lead counts against campaign spend, and to feed external CRM or marketing automation systems.
Sample: list leads with their source promotion code
SELECT lead_number, customer_name, status, source_promotion_code FROM apps.ast_ls_sales_leads_v WHERE deleted_flag = 'N';
Sample: aggregate lead counts and budget by promotion source
SELECT source_promotion_code, COUNT(*) lead_count, SUM(budget_amount) total_budget FROM apps.ast_ls_sales_leads_v WHERE qualified_flag = 'Y' AND deleted_flag = 'N' GROUP BY source_promotion_code ORDER BY lead_count DESC;
Sample: filter by assigned resource and status
SELECT lead_number, assigned_name, status, sales_channel FROM apps.ast_ls_sales_leads_v WHERE assigned_name = :p_resource AND status = 'OPEN';
Always restrict results using DELETED_FLAG, and consider the view’s translation joins when pushing predicates on meaning columns, since those are resolved from the lookup and translation tables at runtime.
-
View: AST_LS_SALES_LEADS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_LS_SALES_LEADS_V, object_name:AST_LS_SALES_LEADS_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_LS_SALES_LEADS_V ,
-
View: AST_LS_SALES_LEADS_CONTACT_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_LS_SALES_LEADS_CONTACT_V, object_name:AST_LS_SALES_LEADS_CONTACT_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_LS_SALES_LEADS_CONTACT_V ,
-
View: AST_LS_SALES_LEADS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_LS_SALES_LEADS_V, object_name:AST_LS_SALES_LEADS_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_LS_SALES_LEADS_V ,
-
View: AST_LS_SALES_LEADS_CONTACT_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_LS_SALES_LEADS_CONTACT_V, object_name:AST_LS_SALES_LEADS_CONTACT_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_LS_SALES_LEADS_CONTACT_V ,
-
View: AST_SALES_LEADS_BASIC_V
12.1.1
product: AST - TeleSales , implementation_dba_data: Not implemented in this database ,
-
View: AST_SALES_LEADS_BASIC_V
12.2.2
product: AST - TeleSales , implementation_dba_data: Not implemented in this database ,
-
View: AST_LS_SALES_LEADS_BSC_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_LS_SALES_LEADS_BSC_V, object_name:AST_LS_SALES_LEADS_BSC_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_LS_SALES_LEADS_BSC_V ,
-
View: AST_LS_SALES_LEADS_BSC_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_LS_SALES_LEADS_BSC_V, object_name:AST_LS_SALES_LEADS_BSC_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_LS_SALES_LEADS_BSC_V ,
-
View: AST_SALES_LEADS_BALI_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_SALES_LEADS_BALI_V, object_name:AST_SALES_LEADS_BALI_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_SALES_LEADS_BALI_V ,
-
View: AST_SALES_LEADS_BALI_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_SALES_LEADS_BALI_V, object_name:AST_SALES_LEADS_BALI_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_SALES_LEADS_BALI_V ,
-
View: AST_SALES_LEADS_REL_BALI_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_SALES_LEADS_REL_BALI_V, object_name:AST_SALES_LEADS_REL_BALI_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_SALES_LEADS_REL_BALI_V ,
-
View: AST_SALES_LEADS_REL_BALI_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_SALES_LEADS_REL_BALI_V, object_name:AST_SALES_LEADS_REL_BALI_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_SALES_LEADS_REL_BALI_V ,
-
View: AST_SALES_LEADS_EBC_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_SALES_LEADS_EBC_V, object_name:AST_SALES_LEADS_EBC_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_SALES_LEADS_EBC_V ,
-
View: AST_SALES_LEADS_EBC_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_SALES_LEADS_EBC_V, object_name:AST_SALES_LEADS_EBC_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_SALES_LEADS_EBC_V ,
-
View: AST_SALES_LEADS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_SALES_LEADS_V, object_name:AST_SALES_LEADS_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_SALES_LEADS_V ,
-
View: AST_SALES_LEADS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_SALES_LEADS_V, object_name:AST_SALES_LEADS_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_SALES_LEADS_V ,