Search Results as_sales_meth_stage_map




Overview
Explore in AI Chat

Overview

The AS_SALES_METH_STAGE_MAP table is a core configuration table within the Oracle E-Business Suite (EBS) Sales Foundation module (AS). It serves as a junction table that formally defines the relationship between sales stages and sales methodologies, a critical component for managing structured sales processes. Its primary role is to map specific sales stages, defined within a sales methodology, to corresponding task template groups and forecast probability ranges. This mapping enables the automation of activity management and forecasting within the sales cycle, ensuring that the correct tasks are generated and the appropriate win probabilities are applied as an opportunity progresses through its defined stages.

Key Information Stored

The table stores the composite key relationship between a sales stage and a sales methodology, along with associated configuration data. The primary key is a combination of SALES_STAGE_ID and SALES_METHODOLOGY_ID, enforcing unique stage-methodology mappings. Key columns include TASK_TEMPLATE_GROUP_ID, which links to a predefined set of tasks (e.g., discovery call, proposal delivery) that should be initiated when an opportunity enters that stage. The MIN_WIN_PROBABILITY and MAX_WIN_PROBABILITY columns link to forecast probability definitions, establishing the valid win probability range for the sales stage, which is essential for accurate revenue forecasting and pipeline analysis.

Common Use Cases and Queries

This table is central to configuring and reporting on sales process adherence. Administrators use it to set up or modify the task automation for a given stage within a methodology. A common reporting use case is to list all stages within a specific methodology along with their associated task groups and probability ranges to validate process setup. For example, to audit the configuration for the 'Complex Sales' methodology (ID: 100), a query would join to related descriptive tables:

  • SELECT stg.name stage_name, ttg.name task_group, fp_min.name min_prob, fp_max.name max_prob FROM osm.as_sales_meth_stage_map map, as_sales_stages_tl stg, jtf_task_temp_groups_tl ttg, as_forecast_prob_all_tl fp_min, as_forecast_prob_all_tl fp_max WHERE map.sales_methodology_id = 100 AND map.sales_stage_id = stg.sales_stage_id AND stg.language = USERENV('LANG') AND map.task_template_group_id = ttg.task_template_group_id (+) AND ttg.language = USERENV('LANG') AND map.min_win_probability = fp_min.forecast_probability_id (+) AND map.max_win_probability = fp_max.forecast_probability_id (+);

This data is also critical for backend logic that automatically generates tasks when a sales opportunity's stage is updated.

Related Objects

The AS_SALES_METH_STAGE_MAP table maintains documented foreign key relationships with several fundamental tables, as per the provided metadata:

  • AS_SALES_STAGES_ALL_B: Joined via SALES_STAGE_ID. This table defines the master list of all sales stages.
  • AS_SALES_METHODOLOGY_B: Joined via SALES_METHODOLOGY_ID. This table defines the master list of sales methodologies.
  • JTF_TASK_TEMP_GROUPS_B: Joined via TASK_TEMPLATE_GROUP_ID. This table stores the task template groups used for activity automation.
  • AS_FORECAST_PROB_ALL_B: Joined twice, via MIN_WIN_PROBABILITY and MAX_WIN_PROBABILITY. This table defines the forecast probability values and their descriptions.

These relationships ensure referential integrity and are essential for any query or integration that needs to retrieve descriptive information about the mapped entities.