Search Results iem_rerouting_hists_pvt




Overview
Explore in AI Chat

Overview

IEM_REROUTING_HISTS_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM (E-Business Suite Technical Reference Manual) as an API of type PVT. In the context of Oracle EBS 12.1.1 and 12.2.2, this package forms part of the Intelligent Email (IEM) infrastructure, which governs inbound and outbound email processing and the routing of email-based interactions to the appropriate agents, queues, or processing logic. The "rerouting history" concept relates to the recording of events where an email or interaction is reassigned from one routing target to another, preserving an auditable trail of those decisions.

The package is designated "PVT," indicating that it is intended for internal, private use rather than as a public integration API. Its documented status is VALID, and it exposes limited, low-level operations that support the higher-level public routing interface. It therefore serves as the persistence layer for rerouting history records, abstracting the insert and delete operations performed against the underlying history tables.

Key Procedures and Functions

The ETRM metadata documents two procedures within IEM_REROUTING_HISTS_PVT:

  • CREATE_ITEM — Responsible for creating a new rerouting history record. This procedure inserts a row representing a rerouting event, capturing the details of the item being rerouted and the resulting history entry. It is the means by which the rerouting lifecycle is persisted.
  • DELETE_ITEM — Responsible for removing an existing rerouting history record. This procedure deletes the corresponding row, supporting cleanup or reversal of a previously recorded rerouting event.

No parameter lists are documented for these procedures in the ETRM metadata; consumers should not assume a signature and should inspect the package specification in the target environment before invoking it directly. As a private package, its procedures are not intended for external use.

Tables Accessed

The package references the following tables via APPS synonyms, as documented:

  • IEM_REROUTE_HISTS — The primary history table holding rerouting event records. This is the table into which CREATE_ITEM inserts and from which DELETE_ITEM deletes.
  • IEM_REROUTE_HISTS_S1 — A secondary table, for example a supplementary or sequence-related structure associated with the history records, also manipulated by the package.
  • DUAL — The standard Oracle single-row utility table, typically used for validation, sequence retrieval, or context checks within the procedural logic.

These tables constitute the persistence surface of the rerouting history feature, ensuring that every rerouting action is captured and can be audited or reversed.

Usage Notes

IEM_REROUTING_HISTS_PVT is not intended for direct invocation by end users or custom code. Its documented dependency graph shows that it is referenced by APPS.IEM_REROUTE_PUB, the public package that exposes rerouting functionality, which in turn calls this private package to persist history. It also depends on SYS.STANDARD.

In practice, the package is invoked indirectly through the email rerouting workflow: when an email or interaction is rerouted, IEM_REROUTE_PUB delegates the history insert to CREATE_ITEM, and when a rerouting record must be removed, DELETE_ITEM is called. Customizations should call IEM_REROUTE_PUB rather than this private package to remain upgrade-safe across 12.1.1 and 12.2.2. Direct calls to a PVT package risk breakage during patching, as signatures are undocumented and subject to change.