Search Results ieu_sh_pub

Overview

IEU_SH_PUB is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Suite. The "SH" prefix and the UWQ_ procedure naming convention identify it as part of the Universal Work Queue (UWQ) infrastructure, which underlies the interaction and telephony components of Oracle EBS — most notably the Interaction Center, iSupport, and telephony/CTI integrations delivered through the IEU (Interaction / Universal Work Queue) product family.

The package provides the programmatic entry points through which a client application signals the lifecycle of a work session and the activities performed within it. In business terms, it lets an agent-facing application tell UWQ that a user has logged in, begun handling a work item, updated progress on that item, and finished it, allowing the work queue to route, track, and report on workload distribution. The package is documented as VALID in the ETRM metadata for both 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents five procedures in the package body:

• UWQ_BEGIN_SESSION — Opens a work queue session for the calling user or agent. This establishes the context under which subsequent activity calls are recorded.
• UWQ_END_SESSION — Closes the previously opened session, releasing the session context and finalizing any session-level tracking.
• UWQ_BEGIN_ACTIVITY — Marks the start of an individual work activity within an open session, such as an agent accepting or opening a work item.
• UWQ_UPDATE_ACTIVITY — Records a status or progress change against an activity already in flight.
• UWQ_END_ACTIVITY — Signals completion of an activity, closing out the corresponding work item tracking record.

These five procedures form a matched lifecycle: session open/close brackets one or more activity open/update/close sequences. Parameter lists are not reproduced here as they are not present in the summarized ETRM extract.

Tables Accessed

The ETRM dependency extract for IEU_SH_PUB lists no directly referenced application tables; the recorded dependencies are limited to the APPS schema itself, FND_API, and the SYS STANDARD package. The absence of table references at this level indicates that IEU_SH_PUB is a thin public wrapper: it depends on FND_API, the standard EBS API error-handling and message framework, which implies the procedures follow the conventional EBS API contract of returning a success/failure status with a message stack rather than raising raw exceptions. Actual persistence of session and activity data is delegated to lower-level UWQ packages invoked internally rather than performed directly by this API.

Usage Notes

IEU_SH_PUB is intended for internal use by the UWQ client layer and by dependent application code. The ETRM metadata records exactly one referencing package, IEM_CLIENT_PUB, indicating that IEM (Interaction Manager / client integration) code drives this API on behalf of the agent desktop. Because the package is classified as a public (PUB) API, Oracle supports its invocation from custom extensions, but callers should expect the documented sequence to be respected: a session must be opened before activities are begun, and each activity should be closed before the session is ended.

In practice the procedures are invoked from the EBS forms and Java/JTT-based agent clients that constitute the Interaction Center desktop, not from concurrent programs; there is no scheduled or batch entry point among the documented procedures. Custom integrations that simulate agent activity — for example, headless workload generators or third-party telephony middleware — may call the same API to register activity against an agent, but must supply a valid session context first. Because FND_API is in the dependency chain, callers should check the returned status code and message rather than relying on exception handling alone.