Search Results as_sales_meth_task_map




Overview
Explore in AI Chat

Overview

The AS_SALES_METH_TASK_MAP table is a core data object within the Oracle E-Business Suite (EBS) Sales Foundation module (AS). It functions as a mapping and audit table for the automated task generation feature of the Sales Methodology engine. When a sales methodology is applied to an opportunity or lead, the system can automatically create a series of predefined tasks to guide the sales process. This table serves as the persistent record linking the source methodology and its target object (e.g., an opportunity) to the specific task or task template that was generated. Its role is critical for maintaining data integrity, enabling traceability, and supporting process automation within the sales cycle for both EBS 12.1.1 and 12.2.2 versions.

Key Information Stored

The table's primary key is a composite of several columns that uniquely identify a methodology-driven task mapping. The key columns are OBJECT_ID, OBJECT_NAME, OBJECT_TYPE_CODE, SALES_METHODOLOGY_ID, and TASK_ID. These columns store the identifier and name of the object (such as an opportunity) to which the methodology was applied, the type of that object, the identifier of the specific sales methodology used, and the identifier of the resulting task. Additional foreign key columns, as documented, link to the task template (TASK_TEMPLATE_ID) or task template group (TASK_TEMPLATE_GROUP_ID) that served as the blueprint for the automatically created task, providing a complete lineage from methodology definition to executed activity.

Common Use Cases and Queries

A primary use case is auditing and reporting on sales process adherence. Analysts can query this table to determine which methodologies are triggering task creation and for which opportunities. A common SQL pattern involves joining to the methodology and task tables to generate a report of all auto-generated tasks for a given period.

  • Sample Query: To list all tasks created for a specific sales methodology:
    SELECT map.object_name, map.object_type_code, jtb.task_number, jtb.task_name
    FROM osm.as_sales_meth_task_map map,
        jtf_tasks_b jtb,
        as_sales_methodology_b meth
    WHERE map.task_id = jtb.task_id
    AND map.sales_methodology_id = meth.sales_methodology_id
    AND meth.name = 'Strategic Selling Methodology';
  • Another critical scenario is data cleanup or migration, where understanding these mappings is necessary before modifying or deleting related methodology or task records.

Related Objects

The table is centrally connected to several key EBS objects via foreign key relationships. It directly references the AS_SALES_METHODOLOGY_B table, which stores the definition of the sales methodology itself. For task data, it links to JTF_TASKS_B (the base task table). For the task definitions used as templates, it references JTF_TASK_TEMPLATES_B and JTF_TASK_TEMP_GROUPS_B. This structure indicates that the sales methodology engine can generate tasks from either individual templates or groups of templates. Any custom reporting or integration touching automated sales tasks will typically involve joining this mapping table to these related entities.