Search Results xnp_mte_insert_element

Overview

XNP_MESSAGE is the core messaging infrastructure package in the Oracle EBS Advanced Planning and Scheduling / Supply Chain module set, owned by the APPS schema and classified as OTHER. It provides the PL/SQL foundation for an asynchronous, queue-based message transport layer used throughout the XNP family of products to move structured messages between concurrent processes, workflow agents, and external subscribers. The package defines the canonical message header structure through the public record type MSG_HEADER_REC_TYPE, which encapsulates identifying and routing attributes such as message_id, message_code, reference_id, opp_reference_id, direction_indr, order_id, wi_instance_id, and fa_instance_id, along with audit fields including creation_date, sender_name, recipient_name, and version. Callers retrieve this populated record via the overloaded GET procedure, making the record type the primary contract between the message store and consuming code.

The package also encapsulates constants governing dequeue behaviour, notably POP_TIMEOUT (initialised to one second) and the visibility constants C_ON_COMMIT and C_IMMEDIATE, together with CURRENT_VERSION. Package-level constants G_PKG_PREFIX ('XNP_') and G_PKG_SUFFIX ('_U') support the generation of user-defined send and publish packages, and the STOP_PROCESSING exception provides a controlled termination signal.

Key Procedures and Functions

The documented public interface comprises GET_SUBSCRIBER_LIST, which returns a comma-separated subscriber list for a given message code; GET, in its original form, which retrieves message text for a supplied message ID, and in an overloaded form that additionally returns the populated MSG_HEADER_REC_TYPE header (added as a performance fix in 2001); GET_HEADER, which returns only the header record; and PROCESS and DEFAULT_PROCESS, which implement the standard message-handling lifecycle. VALIDATE performs message validation, while GET_SEQUENCE supplies sequence values for message identifiers. PUSH, POP, PUSH_WF, and UPDATE_STATUS manage enqueueing, dequeueing, workflow-integrated publication, and status transitions respectively; GET_STATUS returns the current status of a message. NOTIFY_FMC raises notification to the forecasting/message consumer, XNP_MTE_INSERT_ELEMENT inserts message element rows, and FIX and DELETE provide corrective and removal operations.

Tables Accessed

The package operates across the XNP message schema, reading and writing XNP_MSGS and its synonym/sequence-supporting counterpart XNP_MSGS_S for core message records, XNP_MSG_ACKS for acknowledgements, XNP_MSG_ELEMENTS and XNP_MSG_ELEMENTS_S for payload elements, XNP_MSG_STRUCTURES and XNP_MSG_STRUCTURES_S for structural definitions, and XNP_MSG_TYPES_B for message type classification. Subscriber and callback routing is resolved through XNP_EVENT_SUBSCRIBERS and XNP_CALLBACK_EVENTS. Timer-driven publication uses XNP_TIMER_PUBLISHERS and XNP_TIMER_REGISTRY, and forecast-related integration references XDP_FES. Oracle Advanced Queuing is accessed through the DBMS_AQ synonym, and workflow events through WF_EVENT_T.

Usage Notes

XNP_MESSAGE is not typically invoked directly by end users; it is called programmatically by the 87 dependent packages that make up the XNP messaging stack, by concurrent programs responsible for queue processing, and by workflow event subscribers. Customisations should follow the documented pattern of user-defined packages generated using the G_PKG_PREFIX and G_PKG_SUFFIX constants rather than modifying the base package. Developers writing custom subscribers or publishers should declare variables of type MSG_HEADER_REC_TYPE and populate them exclusively through the documented GET or GET_HEADER calls to preserve compatibility with the standard queue-processing contract.