SAP SWA_WORST_MSGTY_GET Function Module for
SWA_WORST_MSGTY_GET is a standard swa worst msgty get 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 swa worst msgty get FM, simply by entering the name SWA_WORST_MSGTY_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SWA2
Program Name: SAPLSWA2
Main Program: SAPLSWA2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SWA_WORST_MSGTY_GET 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 'SWA_WORST_MSGTY_GET'".
EXPORTING
* LAST_WORST_MSGTYPE = ' ' "
* ACTUAL_MSGTYPE = ' ' "
IMPORTING
WORST_MSGTYPE = "
IMPORTING Parameters details for SWA_WORST_MSGTY_GET
LAST_WORST_MSGTYPE -
Data type: SWAEXERROR-MSGTYDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ACTUAL_MSGTYPE -
Data type: SWAEXERROR-MSGTYDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SWA_WORST_MSGTY_GET
WORST_MSGTYPE -
Data type: SWAEXERROR-MSGTYOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SWA_WORST_MSGTY_GET 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_worst_msgtype | TYPE SWAEXERROR-MSGTY, " | |||
| lv_last_worst_msgtype | TYPE SWAEXERROR-MSGTY, " SPACE | |||
| lv_actual_msgtype | TYPE SWAEXERROR-MSGTY. " SPACE |
|   CALL FUNCTION 'SWA_WORST_MSGTY_GET' " |
| EXPORTING | ||
| LAST_WORST_MSGTYPE | = lv_last_worst_msgtype | |
| ACTUAL_MSGTYPE | = lv_actual_msgtype | |
| IMPORTING | ||
| WORST_MSGTYPE | = lv_worst_msgtype | |
| . " SWA_WORST_MSGTY_GET | ||
ABAP code using 7.40 inline data declarations to call FM SWA_WORST_MSGTY_GET
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 MSGTY FROM SWAEXERROR INTO @DATA(ld_worst_msgtype). | ||||
| "SELECT single MSGTY FROM SWAEXERROR INTO @DATA(ld_last_worst_msgtype). | ||||
| DATA(ld_last_worst_msgtype) | = ' '. | |||
| "SELECT single MSGTY FROM SWAEXERROR INTO @DATA(ld_actual_msgtype). | ||||
| DATA(ld_actual_msgtype) | = ' '. | |||
Search for further information about these or an SAP related objects