SAP ISU_DEVICERATE_CHECK Function Module for Internal: Checks Consistency of Rate Data









ISU_DEVICERATE_CHECK is a standard isu devicerate check 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: Checks Consistency of Rate Data 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 devicerate check FM, simply by entering the name ISU_DEVICERATE_CHECK 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_DEVICERATE_CHECK 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_DEVICERATE_CHECK'"Internal: Checks Consistency of Rate Data
  EXPORTING
*  X_ANLAGE =  "Installation
*  X_EQUNR =  "Equipment Number
*  X_AB = '19000101' "
*  X_BIS = '99991231' "

 IMPORTING
   Y_ERROR_AB =  "
   Y_ERROR_BIS =  "

CHANGING
*  XY_OBJ =  "
*  XY_INTEGRATION =  "

EXCEPTIONS
   NOT_FOUND = 1    FOREIGN_LOCK = 2    SYSTEM_ERROR = 3    INTERNAL_ERROR = 4
.



IMPORTING Parameters details for ISU_DEVICERATE_CHECK

X_ANLAGE - Installation

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

X_EQUNR - Equipment Number

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

X_AB -

Data type: REG70-AB
Default: '19000101'
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_BIS -

Data type: REG70-BIS
Default: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISU_DEVICERATE_CHECK

Y_ERROR_AB -

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

Y_ERROR_BIS -

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

CHANGING Parameters details for ISU_DEVICERATE_CHECK

XY_OBJ -

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

XY_INTEGRATION -

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

EXCEPTIONS details

NOT_FOUND - Object Not Found

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

FOREIGN_LOCK - Object is currently locked

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

SYSTEM_ERROR - General system error

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

INTERNAL_ERROR - Error While Checking

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

Copy and paste ABAP code example for ISU_DEVICERATE_CHECK 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 ISU70_DEVICERATE, "   
lv_x_anlage  TYPE REG70-ANLAGE, "   
lv_not_found  TYPE REG70, "   
lv_y_error_ab  TYPE REG70-AB, "   
lv_x_equnr  TYPE REG70-EQUNR, "   
lv_y_error_bis  TYPE REG70-BIS, "   
lv_foreign_lock  TYPE REG70, "   
lv_xy_integration  TYPE ISU07_INTEGRATION_DATA, "   
lv_x_ab  TYPE REG70-AB, "   '19000101'
lv_system_error  TYPE REG70, "   
lv_x_bis  TYPE REG70-BIS, "   '99991231'
lv_internal_error  TYPE REG70. "   

  CALL FUNCTION 'ISU_DEVICERATE_CHECK'  "Internal: Checks Consistency of Rate Data
    EXPORTING
         X_ANLAGE = lv_x_anlage
         X_EQUNR = lv_x_equnr
         X_AB = lv_x_ab
         X_BIS = lv_x_bis
    IMPORTING
         Y_ERROR_AB = lv_y_error_ab
         Y_ERROR_BIS = lv_y_error_bis
    CHANGING
         XY_OBJ = lv_xy_obj
         XY_INTEGRATION = lv_xy_integration
    EXCEPTIONS
        NOT_FOUND = 1
        FOREIGN_LOCK = 2
        SYSTEM_ERROR = 3
        INTERNAL_ERROR = 4
. " ISU_DEVICERATE_CHECK




ABAP code using 7.40 inline data declarations to call FM ISU_DEVICERATE_CHECK

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 ANLAGE FROM REG70 INTO @DATA(ld_x_anlage).
 
 
"SELECT single AB FROM REG70 INTO @DATA(ld_y_error_ab).
 
"SELECT single EQUNR FROM REG70 INTO @DATA(ld_x_equnr).
 
"SELECT single BIS FROM REG70 INTO @DATA(ld_y_error_bis).
 
 
 
"SELECT single AB FROM REG70 INTO @DATA(ld_x_ab).
DATA(ld_x_ab) = '19000101'.
 
 
"SELECT single BIS FROM REG70 INTO @DATA(ld_x_bis).
DATA(ld_x_bis) = '99991231'.
 
 


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!