Search Results doc_source_object_name

Overview

The APPS.AMS_PERSON_INTERACT_ACT_V view is a Marketing (AMS) module reporting and integration object in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a denormalized, person-centric perspective of interaction activities recorded through the Interaction History (JTF_IH) framework, joining each activity to the party who participated in it, to the parent interaction, and to the customer account where one exists. The view is defined with STATUS = VALID and is owned by the APPS schema.

Its principal value is that it flattens the relationship between an activity and a person party, exposing party identifiers and names alongside activity-level attributes such as media, handler, resource, duration, outcome, result, reason, and the INTERACTION_ACTION_TYPE classification. This makes the view suitable for direct consumption by reports, concurrent programs, and downstream integrations without the caller needing to reconstruct the JTF_IH join graph.

The name searched — interaction_action_type — corresponds to a column of this view, INTERACTION_ACTION_TYPE, which classifies the nature of the action performed during the interaction activity. Because it is surfaced at row level, it is commonly used as a filter or grouping dimension in interaction analysis.

Underlying Base Objects

The view is defined over four documented base objects, all referenced as synonyms:

• JTF_IH_ACTIVITIES (aliased JIAV) — the driving table, supplying activity and interaction identifiers, timestamps, media, task, document, duration, description, role, outcome/result/reason, and action attributes.
• JTF_IH_INTERACTIONS (aliased JIIV) — supplies the interaction context, including RESOURCE_ID, HANDLER_ID, and the PARTY_ID used to link to the party.
• HZ_PARTIES (aliased HP) — supplies PARTY_ID and PARTY_NAME, restricted to records where STATUS = 'A' and PARTY_TYPE = 'PERSON'.
• HZ_CUST_ACCOUNTS (aliased HCA) — supplies CUST_ACCOUNT_ID and ACCOUNT_NUMBER, joined with an outer (+) on CUST_ACCOUNT_ID so that activities lacking an associated account are still returned.

The join conditions are: JIAV.INTERACTION_ID = JIIV.INTERACTION_ID, JIIV.PARTY_ID = HP.PARTY_ID, and JIAV.CUST_ACCOUNT_ID = HCA.CUST_ACCOUNT_ID(+). The inner joins to JTF_IH_INTERACTIONS and HZ_PARTIES, combined with the PARTY_TYPE = 'PERSON' predicate, restrict the result set to activities tied to active person parties.

Key Columns

• ACTIVITY_ID / INTERACTION_ID — primary identifiers for the activity and its parent interaction.
• PARTY_ID / PARTY_NAME — the person party associated with the interaction.
• INTERACTION_ACTION_TYPE — the action classification for the activity; a frequent filter and grouping column.
• RESOURCE_ID / HANDLER_ID — the resource and handler recorded on the interaction.
• MEDIA_ID, START_DATE_TIME, END_DATE_TIME, DURATION — media channel and temporal attributes.
• OUTCOME_ID, RESULT_ID, REASON_ID — outcome and result classification of the activity.
• ACTION_ID, ACTION_ITEM_ID, OBJECT_ID, OBJECT_TYPE, SOURCE_CODE, SOURCE_CODE_ID — action and object linkage, including source-of-record references.
• CUST_ACCOUNT_ID / ACCOUNT_NUMBER — customer account context, nullable due to the outer join.
• DOC_ID, DOC_REF, DOC_SOURCE_OBJECT_NAME, TASK_ID, DESCRIPTION, ROLE — descriptive document and task attributes.
• CREATED_BY_NAME, LAST_UPDATED_BY_NAME, LAST_UPDATE_LOGIN_NAME — aliased audit identifiers.

Note that the view does not itself resolve CREATED_BY or the audit columns to user names through FND_USER; the name suffixes reflect the raw columns as aliased in the view text.

Common Use Cases and Queries

Typical uses include analyzing interactions by action type, media, or handler; building person-level activity histories; and feeding data extracts into marketing analytics or external CRM systems.

Activities filtered by action type:

SELECT activity_id, interaction_id, party_id, party_name,
       interaction_action_type, start_date_time, outcome_id,
       handler_id, resource_id, account_number
  FROM apps.ams_person_interact_act_v
 WHERE interaction_action_type = :p_action_type
 ORDER BY start_date_time DESC;

Interaction volumes grouped by type and media for a date range:

SELECT interaction_action_type, media_id,
       COUNT(DISTINCT interaction_id) interactions,
       COUNT(*) activities
  FROM apps.ams_person_interact_act_v
 WHERE start_date_time BETWEEN :p_from AND :p_to
 GROUP BY interaction_action_type, media_id
 ORDER BY activities DESC;

Person-level activity history with account context:

SELECT party_name, account_number, interaction_id,
       activity_id, interaction_action_type, duration
  FROM apps.ams_person_interact_act_v
 WHERE party_id = :p_party_id
 ORDER BY start_date_time;

Because the view joins four underlying objects and enforces PERSON party and active-status predicates, queries should be filtered on interaction date or party where possible to keep execution efficient on high-volume interaction data.