SAP SWU_DIALOG_WEB_ENABLING Function Module for
SWU_DIALOG_WEB_ENABLING is a standard swu dialog web enabling 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 swu dialog web enabling FM, simply by entering the name SWU_DIALOG_WEB_ENABLING into the relevant SAP transaction such as SE37 or SE38.
Function Group: SWU5
Program Name: SAPLSWU5
Main Program: SAPLSWU5
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SWU_DIALOG_WEB_ENABLING 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 'SWU_DIALOG_WEB_ENABLING'".
EXPORTING
* WEB_ENABLED = "
TASK_OTYPE = "Standard object type
TASK_OBJID = "Object ID of standard object
* TADIR_DEVCLASS = "Package for Transport Organizer
* MODE = $SWU_DISPLAY_MODE "
* CONTAINER_DEF_HANDLE = "
CHANGING
TRANSACTION = "Transaction Code
TABLES
* CONTAINER_DEF = "Definition Structure
EXCEPTIONS
WRONG_INPUT_DATA = 1 ABORT_BY_USER = 2
IMPORTING Parameters details for SWU_DIALOG_WEB_ENABLING
WEB_ENABLED -
Data type: HRS1201-WEB_ABLEOptional: Yes
Call by Reference: No ( called with pass by value option)
TASK_OTYPE - Standard object type
Data type: HRSOBJECT-OTYPEOptional: No
Call by Reference: No ( called with pass by value option)
TASK_OBJID - Object ID of standard object
Data type: HRSOBJECT-OBJIDOptional: No
Call by Reference: No ( called with pass by value option)
TADIR_DEVCLASS - Package for Transport Organizer
Data type: TADIR-DEVCLASSOptional: Yes
Call by Reference: No ( called with pass by value option)
MODE -
Data type: CDefault: $SWU_DISPLAY_MODE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CONTAINER_DEF_HANDLE -
Data type: IF_SWF_CNT_CONTAINEROptional: Yes
Call by Reference: Yes
CHANGING Parameters details for SWU_DIALOG_WEB_ENABLING
TRANSACTION - Transaction Code
Data type: TSTC-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SWU_DIALOG_WEB_ENABLING
CONTAINER_DEF - Definition Structure
Data type: SWCONTDEFOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
WRONG_INPUT_DATA -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ABORT_BY_USER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SWU_DIALOG_WEB_ENABLING 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_transaction | TYPE TSTC-TCODE, " | |||
| lv_web_enabled | TYPE HRS1201-WEB_ABLE, " | |||
| lt_container_def | TYPE STANDARD TABLE OF SWCONTDEF, " | |||
| lv_wrong_input_data | TYPE SWCONTDEF, " | |||
| lv_task_otype | TYPE HRSOBJECT-OTYPE, " | |||
| lv_abort_by_user | TYPE HRSOBJECT, " | |||
| lv_task_objid | TYPE HRSOBJECT-OBJID, " | |||
| lv_tadir_devclass | TYPE TADIR-DEVCLASS, " | |||
| lv_mode | TYPE C, " $SWU_DISPLAY_MODE | |||
| lv_container_def_handle | TYPE IF_SWF_CNT_CONTAINER. " |
|   CALL FUNCTION 'SWU_DIALOG_WEB_ENABLING' " |
| EXPORTING | ||
| WEB_ENABLED | = lv_web_enabled | |
| TASK_OTYPE | = lv_task_otype | |
| TASK_OBJID | = lv_task_objid | |
| TADIR_DEVCLASS | = lv_tadir_devclass | |
| MODE | = lv_mode | |
| CONTAINER_DEF_HANDLE | = lv_container_def_handle | |
| CHANGING | ||
| TRANSACTION | = lv_transaction | |
| TABLES | ||
| CONTAINER_DEF | = lt_container_def | |
| EXCEPTIONS | ||
| WRONG_INPUT_DATA = 1 | ||
| ABORT_BY_USER = 2 | ||
| . " SWU_DIALOG_WEB_ENABLING | ||
ABAP code using 7.40 inline data declarations to call FM SWU_DIALOG_WEB_ENABLING
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 TCODE FROM TSTC INTO @DATA(ld_transaction). | ||||
| "SELECT single WEB_ABLE FROM HRS1201 INTO @DATA(ld_web_enabled). | ||||
| "SELECT single OTYPE FROM HRSOBJECT INTO @DATA(ld_task_otype). | ||||
| "SELECT single OBJID FROM HRSOBJECT INTO @DATA(ld_task_objid). | ||||
| "SELECT single DEVCLASS FROM TADIR INTO @DATA(ld_tadir_devclass). | ||||
| DATA(ld_mode) | = $SWU_DISPLAY_MODE. | |||
Search for further information about these or an SAP related objects