SAP ISU_O_DEVICERATE_ACTION Function Module for INTERNAL: Actions of Subscreens

Search SAP Function Modules

ISU_O_DEVICERATE_ACTION is a standard isu o devicerate action SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Actions of Subscreens 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 devicerate action FM, simply by entering the name ISU_O_DEVICERATE_ACTION into the relevant SAP transaction such as SE37 or SE38.

Function Group: EG70
Program Name: SAPLEG70
Main Program: SAPLEG70
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_O_DEVICERATE_ACTION 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_DEVICERATE_ACTION'"INTERNAL: Actions of Subscreens
  EXPORTING
   X_OKCODE =  "OK Code (from IEOKCODE)
*  X_NO_CLOSE =  "Indicator: Do Not Close Object (OTHR & SWTC)
*  X_NO_MESSAGE =  "Indicator: Do Not Print Message (SAVE)
*  X_OTHER_ANLAGE =  "
*  X_OTHER_GERAET =  "
*  X_OTHER_KEYDATE =  "
*  X_KEYDATE =  "

 IMPORTING
   Y_INSTALL_STRUC =  "Category Definition for Entire Installation Structure

CHANGING
   XY_OBJ =  "Object Data

EXCEPTIONS
   CANCELLED = 1    INTERNAL_ERROR = 2    FAILED = 3    SYSTEM_ERROR = 4 

.

IMPORTING Parameters details for ISU_O_DEVICERATE_ACTION

X_OKCODE - OK Code (from IEOKCODE)

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

X_NO_CLOSE - Indicator: Do Not Close Object (OTHR & SWTC)

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

X_NO_MESSAGE - Indicator: Do Not Print Message (SAVE)

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

X_OTHER_ANLAGE -

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

X_OTHER_GERAET -

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

X_OTHER_KEYDATE -

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

X_KEYDATE -

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

EXPORTING Parameters details for ISU_O_DEVICERATE_ACTION

Y_INSTALL_STRUC - Category Definition for Entire Installation Structure

Data type: ISU07_INSTALL_STRUC
Optional: No
Call by Reference: Yes

CHANGING Parameters details for ISU_O_DEVICERATE_ACTION

XY_OBJ - Object Data

Data type: ISU70_DEVICERATE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CANCELLED - Action Cancelled by User

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

INTERNAL_ERROR -

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

FAILED -

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

SYSTEM_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_O_DEVICERATE_ACTION 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_O_DEVICERATE_ACTION

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