Results for “touch_point_type”
8 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AMS_DLG_INTERACTIONS is a transactional table in the AMS (Marketing) schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. Its stated purpose is to capture every user interaction that occurs during the course of a dialog execution. In the Oracle Marketing and Trade Management (formerly iMarketing/ETRM) model, a "dialog" is an automated, multi-step campaign element that branches based on recipient responses and scheduled events; each touch between the dialog engine and a party, resource, or system produces one row in this table. The table therefore functions as the definitive audit and event log for dialog-driven interactions, supporting campaign analytics, response attribution, and troubleshooting of dialog execution.
From a modeling perspective, the metadata's heuristic Data Vault classification is standalone, meaning no parent hub or link relationships were mined from the foreign-key structure. In practice, however, the presence of a surrogate primary key, multiple descriptive and result-bearing columns, and date/time stamps suggests this behaves closest to a satellite-style fact table: a grain-per-interaction record keyed by a generated identifier rather than by a natural business key.
Key Information Stored
The table contains 23 documented columns. The surrogate primary key is INTERACTION_ID, which is also the sole unique index documented (AMS_DLG_INTERACTIONS_U1), making it the strongest business-key candidate for point lookups and joins. The most significant columns are:
- INTERACTION_ID — Surrogate primary key uniquely identifying each dialog interaction.
- OBJECT_TYPE / OBJECT_ID — Together identify the dialog element or object context in which the interaction occurred.
- START_DATE_TIME / END_DATE_TIME — Temporal boundaries of the interaction, enabling response-time and duration analysis.
- SOURCE_CODE / SOURCE_CODE_ID / RELATED_SOURCE_CODE — Classify the origin or channel of the interaction, such as inbound or outbound communication source.
- RESULT_ID / REASON_ID / OUTCOME_ID — Capture the disposition of the interaction, i.e., what happened and why.
- PARTY_ID / RESOURCE_ID — Identify the customer or prospect (party) and the internal resource involved.
- TOUCH_POINT_TYPE / ACTIVE_FLAG / SYNCHRONIZED_FLAG — Describe the channel, whether the row is active, and its synchronization status.
- SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group access.
- OBJECT_VERSION_NUMBER — Optimistic locking column used by the OA Framework.
- CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — Standard WHO audit columns.
Common Use Cases and Queries
Typical reporting scenarios include measuring dialog response rates by touch point, analyzing interactions per party, and auditing execution history for a specific dialog object. Because the FK relationship points to FND_SECURITY_GROUPS, queries must respect security group scoping.
A representative query counting interactions per party and touch point over a period:
- SELECT PARTY_ID, TOUCH_POINT_TYPE, COUNT(*) FROM AMS.AMS_DLG_INTERACTIONS WHERE START_DATE_TIME BETWEEN :p_from AND :p_to GROUP BY PARTY_ID, TOUCH_POINT_TYPE;
To retrieve the outcome of a dialog object, join on OBJECT_ID with OUTCOME_ID and RESULT_ID to resolve disposition, filtered by ACTIVE_FLAG = 'Y'. For execution duration analysis, compute the difference between END_DATE_TIME and START_DATE_TIME.
Related Objects
The documented foreign key AMS_DLG_INTERACTIONS.SECURITY_GROUP_ID references FND_SECURITY_GROUPS, which governs row-level access. Beyond that, related functionality is provided by the OBJECT_ID reference to dialog/object definitions, PARTY_ID to the party (TCA/HZ) model, and RESOURCE_ID to the resource definition. Result, reason, and outcome lookups are typically resolved against AMS lookup tables. Standard WHO audit joins reference FND_USER for CREATED_BY and LAST_UPDATED_BY. Dialog metadata itself resides in the AMS dialog definition tables, from which OBJECT_TYPE and OBJECT_ID values originate.
-
This table captures all user interactions that happens during course of a dialog execution
-
This table captures all user interactions that happens during course of a dialog execution
-
eTRM - AMS Tables and Views 12.2.2
This table is used to store tracking data for web advertisement and offer type schedules
-
eTRM - AMS Tables and Views 12.1.1
This table is used to store tracking data for web advertisement and offer type schedules