Results for “ams_act_type_task_tpls”

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

Overview

AMS_ACT_TYPE_TASK_TPLS is an intersection table in the Oracle Marketing (AMS) schema that defines the relationship between activity types and the task templates available to them. In Oracle EBS 12.1.1 and 12.2.2, marketing activity types provide a classification framework for campaigns, events, and other marketing activities, while task templates (originating from the Oracle Task Manager / JTF foundation) define reusable task definitions. This table resolves the many-to-many association between the two, determining which task templates an end user may select when creating tasks for a given activity type.

The heuristic Data Vault classification mined from the foreign key structure is standalone. In Data Vault modeling terms, this object behaves as an independent link-style table rather than a pure hub or satellite; it carries its own surrogate primary key and connects to reference entities (task templates and security groups) rather than acting as a descriptive satellite of a single parent. Where formal Data Vault modeling is applied, it is best treated as a link table bridging activity types and task templates, with its descriptive columns handled as link attributes or as a dependent satellite.

Key Information Stored

The documented physical schema contains 11 columns. The most significant are summarized below.

• ACTIVITY_TYPE_TASK_TPL_ID — The surrogate primary key, defined by the unique index AMS_ACT_TYPE_TASK_TPLS_U1, which also serves as the documented business-key candidate for the table.
• TASK_TEMPLATE_ID — The foreign key referencing JTF_TASK_TEMPLATES_B. It identifies the task template that is made available for the associated activity type.
• ACT_TASK_TPL_FOR_ID and ARC_ACT_TASK_TPL_FOR — Descriptive attributes that qualify the scope or context in which the task template applies to the activity type, allowing variants of the same template to be distinguished.
• SECURITY_GROUP_ID — The foreign key to FND_SECURITY_GROUPS. This enforces multi-tenant/multi-org data isolation, ensuring that template-activity associations are visible only within the appropriate security group.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Framework (OAF) and concurrent update handling.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN, which capture standard WHO-column auditing for every row.

The surrogate key should not be confused with the business key: while AMS_ACT_TYPE_TASK_TPLS_U1 is unique on the surrogate ACTIVITY_TYPE_TASK_TPL_ID, the logically meaningful uniqueness is the combination of activity type, task template, and security group.

Common Use Cases and Queries

Typical use cases include reporting which task templates are enabled for a marketing activity type, validating setup before launching a campaign, and auditing template availability across security groups. A representative query joins the intersection table to the task template base table to return readable template names:

• Listing templates for an activity type: SELECT t.task_template_id, t.name FROM ams_act_type_task_tpls a, jtf_task_templates_b t WHERE a.task_template_id = t.task_template_id AND a.security_group_id = :sg;
• Audit of changes: filtering by LAST_UPDATE_DATE and LAST_UPDATED_BY to determine when template associations were added or removed.
• Integration and migration checks: comparing configured associations between environments by activity type and security group.
• Reporting: driving discovery of which templates are offered during task creation workflows from the Marketing activity type setup.

Related Objects

The following are the most significant related objects referenced by or dependent on AMS_ACT_TYPE_TASK_TPLS, based on the documented FK relationships:

• JTF_TASK_TEMPLATES_B — Referenced through TASK_TEMPLATE_ID; supplies the task template definitions offered for each activity type.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID; defines the security group scoping used for data isolation.
• AMS_ACT_TYPES_B / activity type entities — Although not enumerated as a direct FK in the metadata, activity type definitions supply the ACT_TASK_TPL_FOR_ID context that qualifies each association.
• JTF_TASK_TEMPLATES_TL — The translation table for task template names, commonly joined in reporting queries.
• AMS Marketing task setup APIs — The AMS task/activity configuration logic that reads and writes these association rows through the OAF-based setup pages.

Because the object is classified as standalone, it should be treated as an independent link-style entity when designing downstream reporting or integration layers, keyed on ACTIVITY_TYPE_TASK_TPL_ID.