SAP SWF_XI_MSG_RAISE_EVENT_BULK Function Module for









SWF_XI_MSG_RAISE_EVENT_BULK is a standard swf xi msg raise event bulk SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for swf xi msg raise event bulk FM, simply by entering the name SWF_XI_MSG_RAISE_EVENT_BULK into the relevant SAP transaction such as SE37 or SE38.

Function Group: SWF_XI_RUN
Program Name: SAPLSWF_XI_RUN
Main Program: SAPLSWF_XI_RUN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SWF_XI_MSG_RAISE_EVENT_BULK pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'SWF_XI_MSG_RAISE_EVENT_BULK'"
  EXPORTING
   IM_OBJECT =  "
*  IM_HASHBASE =  "
*  IM_QOS =  "
*  IM_MSG_SIZE =  "
*  IM_MAX_MSG =  "
*  IM_PP_DATA =  "
*  IM_USERINFO_GUID =  "
*  IM_PP_STATUS =  "
   IM_EVENT =  "
   IM_TASK =  "
*  IM_QUEUE =  "
*  IM_CONF_VERS =  "
*  IM_VERSION =  "
*  IM_TIMESTAMP =  "
*  IM_CRL_NAME =  "
*  IM_HASH =  "

EXCEPTIONS
   INVALID_TID = 1    TID_NOT_FOUND = 2    INTERNAL_ERROR = 3
.



IMPORTING Parameters details for SWF_XI_MSG_RAISE_EVENT_BULK

IM_OBJECT -

Data type: SIBFLPOR
Optional: No
Call by Reference: No ( called with pass by value option)

IM_HASHBASE -

Data type: XSTRING
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_QOS -

Data type: SXMSQOS
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_MSG_SIZE -

Data type: INT4
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_MAX_MSG -

Data type: SWFXIBULKMAXMSG
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_PP_DATA -

Data type: SWFXIPPDATA
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_USERINFO_GUID -

Data type: USERINFO_GUID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_PP_STATUS -

Data type: SWFXIINBPPSTATUS
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_EVENT -

Data type: SIBFEVENT
Optional: No
Call by Reference: No ( called with pass by value option)

IM_TASK -

Data type: SWW_TASK
Optional: No
Call by Reference: No ( called with pass by value option)

IM_QUEUE -

Data type: TRFCQNAM
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_CONF_VERS -

Data type: SWFXIINBCONFVERSION
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_VERSION -

Data type: SWFXIINBVERSION
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_TIMESTAMP -

Data type: TIMESTAMPL
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_CRL_NAME -

Data type: SWFDCRLNAM
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_HASH -

Data type: HASH160
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INVALID_TID -

Data type:
Optional: No
Call by Reference: Yes

TID_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SWF_XI_MSG_RAISE_EVENT_BULK Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lv_im_object  TYPE SIBFLPOR, "   
lv_invalid_tid  TYPE SIBFLPOR, "   
lv_im_hashbase  TYPE XSTRING, "   
lv_im_qos  TYPE SXMSQOS, "   
lv_im_msg_size  TYPE INT4, "   
lv_im_max_msg  TYPE SWFXIBULKMAXMSG, "   
lv_im_pp_data  TYPE SWFXIPPDATA, "   
lv_im_userinfo_guid  TYPE USERINFO_GUID, "   
lv_im_pp_status  TYPE SWFXIINBPPSTATUS, "   
lv_im_event  TYPE SIBFEVENT, "   
lv_tid_not_found  TYPE SIBFEVENT, "   
lv_im_task  TYPE SWW_TASK, "   
lv_internal_error  TYPE SWW_TASK, "   
lv_im_queue  TYPE TRFCQNAM, "   
lv_im_conf_vers  TYPE SWFXIINBCONFVERSION, "   
lv_im_version  TYPE SWFXIINBVERSION, "   
lv_im_timestamp  TYPE TIMESTAMPL, "   
lv_im_crl_name  TYPE SWFDCRLNAM, "   
lv_im_hash  TYPE HASH160. "   

  CALL FUNCTION 'SWF_XI_MSG_RAISE_EVENT_BULK'  "
    EXPORTING
         IM_OBJECT = lv_im_object
         IM_HASHBASE = lv_im_hashbase
         IM_QOS = lv_im_qos
         IM_MSG_SIZE = lv_im_msg_size
         IM_MAX_MSG = lv_im_max_msg
         IM_PP_DATA = lv_im_pp_data
         IM_USERINFO_GUID = lv_im_userinfo_guid
         IM_PP_STATUS = lv_im_pp_status
         IM_EVENT = lv_im_event
         IM_TASK = lv_im_task
         IM_QUEUE = lv_im_queue
         IM_CONF_VERS = lv_im_conf_vers
         IM_VERSION = lv_im_version
         IM_TIMESTAMP = lv_im_timestamp
         IM_CRL_NAME = lv_im_crl_name
         IM_HASH = lv_im_hash
    EXCEPTIONS
        INVALID_TID = 1
        TID_NOT_FOUND = 2
        INTERNAL_ERROR = 3
. " SWF_XI_MSG_RAISE_EVENT_BULK




ABAP code using 7.40 inline data declarations to call FM SWF_XI_MSG_RAISE_EVENT_BULK

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!