Search Results ams_eveh

Overview

APPS.AMS_TASKS_V is a marketing-oriented tasks view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, owned by the APPS schema. It presents a joined, filtered projection of task records managed by the Oracle Marketing (AMS) application, combining task header information from the JTF task framework with assignment details and employee resource attributes. The view is designed to surface only those tasks belonging to the Oracle Marketing task type hierarchy (tasks whose task type carries the rule ORACLE_MARKETING), thereby distinguishing marketing activities from the broader population of tasks stored in the shared JTF_TASKS infrastructure.

The view also resolves the polymorphic source object type code into a human-readable qualifier meaning drawn from the AMS_SYS_ARC_QUALIFIER lookup type. In the definition this decode explicitly maps the source object types AMS_CAMP to CAMP, AMS_EVEO to EVEO, AMS_EVEH to EVEH, and AMS_DELV to DELV. This last mapping is directly relevant to users searching on "ams_delv": the code AMS_DELV identifies a marketing delivery source object, and the view surfaces the corresponding DELV lookup meaning for such tasks. As a reporting and integration surface, AMS_TASKS_V is commonly consumed by concurrent programs, OBIEE/BIP reports, and custom interfaces that need a denormalized, employee-assigned view of marketing tasks.

Underlying Base Objects

ETRM documents the following referenced base objects for this view:

• JTF_TASKS_V (VIEW) — source of the core task columns aliased as "a"
• JTF_TASK_ASSIGNMENTS (SYNONYM) — source of assignment columns aliased as "b"
• AMS_JTF_RS_EMP_V (VIEW) — employee resource attributes aliased as "c"
• AMS_LOOKUPS (VIEW) — lookup meanings aliased as "d"
• JTF_TASK_TYPES_B (SYNONYM) — task type definition aliased as "e"
• JTF_TASK_UTL (PACKAGE) and JTF_TASK_WORKFLOW_PKG (PACKAGE) — supporting task utilities and workflow logic

The joins are driven by a.task_id = b.task_id (task to assignment), b.resource_id = c.resource_id (assignment to employee resource), and a.task_type_id = e.task_type_id with e.rule = 'ORACLE_MARKETING'. The lookup join is an outer join (via the DECODE expression tied to D.LOOKUP_CODE(+) with D.LOOKUP_TYPE(+) = 'AMS_SYS_ARC_QUALIFIER'). Filters restrict results to non-deleted tasks (a.deleted_flag != 'Y') and to employee-owned tasks (a.owner_type_code = 'RS_EMPLOYEE'). Note that both AMS_JTF_RS_EMP_V and AMS_LOOKUPS are themselves views, so AMS_TASKS_V is layered several levels deep over the JTF schema.

Key Columns

The view exposes task identifiers and versioning (task_id, object_version_number), descriptive attributes (task_name, task_type, task_priority, task_status), and scheduling columns (actual_start_date, actual_end_date, planned_start_date, planned_end_date). Ownership is represented by owner_id, owner_type_code, and owner, with employee detail supplied by full_name and email from AMS_JTF_RS_EMP_V.

Source object context is captured by source_object_id, source_object_name, and source_object_type_code; the latter drives the decode into the AMS_SYS_ARC_QUALIFIER lookup whose meaning is returned in the meaning column. Assignment-level columns include task_assignment_id, resource_id, resource_type_code, and assignment_status_id. Additional flags include private_flag and creation_date.

Common Use Cases and Queries

Typical scenarios include listing marketing tasks by owner, reporting on assignment status, and identifying tasks tied to specific marketing source objects such as campaigns, events, or deliveries. A representative query filtering for delivery-sourced tasks follows:

SELECT task_id, task_name, task_status, meaning, full_name, email
FROM apps.ams_tasks_v
WHERE source_object_type_code = 'AMS_DELV';

To report all marketing tasks assigned to employees within a date window:

SELECT task_id, task_name, task_priority, planned_start_date, planned_end_date, full_name
FROM apps.ams_tasks_v
WHERE planned_start_date BETWEEN :p_start AND :p_end
ORDER BY planned_start_date;

Because AMS_TASKS_V restricts to ORACLE_MARKETING task types and employee owners, it is well suited to targeted marketing task reporting while excluding unrelated JTF task records.