Results for “jtf_ih_interactions_v”

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

Overview

JTF_IH_INTERACTIONS_V is a reporting view owned by the APPS schema within the JTF – CRM Foundation product of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. As documented in the E-Business Suite Technical Reference Manual (ETRM), the view is used for generating reports for records in the JTF_IH_INTERACTIONS table. It exposes the full set of interaction tracking attributes maintained by the Interaction History (IH) subsystem, presenting them in a flattened, read-oriented form that is convenient for both concurrent report programs and ad hoc SQL access.

The view contains no aggregation or transformation logic; it is a straight projection of the underlying interaction rows. Its principal value lies in providing a stable, named reporting interface over the transaction table, and in surfacing the ROWID of the base row as the ROW_ID column. The user search term "reference_form" corresponds directly to the REFERENCE_FORM column exposed by this view, which records the entry point or originating form from which an interaction record was created.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: the synonym JTF_IH_INTERACTIONS, which resolves to the APPS-owned table of the same name. The view definition selects from this table using the alias INT, and exposes the ROWID of the base row as ROW_ID to preserve a direct handle to the physical record. Because both objects reside under the APPS schema, the view inherits the standard grants, synonyms, and access controls applied to CRM Foundation entities, and it is therefore consumable by custom reports, BI Publisher data templates, and integration extracts without requiring direct table access.

No joins to related lookup, resource, party, or script tables are present in the documented view text. Values such as RESULT_ID, OUTCOME_ID, REASON_ID, and SCRIPT_ID are returned as identifiers only; consumers must join to the appropriate lookup or reference tables to resolve meaningful descriptions.

Key Columns

• ROW_ID – the base table ROWID, useful for correlation and change-detection queries.
• INTERACTION_ID – primary identifier of the interaction record.
• OBJECT_VERSION_NUMBER – optimistic locking version, relevant when the view is used to drive updates through the base table.
• OBJECT_ID / OBJECT_TYPE – the business object the interaction relates to, enabling contextual linkage.
• SOURCE_CODE / SOURCE_CODE_ID – the channel or source that produced the interaction.
• REFERENCE_FORM – the form or entry point from which the interaction was created; central to origin-based analysis.
• START_DATE_TIME / END_DATE_TIME – the interaction interval.
• DURATION, PRODUCTIVE_TIME_AMOUNT, NON_PRODUCTIVE_TIME_AMOUNT, PREVIEW_TIME_AMOUNT, WRAP_UP_TIME_AMOUNT, INTER_INTERACTION_DURATION – the time accounting measures captured for the interaction.
• RESULT_ID, REASON_ID, OUTCOME_ID – disposition and outcome identifiers.
• HANDLER_ID, RESOURCE_ID, SCRIPT_ID – the agent, resource, and script associated with the interaction.
• PARTY_ID, PRIMARY_PARTY_ID, CONTACT_PARTY_ID, CONTACT_REL_PARTY_ID – party and contact relationships.
• METHOD_CODE, FOLLOW_UP_ACTION, ACTIVE – classification, follow-up, and status indicators.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – standard audit columns.

Common Use Cases and Queries

Typical scenarios include interaction volume reporting, time-and-activity analysis by resource, and origin-based breakdowns by REFERENCE_FORM. A representative query filtering on the reference form is:

• SELECT INTERACTION_ID, START_DATE_TIME, DURATION, HANDLER_ID, RESOURCE_ID, RESULT_ID FROM APPS.JTF_IH_INTERACTIONS_V WHERE REFERENCE_FORM = :p_reference_form AND TRUNC(START_DATE_TIME) BETWEEN :p_from AND :p_to AND ACTIVE = 'Y' ORDER BY START_DATE_TIME;
• SELECT RESOURCE_ID, SUM(DURATION) TOTAL_DURATION, SUM(PRODUCTIVE_TIME_AMOUNT) PRODUCTIVE FROM APPS.JTF_IH_INTERACTIONS_V GROUP BY RESOURCE_ID;
• SELECT b.ROW_ID, b.INTERACTION_ID, b.LAST_UPDATE_DATE FROM APPS.JTF_IH_INTERACTIONS_V b WHERE b.OBJECT_TYPE = :p_object_type AND b.OBJECT_ID = :p_object_id;

Because the view performs no joins, reporting queries written against it remain lightweight, and any enrichment with lookup meanings or party names is performed explicitly by the consuming query or report definition.