SAP SWW_ERRE_EXECUTE_CALLBACK Function Module for
SWW_ERRE_EXECUTE_CALLBACK is a standard sww erre execute callback 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 sww erre execute callback FM, simply by entering the name SWW_ERRE_EXECUTE_CALLBACK into the relevant SAP transaction such as SE37 or SE38.
Function Group: SWW_ERRE
Program Name: SAPLSWW_ERRE
Main Program: SAPLSWW_ERRE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SWW_ERRE_EXECUTE_CALLBACK 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 'SWW_ERRE_EXECUTE_CALLBACK'".
EXPORTING
IM_CALLBACK_ENTRY = "
* IM_RFC_RESOURCES = "
IM_LOG_METHOD = "
IM_SERVICE = "
* IM_USER = SY-UNAME "
* IM_LANGUAGE = SY-LANGU "
* IM_BACKGROUND = 'X' "
* IM_DEBUG_MODE = "
* IM_TRACE_LEVEL = "
* IM_SET_ENQUEUE = 'X' "
EXCEPTIONS
CX_SWF_RUN_WIM_ENQ_FAILED = 1 CX_SWF_RUN_WIM = 2
IMPORTING Parameters details for SWW_ERRE_EXECUTE_CALLBACK
IM_CALLBACK_ENTRY -
Data type: IF_SWF_RUN_CALLBACK_ENTRYOptional: No
Call by Reference: Yes
IM_RFC_RESOURCES -
Data type: CL_SWF_UTL_CHECK_RFC_RESOURCESOptional: Yes
Call by Reference: Yes
IM_LOG_METHOD -
Data type: STRINGOptional: No
Call by Reference: Yes
IM_SERVICE -
Data type: SWW_WIMSRVOptional: No
Call by Reference: Yes
IM_USER -
Data type: SYUNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: Yes
IM_LANGUAGE -
Data type: SYLANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
IM_BACKGROUND -
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: Yes
IM_DEBUG_MODE -
Data type: SWFDBGMODOptional: Yes
Call by Reference: Yes
IM_TRACE_LEVEL -
Data type: SWFTRCLEVOptional: Yes
Call by Reference: Yes
IM_SET_ENQUEUE -
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
CX_SWF_RUN_WIM_ENQ_FAILED -
Data type:Optional: No
Call by Reference: Yes
CX_SWF_RUN_WIM -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SWW_ERRE_EXECUTE_CALLBACK 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_callback_entry | TYPE IF_SWF_RUN_CALLBACK_ENTRY, " | |||
| lv_cx_swf_run_wim_enq_failed | TYPE IF_SWF_RUN_CALLBACK_ENTRY, " | |||
| lv_im_rfc_resources | TYPE CL_SWF_UTL_CHECK_RFC_RESOURCES, " | |||
| lv_im_log_method | TYPE STRING, " | |||
| lv_cx_swf_run_wim | TYPE STRING, " | |||
| lv_im_service | TYPE SWW_WIMSRV, " | |||
| lv_im_user | TYPE SYUNAME, " SY-UNAME | |||
| lv_im_language | TYPE SYLANGU, " SY-LANGU | |||
| lv_im_background | TYPE XFELD, " 'X' | |||
| lv_im_debug_mode | TYPE SWFDBGMOD, " | |||
| lv_im_trace_level | TYPE SWFTRCLEV, " | |||
| lv_im_set_enqueue | TYPE XFELD. " 'X' |
|   CALL FUNCTION 'SWW_ERRE_EXECUTE_CALLBACK' " |
| EXPORTING | ||
| IM_CALLBACK_ENTRY | = lv_im_callback_entry | |
| IM_RFC_RESOURCES | = lv_im_rfc_resources | |
| IM_LOG_METHOD | = lv_im_log_method | |
| IM_SERVICE | = lv_im_service | |
| IM_USER | = lv_im_user | |
| IM_LANGUAGE | = lv_im_language | |
| IM_BACKGROUND | = lv_im_background | |
| IM_DEBUG_MODE | = lv_im_debug_mode | |
| IM_TRACE_LEVEL | = lv_im_trace_level | |
| IM_SET_ENQUEUE | = lv_im_set_enqueue | |
| EXCEPTIONS | ||
| CX_SWF_RUN_WIM_ENQ_FAILED = 1 | ||
| CX_SWF_RUN_WIM = 2 | ||
| . " SWW_ERRE_EXECUTE_CALLBACK | ||
ABAP code using 7.40 inline data declarations to call FM SWW_ERRE_EXECUTE_CALLBACK
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.| DATA(ld_im_user) | = SY-UNAME. | |||
| DATA(ld_im_language) | = SY-LANGU. | |||
| DATA(ld_im_background) | = 'X'. | |||
| DATA(ld_im_set_enqueue) | = 'X'. | |||
Search for further information about these or an SAP related objects