Search Results iem_mailitem_pub




Overview
Explore in AI Chat

Overview

APPS.IEM_MAILITEM_PUB is a public PL/SQL package body in the Oracle E-Business Suite ETRM (Email Center / Interaction Center) module. It provides the core programmatic interface for managing inbound email items as they flow through the Email Center processing pipeline. The package exposes a set of public APIs that allow applications to retrieve, inspect, update, resolve, and dispose of mail items (individual email messages) that have been captured by the Email Center media processing infrastructure.

In the 12.1.1 and 12.2.2 releases, IEM_MAILITEM_PUB acts as the primary abstraction layer over the IEM_MS_* message-store tables and the routing/classification tables. It handles the lifecycle of an email from ingestion through classification, routing, agent assignment, and final disposition, including support for rerouting and archival. Its API classification is PUB, confirming it is intended for supported, external invocation by forms, concurrent programs, and custom extensions. The object carries a VALID status and is owned by the APPS schema.

Key Procedures and Functions

The package documents 15 procedures and functions. The principal public routines include:

  • GETMAILITEMCOUNT — Returns the count of mail items matching a given filter, typically used to populate queue counters and worklist indicators.
  • GETMAILITEM — Retrieves a mail item record, providing the primary single-item read access.
  • DISPOSEMAILITEM — Applies a final disposition (such as resolve, close, or delete) to a processed mail item.
  • RESOLVEDMESSAGE — Marks a message as resolved, completing the agent's handling of the item.
  • GETGROUPDETAILS — Retrieves resource-group details associated with an item for routing or assignment purposes.
  • UPDATEMAILITEM — Updates mutable attributes of an existing mail item record.
  • GETMAILITEMINFO — Returns descriptive metadata about a mail item, supporting UI display and processing logic.
  • GETEMAILHEADERS — Returns the header fields (from, to, subject, date, and similar) for a mail item.
  • GETUNREADEMAILHEADERS — Returns header data restricted to unread messages, supporting inbox-style views.
  • GETQUEUEITEMDATA — Returns queue-oriented data for items awaiting processing or agent action.

These routines collectively cover read, update, disposition, and queue-access operations. The package also relies on internal constants and helper logic, and it uses the standard FND_API, FND_MESSAGE, and FND_MSG_PUB error-handling utilities.

Tables Accessed

IEM_MAILITEM_PUB reads and writes the core Email Center message-store tables, including IEM_MS_BASE_HEADERS, IEM_MS_EXTHDRS, IEM_MS_MIMEMSGS, IEM_MS_MSGBODYS, and IEM_MS_MSGPARTS, which hold the parsed MIME structure of each message. It accesses IEM_AGENTS and IEM_MSTEMAIL_ACCOUNTS for agent and account configuration, IEM_CLASSIFICATIONS, IEM_EMAIL_CLASSIFICATIONS, and IEM_ROUTE_CLASSIFICATIONS for classification and routing decisions, and IEM_REROUTE_HISTS for reroute audit history. Workload and productivity data is drawn from IEM_COMP_RT_STATS and routing processing from IEM_RT_PROC_EMAILS. Knowledge-base lookups reference IEM_KB_RESULTS, and archival uses IEM_ARCH_MSGS and IEM_ARCH_MSGDTLS_PVT. The package also references IEM_ROUTE_RULES and JTF_IH_MEDIA_ITEMS / JTF_IH_PUB for Interaction Center media integration, and JTF_RS_GROUP_MEMBERS for group assignment.

Usage Notes

IEM_MAILITEM_PUB is typically invoked from the Email Center agent forms and from concurrent programs that process the mail queue. Custom code and extensions should call the public procedures rather than manipulating the underlying IEM_MS_* tables directly, since the package encapsulates message-store integrity and routing history. It is referenced by five other packages, indicating it serves as a shared service layer. Because it depends on FND_MSG_PUB and FND_API, callers should initialize the FND message stack and check the returned API status before committing, particularly after DISPOSEMAILITEM, RESOLVEDMESSAGE, and UPDATEMAILITEM operations.