Results for “jtf_task_temp_groups_b”

4 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AS_SALES_METH_TASK_MAP is a transaction and mapping table in the Oracle E-Business Suite Sales Foundation (AS) module, owned by the OSM schema. Its documented purpose is to store information about tasks created automatically by a sales methodology. In practical terms, the table acts as the binding layer between a sales methodology definition and the Oracle Task Manager (JTF) tasks, task templates, and template groups that the methodology generates when it is applied to an object such as an opportunity, lead, or other sales entity.

The ETRM metadata classifies this object heuristically as a link table within a Data Vault modeling approach. This classification is a modeling suggestion derived from the foreign key structure: the table's primary key is a composite of OBJECT_ID, OBJECT_NAME, OBJECT_TYPE_CODE, SALES_METHODOLOGY_ID, and TASK_ID, and each of these attributes participates in relationships to surrounding hub or reference tables. Rather than holding descriptive business attributes about a single entity, the row exists to record the association among a methodology, a task, and the target sales object. The table is marked VALID and includes standard EBS audit columns, indicating it is an actively maintained transactional object in both 12.1.1 and 12.2.2.

Key Information Stored

The documented physical schema for 12.2.2 contains 14 columns. The most important structural elements are as follows.

  • OBJECT_ID, OBJECT_NAME, OBJECT_TYPE_CODE – Together these identify the target sales object to which the methodology-generated task applies. They form the polymorphic reference that allows a single methodology mapping to be associated with different object types.
  • SALES_METHODOLOGY_ID – The sales methodology definition that owns the mapping. This is the governing business key linking to the methodology header.
  • SALES_STAGE_ID – Identifies the sales stage within the methodology at which the task is generated, linking to the sales stage definition.
  • TASK_ID – The actual Task Manager task instance created for the object.
  • TASK_TEMPLATE_ID – The task template from which the task was instantiated.
  • TASK_TEMPLATE_GROUP_ID – The template group that organizes related task templates.
  • OBJECT_VERSION_NUMBER – The standard EBS optimistic locking column used to detect concurrent updates.
  • Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) – Standard who/when columns for audit and reconciliation.

The surrogate primary key is AS_SALES_METH_TASK_MAP_PK, defined over OBJECT_ID, OBJECT_NAME, OBJECT_TYPE_CODE, SALES_METHODOLOGY_ID, and TASK_ID. A documented unique index, AS_SALES_METH_TASK_MAP_U1, covers OBJECT_ID, OBJECT_TYPE_CODE, SALES_METHODOLOGY_ID, and TASK_ID, serving as the principal business-key candidate. Note that the unique index omits OBJECT_NAME from the primary key composition, which is a useful distinction when designing joins or de-duplication logic.

Common Use Cases and Queries

Typical scenarios include determining which tasks a methodology has spawned for a given opportunity, auditing automatic task creation, and reporting on methodology adherence across a sales pipeline.

To find all tasks generated by a methodology for a specific object:

  • SELECT t.task_id, t.subject FROM jtf_tasks_b t, as_sales_meth_task_map m WHERE m.object_id = :object_id AND m.sales_methodology_id = :methodology_id AND m.task_id = t.task_id;

To trace a generated task back to its template and template group:

  • SELECT m.task_id, m.task_template_id, m.task_template_group_id FROM as_sales_meth_task_map m WHERE m.task_template_id IS NOT NULL;

Reporting use cases include counting generated tasks per methodology or sales stage, identifying objects with no mapped tasks, and reconciling methodology-driven task creation against the JTF_TASKS_B base table to detect orphaned or missing task instances. Because the table carries OBJECT_TYPE_CODE, queries can be scoped to a single object type when analyzing a particular sales process.

Related Objects

The table participates in five documented foreign key relationships that define its integration points.

  • AS_SALES_METHODOLOGY_B – joined on SALES_METHODOLOGY_ID; the methodology definition that drives task generation.
  • JTF_TASKS_B – joined on TASK_ID; the Task Manager base table holding the actual task records.
  • JTF_TASK_TEMPLATES_B – joined on TASK_TEMPLATE_ID; defines the reusable task pattern.
  • JTF_TASK_TEMP_GROUPS_B – joined on TASK_TEMPLATE_GROUP_ID; groups related templates.
  • AS_SALES_STAGES_ALL_B – joined on SALES_STAGE_ID; the methodology stage governing when the task is created.

Together these relationships make AS_SALES_METH_TASK_MAP the central junction for methodology-driven task automation within Sales Foundation, and any query joining methodology, stage, and task data should pass through this table.