SAP Function Modules

comments icon Comments

UMG_TEST_DRIVER_METHOD_CALL SAP Function module - Remote test driver call







UMG_TEST_DRIVER_METHOD_CALL is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name UMG_TEST_DRIVER_METHOD_CALL into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: UMG_TEST_DRIVER
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM UMG_TEST_DRIVER_METHOD_CALL - UMG TEST DRIVER METHOD CALL 





CALL FUNCTION 'UMG_TEST_DRIVER_METHOD_CALL' "Remote test driver call
  EXPORTING
    im_scenario =               " umgaszen      Test scenario
    im_settings =               " umgasettings  Settings in one string
    im_name =                   " umgamname     Method name
    im_param =                  " umgaparam     Method parameter
    im_step =                   " umgastep      Step in test scenario
    im_rcexpected =             " int4          Natural number
  IMPORTING
    ex_rc =                     " i             Whole Number with +/- Sign (-2.147.483.648 .. 2.147.483.647)
    ex_log =                    " umgttestlog   Log of test driver
    .  "  UMG_TEST_DRIVER_METHOD_CALL

ABAP code example for Function Module UMG_TEST_DRIVER_METHOD_CALL





The ABAP code below is a full code listing to execute function module UMG_TEST_DRIVER_METHOD_CALL including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_ex_rc    TYPE I
,
ld_ex_log    TYPE UMGTTESTLOG
.




DATA(ld_im_scenario) = 'Check type of data required'.

DATA(ld_im_settings) = 'Check type of data required'.

DATA(ld_im_name) = 'Check type of data required'.

DATA(ld_im_param) = 'Check type of data required'.

DATA(ld_im_step) = 'Check type of data required'.

DATA(ld_im_rcexpected) = 'Check type of data required'.
.

CALL FUNCTION 'UMG_TEST_DRIVER_METHOD_CALL'
  EXPORTING
    im_scenario =                ld_im_scenario
    im_settings =                ld_im_settings
    im_name =                    ld_im_name
    im_param =                   ld_im_param
    im_step =                    ld_im_step
    im_rcexpected =              ld_im_rcexpected
  IMPORTING
    ex_rc =                      ld_ex_rc
    ex_log =                     ld_ex_log
    .  "  UMG_TEST_DRIVER_METHOD_CALL

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_ex_rc  TYPE I ,
ld_im_scenario  TYPE UMGASZEN ,
ld_ex_log  TYPE UMGTTESTLOG ,
ld_im_settings  TYPE UMGASETTINGS ,
ld_im_name  TYPE UMGAMNAME ,
ld_im_param  TYPE UMGAPARAM ,
ld_im_step  TYPE UMGASTEP ,
ld_im_rcexpected  TYPE INT4 .




ld_im_scenario = 'Check type of data required'.
ld_im_settings = 'Check type of data required'.
ld_im_name = 'Check type of data required'.
ld_im_param = 'Check type of data required'.
ld_im_step = 'Check type of data required'.
ld_im_rcexpected = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name UMG_TEST_DRIVER_METHOD_CALL or its description.


   
 

UMG_TEST_DRIVER_METHOD_CALL - Remote test driver call
UMG_TEST_DRIVER_GET_VERSIONS - Get versions of expected results
UMG_TEST_DRIVER_GET_SYSINFO - Get some information on a remote system
UMG_TEST_DRIVER_EXP_IMP - Remote function call for R3load testing
UMG_TEST_DRIVER_EXISTENCE - Check the existence of a scenario
UMG_TEST_DRIVER_CREATE_ANTABS - Create alternate nametabs