SAP RDB_REC_NR_RANGE_INSERT Function Module for RDB: Subobjekt und Nummernkreis für ES anlegen
RDB_REC_NR_RANGE_INSERT is a standard rdb rec nr range insert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RDB: Subobjekt und Nummernkreis für ES anlegen 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 rdb rec nr range insert FM, simply by entering the name RDB_REC_NR_RANGE_INSERT into the relevant SAP transaction such as SE37 or SE38.
Function Group: RDB_INTF_RNR
Program Name: SAPLRDB_INTF_RNR
Main Program: SAPLRDB_INTF_RNR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RDB_REC_NR_RANGE_INSERT 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 'RDB_REC_NR_RANGE_INSERT'"RDB: Subobjekt und Nummernkreis für ES anlegen.
EXPORTING
I_KEYDATE = "Stichtag
I_APPLICATION = "Anwendung (Analyzer)
EXCEPTIONS
INTERNAL_ERROR = 1
IMPORTING Parameters details for RDB_REC_NR_RANGE_INSERT
I_KEYDATE - Stichtag
Data type: RDB_KEYDATEOptional: No
Call by Reference: Yes
I_APPLICATION - Anwendung (Analyzer)
Data type: AFW_APPLICATIONOptional: No
Call by Reference: Yes
EXCEPTIONS details
INTERNAL_ERROR - Fehler in der Verarbeitung
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RDB_REC_NR_RANGE_INSERT 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_keydate | TYPE RDB_KEYDATE, " | |||
| lv_internal_error | TYPE RDB_KEYDATE, " | |||
| lv_i_application | TYPE AFW_APPLICATION. " |
|   CALL FUNCTION 'RDB_REC_NR_RANGE_INSERT' "RDB: Subobjekt und Nummernkreis für ES anlegen |
| EXPORTING | ||
| I_KEYDATE | = lv_i_keydate | |
| I_APPLICATION | = lv_i_application | |
| EXCEPTIONS | ||
| INTERNAL_ERROR = 1 | ||
| . " RDB_REC_NR_RANGE_INSERT | ||
ABAP code using 7.40 inline data declarations to call FM RDB_REC_NR_RANGE_INSERT
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