Search Results import_flag




Overview
Explore in AI Chat

Overview

AST_SALES_LEADS_BALI_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the AST (TeleSales) product family and exposes sales lead records maintained by the Oracle TeleSales application. The view is built primarily over the AS_SALES_LEADS entity and decorates the base lead columns with translated or human-readable meaning values sourced from several lookup and reference views. Its principal role is to present a reporting- and integration-friendly projection of the sales lead model: instead of requiring external consumers to resolve coded columns (status, rank, budget status, channel, close reason, vehicle response) against multiple lookup objects, the view performs those joins internally and returns decoded meanings alongside the raw codes.

The view exposes the standard Oracle EBS who-columns and concurrent-program columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), which makes it suitable for audit reporting and for incremental extracts driven by LAST_UPDATE_DATE. It also exposes the descriptive flexfield segment columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15, allowing customer-specific lead attributes to be surfaced without querying the base table directly.

Underlying Base Objects

The documented base objects for this view are:

  • AS_SALES_LEADS (SYNONYM) — the primary driving entity, aliased LEAD, holding one row per sales lead.
  • AS_STATUSES_VL (VIEW) — supplies the STATUS_MEANING column by joining on STATUS_CODE.
  • AS_SALES_LEAD_RANKS_TL (SYNONYM) — an outer-joined, language-aware translation source for lead rank meanings, constrained by USERENV('LANG').
  • AS_LOOKUPS (VIEW) — referenced four times (aliases AS_LOOKUPS2 through AS_LOOKUPS5) to decode budget status, decision timeframe, close reason, and vehicle response codes.
  • OE_LOOKUPS (VIEW) — aliased OELKP, providing the meaning for CHANNEL_CODE.

Because RANK is joined with the outer-join operator (+) and filtered on USERENV('LANG'), rows without a rank or without a translation for the session language are retained with a null rank meaning. The lookup joins are likewise outer joins, so leads with unpopulated lookup codes still appear.

h4>Key Columns

Common Use Cases and Queries

Typical uses include lead pipeline reporting, assignment and acceptance monitoring, promotion effectiveness analysis, and extracting leads to external CRM or analytics platforms. Because decoding is built in, reports and interfaces avoid re-implementing lookup joins.

Retrieve leads initiated by a specific contact:

SELECT sales_lead_id, lead_number, status_meaning, initiating_contact_id
FROM   apps.ast_sales_leads_bali_v
WHERE  initiating_contact_id = :p_contact_id
AND    deleted_flag = 'N';

Open pipeline by status and rank:

SELECT status_meaning, meaning_rank, budget_status, budget_amount, currency_code, lead_number
FROM   apps.ast_sales_leads_bali_v
WHERE  status_open_flag = 'Y'
AND    deleted_flag = 'N'
ORDER BY budget_amount DESC;

Incremental extract driven by the audit columns:

SELECT sales_lead_id, lead_number, status_code, assign_to_person_id,
       accepting_flag, last_update_date
FROM   apps.ast_sales_leads_bali_v
WHERE  last_update_date >= :p_since;

Promotion attribution and scoring analysis:

SELECT source_promotion_id, offer_id, total_score, meaning, channel_code
FROM   apps.ast_sales_leads_bali_v
WHERE  source_promotion_id IS NOT NULL
AND    qualified_flag = 'Y';