SAP GRPC_API_TESTLOG_UPDATE Function Module for Update testing









GRPC_API_TESTLOG_UPDATE is a standard grpc api testlog update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update testing 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 grpc api testlog update FM, simply by entering the name GRPC_API_TESTLOG_UPDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: GRPC_API_TESTLOG
Program Name: SAPLGRPC_API_TESTLOG
Main Program: SAPLGRPC_API_TESTLOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function GRPC_API_TESTLOG_UPDATE 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 'GRPC_API_TESTLOG_UPDATE'"Update testing
  EXPORTING
*  I_SESSION_ID =  "GRPC unique session ID
   I_TESTLOG_ID =  "GRPC ID of the individual object
   IS_TESTLOG_DATA_CHANGED =  "Assessment
*  IV_NEED_TLLOG =  "need testlog action log flag
*  IV_OWNER =  "User Name

 IMPORTING
   E_RETURN_CODE =  "Natural number

TABLES
*  IT_AC_RESULT =  "Table type for Automated test result
*  IT_TESTSTEP_CHANGED =  "Table type for test step response
*  ET_MESSAGE =  "Table with BAPI Return Information
.



IMPORTING Parameters details for GRPC_API_TESTLOG_UPDATE

I_SESSION_ID - GRPC unique session ID

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

I_TESTLOG_ID - GRPC ID of the individual object

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

IS_TESTLOG_DATA_CHANGED - Assessment

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

IV_NEED_TLLOG - need testlog action log flag

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

IV_OWNER - User Name

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

EXPORTING Parameters details for GRPC_API_TESTLOG_UPDATE

E_RETURN_CODE - Natural number

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

TABLES Parameters details for GRPC_API_TESTLOG_UPDATE

IT_AC_RESULT - Table type for Automated test result

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

IT_TESTSTEP_CHANGED - Table type for test step response

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

ET_MESSAGE - Table with BAPI Return Information

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

Copy and paste ABAP code example for GRPC_API_TESTLOG_UPDATE 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_it_ac_result  TYPE STANDARD TABLE OF GRPC_T_API_AC_TESTRESULT, "   
lv_i_session_id  TYPE GRPC_API_SESSION_ID, "   
lv_e_return_code  TYPE INT4, "   
lv_i_testlog_id  TYPE GRPC_API_OBJECT_ID, "   
lt_it_teststep_changed  TYPE STANDARD TABLE OF GRPC_T_API_TESTSTEP, "   
lt_et_message  TYPE STANDARD TABLE OF BAPIRETTAB, "   
lv_is_testlog_data_changed  TYPE GRPC_S_API_TESTLOG, "   
lv_iv_need_tllog  TYPE SAP_BOOL, "   
lv_iv_owner  TYPE UNAME. "   

  CALL FUNCTION 'GRPC_API_TESTLOG_UPDATE'  "Update testing
    EXPORTING
         I_SESSION_ID = lv_i_session_id
         I_TESTLOG_ID = lv_i_testlog_id
         IS_TESTLOG_DATA_CHANGED = lv_is_testlog_data_changed
         IV_NEED_TLLOG = lv_iv_need_tllog
         IV_OWNER = lv_iv_owner
    IMPORTING
         E_RETURN_CODE = lv_e_return_code
    TABLES
         IT_AC_RESULT = lt_it_ac_result
         IT_TESTSTEP_CHANGED = lt_it_teststep_changed
         ET_MESSAGE = lt_et_message
. " GRPC_API_TESTLOG_UPDATE




ABAP code using 7.40 inline data declarations to call FM GRPC_API_TESTLOG_UPDATE

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



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!