Search Results lead_rating




Overview
Explore in AI Chat

Overview

APPS.AML_LEAD_PROCESSING_STAGES_V is a consolidated, read-only Oracle EBS view that presents the enumerated stages used throughout the Oracle Sales lead-to-opportunity lifecycle. Rather than storing data of its own, the view normalizes three independent code sources — sales channels, lead qualification statuses, and lead rating ranks — into a single result set keyed by a discriminator column named PROCESS_TYPE. This design allows Oracle Marketing and Oracle Sales application code, plus customer-built reports and integrations, to retrieve all valid lead-processing stage values through one consistent interface.

The view originates from Oracle's ETRM (E-Business Suite Technical Reference Manual) documentation and is owned by the APPS schema. The user search term "process_type" corresponds directly to the first column projected by every branch of the UNION ALL, making it the primary filter predicate for consumers of this view.

Underlying Base Objects

The view is defined as a UNION ALL of three segments, each contributing a constant literal for PROCESS_TYPE:

The documented metadata also lists FND_GLOBAL as a referenced base object. FND_GLOBAL is the standard EBS package providing session-level context (user ID, responsibility, application) that Oracle frequently references within view definitions to enforce security or resolve language. Because OE_LOOKUPS and FND_LOOKUPS are themselves views over the FND_LOOKUP_VALUES and related lookup tables, changes to lookup codes in the Oracle Sales application are immediately reflected here without view recompilation.

Key Columns

  • PROCESS_TYPE — VARCHAR2 literal discriminator. Values are 'CHANNEL_SELECTION', 'LEAD_QUALIFICATION', and 'LEAD_RATING'.
  • LOOKUP_CODE — The stage identifier. Returned as a native code from the lookup views; for lead rating it is the character-converted RANK_ID.
  • MEANING — The user-facing display name for the stage.

Because each UNION ALL branch must align columns, the view exposes exactly three columns: PROCESS_TYPE, LOOKUP_CODE, and MEANING. No additional attributes such as descriptions, enabled flags, or date ranges are projected, so consumers requiring lookup metadata beyond code and meaning must join back to the underlying lookup tables.

Common Use Cases and Queries

Typical usage includes populating LOVs and dependent fields in lead-processing forms, driving workflow or BPEL routing decisions, validating inbound lead feeds via interface tables, and building BI Publisher or OBIEE reports on pipeline stage progression. A representative query retrieving all qualification statuses follows:

  • SELECT process_type, lookup_code, meaning FROM apps.aml_lead_processing_stages_v WHERE process_type = 'LEAD_QUALIFICATION' ORDER BY meaning;
  • SELECT process_type, lookup_code, meaning FROM apps.aml_lead_processing_stages_v WHERE process_type IN ('CHANNEL_SELECTION','LEAD_RATING');

When integrating with external CRM systems, the view provides an authoritative reference list that avoids hard-coding lookup values. Because the view spans three lookup domains, a DISTINCT query on PROCESS_TYPE yields the complete set of enumerations that a lead record may traverse from channel selection through qualification to rating.