Search Results source_promotion_code




Overview
Explore in AI Chat

Overview

The AST_LS_SALES_LEADS_CONTACT_V view is an Oracle E-Business Suite (EBS) reporting object owned by the APPS schema and delivered as part of the AST (TeleSales) product family. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2. The view consolidates sales lead header information held in AS_SALES_LEADS with the associated contact records held in AS_SALES_LEAD_CONTACTS, producing a single denormalized rowset suitable for lead management reporting, TeleSales dashboards, lead-to-contact extracts, and outbound integration feeds. It denormalizes foreign-key codes into their user-facing meanings and joins party, resource, and lookup data so that consumers do not need to replicate the multi-table resolution logic themselves. The object is read-only and is intended primarily for inquiry and reporting rather than transactional DML.

Underlying Base Objects

The view is defined over the following documented base objects:

  • AS_SALES_LEADS (synonym) — the lead header table, aliased as LDH, supplying lead number, customer, status, budget, flags, assignment attributes, and descriptive flexfield columns.
  • AS_SALES_LEAD_CONTACTS (synonym) — the lead contact table, aliased as LDC, supplying contact role and contact person identifiers.
  • AS_LOOKUPS / OE_LOOKUPS (views) — aliased AL1 through AL6, resolving status, decision time frame, budget status, sales channel, contact role, and related codes into meanings.
  • AS_STATUSES_TL (synonym) — translated status definitions.
  • AS_SALES_LEAD_RANKS_TL (synonym) — aliased RNK, resolving the lead rank code to its meaning.
  • AMS_SOURCE_CODES (synonym) — aliased CMP, resolving the source promotion code.
  • HZ_PARTIES (synonym) — aliased CUS, supplying customer (party) name and party type.
  • HZ_RELATIONSHIPS (synonym) — used to resolve the contact person's name through the customer relationship model.
  • JTF_RS_RESOURCE_EXTNS (synonym) — aliased PER, supplying the assigned-to resource's first name, last name, and full name.

Header and contact records are joined on the sales lead identifier; the customer, contact person, and assigned resource are resolved through their respective party and resource tables; codes are translated through the lookup and _TL views.

Key Columns

Common Use Cases and Queries

Typical usage includes lead pipeline reporting, workload distribution analysis by assigned resource or sales group, and lead-to-contact extracts. To list all leads assigned to a specific resource with their decoded status:

SELECT lead_number, customer_name, status, lead_rank,
       assigned_name, budget_amount, currency_code
  FROM apps.ast_ls_sales_leads_contact_v
 WHERE assign_to_person_id = :p_person_id
   AND deleted_flag = 'N';

To produce a contact roster for a given lead:

SELECT lead_number, contact_full_name, contact_role
  FROM apps.ast_ls_sales_leads_contact_v
 WHERE sales_lead_id = :p_lead_id
 ORDER BY contact_role;

Because the view exposes only the columns defined in its SQL text, querying the ASSIGN_TO_PERSON_ID column for filtering is the supported pattern; the assigned resource's name is obtained via the joined ASSIGNED_NAME column rather than by re-joining to JTF_RS_RESOURCE_EXTNS. Performance tuning should focus on the AS_SALES_LEADS header join, since the lookup and party joins are largely dimensional in nature.