Search Results wf_parameter_t




Overview
Explore in AI Chat

Overview

M4U_UCC_ADAPTER is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that serves as an integration adapter between Oracle Workflow and the Oracle Advanced Queuing (AQ) infrastructure. Its principal business function is to transform an outbound XML/CLOB payload into an AQ JMS text message and enqueue it onto a JMS queue, thereby enabling asynchronous, message-oriented communication with external trading partners and hubs. The package is part of the M4U (a legacy UCCnet/collaboration module) code family and is closely associated with the ECX event framework used by Oracle's EDI/e-commerce gateway architecture. The header comment ($Header: m4uinaqb.pls 120.0 2005/05/24 ...) confirms the adapter has been stable since the 11i era and is carried forward unchanged into 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents a single callable routine in this package body.

  • PUSHTOAQ — A function that accepts a CLOB payload and enqueues it onto the AQ queue named WF_JMS_IN in the APPLSYS schema as a SYS.AQ$_JMS_TEXT_MESSAGE. Internally it generates a message identifier via SYS_GUID and a sequence value from M4U_WLQID_S, then constructs a Workflow parameter list to carry ECX event attributes (for example ECX_PARAMETER1, ECX_PARAMETER2, ECX_TRANSACTION_TYPE, ECX_TRANSACTION_SUBTYPE, ECX_PARTY_SITE_ID, ECX_DOCUMENT_ID). These attributes are attached to the ECX_EVENT_MESSAGE item type and are subsequently consumed by the queue handler to set the AQ correlation identifier. The function also emits diagnostic messages through cln_debug_pub at configurable debug levels. Its stated purpose in the source is to set the PROTOCOL_TYPE event attribute so that the queue handler can populate the AQ correlation ID.

No other procedures or functions are documented in the ETRM record for this package body.

Tables Accessed

  • M4U_WLQID_S — A sequence (accessed via the APPS synonym) supplying the next numeric message identifier (l_nextval) used to uniquely tag each enqueued message.
  • WF_EVENT_T — The Workflow event type object used to model the business event carried in the payload.
  • WF_PARAMETER_LIST_T — The Workflow parameter list collection type that packages the ECX event attributes into a form the event system can process.
  • WF_PARAMETER_T — The individual parameter type used to construct each name/value pair within the parameter list; this is the object the user's search term "wf_parameter_t" refers to.
  • DBMS_AQ — The Oracle AQ PL/SQL API package invoked to perform the actual enqueue operation.
  • DUAL — The standard single-row dummy table used to select SYS_GUID().

Usage Notes

The package is typically invoked from Oracle Workflow function activities or from custom PL/SQL code executing within the ECX/EDI event flow, where an outbound document must be handed to the JMS queue for downstream delivery. Because it depends on WF_PARAMETER_T and related Workflow collection types, the caller must have EXECUTE privileges on the package and must supply the fully constructed CLOB payload. Administrators should note the hard-coded queue schema name ('APPLSYS') referenced in the source as a documented code workaround associated with a GSCC error, and that the queue name defaults to WF_JMS_IN. Debug output is governed by the l_debug_level variable routed through cln_debug_pub, so tracing can be enabled without code changes. The package is not referenced by other PL/SQL packages according to ETRM, meaning it is a leaf-level adapter intended to be called directly by workflow or external integration logic rather than reused internally.