SAP SWD_SET_OBJECT_TYPE Function Module for
SWD_SET_OBJECT_TYPE is a standard swd set object type 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 swd set object type FM, simply by entering the name SWD_SET_OBJECT_TYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SWDB_SERVICES
Program Name: SAPLSWDB_SERVICES
Main Program: SAPLSWDB_SERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SWD_SET_OBJECT_TYPE 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 'SWD_SET_OBJECT_TYPE'".
EXPORTING
IM_TASK = "
IM_WFDKEY = "
IMPORTING
EX_OTYPE = "
EX_BUFFERED = "
IMPORTING Parameters details for SWD_SET_OBJECT_TYPE
IM_TASK -
Data type: SWD_STEP_TOptional: No
Call by Reference: Yes
IM_WFDKEY -
Data type: SWD_WFDKEYOptional: No
Call by Reference: Yes
EXPORTING Parameters details for SWD_SET_OBJECT_TYPE
EX_OTYPE -
Data type:Optional: No
Call by Reference: Yes
EX_BUFFERED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SWD_SET_OBJECT_TYPE 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_im_task | TYPE SWD_STEP_T, " | |||
| lv_ex_otype | TYPE SWD_STEP_T, " | |||
| lv_im_wfdkey | TYPE SWD_WFDKEY, " | |||
| lv_ex_buffered | TYPE SWD_WFDKEY. " |
|   CALL FUNCTION 'SWD_SET_OBJECT_TYPE' " |
| EXPORTING | ||
| IM_TASK | = lv_im_task | |
| IM_WFDKEY | = lv_im_wfdkey | |
| IMPORTING | ||
| EX_OTYPE | = lv_ex_otype | |
| EX_BUFFERED | = lv_ex_buffered | |
| . " SWD_SET_OBJECT_TYPE | ||
ABAP code using 7.40 inline data declarations to call FM SWD_SET_OBJECT_TYPE
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