Search Results time_frame




Overview
Explore in AI Chat

Overview

The APPS.AST_SALES_LEADS_REL_BALI_V view is a TeleSales (AST) reporting object in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes sales lead records from the AS_SALES_LEADS entity, denormalized with decoded lookup meanings and associated contact party information. The naming suffix REL_BALI indicates a release-specific variant that consolidates lead attributes with their translated status, rank, budget, channel, close-reason, and vehicle-response descriptions so that consumers do not need to rejoin the lookup and status views.

The view is particularly relevant to users investigating the IMPORT_FLAG column, which is exposed directly from the underlying lead record. This flag identifies leads created or loaded through an external import process, such as a bulk data load or integration feed, rather than through manual TeleSales entry. Analysts, integration developers, and reporting practitioners use this view to reconcile imported lead populations and to trace their progression through the sales pipeline.

Underlying Base Objects

The documented ETRM metadata lists the following referenced base objects:

  • AS_SALES_LEADS (synonym) — the primary lead table, aliased LEAD, supplying the majority of columns.
  • AS_SALES_LEAD_CONTACTS (synonym) — aliased ASLC, contributing the CONTACT_PARTY_ID.
  • AS_STATUSES_VL (view) — aliased STATUS, supplying the untranslated STATUS_CODE and its MEANING.
  • AS_SALES_LEAD_RANKS_TL (synonym) — aliased RANK, an outer-joined translation table supplying the rank MEANING filtered by USERENV('LANG').
  • AS_LOOKUPS (view) — instantiated four times as AS_LOOKUPS2 through AS_LOOKUPS5 to decode budget status, decision timeframe, close reason, and vehicle response codes.
  • OE_LOOKUPS (view) — aliased OELKP, decoding the channel code.

The outer join on the rank translation table allows leads without a valid rank to remain visible, while the lookup joins require matching codes.

Key Columns

Common Use Cases and Queries

A frequent requirement is isolating imported leads and reviewing their status distribution:

  • SELECT lead_number, import_flag, status_code, meaning FROM ast_sales_leads_rel_bali_v WHERE import_flag = 'Y';
  • SELECT import_flag, COUNT(*) FROM ast_sales_leads_rel_bali_v GROUP BY import_flag;
  • SELECT lead_number, assign_to_person_id, budget_amount FROM ast_sales_leads_rel_bali_v WHERE import_flag = 'Y' AND status_open_flag = 'Y';

Because the view already resolves lookup meanings, it is well suited to ad hoc reporting, Oracle Discoverer workbooks, and BI Publisher data templates where decoded values are required without additional joins. Integration developers may also query it to validate that imported leads successfully landed and received a rank and status.