Search Results jtf_ih_import




Overview
Explore in AI Chat

Overview

The APPS.JTF_IH_IMPORT package body is a core component of the Oracle E-Business Suite Interaction History (IH) data import infrastructure. Its business function is to load staged interaction history data — customer interactions, activities performed during those interactions, and associated media items — into the production Interaction History tables. The package supports a two-phase import model: records can first be tested for validity and then imported, with both phases tracked through status flags (0 = not tested or tested/imported with errors, 1 = tested successfully, 2 = imported). This staging model allows data stewards to review errors and duplicates before committing records to the live IH schema.

The most recent documented header revision is 115.50 (2004/07/28). The package is owned by APPS and is classified as OTHER in the ETRM metadata for 12.2.2. Interaction History is used predominantly by CRM Foundation / TeleSales and Contact Center deployments, where external call detail records, campaign responses, or legacy interaction data must be bulk-loaded into EBS.

Key Procedures and Functions

  • GO_TEST — The validation entry point. It evaluates staged interaction, activity, and media item records without committing them to the production IH tables, recording outcomes in the corresponding staging log tables. Records that pass validation are flagged as tested successfully (status 1).
  • GO_IMPORT — The import entry point. It reads staged records (typically those that passed GO_TEST) and inserts them into the production Interaction History tables, updating log records with status 2 to indicate successful import.

The package body additionally relies on internal (undocumented in ETRM) helper structures, including Insert_Interaction_Log, Insert_Activity_Log, Insert_Media_Item_Log, and the function ChkDuplicate, all of which accept a nSessionNo (session number) parameter. This is the identifier that ties every row produced during a single import run together, and it is why the search term session_no maps directly to this package. Each invocation of GO_TEST or GO_IMPORT generates or receives a session number, and every log row written during that run is stamped with the same value, enabling later query of the complete audit trail for a given import batch.

Tables Accessed

The package operates against staging and log tables via APPS synonyms:

Production IH tables (such as JTF_IH_INTERACTIONS, JTF_IH_ACTIVITIES, and JTF_IH_MEDIA_ITEMS) are populated as part of GO_IMPORT. The log tables are the primary mechanism by which session-level diagnostics are surfaced to the user.

Usage Notes

JTF_IH_IMPORT is typically invoked by a concurrent program that accepts a session number (or generates one) and drives the test/import cycle. It may also be called from custom PL/SQL that pre-populates the staging tables and then calls GO_TEST followed by GO_IMPORT. Because the header dates from 2004 and later bug fixes existed (for example, bug 3163407, which removed a hard-coded APPS schema reference), the 12.1.1 and 12.2.2 versions may differ in minor internal behavior even though the public procedure names are stable. The package is not referenced by any other documented package, so callers should treat it as a direct entry point. When troubleshooting failed imports, querying the three staging log tables filtered by SESSION_NO is the standard diagnostic path.