SAP G_VSR_VALIDATION_CALL Function Module for RuleMan: Validation Call









G_VSR_VALIDATION_CALL is a standard g vsr validation call SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RuleMan: Validation Call 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 g vsr validation call FM, simply by entering the name G_VSR_VALIDATION_CALL into the relevant SAP transaction such as SE37 or SE38.

Function Group: GBL5
Program Name: SAPLGBL5
Main Program:
Appliation area: G
Release date: 20-Jul-1999
Mode(Normal, Remote etc): Normal Function Module
Update:



Function G_VSR_VALIDATION_CALL 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 'G_VSR_VALIDATION_CALL'"RuleMan: Validation Call
EXPORTING
* CALLUP_POINT = ' ' "
* TAB_DATA8 = ' ' "Table Structure to Import 8
* TAB_DATA9 = ' ' "Table Structure to Import 9
VALIDATION = "Name of Validation
VALUSER = "ID of Validation User
* ZEILE = ' ' "Reference Line for Message Handler
* TABNAME = ' ' "Table Structure to Import 4
* TAB_DATA1 = ' ' "Table Structure to Import 1
* TAB_DATA2 = ' ' "Table Structure to Import 10
* TAB_DATA3 = ' ' "Table Structure to Import 3
* TAB_DATA4 = ' ' "Table Structure to Import 2
* TAB_DATA5 = ' ' "Table Structure to Import 5
* TAB_DATA6 = ' ' "Table Structure to Import 6
* TAB_DATA7 = ' ' "Table Structure to Import 7

IMPORTING
MSG_SEVERITY = "Maximum Severity of the Messages Displayed.

TABLES
TABNAMES = "List of Tables/Mem_Ids. Used if Tabname Blank.

EXCEPTIONS
ABEND_MESSAGE = 1 ERRORMESSAGE = 2 NOT_FOUND = 3
.



IMPORTING Parameters details for G_VSR_VALIDATION_CALL

CALLUP_POINT -

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

TAB_DATA8 - Table Structure to Import 8

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

TAB_DATA9 - Table Structure to Import 9

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

VALIDATION - Name of Validation

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

VALUSER - ID of Validation User

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

ZEILE - Reference Line for Message Handler

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

TABNAME - Table Structure to Import 4

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

TAB_DATA1 - Table Structure to Import 1

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

TAB_DATA2 - Table Structure to Import 10

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

TAB_DATA3 - Table Structure to Import 3

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

TAB_DATA4 - Table Structure to Import 2

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

TAB_DATA5 - Table Structure to Import 5

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

TAB_DATA6 - Table Structure to Import 6

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

TAB_DATA7 - Table Structure to Import 7

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

EXPORTING Parameters details for G_VSR_VALIDATION_CALL

MSG_SEVERITY - Maximum Severity of the Messages Displayed.

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

TABLES Parameters details for G_VSR_VALIDATION_CALL

TABNAMES - List of Tables/Mem_Ids. Used if Tabname Blank.

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

EXCEPTIONS details

ABEND_MESSAGE - Use ONLY if You Want to Handle 'A' Messages Yourself

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

ERRORMESSAGE - Use ONLY if You Want to Handle 'E' Messages Yourself

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

NOT_FOUND - Not found

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

Copy and paste ABAP code example for G_VSR_VALIDATION_CALL 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_tabnames  TYPE STANDARD TABLE OF RGBL5, "   
lv_callup_point  TYPE GB31-VALEVENT, "   SPACE
lv_msg_severity  TYPE GB931-VALSEVERE, "   
lv_abend_message  TYPE GB931, "   
lv_tab_data8  TYPE GB931, "   SPACE
lv_tab_data9  TYPE GB931, "   SPACE
lv_validation  TYPE GB93-VALID, "   
lv_valuser  TYPE GB03-VALUSER, "   
lv_zeile  TYPE GB03, "   SPACE
lv_tabname  TYPE RGBL5-TABNAME, "   SPACE
lv_errormessage  TYPE RGBL5, "   
lv_not_found  TYPE RGBL5, "   
lv_tab_data1  TYPE RGBL5, "   SPACE
lv_tab_data2  TYPE RGBL5, "   SPACE
lv_tab_data3  TYPE RGBL5, "   SPACE
lv_tab_data4  TYPE RGBL5, "   SPACE
lv_tab_data5  TYPE RGBL5, "   SPACE
lv_tab_data6  TYPE RGBL5, "   SPACE
lv_tab_data7  TYPE RGBL5. "   SPACE

  CALL FUNCTION 'G_VSR_VALIDATION_CALL'  "RuleMan: Validation Call
    EXPORTING
         CALLUP_POINT = lv_callup_point
         TAB_DATA8 = lv_tab_data8
         TAB_DATA9 = lv_tab_data9
         VALIDATION = lv_validation
         VALUSER = lv_valuser
         ZEILE = lv_zeile
         TABNAME = lv_tabname
         TAB_DATA1 = lv_tab_data1
         TAB_DATA2 = lv_tab_data2
         TAB_DATA3 = lv_tab_data3
         TAB_DATA4 = lv_tab_data4
         TAB_DATA5 = lv_tab_data5
         TAB_DATA6 = lv_tab_data6
         TAB_DATA7 = lv_tab_data7
    IMPORTING
         MSG_SEVERITY = lv_msg_severity
    TABLES
         TABNAMES = lt_tabnames
    EXCEPTIONS
        ABEND_MESSAGE = 1
        ERRORMESSAGE = 2
        NOT_FOUND = 3
. " G_VSR_VALIDATION_CALL




ABAP code using 7.40 inline data declarations to call FM G_VSR_VALIDATION_CALL

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.

 
"SELECT single VALEVENT FROM GB31 INTO @DATA(ld_callup_point).
DATA(ld_callup_point) = ' '.
 
"SELECT single VALSEVERE FROM GB931 INTO @DATA(ld_msg_severity).
 
 
DATA(ld_tab_data8) = ' '.
 
DATA(ld_tab_data9) = ' '.
 
"SELECT single VALID FROM GB93 INTO @DATA(ld_validation).
 
"SELECT single VALUSER FROM GB03 INTO @DATA(ld_valuser).
 
DATA(ld_zeile) = ' '.
 
"SELECT single TABNAME FROM RGBL5 INTO @DATA(ld_tabname).
DATA(ld_tabname) = ' '.
 
 
 
DATA(ld_tab_data1) = ' '.
 
DATA(ld_tab_data2) = ' '.
 
DATA(ld_tab_data3) = ' '.
 
DATA(ld_tab_data4) = ' '.
 
DATA(ld_tab_data5) = ' '.
 
DATA(ld_tab_data6) = ' '.
 
DATA(ld_tab_data7) = ' '.
 


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!