Search Results ieu_uwq_media_data_obj




Overview
Explore in AI Chat

Overview

IEU_UWQ_FORM_ROUTE is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM repository as a miscellaneous (OTHER) API rather than a public or private interface. Its name indicates that it belongs to the Interaction Center / Universal Work Queue (IEU) family of components and that its responsibilities are tied to form routing within the UWQ media framework. In EBS 12.1.1 and 12.2.2 the UWQ subsystem presents agents in the Interaction Center with work items drawn from multiple channels — media such as e-mail, chat, and phone — and dispatches those items to the appropriate Oracle Forms interface. IEU_UWQ_FORM_ROUTE encapsulates the routing decisions that determine which form is launched for a given media item and how the runtime context of that item is passed to the target form. The object is valid in the dictionary and is documented with a single entry point. In the 12.2.2 metadata it is recorded as not referenced by any other database object, confirming that it is invoked from the application tier — typically from forms or from Java/OC4J middleware — rather than being called from dependent PL/SQL packages.

Key Procedures and Functions

The ETRM documentation records one program unit in this package body:

  • IEU_UWQ_FORM_OBJ — The single documented procedure/function of the package. It provides the object-level handle used by the form routing logic. In practice this unit resolves the target form object associated with a work item's media type and exposes the information needed by the caller to open or navigate to that form. The metadata does not publish a formal parameter list, and no signature should be assumed; consumers should treat the unit as an internal routing entry point rather than a supported public API. Its purpose is to map a UWQ media context to a concrete Forms object so that the Interaction Center can hand off the agent to the correct application screen.

The package therefore performs a narrow, single-purpose function: it is the translation layer between media data objects and the forms that display them.

Tables Accessed

The documented table reference for this package body is PLITBLM, an Oracle-supplied dictionary table that stores information about PL/SQL library objects and their associated program units. Because IEU_UWQ_FORM_ROUTE operates on form and media object definitions, PLITBLM is read to resolve metadata about the forms or library units that participate in the routing decision. The package does not own or maintain application tables of its own. Its dependency list additionally shows references to IEU_UWQ_MEDIA_DATA_OBJ and IEU_UWQ_MEDIA_DATA_NST, which together form the UWQ media data object model. These objects supply the media-type context — the record representing the work item being routed — that the form routing logic consumes. No write operations against persistent application data are documented; the package behaves as a read-only resolver over media and form metadata.

Usage Notes

IEU_UWQ_FORM_ROUTE is an internal runtime component of the Universal Work Queue. It is not intended for direct invocation from customer-written PL/SQL, and the metadata confirms it is not referenced by any other package, meaning its callers lie outside the PL/SQL dependency graph — in Oracle Forms triggers or in the UWQ middle-tier classes that run when an agent accepts or opens a work item. The most common invocation scenario is agent navigation: when a UWQ push or pull request identifies a media item, the UWQ runtime calls this package to determine which form should be opened and with what context. Because the routing behavior is driven by media data object definitions, extensions that introduce new media types or custom work item classes must register the corresponding form mapping through the standard UWQ media data object configuration rather than by modifying this package. Customizations should avoid altering the package body directly, since it may be regenerated by patching; any change in routing behavior should instead be implemented through the supported UWQ configuration tables. In environments upgraded from 12.1.1 to 12.2.2, the package remains valid and continues to serve the same routing role, as its logic is independent of the Online Patching editioning model applied to schema objects in later releases.