SAP ISU_DB_EVER_SELECT_IN_RANGE Function Module for INTERNAL: Array Select EVER for Multiple Ranges









ISU_DB_EVER_SELECT_IN_RANGE is a standard isu db ever select in range SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Array Select EVER for Multiple Ranges 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 db ever select in range FM, simply by entering the name ISU_DB_EVER_SELECT_IN_RANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_DB_EVER_SELECT_IN_RANGE 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_DB_EVER_SELECT_IN_RANGE'"INTERNAL: Array Select EVER for Multiple Ranges
EXPORTING
* X_ACTUAL = "Flag: Read Data from Database
X_MAXROWS = "

IMPORTING
Y_COUNT = "

TABLES
TY_EVER = "
* TX_VERTRAG = "
* TX_VKONTO = "
* TX_ANLAGE = "
* TX_SPARTE = "
* TX_BUKRS = "
* TX_EINZDAT = "
* TX_AUSZDAT = "
* TX_WHERETAB = "

EXCEPTIONS
NOT_FOUND = 1 SYSTEM_ERROR = 2
.



IMPORTING Parameters details for ISU_DB_EVER_SELECT_IN_RANGE

X_ACTUAL - Flag: Read Data from Database

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

X_MAXROWS -

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

EXPORTING Parameters details for ISU_DB_EVER_SELECT_IN_RANGE

Y_COUNT -

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

TABLES Parameters details for ISU_DB_EVER_SELECT_IN_RANGE

TY_EVER -

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

TX_VERTRAG -

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

TX_VKONTO -

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

TX_ANLAGE -

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

TX_SPARTE -

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

TX_BUKRS -

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

TX_EINZDAT -

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

TX_AUSZDAT -

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

TX_WHERETAB -

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

EXCEPTIONS details

NOT_FOUND - Record does not exist

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

SYSTEM_ERROR - Other Error

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

Copy and paste ABAP code example for ISU_DB_EVER_SELECT_IN_RANGE 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:
lt_ty_ever  TYPE STANDARD TABLE OF EVER, "   
lv_y_count  TYPE REGEN-MAXCOUNT, "   
lv_x_actual  TYPE REGEN-ACTUAL, "   
lv_not_found  TYPE REGEN, "   
lv_x_maxrows  TYPE SY-INDEX, "   
lt_tx_vertrag  TYPE STANDARD TABLE OF ISU_RANGES, "   
lv_system_error  TYPE ISU_RANGES, "   
lt_tx_vkonto  TYPE STANDARD TABLE OF ISU_RANGES, "   
lt_tx_anlage  TYPE STANDARD TABLE OF ISU_RANGES, "   
lt_tx_sparte  TYPE STANDARD TABLE OF ISU_RANGES, "   
lt_tx_bukrs  TYPE STANDARD TABLE OF ISU_RANGES, "   
lt_tx_einzdat  TYPE STANDARD TABLE OF ISU_RANGES, "   
lt_tx_auszdat  TYPE STANDARD TABLE OF ISU_RANGES, "   
lt_tx_wheretab  TYPE STANDARD TABLE OF RSDSWHERE. "   

  CALL FUNCTION 'ISU_DB_EVER_SELECT_IN_RANGE'  "INTERNAL: Array Select EVER for Multiple Ranges
    EXPORTING
         X_ACTUAL = lv_x_actual
         X_MAXROWS = lv_x_maxrows
    IMPORTING
         Y_COUNT = lv_y_count
    TABLES
         TY_EVER = lt_ty_ever
         TX_VERTRAG = lt_tx_vertrag
         TX_VKONTO = lt_tx_vkonto
         TX_ANLAGE = lt_tx_anlage
         TX_SPARTE = lt_tx_sparte
         TX_BUKRS = lt_tx_bukrs
         TX_EINZDAT = lt_tx_einzdat
         TX_AUSZDAT = lt_tx_auszdat
         TX_WHERETAB = lt_tx_wheretab
    EXCEPTIONS
        NOT_FOUND = 1
        SYSTEM_ERROR = 2
. " ISU_DB_EVER_SELECT_IN_RANGE




ABAP code using 7.40 inline data declarations to call FM ISU_DB_EVER_SELECT_IN_RANGE

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 MAXCOUNT FROM REGEN INTO @DATA(ld_y_count).
 
"SELECT single ACTUAL FROM REGEN INTO @DATA(ld_x_actual).
 
 
"SELECT single INDEX FROM SY INTO @DATA(ld_x_maxrows).
 
 
 
 
 
 
 
 
 
 


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!