SAP SWW_WI_TRACE_DISABLE Function Module for
SWW_WI_TRACE_DISABLE is a standard sww wi trace disable 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 wi trace disable FM, simply by entering the name SWW_WI_TRACE_DISABLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SWWF
Program Name: SAPLSWWF
Main Program: SAPLSWWF
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SWW_WI_TRACE_DISABLE 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_WI_TRACE_DISABLE'".
EXPORTING
WI_ID = "Work item ID
* TRACE_HANDLE = "Complete workflow trace
EXCEPTIONS
UPDATE_FAILED = 1
IMPORTING Parameters details for SWW_WI_TRACE_DISABLE
WI_ID - Work item ID
Data type: SWWWIHEAD-WI_IDOptional: No
Call by Reference: No ( called with pass by value option)
TRACE_HANDLE - Complete workflow trace
Data type: SWT_HANDLEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
UPDATE_FAILED - Work item update failed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SWW_WI_TRACE_DISABLE 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_wi_id | TYPE SWWWIHEAD-WI_ID, " | |||
| lv_update_failed | TYPE SWWWIHEAD, " | |||
| lv_trace_handle | TYPE SWT_HANDLE. " |
|   CALL FUNCTION 'SWW_WI_TRACE_DISABLE' " |
| EXPORTING | ||
| WI_ID | = lv_wi_id | |
| TRACE_HANDLE | = lv_trace_handle | |
| EXCEPTIONS | ||
| UPDATE_FAILED = 1 | ||
| . " SWW_WI_TRACE_DISABLE | ||
ABAP code using 7.40 inline data declarations to call FM SWW_WI_TRACE_DISABLE
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 WI_ID FROM SWWWIHEAD INTO @DATA(ld_wi_id). | ||||
Search for further information about these or an SAP related objects