SAP VE_IV_SET_RANGE Function Module for NOTRANSL: Speichert Rangetabelle als globales Datum

Search SAP Function Modules

VE_IV_SET_RANGE is a standard ve iv set range SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Speichert Rangetabelle als globales Datum 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 ve iv set range FM, simply by entering the name VE_IV_SET_RANGE into the relevant SAP transaction such as SE37 or SE38.

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

Function VE_IV_SET_RANGE 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 'VE_IV_SET_RANGE'"NOTRANSL: Speichert Rangetabelle als globales Datum
  EXPORTING
*  T_RANGE_BELNR =  "Range Table Document Numbers
*  T_RANGE_GJAHR =  "Range Table Fiscal Year

.

IMPORTING Parameters details for VE_IV_SET_RANGE

T_RANGE_BELNR - Range Table Document Numbers

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

T_RANGE_GJAHR - Range Table Fiscal Year

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

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

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