SAP ISU_S_UI_DISPLAY Function Module for Display Service for Point of Delivery









ISU_S_UI_DISPLAY is a standard isu s ui display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display Service for Point of Delivery 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 s ui display FM, simply by entering the name ISU_S_UI_DISPLAY 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_S_UI_DISPLAY 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_S_UI_DISPLAY'"Display Service for Point of Delivery
EXPORTING
* X_INT_UI = "
* X_EXT_UI = "External reporting point description
* X_KEYDATE = SY-DATUM "Start of Period
* X_KEYTIME = "From-Time
* X_UPD_ONLINE = "Update online
* X_NO_CHANGE = "No Changes Allowed
* X_NO_OTHER = "No other Object Permitted
* XT_HIGHLIGHTED_NBSERV = "

IMPORTING
Y_DB_UPDATE = "Database Updated (X) or not (' ')
Y_EXIT_TYPE = "Function with which editing was exited

EXCEPTIONS
NOT_FOUND = 1 SYSTEM_ERROR = 2
.



IMPORTING Parameters details for ISU_S_UI_DISPLAY

X_INT_UI -

Data type: INT_UI
Optional: Yes
Call by Reference: Yes

X_EXT_UI - External reporting point description

Data type: EXT_UI
Optional: Yes
Call by Reference: Yes

X_KEYDATE - Start of Period

Data type: E_EDMDATEFROM
Default: SY-DATUM
Optional: Yes
Call by Reference: Yes

X_KEYTIME - From-Time

Data type: E_EDMTIMEFROM
Optional: Yes
Call by Reference: Yes

X_UPD_ONLINE - Update online

Data type: REGEN-UPD_ONLINE
Optional: Yes
Call by Reference: Yes

X_NO_CHANGE - No Changes Allowed

Data type: REGEN-NO_CHANGE
Optional: Yes
Call by Reference: Yes

X_NO_OTHER - No other Object Permitted

Data type: REGEN-NO_OTHER
Optional: Yes
Call by Reference: Yes

XT_HIGHLIGHTED_NBSERV -

Data type: ISERVICE_KEY
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISU_S_UI_DISPLAY

Y_DB_UPDATE - Database Updated (X) or not (SPACE)

Data type: REGEN-DB_UPDATE
Optional: No
Call by Reference: Yes

Y_EXIT_TYPE - Function with which editing was exited

Data type: REGEN-EXIT_TYPE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND -

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_S_UI_DISPLAY 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_x_int_ui  TYPE INT_UI, "   
lv_not_found  TYPE INT_UI, "   
lv_y_db_update  TYPE REGEN-DB_UPDATE, "   
lv_x_ext_ui  TYPE EXT_UI, "   
lv_y_exit_type  TYPE REGEN-EXIT_TYPE, "   
lv_system_error  TYPE REGEN, "   
lv_x_keydate  TYPE E_EDMDATEFROM, "   SY-DATUM
lv_x_keytime  TYPE E_EDMTIMEFROM, "   
lv_x_upd_online  TYPE REGEN-UPD_ONLINE, "   
lv_x_no_change  TYPE REGEN-NO_CHANGE, "   
lv_x_no_other  TYPE REGEN-NO_OTHER, "   
lv_xt_highlighted_nbserv  TYPE ISERVICE_KEY. "   

  CALL FUNCTION 'ISU_S_UI_DISPLAY'  "Display Service for Point of Delivery
    EXPORTING
         X_INT_UI = lv_x_int_ui
         X_EXT_UI = lv_x_ext_ui
         X_KEYDATE = lv_x_keydate
         X_KEYTIME = lv_x_keytime
         X_UPD_ONLINE = lv_x_upd_online
         X_NO_CHANGE = lv_x_no_change
         X_NO_OTHER = lv_x_no_other
         XT_HIGHLIGHTED_NBSERV = lv_xt_highlighted_nbserv
    IMPORTING
         Y_DB_UPDATE = lv_y_db_update
         Y_EXIT_TYPE = lv_y_exit_type
    EXCEPTIONS
        NOT_FOUND = 1
        SYSTEM_ERROR = 2
. " ISU_S_UI_DISPLAY




ABAP code using 7.40 inline data declarations to call FM ISU_S_UI_DISPLAY

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 DB_UPDATE FROM REGEN INTO @DATA(ld_y_db_update).
 
 
"SELECT single EXIT_TYPE FROM REGEN INTO @DATA(ld_y_exit_type).
 
 
DATA(ld_x_keydate) = SY-DATUM.
 
 
"SELECT single UPD_ONLINE FROM REGEN INTO @DATA(ld_x_upd_online).
 
"SELECT single NO_CHANGE FROM REGEN INTO @DATA(ld_x_no_change).
 
"SELECT single NO_OTHER FROM REGEN INTO @DATA(ld_x_no_other).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!