Search Results m4u_dmd_payloadid_s

Overview

The APPS.M4U_DMD_REQUESTS package body is a core component of the Oracle E-Business Suite 12.1.1 / 12.2.2 "M4U" demand management module. The "M4U" prefix and its dependencies on WF_EVENT, WF_PARAMETER_LIST_T, and FND_API indicate that this package implements a subscription and messaging framework built on top of the Oracle Workflow Business Event System. It coordinates the creation, persistence, and lifecycle management of outbound and inbound "requests," each of which carries one or more "payloads" and "documents" representing business messages exchanged between EBS and downstream or upstream systems.

Its central responsibility is to generate and manage the request records that associate an incoming or outgoing demand trigger with the message content (payload) and structured document (an XML or other formatted body) needed for delivery. It also manages retry logic for failed deliveries, providing a controlled mechanism to re-drive requests without operator intervention at the application layer.

Key Procedures and Functions

Six documented program units make up the package interface:

• CREATE_REQUEST — Establishes a new demand request record in M4U_DMD_REQUESTS, initializing the request-level status and header information that downstream payload and document builders rely upon.
• CREATE_PAYLOAD — Creates payload content and assigns the payload identifier from the M4U_DMD_PAYLOADID_S sequence, associating the payload with its parent request.
• CREATE_DOCUMENT — Persists a generated document body, drawing its identifier from M4U_DMD_DOCID_S and attaching it to the request structure.
• RETRY_REQUEST — Resets and re-initiates processing of a request that previously failed, typically by clearing error state and re-raising the associated workflow event.
• UPDATE_REQUEST — Modifies the state or attributes of an existing request, including status transitions captured in M4U_DMD_MESSAGES.
• UPDATE_DOCUMENT — Amends an existing document body, allowing regeneration or correction of message content after initial creation.

Tables Accessed

The package operates against the following objects via APPS synonyms:

• M4U_DMD_REQUESTS — The central request header table, read and written by CREATE/UPDATE/RETRY_REQUEST. Its recursive self-dependency confirms internal read-back of prior request state.
• M4U_DMD_PAYLOADS and M4U_DMD_PAYLOADID_S — Store message payloads and supply unique identifiers through the sequence.
• M4U_DMD_DOCUMENTS and M4U_DMD_DOCID_S — Hold document bodies with their sequence-generated primary keys.
• M4U_DMD_MESSAGES and M4U_DMD_MSGID_S — Capture status and error messages linked to a request, supporting retry diagnostics.
• M4U_DMD_SUBSCRIPTIONS — Defines the routing/subscription rules that determine how a request is dispatched.
• WF_PARAMETER_LIST_T and WF_EVENT — Workflow Business Event structures used to raise and parameterize events for delivery.
• DUAL — Used for sequence/function evaluation within PL/SQL.

Usage Notes

M4U_DMD_REQUESTS is not referenced by any other database object, so it is an entry-point package rather than a low-level utility. It is typically invoked from a Business Event subscription, from concurrent programs that batch-generate demand messages, or from custom PL/SQL that triggers a demand flow. Retry processing via RETRY_REQUEST is usually scheduled or invoked by an administrator-driven concurrent request. Because the package relies on FND_API and FND_GLOBAL, it inherits standard EBS APIs for error handling and session context, ensuring compliant behavior across 12.1.1 and 12.2.2 environments.