SAP ISU_BI_SIMINDICES_CREATE Function Module for Create Simulation Indexes









ISU_BI_SIMINDICES_CREATE is a standard isu bi simindices create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Simulation Indexes 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 bi simindices create FM, simply by entering the name ISU_BI_SIMINDICES_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_BI_SIMINDICES_CREATE 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_BI_SIMINDICES_CREATE'"Create Simulation Indexes
  EXPORTING
   X_SIMRUNID =  "Identification of simulation run
*  X_RANGE_SPARTE =  "Selection criteria table: Division
*  X_RANGE_AKLASSE =  "Selection criteria table: Billing class
*  X_RANGE_TARIFTYP =  "Selection table: Rate category
*  X_RANGE_ANLAGE =  "Range for Installation
*  X_RANGE_ABLEINH =  "Selection criteria table, meter reading unit
*  X_RANGE_BRANCHE =  "Range table for industry
*  X_RANGE_SERVICE =  "Range for Service Type

 IMPORTING
   Y_COUNT =  "
   Y_DUPLICATE_KEYS =  "Indicator

EXCEPTIONS
   GENERAL_FAULT = 1
.



IMPORTING Parameters details for ISU_BI_SIMINDICES_CREATE

X_SIMRUNID - Identification of simulation run

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

X_RANGE_SPARTE - Selection criteria table: Division

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

X_RANGE_AKLASSE - Selection criteria table: Billing class

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

X_RANGE_TARIFTYP - Selection table: Rate category

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

X_RANGE_ANLAGE - Range for Installation

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

X_RANGE_ABLEINH - Selection criteria table, meter reading unit

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

X_RANGE_BRANCHE - Range table for industry

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

X_RANGE_SERVICE - Range for Service Type

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

EXPORTING Parameters details for ISU_BI_SIMINDICES_CREATE

Y_COUNT -

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

Y_DUPLICATE_KEYS - Indicator

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

EXCEPTIONS details

GENERAL_FAULT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_BI_SIMINDICES_CREATE 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_y_count  TYPE I, "   
lv_x_simrunid  TYPE SIMRUNID, "   
lv_general_fault  TYPE SIMRUNID, "   
lv_x_range_sparte  TYPE ISU_RANGES_SPARTE, "   
lv_y_duplicate_keys  TYPE KENNZX, "   
lv_x_range_aklasse  TYPE ISU_RANGES_AKLASSE, "   
lv_x_range_tariftyp  TYPE ISU_RANGES_TARIFTYP, "   
lv_x_range_anlage  TYPE RANGES_ANLAGE, "   
lv_x_range_ableinh  TYPE ISU_RANGES_ABLEINH, "   
lv_x_range_branche  TYPE ISU_RANGES_BRANCHE, "   
lv_x_range_service  TYPE ISU_RANGES_SERVICE. "   

  CALL FUNCTION 'ISU_BI_SIMINDICES_CREATE'  "Create Simulation Indexes
    EXPORTING
         X_SIMRUNID = lv_x_simrunid
         X_RANGE_SPARTE = lv_x_range_sparte
         X_RANGE_AKLASSE = lv_x_range_aklasse
         X_RANGE_TARIFTYP = lv_x_range_tariftyp
         X_RANGE_ANLAGE = lv_x_range_anlage
         X_RANGE_ABLEINH = lv_x_range_ableinh
         X_RANGE_BRANCHE = lv_x_range_branche
         X_RANGE_SERVICE = lv_x_range_service
    IMPORTING
         Y_COUNT = lv_y_count
         Y_DUPLICATE_KEYS = lv_y_duplicate_keys
    EXCEPTIONS
        GENERAL_FAULT = 1
. " ISU_BI_SIMINDICES_CREATE




ABAP code using 7.40 inline data declarations to call FM ISU_BI_SIMINDICES_CREATE

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



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!