Search Results go_test

Overview

APPS.JTF_IH_IMPORT is an Oracle E-Business Suite package that belongs to the Interaction History (JTF_IH) schema family, which underpins the Telephony and Interaction Center functionality within Oracle CRM. Its principal business function is to import Interaction History data—interactions, their associated activities, and related media items—from staging tables into the production Interaction History tables. The package header carries the AUTHID CURRENT_USER clause, meaning the package executes with the privileges of the invoking schema rather than the definer, which allows importing sessions to resolve objects under the caller's own schema context.

The excerpt of JTFIHIMS.pls reveals several constants and package-level variables that hint at the package's design. Message constants such as 'Activities Not Found', 'Media Items Not Found', 'Media Item already exists in JTF_IH_MEDIA_ITEMS table', and 'Interactions was not closed' indicate that the import process validates the presence of activities and media items and enforces idempotency before inserting records. The variable nCntTransRows (default 1000) controls commit frequency, and pnSessionNo/nNxtSessionNo support session-based import runs, enabling multiple concurrent or sequential import batches to be distinguished.

Key Procedures and Functions

• GO_TEST — Performs validation only. This procedure tests staged Interaction History data without committing any changes to the production tables, surfacing issues such as missing activities or missing media items before the real import runs. The header comment "bTest OFF - if you need import only without testing of data" clarifies that a test pass is the default state and that turning it off bypasses this validation.
• GO_IMPORT — Executes the actual import. It accepts two OUT parameters (ERRBUF and RETCODE), the standard concurrent-program signature used throughout EBS for capturing error text and a status code. It reads staged records, writes them into the production Interaction History tables, and reports success or failure through these parameters.

Only these two procedures are documented in the ETRM metadata; no additional public functions are exposed.

Tables Accessed

The package operates against two logical sets of tables joined by *_STG and *_STG_LOG naming conventions:

• Staging tables — JTF_IH_INTERACTIONS_STG, JTF_IH_ACTIVITIES_STG, and JTF_IH_MEDIA_ITEMS_STG. These hold inbound data awaiting import; they are the source of records processed by GO_TEST and GO_IMPORT.
• Log tables — JTF_IH_INTERACTIONS_STG_LOG, JTF_IH_ACTIVITIES_STG_LOG, and JTF_IH_MEDIA_ITEMS_STG_LOG. These capture the results of each import run, including errors such as 'Interaction was not created', 'Activity was not created', and 'Media_Items was not created'.
• JTF_IH_IMPORT_S1 — A sequence (indicated by the _S1 suffix) used to generate session numbers reflected in pnSessionNo and nNxtSessionNo.
• DUAL — Used for singleton queries typical of PL/SQL utility logic.

The production target tables (JTF_IH_INTERACTIONS, JTF_IH_ACTIVITIES, JTF_IH_MEDIA_ITEMS) are referenced implicitly through the constants and error messages, though only the staging and log objects appear in the documented reference list.

Usage Notes

JTF_IH_IMPORT is designed to be invoked as a concurrent program within the Oracle EBS concurrent manager framework, consistent with its GO_IMPORT(ERRBUF, RETCODE) signature and the session-numbering scheme. Typical deployments run GO_TEST as a validation step in a test environment or as a pre-import check, then execute GO_IMPORT to commit the staged records. External systems—such as telephony switches, CTI middleware, or third-party customer-interaction feeds—populate the *_STG tables, and the package is scheduled to drain those tables on a periodic basis.

The package is not referenced by any other PL/SQL package (per the ETRM metadata), so its invocation surface is limited to concurrent programs, SQL*Plus scripts, or custom code that calls the procedures explicitly. Because it uses AUTHID CURRENT_USER, callers must ensure they own or have been granted the necessary privileges on all referenced staging, log, and production objects.