Search Results jtf_ih_interactions_stg_log




Overview
Explore in AI Chat

Overview

The JTF.JTF_IH_INTERACTIONS_STG_LOG table is a CRM Foundation (JTF) staging and logging table that supports the Oracle Interaction History (IH) subsystem within Oracle E-Business Suite 12.1.1 and 12.2.2. Conceptually, an interaction represents a contact point between a customer, customer system, or potential customer and a single human or automated agent — the Handler and Handler Resource. Interactions are timed, carry an outcome and result that can be tracked, and may span multiple interaction records. The staging log preserves this interaction data before, during, or after its consolidation into the primary interaction history tables, and it also captures processing status and error information for bulk or asynchronous loads.

The table resides in the JTF schema and is documented as VALID, with 68 columns in the 12.2.2 physical schema. Its primary key is JTF_IH_INTERACTIONS_STG_LOG_PK, defined over the composite of INTERACTION_ID and SESSION_NO. Under a heuristic Data Vault classification mined from the foreign key structure, this object is satellite-leaning: it is keyed to a parent interaction identity and carries descriptive, stateful, and audit attributes rather than acting as a standalone hub or a pure link.

Key Information Stored

The table stores a mix of interaction business attributes, staging control fields, and standard EBS audit columns. The most significant columns are:

Common Use Cases and Queries

Typical use cases center on monitoring staging loads, diagnosing failures, and auditing interaction activity. A common pattern checks for unprocessed or failed rows:

  • Failure triage: SELECT INTERACTION_ID, SESSION_NO, STATUS_FL, ERROR_MESSAGE FROM JTF.JTF_IH_INTERACTIONS_STG_LOG WHERE STATUS_FL IS NULL OR STATUS_FL = 'E';
  • Concurrent program reconciliation: Filter by REQUEST_ID and PROGRAM_ID to reconcile a specific load run and report row counts and error volume.
  • Party activity reporting: Join PARTY_ID to HZ_PARTIES to summarize staged interactions per customer or contact over SESSION_DATE ranges.
  • Handler/agent productivity: Aggregate on HANDLER_ID and RESOURCE_ID, using DURATION and the productive/non-productive time columns for interval analysis.
  • Security-scoped extraction: Restrict by ORG_ID or SECURITY_GROUP_ID to honor multi-org and data security boundaries in custom reports.

Because this is a log/staging object, queries are generally read-only and should be bounded by date or request to avoid full scans on a potentially large table.

Related Objects

Documented relationships anchor this table to several CRM Foundation and Trading Community objects:

  • HZ_PARTIES — joined via JTF_IH_INTERACTIONS_STG_LOG.PARTY_ID to resolve customer and contact identities.
  • JTF_IH_SCRIPTS — joined via SCRIPT_ID to identify the interaction script used.
  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for security-group resolution.
  • JTF_IH_INTERACTIONS — the primary interaction history table, related through INTERACTION_ID as the parent interaction identity and consolidation target.
  • FND_CONCURRENT_REQUESTS — related through REQUEST_ID and PROGRAM_ID for load-run context.
  • HZ_CUST_ACCOUNTS and FND_USER — commonly joined for account context and handler/agent identity in reporting, though not enumerated as formal foreign keys in the documented metadata.

Together these relationships position JTF_IH_INTERACTIONS_STG_LOG as the auditable staging counterpart to the live interaction history model in Oracle CRM Foundation.