Search Results xnp_msg_elements_s

Overview

XNP_MSG_BUILDER is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It forms part of the Oracle XML Publisher (formerly Oracle E-Business Suite Publisher) and ETRM messaging infrastructure, providing the server-side logic used to construct, compile, and clone message definitions that drive outbound messaging and XML schema generation. The package is a member of the XNP family of objects, which collectively manage message types, message structures, message elements, and the schema artifacts derived from them.

The package is classified as OTHER within the ETRM documentation, meaning it is not exposed as a formal public API but is instead an internal utility package invoked by other ETRM components. Its dependency list confirms this role: it references XNP_MSG_SCHEMA, XNP_MSG_TYPES_PKG, XNP_MESSAGE, XNP_EVENT, XNP_ERRORS, and XDP_UTILITIES, but is not itself referenced by any other database object. This indicates a terminal utility package used directly by forms, concurrent programs, or administrative scripts rather than by downstream PL/SQL callers.

The user search term "xnp_msg_structures_s" corresponds to one of the base tables this package manipulates — the translated (TL) or synonym view of XNP_MSG_STRUCTURES, which stores header-level definitions of message structures. XNP_MSG_BUILDER reads and writes these structures as part of its compile and copy operations.

Key Procedures and Functions

The ETRM metadata documents two procedures or functions within XNP_MSG_BUILDER:

• COMPILE — Compiles a message definition into its runtime or schema representation. This procedure resolves the message structure and its constituent elements, validates them against the message type, and generates the derived schema metadata stored in the XNP_MSG_SCHEMA objects. It relies on AD_DDL and PLITBLM to create or rebuild underlying database objects, and on DBMS_STANDARD and FND_MESSAGE for error signalling.
• COPYMESG — Copies an existing message definition, including its structure and element associations, to a new message. This supports versioning and template-based message creation, allowing an administrator to duplicate a working message configuration and modify it without rebuilding from scratch.

Both procedures depend on XDP_TYPES, XDP_UTILITIES, FND_GLOBAL, FND_INSTALLATION, and FND_PROFILE, indicating that they observe the current application context (organization, user, language) and profile options when performing their work.

Tables Accessed

The package reads and writes the following documented tables and views through APPS synonyms:

• XNP_MSG_STRUCTURES / XNP_MSG_STRUCTURES_S — Header definitions of message structures. The package reads existing structures during COMPILE and inserts or duplicates rows during COPYMESG. The _S suffix denotes the translated or denormalized synonym typically referenced by the messaging engine.
• XNP_MSG_ELEMENTS / XNP_MSG_ELEMENTS_S — The element-level detail belonging to each structure; COMPILE resolves these into schema fields, and COPYMESG duplicates them for the new message.
• XNP_MSG_TYPES_B / XNP_MSG_TYPES_VL — The message type definition and its translated view, used to validate that a structure belongs to a recognized type and to resolve display names during compilation.
• AD_DDL — Used to obtain the DDL syntax or statement builders required when COMPILE materialises schema objects.
• PLITBLM — Supplies PL/SQL table and bulk-collection utilities used internally by the package.
• USER_ERRORS — Queried after compilation to detect and surface PL/SQL compilation errors back to the caller.

Usage Notes

XNP_MSG_BUILDER is an internal ETRM utility and is not part of a supported public API. It is typically invoked from the Oracle E-Business Suite administrative forms used to define and maintain message types and structures, from concurrent programs that regenerate message schemas, and from upgrade or patch scripts that copy or recompile message definitions during an ETRM patch application. Custom code should not call XNP_MSG_BUILDER directly; the supported entry points for messaging configuration remain the XNP_MSG_TYPES_PKG and XNP_MESSAGE APIs. Because the package depends on FND_GLOBAL and FND_PROFILE, any invocation must occur within an initialized EBS session. When troubleshooting compilation failures, administrators can query USER_ERRORS for the APPS schema after running COMPILE, as this package records errors through that standard dictionary view.