Search Results m4u_dmd_requests




Overview
Explore in AI Chat

Overview

The APPS.M4U_DMD_REQUESTS package is a PL/SQL API within the Oracle E-Business Suite communications and demand-signal infrastructure, delivered under the M4U (Message/Data) namespace and classified as an OTHER API. Its primary business function is to manage the lifecycle of inbound and outbound demand messages and their associated XML payload documents. The package encapsulates the creation and maintenance of request records, payload records, and document records that flow through the ETRM messaging tables, allowing calling applications to persist, register, and later update or retry message processing without directly manipulating the underlying schema objects.

The package is declared with AUTHID CURRENT_USER, meaning procedures execute with the privileges of the invoking schema rather than the definer. The $Header comment indicates a last revision of M4UDREQS.pls version 120.1 dated 2007/09/12, confirming its long-standing role across the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The documented API exposes six procedures. The user search term create_payload corresponds directly to the CREATE_PAYLOAD procedure.

  • CREATE_REQUEST — Registers a new demand request record. It accepts message type, direction, and status parameters, along with reference and original message identifiers, a timestamp, an optional payload identifier, and a set of GLN (Global Location Number) identifiers for sender, receiver, representative party, and user. It returns an outbound message identifier plus standard return status and return message outputs.
  • CREATE_PAYLOAD — Persists an XML document held in a CLOB into the payload store. It accepts the XML content (p_xml IN CLOB), a type and a direction, and returns the generated payload identifier together with return status and return message outputs. This is the entry point referenced by the search term create_payload and is the mechanism by which raw XML messages are committed for downstream document creation.
  • CREATE_DOCUMENT — Creates a document record tied to a message. It captures document type, action, document status, and functional status, and supports an extensive set of optional attributes including timestamp, processing message, referenced and original document identifiers, top-level GTIN, information provider GLN, data recipient GLN, target market country and division, ten generic parameters (five p_param and five p_lparam), and the associated payload identifier, direction, and type. It returns the new document identifier.
  • RETRY_REQUEST — Re-processes a request that previously failed or was deferred.
  • UPDATE_REQUEST — Modifies attributes of an existing demand request.
  • UPDATE_DOCUMENT — Modifies attributes of an existing document record.

Tables Accessed

The package operates against the following objects, accessed through APPS synonyms:

Usage Notes

The package is typically invoked from ETRM processing flows, concurrent programs, or custom integration code that ingests or emits demand signals. A common pattern is to call CREATE_PAYLOAD to persist the raw XML, then CREATE_DOCUMENT to associate the payload with a typed document, and finally CREATE_REQUEST to register the enclosing message. Callers should check x_ret_sts and x_ret_msg after each call, as the procedures communicate success or failure through these out parameters rather than exceptions. The package is referenced by one other package, indicating it forms a low-level dependency within the M4U messaging layer rather than a top-level entry point.