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

Function SWD_HEADER_SCREEN_CALL 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_HEADER_SCREEN_CALL'"Call details.
EXPORTING
IM_SCREEN = "
IM_DISPLAY = "
IMPORTING
EX_CHANGED = "Checkbox Field
IMPORTING Parameters details for SWD_HEADER_SCREEN_CALL
IM_SCREEN -
Data type: SWD_DYNNROptional: No
Call by Reference: Yes
IM_DISPLAY -
Data type: SWD_DATA-XFELDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for SWD_HEADER_SCREEN_CALL
EX_CHANGED - Checkbox Field
Data type: SYINPUTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for SWD_HEADER_SCREEN_CALL 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_screen | TYPE SWD_DYNNR, " | |||
| lv_ex_changed | TYPE SYINPUT, " | |||
| lv_im_display | TYPE SWD_DATA-XFELD. " |
|   CALL FUNCTION 'SWD_HEADER_SCREEN_CALL' "Call details |
| EXPORTING | ||
| IM_SCREEN | = lv_im_screen | |
| IM_DISPLAY | = lv_im_display | |
| IMPORTING | ||
| EX_CHANGED | = lv_ex_changed | |
| . " SWD_HEADER_SCREEN_CALL | ||
ABAP code using 7.40 inline data declarations to call FM SWD_HEADER_SCREEN_CALL
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 XFELD FROM SWD_DATA INTO @DATA(ld_im_display). | ||||
Search for further information about these or an SAP related objects