SAP IWO_UI_DL_UI_ENTRY Function Module for NOTRANSL: Einsprung in flexibles Auftrags-UI
IWO_UI_DL_UI_ENTRY is a standard iwo ui dl ui entry SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Einsprung in flexibles Auftrags-UI 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 iwo ui dl ui entry FM, simply by entering the name IWO_UI_DL_UI_ENTRY into the relevant SAP transaction such as SE37 or SE38.
Function Group: IWO_UI_DL
Program Name: SAPLIWO_UI_DL
Main Program: SAPLIWO_UI_DL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IWO_UI_DL_UI_ENTRY 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 'IWO_UI_DL_UI_ENTRY'"NOTRANSL: Einsprung in flexibles Auftrags-UI.
EXPORTING
IS_HEADER = "Dialog Structure for Order Headers and Item
IV_FCODE = "Menu Painter: Function Code
IV_ACTIVITYTYPE = "Transaction Type
EXCEPTIONS
NOT_AVAILABLE = 1 NO_OBJECT_LIST = 2
IMPORTING Parameters details for IWO_UI_DL_UI_ENTRY
IS_HEADER - Dialog Structure for Order Headers and Item
Data type: CAUFVDOptional: No
Call by Reference: Yes
IV_FCODE - Menu Painter: Function Code
Data type: GUI_FUNCOptional: No
Call by Reference: Yes
IV_ACTIVITYTYPE - Transaction Type
Data type: TRTYPOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_AVAILABLE -
Data type:Optional: No
Call by Reference: Yes
NO_OBJECT_LIST -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for IWO_UI_DL_UI_ENTRY 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_is_header | TYPE CAUFVD, " | |||
| lv_not_available | TYPE CAUFVD, " | |||
| lv_iv_fcode | TYPE GUI_FUNC, " | |||
| lv_no_object_list | TYPE GUI_FUNC, " | |||
| lv_iv_activitytype | TYPE TRTYP. " |
|   CALL FUNCTION 'IWO_UI_DL_UI_ENTRY' "NOTRANSL: Einsprung in flexibles Auftrags-UI |
| EXPORTING | ||
| IS_HEADER | = lv_is_header | |
| IV_FCODE | = lv_iv_fcode | |
| IV_ACTIVITYTYPE | = lv_iv_activitytype | |
| EXCEPTIONS | ||
| NOT_AVAILABLE = 1 | ||
| NO_OBJECT_LIST = 2 | ||
| . " IWO_UI_DL_UI_ENTRY | ||
ABAP code using 7.40 inline data declarations to call FM IWO_UI_DL_UI_ENTRY
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