SAP NUMBER_CHECK Function Module for Number range: Checks whether number lies in the number interval

Search SAP Function Modules

NUMBER_CHECK is a standard number check 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: Checks whether number lies in the number interval 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 check FM, simply by entering the name NUMBER_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: SNR3
Program Name: SAPLSNR3
Main Program: SAPLSNR3
Appliation area: *
Release date: 22-Dec-1994
Mode(Normal, Remote etc): Normal Function Module
Update:

Function NUMBER_CHECK 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_CHECK'"Number range: Checks whether number lies in the number interval
  EXPORTING
   NR_RANGE_NR =  "Number range number
   NUMBER =  "number to be checked
   OBJECT =  "Name of number range object
*  SUBOBJECT = ' ' "Value of subobject
*  TOYEAR = '0000' "Value of To-fiscal year
*  NUMERIC_CHECK = ' ' "Numeric check (only for num. intervals)

 IMPORTING
   RETURNCODE =  "Return code

EXCEPTIONS
   INTERVAL_NOT_FOUND = 1    NUMBER_RANGE_NOT_EXTERN = 2    OBJECT_NOT_FOUND = 3 

.

IMPORTING Parameters details for NUMBER_CHECK

NR_RANGE_NR - Number range number

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

NUMBER - number to be checked

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

OBJECT - Name of number range object

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

SUBOBJECT - Value of subobject

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

TOYEAR - Value of To-fiscal year

Data type: INRI-TOYEAR
Default: '0000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

NUMERIC_CHECK - Numeric check (only for num. intervals)

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

EXPORTING Parameters details for NUMBER_CHECK

RETURNCODE - Return code

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

EXCEPTIONS details

INTERVAL_NOT_FOUND - Interval not found

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

NUMBER_RANGE_NOT_EXTERN - Number range is not external

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)

Copy and paste ABAP code example for NUMBER_CHECK 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.

ABAP code using 7.40 inline data declarations to call FM NUMBER_CHECK

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