Search Results get_activity_status

Overview

APPS.IEX_CALL_HISTORY is a PL/SQL package body in the Oracle E-Business Oracle Interaction Center (IEX) module. Its business purpose is to retrieve and present the interaction history of a customer or call — the chronological log of inbound and outbound telephony interactions, activities, and their associated outcomes, reasons, results, and actions — within the Oracle Telephony / Interaction Center agent interface. The package provides the data layer that backs the Call History form block, allowing agents and supervisors to query historical interaction records over a specified date range and to inspect the individual activities performed against those interactions. It also encapsulates logic that determines whether a given activity already exists for an interaction, which prevents duplicate logging and drives conditional behavior in the history screen.

Key Procedures and Functions

• QUERY_INTERACTION_RECORDS — The primary query driver documented in this package. It accepts input/output parameters for the query mode, an identifier, a from-date and to-date range, a collection of interaction records (interaction table), and error code/error message outputs. It queries and returns history records for the passed date range and is called from the form block, populating the interaction collection consumed by the UI. (Parameter signatures are not restated here; only purposes are described.)
• QUERY_ACTIVITY_RECORDS — The companion query procedure documented in package metadata. It returns activity-level records associated with interactions, supporting the detail view of the call history screen.

The package body further declares private/forward-declared helper routines referenced in the source excerpt, including Get_Activity_Status (determines whether an activity already exists for a given interaction and document reference, returning an OUT status flag), and description lookups Get_Action_Description, Get_OUTCOME_Description, Get_REASON_Description, Get_result_description, and Get_Object_Name. These helpers map internal IDs to user-facing short descriptions and object names for display in the history records.

Tables Accessed

Per documented metadata, the package references the following via APPS synonyms:

• JTF_IH_INTERACTIONS — the master interaction record store; the source of interaction history rows.
• JTF_IH_ACTIVITIES — individual activities recorded against interactions; queried by QUERY_ACTIVITY_RECORDS and by Get_Activity_Status.
• JTF_IH_ACTIONS_TL — translated action definitions; source for action descriptions.
• JTF_IH_OUTCOMES_TL — translated outcome definitions; source for outcome descriptions.
• JTF_IH_REASONS_TL — translated reason definitions; source for reason descriptions.
• JTF_IH_RESULTS_TL — translated result definitions; source for result descriptions.
• PLITBLM — the standard Oracle EBS PL/SQL table-of-strings utility, used for list handling within the package.

These tables belong to the JTF (Oracle CRM Foundation / Interaction History) schema and provide the interaction, activity, and reference-data foundation used across the Interaction Center stack.

Usage Notes

IEX_CALL_HISTORY is classified as an OTHER API in ETRM and is referenced by zero other packages, indicating it is a form-supporting/isolation layer rather than a shared integration API. It is invoked primarily from the Call History form block to populate interaction and activity collections based on user-entered date ranges. Custom code can call QUERY_INTERACTION_RECORDS and QUERY_ACTIVITY_RECORDS, but the caller must supply the collection types (Interaction_Tbl and related) and be prepared to handle the error code and error message OUT parameters. The package honors the IEX_DEBUG_LEVEL profile option (default 20) via PG_DEBUG for diagnostic logging. Notably, though Get_Activity_Status appears in the package body declarations and is the frequently searched entry point for "get_activity_status," it is not among the two procedures documented as public/documented in ETRM 12.2.2; it should be treated as a helper whose signature (interaction ID, document reference, activity-exists OUT flag) reflects an existence check rather than a general-purpose API. Because no formal parameter metadata is published, developers should inspect the deployed source in the target 12.1.1 or 12.2.2 instance before binding calls. Do not modify this package; Oracle-supplied IEX objects should be extended by wrapping rather than editing.