Search Results lead_channel




Overview
Explore in AI Chat

Overview

APPS.AS_SALES_OPP_UWQ_V is an Oracle E-Business Suite view owned by the APPS schema and registered in FND Design Data as AS.AS_SALES_OPP_UWQ_V. It belongs to the Oracle Sales (AS) product family and exposes sales opportunity and lead data in a denormalized, presentation-ready form. The "_UWQ_" naming convention indicates that the view was constructed for use within a Universal Work Queue or comparable worklist-style inquiry context, while the "_V" suffix confirms its status as a database view rather than a table. The object is marked VALID and carries an Oracle Internal Use Only warning: Oracle Corporation does not support direct access to applications data through this object except from standard Oracle Applications programs. As a result, it should be treated as a read-only reporting and integration surface rather than a supported customization point.

The view consolidates lead identification, party (customer or prospect) information, sales stage, status, win probability, and channel attributes into a single rowset. This makes it suitable for lead funnel analysis, opportunity pipeline reporting, and dashboard-style inquiries that must join multiple AS and HZ tables without replicating that logic in every consumer.

Underlying Base Objects

The view is defined over the following documented objects in ETRM 12.2.2:

Key Columns

The view exposes a mixture of identifiers, descriptive text, and measures. LEAD_ID is the unique identifier for the forecast, with LEAD_NUMBER carrying the system-generated sequence value from as_lead_number_s. PARTY_ID and PARTY_NAME identify the customer or prospect from HZ_PARTIES. SALES_STAGE_ID and SALES_STAGE_NAME describe the opportunity's position in the sales cycle, while STATUS_CODE and STATUS_MEANING indicate its current disposition. WIN_PROBABILITY and PROBABILITY_MEANING convey likely close percentage. Financial context is provided by TOTAL_AMOUNT, CUSTOMER_BUDGET, and CURRENCY_CODE (validated against fnd_currencies_vl). CHANNEL_CODE and SALES_CHANNEL capture the sales channel for the lead; both are validated against the 'LEAD_CHANNEL' lookup from order capture, and both must be considered when filtering or grouping by channel. DECISION_DATE, DECISION_TIMEFRAME_CODE, and DECISION_TIMEFRAME support time-based qualification, and PARENT_PROJECT attributes the lead to a project. Standard who-columns record audit information.

Common Use Cases and Queries

Typical consumers use the view for pipeline reports, lead aging analysis, and channel attribution summaries. The following query answers the specific "lead_channel" search by counting and measuring leads per sales channel:

  • SELECT channel_code, sales_channel, COUNT(*) AS lead_count, SUM(total_amount) AS pipeline_amount FROM apps.as_sales_opp_uwq_v GROUP BY channel_code, sales_channel ORDER BY pipeline_amount DESC;
  • Leads by sales stage and status: SELECT sales_stage_name, status_meaning, win_probability, COUNT(*) FROM apps.as_sales_opp_uwq_v GROUP BY sales_stage_name, status_meaning, win_probability;
  • Salesperson workload: SELECT resource_id, COUNT(*) FROM apps.as_sales_opp_uwq_v GROUP BY resource_id;
  • Upcoming decisions: SELECT lead_number, party_name, decision_date FROM apps.as_sales_opp_uwq_v WHERE decision_date >= TRUNC(SYSDATE) ORDER BY decision_date;
  • Currency exposure: SELECT currency_code, SUM(total_amount) FROM apps.as_sales_opp_uwq_v GROUP BY currency_code;

Because the object is marked Oracle Internal Use Only, analytic queries should be directed to supported reporting tools or concurrent programs wherever possible, and any dependency on column semantics should be validated against the current ETRM release before production use.