Search Results mwa_utl_sm_pkg

Overview

The APPS.MWA_UTL_SM_PKG package is a utility package within the Oracle E-Business Suite Applications schema. Based on its object name and the procedures it exposes, the package belongs to the family of MWA (Mobile Web Applications) utility routines that support the Oracle EBS Mobile Supply Chain Applications framework. Its principal role is to provide a lightweight messaging and session-management utility layer that other MWA components can call to retrieve user context and dispatch outbound messages. The package is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, indicating it remains a supported and compiled object across both release streams.

The package is classified under the API classification "OTHER," meaning Oracle does not publish it as a formal, supported public API. It is therefore best understood as an internal helper package rather than a documented integration point for customer extensions. Its only formal dependency is on the SYS.STANDARD package, and it references the UTL_HTTP package via an APPS synonym, which indicates that its messaging functionality is implemented over HTTP rather than through the database's native mail or advanced queuing facilities.

Key Procedures and Functions

ETRM documents three procedures or functions within APPS.MWA_UTL_SM_PKG:

• GET_USERS — Retrieves user information relevant to the package's messaging context. In the MWA utility context this is typically used to resolve the set of recipients, or the current user identity, before a message is dispatched.
• SEND_MESSAGE — Performs the core outbound messaging operation. Given the dependency on UTL_HTTP, this routine is expected to construct and transmit an HTTP request carrying the message payload to a configured endpoint or service.
• TEST — A diagnostic or self-test entry point, allowing the package's messaging behavior to be exercised independently of normal application flow.

Parameter lists for these routines are not published in the ETRM metadata and should not be assumed. Any direct invocation must be confirmed by inspecting the package specification in the target environment.

Tables Accessed

The ETRM metadata lists only UTL_HTTP among the objects referenced by this package, accessed through an APPS synonym. No application tables are documented as being read or written. UTL_HTTP is the Oracle-supplied PL/SQL package that enables database sessions to make HTTP requests, which confirms that SEND_MESSAGE performs its delivery over the HTTP protocol rather than through database mail, workflow notifications, or Advanced Queuing. Because no EBS base tables are documented, the package should be regarded as stateless with respect to the application data model; any persistence of messages or recipient definitions occurs outside the objects recorded in the metadata.

Usage Notes

APPS.MWA_UTL_SM_PKG is referenced by zero other packages according to the documented dependency graph, which suggests it is called from contexts that fall outside the standard packaged API hierarchy — most likely from Mobile Supply Chain Applications forms, servlet-based mobile pages, or custom code that has been layered on top of the MWA framework. Typical invocation scenarios include:

• Mobile device transactions where a short notification or alert must be pushed to a user or external service upon completion of a scan or transaction.
• Custom concurrent programs or database jobs that require a lightweight HTTP-based notification without invoking the full Oracle Workflow notification stack.
• Diagnostic execution of the TEST procedure during implementation or troubleshooting to verify connectivity and message formatting.

Because the package is classified as OTHER and is not a published Oracle API, customers should treat it as subject to change between releases and should not build supported extensions directly against its signatures. Where the functionality is required for a custom solution, the recommended approach is to wrap the call in customer-owned code and validate behavior during any upgrade from 12.1.1 to 12.2.2. As with all UTL_HTTP usage, outbound network access must be permitted by the database's access control list configuration, and any proxy or firewall settings must be in place for SEND_MESSAGE to function.