Results for “iem_arch_msgdtls_pvt”

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

Overview

IEM_ARCH_MSGDTLS_PVT is a private PL/SQL package in the Oracle E-Business Suite APPS schema that supports the archiving of inbound interaction message details within the iMarketing and interaction management infrastructure. It is classified as a PVT (private) API, meaning it is intended for internal consumption by other EBS components rather than as a public integration interface. The package is declared with AUTHID CURRENT_USER, so all database object references resolve under the privileges of the calling session rather than the package owner.

The package's core responsibility is persisting a fully formed inbound message record — including routing, classification, addressing, and contact attributes — into the IEM_ARCH_MSGDTLS archive table, while generating a surrogate message identifier used by downstream processing. The header comment ($Header: iemvarms.pls, dated 2005) and its inclusion in the 12.1.1 and 12.2.2 code lines confirm it has been a stable element of the interaction message architecture across both releases.

Key Procedures and Functions

The package exposes one documented procedure:

• CREATE_ITEM — The single public entry point of the package. It accepts a broad set of inbound parameters describing a message: identifiers (message, inbound message, email account, agent, group, media item, customer, contact, relationship, classification), addressing fields (from, reply-to, to, cc, bcc), message metadata (subject, body text, size, mail type, mail processing status, sent and received dates, top intent), and fifteen generic ATTRIBUTE columns for site-specific extensibility. Standard EBS API conventions apply: p_api_version_number for version control, p_init_msg_list to govern message-stack initialization, and p_commit to control transaction control. The procedure returns x_message_id (the created record identifier) along with the standard x_return_status, x_msg_count, and x_msg_data outputs for error handling. All parameters are passed by value with NOCOPY only on the OUT parameters.

Tables Accessed

Three tables are documented as referenced through APPS synonyms:

• IEM_ARCH_MSGDTLS — The primary archive table into which CREATE_ITEM inserts the assembled message record, including the attribute columns and classification data.
• IEM_MS_BASE_HEADERS_S1 — The base header sequence used to generate a unique header/message identifier, referenced to obtain the surrogate key returned as x_message_id.
• DUAL — Used for lightweight PL/SQL constructs such as sequence selection and default evaluations.

The package is itself referenced by two other packages, indicating it operates as a lower-level building block within the interaction message archiving stack.

Usage Notes

Because IEM_ARCH_MSGDTLS_PVT is a private package, it is not exposed to end users and should not be called directly from customization or extension code unless no public alternative exists. Typical invocation sources are higher-level interaction management packages and concurrent programs that process inbound email or other media into the archiving tables. It may also be called indirectly by inbound email agent workflows that parse and route messages before archive insertion.

Developers integrating with this area should treat the ATTRIBUTE columns and the message identifiers as the stable extension surface, and should respect the API version and commit parameters to avoid disrupting the caller's transaction scope. All access should occur through the APPS synonym and the calling user's privileges, consistent with the AUTHID CURRENT_USER declaration.