Search Results xnp_msgs_s

Overview

XNP_MESSAGE is the core message-handling package body within the Oracle E-Business Suite XML Network Protocol (XNP) infrastructure. XNP provides the messaging foundation used by Oracle's e-commerce gateway, EDI/XML transaction processing, and the broader E-Business Suite integration layer. The APPS.XNP_MESSAGE package body encapsulates the runtime logic that constructs, validates, queues, dequeues, and tracks inbound and outbound messages exchanged between Oracle EBS and external trading partners. Its status as VALID in the APPS schema confirms that it is a compiled, deployed component in both 12.1.1 and 12.2.2 releases. The package orchestrates workflow events, Advanced Queuing (AQ) enqueue/dequeue operations, XML payload assembly, and acknowledgement handling, effectively acting as the central dispatcher for XNP message lifecycle management.

Key Procedures and Functions

The package exposes 22 documented procedures and functions, each addressing a distinct phase of the message lifecycle:

• GET_SUBSCRIBER_LIST — Resolves the set of subscribers designated to receive a given message, based on message type and routing configuration.
• GET and GET_HEADER — Retrieve message content and message header metadata respectively, supporting both full payload and header-only access patterns.
• NOTIFY_FMC — Notifies the Financial Management Center or designated monitoring component of message state transitions.
• PROCESS and DEFAULT_PROCESS — Execute the processing logic associated with a message, with DEFAULT_PROCESS supplying fallback handling when no custom processor is defined.
• VALIDATE — Performs structural and content validation of messages against expected message-type definitions.
• GET_SEQUENCE — Obtains the next sequence value used to key and order message records.
• PUSH and POP — Enqueue and dequeue operations against the underlying queue infrastructure.
• UPDATE_STATUS and GET_STATUS — Maintain and query the processing status of a message through its lifecycle.
• XNP_MTE_INSERT_ELEMENT — Inserts message elements into the element structure that composes the message body.
• FIX — Applies corrective logic to messages requiring repair or normalization.
• DELETE — Removes message records and associated data.
• PUSH_WF — Raises a Workflow event to trigger downstream workflow-driven processing.

Tables Accessed

XNP_MESSAGE reads and writes a well-defined set of XNP schema objects (accessed via APPS synonyms). The transactional message tables XNP_MSGS and XNP_MSGS_S hold message instances and their sequence data. XNP_MSG_ELEMENTS and XNP_MSG_ELEMENTS_S store the granular XML/data elements composing each message. XNP_MSG_STRUCTURES and XNP_MSG_STRUCTURES_S define the structural templates, while XNP_MSG_TYPES_B and the XNP_MSG_TYPES_PKG package provide message-type definitions invoked by the type package. Acknowledgement tracking uses XNP_MSG_ACKS. Routing and subscriber resolution draw on XNP_EVENT_SUBSCRIBERS, XNP_CALLBACK_EVENTS, XNP_TIMER_PUBLISHERS, and XNP_TIMER_REGISTRY. The package also leverages DBMS_AQ, DBMS_LOB, and AQ$_AGENT for queue and large-object operations, plus standard Oracle facilities such as FND_FILE, FND_GLOBAL, FND_MESSAGE, FND_PROFILE, WF_CORE, and WF_ENGINE.

Usage Notes

XNP_MESSAGE is principally invoked by internal XNP infrastructure rather than directly by end users. It is referenced by 87 other database objects, confirming its role as a shared utility underpinning the XNP runtime. Typical invocation paths include concurrent programs that process inbound and outbound messages, workflow background processes triggered through PUSH_WF and WF_ENGINE calls, and callback/event handlers registered via XNP_CALLBACK_EVENTS and XNP_EVENT_SUBSCRIBERS. Custom integrations extending Oracle's e-commerce gateway messaging commonly call GET, GET_HEADER, PUSH, POP, and the status routines to integrate messages with external systems. Because it depends on FND_MESSAGE and FND_GLOBAL, diagnostic output and session context follow standard EBS conventions. Developers extending XNP should treat XNP_MESSAGE as a foundational dependency and avoid direct modification, relying instead on the documented procedures to preserve integrity across the message lifecycle.