SAP ISU_METERREAD_INPUTCHECK_RELEV Function Module for









ISU_METERREAD_INPUTCHECK_RELEV is a standard isu meterread inputcheck relev SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 meterread inputcheck relev FM, simply by entering the name ISU_METERREAD_INPUTCHECK_RELEV into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_METERREAD_INPUTCHECK_RELEV 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_METERREAD_INPUTCHECK_RELEV'"
EXPORTING
X_OKCODE = "Date to Be Checked

IMPORTING
Y_NO_CHECKINPUT = "Indicator
Y_ACTION_WITH_INPUT = "Indicator

CHANGING
XY_OBJ = "

EXCEPTIONS
INPUT_ERROR = 1
.



IMPORTING Parameters details for ISU_METERREAD_INPUTCHECK_RELEV

X_OKCODE - Date to Be Checked

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

EXPORTING Parameters details for ISU_METERREAD_INPUTCHECK_RELEV

Y_NO_CHECKINPUT - Indicator

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

Y_ACTION_WITH_INPUT - Indicator

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

CHANGING Parameters details for ISU_METERREAD_INPUTCHECK_RELEV

XY_OBJ -

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

EXCEPTIONS details

INPUT_ERROR - Input error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_METERREAD_INPUTCHECK_RELEV 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 ISU17_METERREAD, "   
lv_x_okcode  TYPE REGEN-OKCODE, "   
lv_input_error  TYPE REGEN, "   
lv_y_no_checkinput  TYPE REGEN-KENNZX, "   
lv_y_action_with_input  TYPE REGEN-KENNZX. "   

  CALL FUNCTION 'ISU_METERREAD_INPUTCHECK_RELEV'  "
    EXPORTING
         X_OKCODE = lv_x_okcode
    IMPORTING
         Y_NO_CHECKINPUT = lv_y_no_checkinput
         Y_ACTION_WITH_INPUT = lv_y_action_with_input
    CHANGING
         XY_OBJ = lv_xy_obj
    EXCEPTIONS
        INPUT_ERROR = 1
. " ISU_METERREAD_INPUTCHECK_RELEV




ABAP code using 7.40 inline data declarations to call FM ISU_METERREAD_INPUTCHECK_RELEV

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 OKCODE FROM REGEN INTO @DATA(ld_x_okcode).
 
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_y_no_checkinput).
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_y_action_with_input).
 


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!