Results for “iec_ih_hlpr_pvt”

22 results




Overview
Explore in AI Chat

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

Overview

IEC_IH_HLPR_PVT is a private PL/SQL helper package owned by the APPS schema in Oracle E-Business Suite, and falls within the Interaction History (I&I HCLS, Interaction History Communication Lifecycle) subsystem. Its stated purpose, drawn from the package header comment, is to supply "generic initial parameter, record and table definitions used by CALL_IH." In practical terms, the package encapsulates the low-level work required to open, update, and close interaction and media-item records that represent customer contacts — inbound or outbound calls, and their associated segments — captured by Interaction History.

The package is declared AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the calling schema rather than the definer. This is a deliberate security design that requires callers (typically APPS-side I&I code or the call-routing infrastructure) to hold the necessary object privileges themselves. The API classification is PVT, so the package is not intended as a public integration surface; it is an internal utility consumed by the Interaction History caller layer.

The header declares several package-level globals that are initialized once per session and reused by the calling framework: L_INTERACTION_INITIAL and L_MEDIA_LC_INITIAL (numeric initial values), a public interaction record L_INTERACTION_REC, an activities table L_ACTIVITIES_TBL, and a media lifecycle record L_MEDIA_LC_REC, all typed from the JTF_IH_PUB public specification. These types keep helper logic consistent with the published Interaction History API.

Key Procedures and Functions

  • CREATE_INTERACTION — Creates a new Interaction History interaction record. It accepts a media identifier, a party identifier, start and end timestamps, and the outcome, reason, and result classification identifiers. This procedure is the entry point for materializing a contact against a media item and a party.
  • UPDATE_CLOSE_MEDIA_ITEM — Updates and closes an Automatic Object (AO) media item. It receives the media identifier, a subset identifier, a server group identifier, start and end times, an address, an abandon flag, and a hard-close flag. The abandon and hard-close parameters allow the caller to distinguish a normally completed contact from an abandoned or forcibly terminated one.
  • CREATE_MILCS — Creates a media item life cycle segment (MILCS). It takes the media identifier, the MILCS type, and start and end times, capturing a discrete phase of the media item's life cycle.

Two additional package-level constructs support internal cursor processing: the MEDIA_ID_CURSOR REF CURSOR type and the MEDIA_ID_TAB associative array indexed by BINARY_INTEGER, typed against JTF_IH_MEDIA_ITEMS.MEDIA_ID. The documented procedure count is three.

Tables Accessed

  • JTF_IH_MEDIA_ITEMS — the base media item table. Both UPDATE_CLOSE_MEDIA_ITEM and the MEDIA_ID_TAB type definition reference it, reflecting the package's central role in maintaining media item state.
  • JTF_RS_RESOURCE_EXTNS — accessed via APPS synonyms, supporting resource-related attributes associated with interaction processing.

References are made through APPS synonyms, consistent with the AUTHID CURRENT_USER declaration.

Usage Notes

Because the package is classified PVT, it is normally invoked indirectly: the Interaction History caller infrastructure (for example, the CALL_IH entry point and the surrounding I&I HCLS flow) invokes these helpers during telephony and contact-center processing. Typical callers are Interaction History forms, the call-routing or CTI middleware layer, and Agent Dashboard-style interactions, rather than end-user customizations.

The metadata records that no other packages are referenced by IEC_IH_HLPR_PVT, indicating that it sits near the bottom of the Interaction History dependency stack. Custom code should treat it as internal, prefer supported public JTF_IH_PUB APIs, and never assume signature stability across patches or upgrades, given the $Header: marker 115.14 and 2004 copyright line in the source.