SAP SWO_INVALIDATE Function Module for Invalidate Runtime Buffer
SWO_INVALIDATE is a standard swo invalidate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Invalidate Runtime Buffer processing and below is the pattern details for this FM, 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 swo invalidate FM, simply by entering the name SWO_INVALIDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SWOR
Program Name: SAPLSWOR
Main Program: SAPLSWOR
Appliation area: S
Release date: 01-Jul-1996
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SWO_INVALIDATE 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 'SWO_INVALIDATE'"Invalidate Runtime Buffer.
EXPORTING
* OBJTYPE = ' ' "
* CLEAR_PROGRAM_MEMORY = ' ' "Release Program Memory
IMPORTING Parameters details for SWO_INVALIDATE
OBJTYPE -
Data type: SWOTBASDAT-OBJTYPEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CLEAR_PROGRAM_MEMORY - Release Program Memory
Data type: CHAR1Default: SPACE
Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for SWO_INVALIDATE 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_objtype | TYPE SWOTBASDAT-OBJTYPE, " SPACE | |||
| lv_clear_program_memory | TYPE CHAR1. " SPACE |
|   CALL FUNCTION 'SWO_INVALIDATE' "Invalidate Runtime Buffer |
| EXPORTING | ||
| OBJTYPE | = lv_objtype | |
| CLEAR_PROGRAM_MEMORY | = lv_clear_program_memory | |
| . " SWO_INVALIDATE | ||
ABAP code using 7.40 inline data declarations to call FM SWO_INVALIDATE
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 OBJTYPE FROM SWOTBASDAT INTO @DATA(ld_objtype). | ||||
| DATA(ld_objtype) | = ' '. | |||
| DATA(ld_clear_program_memory) | = ' '. | |||
Search for further information about these or an SAP related objects