SAP SIW_CHANGE_TESTDATA Function Module for change testdate
SIW_CHANGE_TESTDATA is a standard siw change testdata SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for change testdate 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 siw change testdata FM, simply by entering the name SIW_CHANGE_TESTDATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: FS_SIW_UI_TESTDATA
Program Name: SAPLFS_SIW_UI_TESTDATA
Main Program: SAPLFS_SIW_UI_TESTDATA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SIW_CHANGE_TESTDATA 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 'SIW_CHANGE_TESTDATA'"change testdate.
EXPORTING
IO_PROJECT = "Service Implementation Project
* ID_VARIANT_ID = "variant id
* I_FLG_EDITMODE = "general flag
IMPORTING Parameters details for SIW_CHANGE_TESTDATA
IO_PROJECT - Service Implementation Project
Data type: IF_SIW_PROJECTOptional: No
Call by Reference: Yes
ID_VARIANT_ID - variant id
Data type: SIW_DTE_VARIANT_IDOptional: Yes
Call by Reference: Yes
I_FLG_EDITMODE - general flag
Data type: SIW_DTE_FLGOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for SIW_CHANGE_TESTDATA 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_io_project | TYPE IF_SIW_PROJECT, " | |||
| lv_id_variant_id | TYPE SIW_DTE_VARIANT_ID, " | |||
| lv_i_flg_editmode | TYPE SIW_DTE_FLG. " |
|   CALL FUNCTION 'SIW_CHANGE_TESTDATA' "change testdate |
| EXPORTING | ||
| IO_PROJECT | = lv_io_project | |
| ID_VARIANT_ID | = lv_id_variant_id | |
| I_FLG_EDITMODE | = lv_i_flg_editmode | |
| . " SIW_CHANGE_TESTDATA | ||
ABAP code using 7.40 inline data declarations to call FM SIW_CHANGE_TESTDATA
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.Search for further information about these or an SAP related objects