Search Results aml_lead_processing_stages_v




Overview
Explore in AI Chat

Overview

AML_LEAD_PROCESSING_STAGES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AMS (Marketing) product family. The view exposes the descriptive meaning of the evaluation stages applied to sales leads within Oracle Marketing and Oracle Sales. Rather than storing data of its own, it consolidates lookup values from three distinct reference sources into a single, unified result set, allowing lead-processing stages to be presented consistently across forms, reports, and integration interfaces.

The object carries a status of VALID and is available in both Oracle EBS 12.1.1 and 12.2.2. Its documentation is explicitly framed around the PROCESS_TYPE discriminator, which is the column users most commonly search for when building lead-qualification reports or troubleshooting stage display behavior.

Underlying Base Objects

The view is defined over a UNION ALL of three SELECT statements, each pulling a specific class of stage values. The documented referenced base objects are:

Because these sources are views and lookup tables rather than transactional tables, AML_LEAD_PROCESSING_STAGES_V presents reference data only. It therefore requires no write privileges and is safe to query in high-volume reporting environments.

Key Columns

  • PROCESS_TYPE — the discriminator identifying which evaluation stage the row belongs to. Documented literal values are 'CHANNEL_SELECTION', 'LEAD_QUALIFICATION', and 'LEAD_RATING'.
  • LOOKUP_CODE — the coded identifier for the stage value. For channel selection and qualification this is the lookup code; for lead rating it is the character representation of the rank identifier.
  • MEANING — the translated, user-facing description of the code, sourced from each underlying reference object.

Note that LOOKUP_CODE is heterogeneous in origin: it maps to a lookup code in two branches and to a numeric rank identifier in the third. Consumers should treat it as a display key rather than a single consistent domain.

Common Use Cases and Queries

Typical scenarios include populating LOVs for lead evaluation stages, joining stage meanings onto lead records for reporting, and validating configuration of the underlying lookups and ranks.

To retrieve all stages grouped by process type:

  • SELECT process_type, lookup_code, meaning FROM aml_lead_processing_stages_v ORDER BY process_type, lookup_code;

To isolate a single evaluation stage, for example lead qualification:

  • SELECT lookup_code, meaning FROM aml_lead_processing_stages_v WHERE process_type = 'LEAD_QUALIFICATION';

To drive a form LOV or integration picklist filtered to rating values:

  • SELECT meaning FROM aml_lead_processing_stages_v WHERE process_type = 'LEAD_RATING';

Because the view performs no aggregation and no joins beyond its UNION ALL definition, queries execute efficiently and can be embedded in custom concurrent programs or Oracle BI Publisher templates. When joining to lead data, always constrain on PROCESS_TYPE to avoid mixing stage categories within a single result set.