SAP NUMBER_RANGE_UPDATE_CLOSE Function Module for Number range: Close number range changes on database
NUMBER_RANGE_UPDATE_CLOSE is a standard number range update close SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Number range: Close number range changes on database 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 number range update close FM, simply by entering the name NUMBER_RANGE_UPDATE_CLOSE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SNR1
Program Name: SAPLSNR1
Main Program: SAPLSNR1
Appliation area: *
Release date: 22-Dec-1994
Mode(Normal, Remote etc): Normal Function Module
Update:

Function NUMBER_RANGE_UPDATE_CLOSE 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 'NUMBER_RANGE_UPDATE_CLOSE'"Number range: Close number range changes on database.
EXPORTING
OBJECT = "Name of number range object
* INTERVALS = "Number range intervals
EXCEPTIONS
NO_CHANGES_MADE = 1 OBJECT_NOT_INITIALIZED = 2
IMPORTING Parameters details for NUMBER_RANGE_UPDATE_CLOSE
OBJECT - Name of number range object
Data type: TNRO-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
INTERVALS - Number range intervals
Data type: INRIV_TTOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_CHANGES_MADE - nothing was changed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NOT_INITIALIZED - the object was not initialized
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for NUMBER_RANGE_UPDATE_CLOSE 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_object | TYPE TNRO-OBJECT, " | |||
| lv_no_changes_made | TYPE TNRO, " | |||
| lv_intervals | TYPE INRIV_TT, " | |||
| lv_object_not_initialized | TYPE INRIV_TT. " |
|   CALL FUNCTION 'NUMBER_RANGE_UPDATE_CLOSE' "Number range: Close number range changes on database |
| EXPORTING | ||
| OBJECT | = lv_object | |
| INTERVALS | = lv_intervals | |
| EXCEPTIONS | ||
| NO_CHANGES_MADE = 1 | ||
| OBJECT_NOT_INITIALIZED = 2 | ||
| . " NUMBER_RANGE_UPDATE_CLOSE | ||
ABAP code using 7.40 inline data declarations to call FM NUMBER_RANGE_UPDATE_CLOSE
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 OBJECT FROM TNRO INTO @DATA(ld_object). | ||||
Search for further information about these or an SAP related objects