SAP ISU_ESTIMATION_CREATE_V640 Function Module for Mass Activities: Create Meter Reading Orders
ISU_ESTIMATION_CREATE_V640 is a standard isu estimation create v640 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Mass Activities: Create Meter Reading Orders 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 estimation create v640 FM, simply by entering the name ISU_ESTIMATION_CREATE_V640 into the relevant SAP transaction such as SE37 or SE38.
Function Group: ELMS
Program Name: SAPLELMS
Main Program: SAPLELMS
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_ESTIMATION_CREATE_V640 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_ESTIMATION_CREATE_V640'"Mass Activities: Create Meter Reading Orders.
EXPORTING
I_LOW = "Lower Spec. Limit
I_HIGH = "Upper Spec. Limit
* I_FKKCOCC = "Run Parameters
* I_FKK_PROT = "Additional Log: Parameters
* I_BASICS = "
CHANGING
C_TEST_NUM = "Tested Attempts
C_SUCCESS_NUM = "Successful Attempts
TABLES
* T_FIMSG = "FI Message Table
* T_FKKCOINFO = "Required Periods
* T_PROT_ABLEINH = "Additional Log: Meter Reading Unit
* T_PROT_ADATSOLL = "Additional Log: Dates
* T_COUNTER = "
EXCEPTIONS
GENERAL_FAULT = 1
IMPORTING Parameters details for ISU_ESTIMATION_CREATE_V640
I_LOW - Lower Spec. Limit
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
I_HIGH - Upper Spec. Limit
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
I_FKKCOCC - Run Parameters
Data type: FKKCOCCOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FKK_PROT - Additional Log: Parameters
Data type: FKKPROTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BASICS -
Data type: FKK_MAD_BASICSOptional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for ISU_ESTIMATION_CREATE_V640
C_TEST_NUM - Tested Attempts
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
C_SUCCESS_NUM - Successful Attempts
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISU_ESTIMATION_CREATE_V640
T_FIMSG - FI Message Table
Data type: FIMSGOptional: Yes
Call by Reference: No ( called with pass by value option)
T_FKKCOINFO - Required Periods
Data type: FKKCOINFOOptional: Yes
Call by Reference: No ( called with pass by value option)
T_PROT_ABLEINH - Additional Log: Meter Reading Unit
Data type: FKKR_ABLEINHOptional: Yes
Call by Reference: No ( called with pass by value option)
T_PROT_ADATSOLL - Additional Log: Dates
Data type: FKKR_ADATSOLLOptional: Yes
Call by Reference: Yes
T_COUNTER -
Data type: FKK_MASS_ACT_COUNTOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
GENERAL_FAULT - General Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_ESTIMATION_CREATE_V640 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_i_low | TYPE C, " | |||
| lt_t_fimsg | TYPE STANDARD TABLE OF FIMSG, " | |||
| lv_c_test_num | TYPE I, " | |||
| lv_general_fault | TYPE I, " | |||
| lv_i_high | TYPE C, " | |||
| lt_t_fkkcoinfo | TYPE STANDARD TABLE OF FKKCOINFO, " | |||
| lv_c_success_num | TYPE I, " | |||
| lv_i_fkkcocc | TYPE FKKCOCC, " | |||
| lt_t_prot_ableinh | TYPE STANDARD TABLE OF FKKR_ABLEINH, " | |||
| lv_i_fkk_prot | TYPE FKKPROT, " | |||
| lt_t_prot_adatsoll | TYPE STANDARD TABLE OF FKKR_ADATSOLL, " | |||
| lv_i_basics | TYPE FKK_MAD_BASICS, " | |||
| lt_t_counter | TYPE STANDARD TABLE OF FKK_MASS_ACT_COUNT. " |
|   CALL FUNCTION 'ISU_ESTIMATION_CREATE_V640' "Mass Activities: Create Meter Reading Orders |
| EXPORTING | ||
| I_LOW | = lv_i_low | |
| I_HIGH | = lv_i_high | |
| I_FKKCOCC | = lv_i_fkkcocc | |
| I_FKK_PROT | = lv_i_fkk_prot | |
| I_BASICS | = lv_i_basics | |
| CHANGING | ||
| C_TEST_NUM | = lv_c_test_num | |
| C_SUCCESS_NUM | = lv_c_success_num | |
| TABLES | ||
| T_FIMSG | = lt_t_fimsg | |
| T_FKKCOINFO | = lt_t_fkkcoinfo | |
| T_PROT_ABLEINH | = lt_t_prot_ableinh | |
| T_PROT_ADATSOLL | = lt_t_prot_adatsoll | |
| T_COUNTER | = lt_t_counter | |
| EXCEPTIONS | ||
| GENERAL_FAULT = 1 | ||
| . " ISU_ESTIMATION_CREATE_V640 | ||
ABAP code using 7.40 inline data declarations to call FM ISU_ESTIMATION_CREATE_V640
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