SAP NUMBER_RANGE_OBJECT_UPDATE Function Module for Number range: Insert or change object
NUMBER_RANGE_OBJECT_UPDATE is a standard number range object update 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: Insert or change object 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 object update FM, simply by entering the name NUMBER_RANGE_OBJECT_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SNR2
Program Name: SAPLSNR2
Main Program: SAPLSNR2
Appliation area: *
Release date: 22-Dec-1994
Mode(Normal, Remote etc): Normal Function Module
Update:

Function NUMBER_RANGE_OBJECT_UPDATE 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_OBJECT_UPDATE'"Number range: Insert or change object.
EXPORTING
* INDICATOR = 'U' "Processing flag
* OBJECT_ATTRIBUTES = ' ' "Object attributes
* OBJECT_TEXT = ' ' "Object text
IMPORTING
RETURNCODE = "Return code
TABLES
ERRORS = "Error messages
EXCEPTIONS
OBJECT_ALREADY_EXISTS = 1 OBJECT_ATTRIBUTES_MISSING = 2 OBJECT_NOT_FOUND = 3 OBJECT_TEXT_MISSING = 4 WRONG_INDICATOR = 5
IMPORTING Parameters details for NUMBER_RANGE_OBJECT_UPDATE
INDICATOR - Processing flag
Data type:Default: 'U'
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT_ATTRIBUTES - Object attributes
Data type: TNRODefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT_TEXT - Object text
Data type: TNROTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for NUMBER_RANGE_OBJECT_UPDATE
RETURNCODE - Return code
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for NUMBER_RANGE_OBJECT_UPDATE
ERRORS - Error messages
Data type: INOEROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJECT_ALREADY_EXISTS - Number range object already exists
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_ATTRIBUTES_MISSING - Attributes were not passed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NOT_FOUND - Object not defined in TNRO
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_TEXT_MISSING - Texts were not passed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_INDICATOR - incorrect processing flag passed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for NUMBER_RANGE_OBJECT_UPDATE 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_errors | TYPE STANDARD TABLE OF INOER, " | |||
| lv_indicator | TYPE INOER, " 'U' | |||
| lv_returncode | TYPE INOER, " | |||
| lv_object_already_exists | TYPE INOER, " | |||
| lv_object_attributes | TYPE TNRO, " SPACE | |||
| lv_object_attributes_missing | TYPE TNRO, " | |||
| lv_object_text | TYPE TNROT, " SPACE | |||
| lv_object_not_found | TYPE TNROT, " | |||
| lv_object_text_missing | TYPE TNROT, " | |||
| lv_wrong_indicator | TYPE TNROT. " |
|   CALL FUNCTION 'NUMBER_RANGE_OBJECT_UPDATE' "Number range: Insert or change object |
| EXPORTING | ||
| INDICATOR | = lv_indicator | |
| OBJECT_ATTRIBUTES | = lv_object_attributes | |
| OBJECT_TEXT | = lv_object_text | |
| IMPORTING | ||
| RETURNCODE | = lv_returncode | |
| TABLES | ||
| ERRORS | = lt_errors | |
| EXCEPTIONS | ||
| OBJECT_ALREADY_EXISTS = 1 | ||
| OBJECT_ATTRIBUTES_MISSING = 2 | ||
| OBJECT_NOT_FOUND = 3 | ||
| OBJECT_TEXT_MISSING = 4 | ||
| WRONG_INDICATOR = 5 | ||
| . " NUMBER_RANGE_OBJECT_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM NUMBER_RANGE_OBJECT_UPDATE
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.| DATA(ld_indicator) | = 'U'. | |||
| DATA(ld_object_attributes) | = ' '. | |||
| DATA(ld_object_text) | = ' '. | |||
Search for further information about these or an SAP related objects