SAP ISU_O_UI_INPUT Function Module for Operation for Point of Delivery Dialog - Input
ISU_O_UI_INPUT is a standard isu o ui input SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Operation for Point of Delivery Dialog - Input 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 isu o ui input FM, simply by entering the name ISU_O_UI_INPUT into the relevant SAP transaction such as SE37 or SE38.
Function Group: EEDM_UI_DIALOG
Program Name: SAPLEEDM_UI_DIALOG
Main Program: SAPLEEDM_UI_DIALOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_O_UI_INPUT 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 'ISU_O_UI_INPUT'"Operation for Point of Delivery Dialog - Input.
CHANGING
XY_OBJ = "Point of Delivery Object
EXCEPTIONS
FOREIGN_LOCK = 1 USER_ERROR = 2 SYSTEM_ERROR = 3
CHANGING Parameters details for ISU_O_UI_INPUT
XY_OBJ - Point of Delivery Object
Data type: EEDM_UI_OBJECTOptional: No
Call by Reference: Yes
EXCEPTIONS details
FOREIGN_LOCK -
Data type:Optional: No
Call by Reference: Yes
USER_ERROR -
Data type:Optional: No
Call by Reference: Yes
SYSTEM_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_O_UI_INPUT 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_xy_obj | TYPE EEDM_UI_OBJECT, " | |||
| lv_foreign_lock | TYPE EEDM_UI_OBJECT, " | |||
| lv_user_error | TYPE EEDM_UI_OBJECT, " | |||
| lv_system_error | TYPE EEDM_UI_OBJECT. " |
|   CALL FUNCTION 'ISU_O_UI_INPUT' "Operation for Point of Delivery Dialog - Input |
| CHANGING | ||
| XY_OBJ | = lv_xy_obj | |
| EXCEPTIONS | ||
| FOREIGN_LOCK = 1 | ||
| USER_ERROR = 2 | ||
| SYSTEM_ERROR = 3 | ||
| . " ISU_O_UI_INPUT | ||
ABAP code using 7.40 inline data declarations to call FM ISU_O_UI_INPUT
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