SAP ISU_DB_TEPYPM_SELECT_RANGE Function Module for Do Not Use
ISU_DB_TEPYPM_SELECT_RANGE is a standard isu db tepypm select 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 Do Not Use 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 tepypm select range FM, simply by entering the name ISU_DB_TEPYPM_SELECT_RANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: E325
Program Name: SAPLE325
Main Program: SAPLE325
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_DB_TEPYPM_SELECT_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_TEPYPM_SELECT_RANGE'"Do Not Use.
EXPORTING
* X_VERTRAG = "Contract
* X_MAXCOUNT = "Maximum Number of Objects to be Selected
* X_ACTUAL = "Consistent data
* X_SORT = "
IMPORTING
Y_COUNT = "Maximum Number of Objects to be Selected
Y_OVERFLOW = "Indicator: overflow
Y_TEPYPM = "Contract history for generating payment schedule
TABLES
* XT_VERTRAG = "Structure: Select Options
* YT_TEPYPM = "Contract history for generating payment schedule
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for ISU_DB_TEPYPM_SELECT_RANGE
X_VERTRAG - Contract
Data type: VERTRAGOptional: Yes
Call by Reference: Yes
X_MAXCOUNT - Maximum Number of Objects to be Selected
Data type: REGEN-MAXCOUNTOptional: Yes
Call by Reference: No ( called with pass by value option)
X_ACTUAL - Consistent data
Data type: REGEN-ACTUALOptional: Yes
Call by Reference: Yes
X_SORT -
Data type: REGEN-KZ_SORTOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISU_DB_TEPYPM_SELECT_RANGE
Y_COUNT - Maximum Number of Objects to be Selected
Data type: REGEN-MAXCOUNTOptional: No
Call by Reference: Yes
Y_OVERFLOW - Indicator: overflow
Data type: REGEN-OVERFLOWOptional: No
Call by Reference: Yes
Y_TEPYPM - Contract history for generating payment schedule
Data type: TEPYPMOptional: No
Call by Reference: Yes
TABLES Parameters details for ISU_DB_TEPYPM_SELECT_RANGE
XT_VERTRAG - Structure: Select Options
Data type: ISU_RANGESOptional: Yes
Call by Reference: Yes
YT_TEPYPM - Contract history for generating payment schedule
Data type: TEPYPMOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_DB_TEPYPM_SELECT_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: | ||||
| lv_y_count | TYPE REGEN-MAXCOUNT, " | |||
| lv_not_found | TYPE REGEN, " | |||
| lv_x_vertrag | TYPE VERTRAG, " | |||
| lt_xt_vertrag | TYPE STANDARD TABLE OF ISU_RANGES, " | |||
| lt_yt_tepypm | TYPE STANDARD TABLE OF TEPYPM, " | |||
| lv_x_maxcount | TYPE REGEN-MAXCOUNT, " | |||
| lv_y_overflow | TYPE REGEN-OVERFLOW, " | |||
| lv_x_actual | TYPE REGEN-ACTUAL, " | |||
| lv_y_tepypm | TYPE TEPYPM, " | |||
| lv_x_sort | TYPE REGEN-KZ_SORT. " |
|   CALL FUNCTION 'ISU_DB_TEPYPM_SELECT_RANGE' "Do Not Use |
| EXPORTING | ||
| X_VERTRAG | = lv_x_vertrag | |
| X_MAXCOUNT | = lv_x_maxcount | |
| X_ACTUAL | = lv_x_actual | |
| X_SORT | = lv_x_sort | |
| IMPORTING | ||
| Y_COUNT | = lv_y_count | |
| Y_OVERFLOW | = lv_y_overflow | |
| Y_TEPYPM | = lv_y_tepypm | |
| TABLES | ||
| XT_VERTRAG | = lt_xt_vertrag | |
| YT_TEPYPM | = lt_yt_tepypm | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " ISU_DB_TEPYPM_SELECT_RANGE | ||
ABAP code using 7.40 inline data declarations to call FM ISU_DB_TEPYPM_SELECT_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 MAXCOUNT FROM REGEN INTO @DATA(ld_x_maxcount). | ||||
| "SELECT single OVERFLOW FROM REGEN INTO @DATA(ld_y_overflow). | ||||
| "SELECT single ACTUAL FROM REGEN INTO @DATA(ld_x_actual). | ||||
| "SELECT single KZ_SORT FROM REGEN INTO @DATA(ld_x_sort). | ||||
Search for further information about these or an SAP related objects