SAP TABLE_RANGE_CHECK Function Module for









TABLE_RANGE_CHECK is a standard table range check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 table range check FM, simply by entering the name TABLE_RANGE_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: SVIX
Program Name: SAPLSVIX
Main Program: SAPLSVIX
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function TABLE_RANGE_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 'TABLE_RANGE_CHECK'"
  EXPORTING
   TABNAME =  "Table Name
   DDIC =  "Also take requirements from DDIC i
   ENTRY =  "entry to be checked
   ENTRY_TEXT =  "
*  IGNORE_BLANK_SUBSETFIELDS = 'J' "ignore initial subset fields (Y/N)
   KEY =  "ONLY take key fields into account

TABLES
   SELLIST =  "Selection conditions table
   X_NAMTAB =  "View fields control block table
   X_HEADER =  "Control Block Structure for View Maintenance

EXCEPTIONS
   ENTRY_NOT_FITS = 1    NO_VALUE_FOR_SUBSET_IDENT = 2
.



IMPORTING Parameters details for TABLE_RANGE_CHECK

TABNAME - Table Name

Data type: TABNAME
Optional: No
Call by Reference: Yes

DDIC - Also take requirements from DDIC i

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

ENTRY - entry to be checked

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

ENTRY_TEXT -

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

IGNORE_BLANK_SUBSETFIELDS - ignore initial subset fields (Y/N)

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

KEY - ONLY take key fields into account

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

TABLES Parameters details for TABLE_RANGE_CHECK

SELLIST - Selection conditions table

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

X_NAMTAB - View fields control block table

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

X_HEADER - Control Block Structure for View Maintenance

Data type: VIMDESC
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ENTRY_NOT_FITS - Entry does not meet the selection

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

NO_VALUE_FOR_SUBSET_IDENT - no default value for 'SUBSET' field

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

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

DATA:
lt_sellist  TYPE STANDARD TABLE OF VIMSELLIST, "   
lv_tabname  TYPE TABNAME, "   
lv_entry_not_fits  TYPE TABNAME, "   
lv_ddic  TYPE TABNAME, "   
lt_x_namtab  TYPE STANDARD TABLE OF VIMNAMTAB, "   
lv_no_value_for_subset_ident  TYPE VIMNAMTAB, "   
lv_entry  TYPE ANY, "   
lt_x_header  TYPE STANDARD TABLE OF VIMDESC, "   
lv_entry_text  TYPE ANY, "   
lv_ignore_blank_subsetfields  TYPE ANY, "   'J'
lv_key  TYPE ANY. "   

  CALL FUNCTION 'TABLE_RANGE_CHECK'  "
    EXPORTING
         TABNAME = lv_tabname
         DDIC = lv_ddic
         ENTRY = lv_entry
         ENTRY_TEXT = lv_entry_text
         IGNORE_BLANK_SUBSETFIELDS = lv_ignore_blank_subsetfields
         KEY = lv_key
    TABLES
         SELLIST = lt_sellist
         X_NAMTAB = lt_x_namtab
         X_HEADER = lt_x_header
    EXCEPTIONS
        ENTRY_NOT_FITS = 1
        NO_VALUE_FOR_SUBSET_IDENT = 2
. " TABLE_RANGE_CHECK




ABAP code using 7.40 inline data declarations to call FM TABLE_RANGE_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.

 
 
 
 
 
 
 
 
 
DATA(ld_ignore_blank_subsetfields) = 'J'.
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!