SAP SWP_LOG_WRITE_EXCEPTION Function Module for
SWP_LOG_WRITE_EXCEPTION is a standard swp log write exception 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 swp log write exception FM, simply by entering the name SWP_LOG_WRITE_EXCEPTION into the relevant SAP transaction such as SE37 or SE38.
Function Group: SWP4
Program Name: SAPLSWP4
Main Program: SAPLSWP4
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SWP_LOG_WRITE_EXCEPTION 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 'SWP_LOG_WRITE_EXCEPTION'".
EXPORTING
FB_NAME = "Name of function module called
* IM_EXCEPTION = "Workflow Exception
* MSGID = 'WL' "Message ID of exception (e.g. WD, WL etc.)
MSGNO = "Message number of exception
* MSGTY = 'E' "Message type of exception (e.g. E, A, I, etc.)
* MSGV1 = ' ' "Message variable 1
* MSGV2 = ' ' "Message variable 2
* MSGV3 = ' ' "Message variable 3
* MSGV4 = ' ' "Message variable 4
* DO_COMMIT = ' ' "
IMPORTING
WORST_MSGTYPE = "
EX_EXCEPTION = "Exception in WIM
CHANGING
* WF = "
IMPORTING Parameters details for SWP_LOG_WRITE_EXCEPTION
FB_NAME - Name of function module called
Data type: SWLLOGHIST-METHODOptional: No
Call by Reference: No ( called with pass by value option)
IM_EXCEPTION - Workflow Exception
Data type: CX_SWF_IFS_EXCEPTIONOptional: Yes
Call by Reference: Yes
MSGID - Message ID of exception (e.g. WD, WL etc.)
Data type: SY-MSGIDDefault: 'WL'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSGNO - Message number of exception
Data type: SY-MSGNOOptional: No
Call by Reference: No ( called with pass by value option)
MSGTY - Message type of exception (e.g. E, A, I, etc.)
Data type: SY-MSGTYDefault: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSGV1 - Message variable 1
Data type: ANYDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSGV2 - Message variable 2
Data type: ANYDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSGV3 - Message variable 3
Data type: ANYDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSGV4 - Message variable 4
Data type: ANYDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DO_COMMIT -
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for SWP_LOG_WRITE_EXCEPTION
WORST_MSGTYPE -
Data type: SY-MSGTYOptional: No
Call by Reference: No ( called with pass by value option)
EX_EXCEPTION - Exception in WIM
Data type: CX_SWF_IFS_EXCEPTIONOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for SWP_LOG_WRITE_EXCEPTION
WF -
Data type: SWP1_WORKFLOWOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for SWP_LOG_WRITE_EXCEPTION 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_wf | TYPE SWP1_WORKFLOW, " | |||
| lv_fb_name | TYPE SWLLOGHIST-METHOD, " | |||
| lv_worst_msgtype | TYPE SY-MSGTY, " | |||
| lv_im_exception | TYPE CX_SWF_IFS_EXCEPTION, " | |||
| lv_msgid | TYPE SY-MSGID, " 'WL' | |||
| lv_ex_exception | TYPE CX_SWF_IFS_EXCEPTION, " | |||
| lv_msgno | TYPE SY-MSGNO, " | |||
| lv_msgty | TYPE SY-MSGTY, " 'E' | |||
| lv_msgv1 | TYPE ANY, " SPACE | |||
| lv_msgv2 | TYPE ANY, " SPACE | |||
| lv_msgv3 | TYPE ANY, " SPACE | |||
| lv_msgv4 | TYPE ANY, " SPACE | |||
| lv_do_commit | TYPE XFELD. " ' ' |
|   CALL FUNCTION 'SWP_LOG_WRITE_EXCEPTION' " |
| EXPORTING | ||
| FB_NAME | = lv_fb_name | |
| IM_EXCEPTION | = lv_im_exception | |
| MSGID | = lv_msgid | |
| MSGNO | = lv_msgno | |
| MSGTY | = lv_msgty | |
| MSGV1 | = lv_msgv1 | |
| MSGV2 | = lv_msgv2 | |
| MSGV3 | = lv_msgv3 | |
| MSGV4 | = lv_msgv4 | |
| DO_COMMIT | = lv_do_commit | |
| IMPORTING | ||
| WORST_MSGTYPE | = lv_worst_msgtype | |
| EX_EXCEPTION | = lv_ex_exception | |
| CHANGING | ||
| WF | = lv_wf | |
| . " SWP_LOG_WRITE_EXCEPTION | ||
ABAP code using 7.40 inline data declarations to call FM SWP_LOG_WRITE_EXCEPTION
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.| "SELECT single METHOD FROM SWLLOGHIST INTO @DATA(ld_fb_name). | ||||
| "SELECT single MSGTY FROM SY INTO @DATA(ld_worst_msgtype). | ||||
| "SELECT single MSGID FROM SY INTO @DATA(ld_msgid). | ||||
| DATA(ld_msgid) | = 'WL'. | |||
| "SELECT single MSGNO FROM SY INTO @DATA(ld_msgno). | ||||
| "SELECT single MSGTY FROM SY INTO @DATA(ld_msgty). | ||||
| DATA(ld_msgty) | = 'E'. | |||
| DATA(ld_msgv1) | = ' '. | |||
| DATA(ld_msgv2) | = ' '. | |||
| DATA(ld_msgv3) | = ' '. | |||
| DATA(ld_msgv4) | = ' '. | |||
| DATA(ld_do_commit) | = ' '. | |||
Search for further information about these or an SAP related objects