SAP ISU_S_UI_CHANGE Function Module for Change Service for Point of Delivery

Search SAP Function Modules

ISU_S_UI_CHANGE is a standard isu s ui change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change 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 change FM, simply by entering the name ISU_S_UI_CHANGE 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_CHANGE 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_CHANGE'"Change Service for Point of Delivery
  EXPORTING
*  X_INT_UI =  "
*  X_INST_CALL =  "
*  X_EXT_UI =  "External reporting point description
*  X_KEYDATE = SY-DATUM "Start of Period
*  X_KEYTIME =  "Time
*  X_UPD_ONLINE =  "Update online
*  X_NO_OTHER =  "No other Object Permitted
*  X_NO_DIALOG =  "Suppress maintenance screens
*  X_OBJ =  "Point of Delivery Object
*  X_AUTO =  "Automation data

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

EXCEPTIONS
   NOT_FOUND = 1    FOREIGN_LOCK = 2    INPUT_ERROR = 3    SYSTEM_ERROR = 4 

.

IMPORTING Parameters details for ISU_S_UI_CHANGE

X_INT_UI -

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

X_INST_CALL -

Data type: FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

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 - 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_OTHER - No other Object Permitted

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

X_NO_DIALOG - Suppress maintenance screens

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

X_OBJ - Point of Delivery Object

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

X_AUTO - Automation data

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

EXPORTING Parameters details for ISU_S_UI_CHANGE

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

FOREIGN_LOCK -

Data type:
Optional: No
Call by Reference: Yes

INPUT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

SYSTEM_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ISU_S_UI_CHANGE 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.

ABAP code using 7.40 inline data declarations to call FM ISU_S_UI_CHANGE

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