SAP EXIT_SAPLEL01_005 Function Module for IS-U: Define Follow-Up Action for MR Result Entered During Upload
EXIT_SAPLEL01_005 is a standard exit saplel01 005 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-U: Define Follow-Up Action for MR Result Entered During Upload 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 exit saplel01 005 FM, simply by entering the name EXIT_SAPLEL01_005 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XEL1
Program Name: SAPLXEL1
Main Program: SAPLXEL1
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPLEL01_005 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 'EXIT_SAPLEL01_005'"IS-U: Define Follow-Up Action for MR Result Entered During Upload.
EXPORTING
X_REABLD = "Data of MR result to be entered
X_NO_DIALOG = "Indicator: dialog or background processing
X_OBJ = "
X_INST_OLD = "Category Definition for Entire Installation Structure
X_INST_NEW = "Category Definition for Entire Installation Structure
IMPORTING
Y_ACTCODE = "Action code
Y_NO_EABL_SAVE = "Indicator: Save reading in database
TABLES
YT_IEMSG = "Transfer Table for Messages Issued
EXCEPTIONS
GENERAL_ERROR = 1
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.ISU_CHECK_DEVINSNOMR
ISU_O_METERREAD_ACTION
ISU_O_METERREAD_CLOSE
ISU_O_METERREAD_INPUT
ISU_O_METERREAD_INPUT1
ISU_O_METERREAD_INPUT_GENERAL
ISU_O_METERREAD_OPEN
ISU_O_METERREAD_OPEN_SUBOBJ
ISU_O_METERREAD_PAI_AFTER
ISU_O_METERREAD_PAI_BEFORE
ISU_O_METERREAD_PBO
ISU_O_METERREAD_PBO_AFTER
ISU_O_METERREAD_PREPARE_CLOSE
ISU_S_METERREAD_CHANGE
ISU_S_METERREAD_CREATE
IMPORTING Parameters details for EXIT_SAPLEL01_005
X_REABLD - Data of MR result to be entered
Data type: REABLDOptional: No
Call by Reference: No ( called with pass by value option)
X_NO_DIALOG - Indicator: dialog or background processing
Data type: REGEN-KENNZXOptional: No
Call by Reference: No ( called with pass by value option)
X_OBJ -
Data type: ISU17_METERREADOptional: No
Call by Reference: No ( called with pass by value option)
X_INST_OLD - Category Definition for Entire Installation Structure
Data type: ISU07_INSTALL_STRUCOptional: No
Call by Reference: No ( called with pass by value option)
X_INST_NEW - Category Definition for Entire Installation Structure
Data type: ISU07_INSTALL_STRUCOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXIT_SAPLEL01_005
Y_ACTCODE - Action code
Data type: EEVNTFUACT-ACTCODEOptional: No
Call by Reference: No ( called with pass by value option)
Y_NO_EABL_SAVE - Indicator: Save reading in database
Data type: REGEN-KENNZXOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPLEL01_005
YT_IEMSG - Transfer Table for Messages Issued
Data type: EMSGOptional: No
Call by Reference: Yes
EXCEPTIONS details
GENERAL_ERROR - General Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLEL01_005 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_x_reabld | TYPE REABLD, " | |||
| lt_yt_iemsg | TYPE STANDARD TABLE OF EMSG, " | |||
| lv_y_actcode | TYPE EEVNTFUACT-ACTCODE, " | |||
| lv_general_error | TYPE EEVNTFUACT, " | |||
| lv_x_no_dialog | TYPE REGEN-KENNZX, " | |||
| lv_y_no_eabl_save | TYPE REGEN-KENNZX, " | |||
| lv_x_obj | TYPE ISU17_METERREAD, " | |||
| lv_x_inst_old | TYPE ISU07_INSTALL_STRUC, " | |||
| lv_x_inst_new | TYPE ISU07_INSTALL_STRUC. " |
| CALL FUNCTION 'EXIT_SAPLEL01_005' "IS-U: Define Follow-Up Action for MR Result Entered During Upload |
| EXPORTING | ||
| X_REABLD | = lv_x_reabld | |
| X_NO_DIALOG | = lv_x_no_dialog | |
| X_OBJ | = lv_x_obj | |
| X_INST_OLD | = lv_x_inst_old | |
| X_INST_NEW | = lv_x_inst_new | |
| IMPORTING | ||
| Y_ACTCODE | = lv_y_actcode | |
| Y_NO_EABL_SAVE | = lv_y_no_eabl_save | |
| TABLES | ||
| YT_IEMSG | = lt_yt_iemsg | |
| EXCEPTIONS | ||
| GENERAL_ERROR = 1 | ||
| . " EXIT_SAPLEL01_005 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLEL01_005
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 ACTCODE FROM EEVNTFUACT INTO @DATA(ld_y_actcode). | ||||
| "SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_no_dialog). | ||||
| "SELECT single KENNZX FROM REGEN INTO @DATA(ld_y_no_eabl_save). | ||||
Search for further information about these or an SAP related objects