SAP TABLE_RANGE_INPUT Function Module for Fill the Views Selection Conditions Table in Dialog Box

Search SAP Function Modules

TABLE_RANGE_INPUT is a standard table range input SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fill the Views Selection Conditions Table in Dialog Box 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 table range input FM, simply by entering the name TABLE_RANGE_INPUT 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_INPUT 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_INPUT'"Fill the Views Selection Conditions Table in Dialog Box
  EXPORTING
   TABLE =  "Name of the table/structure to be edited
*  NO_INPUT = ' ' "Flag: X display only
*  NO_SAVING_AS_VARIANT = 'X' "Flag: X can not be saved as variant
*  OC_INST =  "Organizational Criteria for Row Authorization
*  SUPPRESS_WA_POPUP = ' ' "Flag: Suppress 'Specify Work Area' Dialog Box
*  SHOW_SELECTION_POPUP = ' ' "Flag: Display 'Specify Work Area' Dialog Box, If Necessary

TABLES
   SELLIST =  "Selection conditions table
   X_HEADER =  "Control block table for the entire
   X_NAMTAB =  "View fields control block table

EXCEPTIONS
   CANCELLED_BY_USER = 1    NO_INPUT = 2 

.

IMPORTING Parameters details for TABLE_RANGE_INPUT

TABLE - Name of the table/structure to be edited

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

NO_INPUT - Flag: X display only

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

NO_SAVING_AS_VARIANT - Flag: X can not be saved as variant

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

OC_INST - Organizational Criteria for Row Authorization

Data type: CL_VIEWFIELDS_ORG_CRIT
Optional: Yes
Call by Reference: Yes

SUPPRESS_WA_POPUP - Flag: Suppress 'Specify Work Area' Dialog Box

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

SHOW_SELECTION_POPUP - Flag: Display 'Specify Work Area' Dialog Box, If Necessary

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

TABLES Parameters details for TABLE_RANGE_INPUT

SELLIST - Selection conditions table

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

X_HEADER - Control block table for the entire

Data type: VIMDESC
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)

EXCEPTIONS details

CANCELLED_BY_USER - Cancel by F12

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

NO_INPUT - Flag: X display only

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

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

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