SAP ISU_O_METERREAD_CLOSE Function Module for









ISU_O_METERREAD_CLOSE is a standard isu o meterread close 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 o meterread close FM, simply by entering the name ISU_O_METERREAD_CLOSE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_O_METERREAD_CLOSE 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_METERREAD_CLOSE'"
EXPORTING
* X_NO_DIALOG = "Suppress maintenance screens
* X_DEQ_SYNC = ' ' "

IMPORTING
Y_DB_UPDATE = "Indicator: Database Change Made
Y_EXIT_TYPE = "BACK=Back(F3), EXIT=Ende(F15), CANC=Cancel(F12)

CHANGING
XY_OBJ = "

TABLES
* YT_NEW_EABL = "
* YT_NEW_EABLG = "
* YT_NEW_ETRG = "

EXCEPTIONS
NOT_CUSTOMIZED = 1 FAILED = 2 GENERAL_FAULT = 3
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLEL01_001 IS-U: User-defined order code control for SM orders
EXIT_SAPLEL01_004 IS-U: Modify Meter Reading During Upload of MR Data (Before Validation)
EXIT_SAPLEL01_005 IS-U: Define Follow-Up Action for MR Result Entered During Upload
EXIT_SAPLEL01_006 IS-U: User Exit PBO: PBO for Customer Subscreen
EXIT_SAPLEL01_007 IS-U: User Exit PAI_BEFORE: Prepares the CALL SUBSCREEN PAI
EXIT_SAPLEL01_008 IS-U: User Exit PAI_AFTER: Closes the CALL SUBSCREEN PAI
EXIT_SAPLEL01_009 IS-U: Change Gas Date in Meter Reading Processing
EXIT_SAPLEL01_010 IS-U: Fills Customer Include During Order Creation
EXIT_SAPLEL01_011 Transfers Data to Customer Include when Uploading Meter Readings
EXIT_SAPLEL01_015 ISU: Check - Automatic Suppression of the Billing
EXIT_SAPLEL01_020 IS-U: User-Defined Control of Automatic Meter Reading Data Monitoring

IMPORTING Parameters details for ISU_O_METERREAD_CLOSE

X_NO_DIALOG - Suppress maintenance screens

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

X_DEQ_SYNC -

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

EXPORTING Parameters details for ISU_O_METERREAD_CLOSE

Y_DB_UPDATE - Indicator: Database Change Made

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

Y_EXIT_TYPE - BACK=Back(F3), EXIT=Ende(F15), CANC=Cancel(F12)

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

CHANGING Parameters details for ISU_O_METERREAD_CLOSE

XY_OBJ -

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

TABLES Parameters details for ISU_O_METERREAD_CLOSE

YT_NEW_EABL -

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

YT_NEW_EABLG -

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

YT_NEW_ETRG -

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

EXCEPTIONS details

NOT_CUSTOMIZED -

Data type:
Optional: No
Call by Reference: Yes

FAILED - Function failed

Data type:
Optional: No
Call by Reference: Yes

GENERAL_FAULT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_O_METERREAD_CLOSE 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_no_dialog  TYPE REGEN-NO_DIALOG, "   
lt_yt_new_eabl  TYPE STANDARD TABLE OF EABL, "   
lv_y_db_update  TYPE REGEN-DB_UPDATE, "   
lv_not_customized  TYPE REGEN, "   
lv_failed  TYPE REGEN, "   
lv_x_deq_sync  TYPE CHAR1, "   ' '
lv_y_exit_type  TYPE REGEN-EXIT_TYPE, "   
lt_yt_new_eablg  TYPE STANDARD TABLE OF EABLG, "   
lt_yt_new_etrg  TYPE STANDARD TABLE OF ETRG, "   
lv_general_fault  TYPE ETRG. "   

  CALL FUNCTION 'ISU_O_METERREAD_CLOSE'  "
    EXPORTING
         X_NO_DIALOG = lv_x_no_dialog
         X_DEQ_SYNC = lv_x_deq_sync
    IMPORTING
         Y_DB_UPDATE = lv_y_db_update
         Y_EXIT_TYPE = lv_y_exit_type
    CHANGING
         XY_OBJ = lv_xy_obj
    TABLES
         YT_NEW_EABL = lt_yt_new_eabl
         YT_NEW_EABLG = lt_yt_new_eablg
         YT_NEW_ETRG = lt_yt_new_etrg
    EXCEPTIONS
        NOT_CUSTOMIZED = 1
        FAILED = 2
        GENERAL_FAULT = 3
. " ISU_O_METERREAD_CLOSE




ABAP code using 7.40 inline data declarations to call FM ISU_O_METERREAD_CLOSE

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 NO_DIALOG FROM REGEN INTO @DATA(ld_x_no_dialog).
 
 
"SELECT single DB_UPDATE FROM REGEN INTO @DATA(ld_y_db_update).
 
 
 
DATA(ld_x_deq_sync) = ' '.
 
"SELECT single EXIT_TYPE FROM REGEN INTO @DATA(ld_y_exit_type).
 
 
 
 


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!