SAP GRPC_API_ASSMNT_UPDATE Function Module for Update assessment









GRPC_API_ASSMNT_UPDATE is a standard grpc api assmnt 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 assessment 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 assmnt update FM, simply by entering the name GRPC_API_ASSMNT_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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



Function GRPC_API_ASSMNT_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_ASSMNT_UPDATE'"Update assessment
EXPORTING
* I_SESSION_ID = "GRPC unique session ID
I_ASSMNT_ID = "GRPC ID of the individual object
IS_ASSMNT_NEW = "Assessment
* IT_RISK = "Table type of GRPC_S_API_RISK_ASS_DATA
* IT_CR_LIST = "Control Risk Assessment Data
* IT_FACTOR_LIST = "Control Risk Assessment Factor
* IV_NEED_UPDATE_MASTER_DATA = ABAP_FALSE "

IMPORTING
E_RETURN_CODE = "Natural number

TABLES
* ET_MESSAGE = "Table with BAPI Return Information
* IT_QANSWER = "Question answers table
.



IMPORTING Parameters details for GRPC_API_ASSMNT_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_ASSMNT_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_ASSMNT_NEW - Assessment

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

IT_RISK - Table type of GRPC_S_API_RISK_ASS_DATA

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

IT_CR_LIST - Control Risk Assessment Data

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

IT_FACTOR_LIST - Control Risk Assessment Factor

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

IV_NEED_UPDATE_MASTER_DATA -

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

EXPORTING Parameters details for GRPC_API_ASSMNT_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_ASSMNT_UPDATE

ET_MESSAGE - Table with BAPI Return Information

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

IT_QANSWER - Question answers table

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

Copy and paste ABAP code example for GRPC_API_ASSMNT_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_et_message  TYPE STANDARD TABLE OF BAPIRETTAB, "   
lv_i_session_id  TYPE GRPC_API_SESSION_ID, "   
lv_e_return_code  TYPE INT4, "   
lt_it_qanswer  TYPE STANDARD TABLE OF GRPC_T_API_QANSWER, "   
lv_i_assmnt_id  TYPE GRPC_API_OBJECT_ID, "   
lv_is_assmnt_new  TYPE GRPC_S_API_ASSESSMENT, "   
lv_it_risk  TYPE GRPC_T_API_RISK_ASS_DATA, "   
lv_it_cr_list  TYPE GRPC_T_API_CR_ASS_DATA, "   
lv_it_factor_list  TYPE GRPC_T_API_CR_ASS_FACTOR, "   
lv_iv_need_update_master_data  TYPE ABAP_BOOL. "   ABAP_FALSE

  CALL FUNCTION 'GRPC_API_ASSMNT_UPDATE'  "Update assessment
    EXPORTING
         I_SESSION_ID = lv_i_session_id
         I_ASSMNT_ID = lv_i_assmnt_id
         IS_ASSMNT_NEW = lv_is_assmnt_new
         IT_RISK = lv_it_risk
         IT_CR_LIST = lv_it_cr_list
         IT_FACTOR_LIST = lv_it_factor_list
         IV_NEED_UPDATE_MASTER_DATA = lv_iv_need_update_master_data
    IMPORTING
         E_RETURN_CODE = lv_e_return_code
    TABLES
         ET_MESSAGE = lt_et_message
         IT_QANSWER = lt_it_qanswer
. " GRPC_API_ASSMNT_UPDATE




ABAP code using 7.40 inline data declarations to call FM GRPC_API_ASSMNT_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.

 
 
 
 
 
 
 
 
 
DATA(ld_iv_need_update_master_data) = ABAP_FALSE.
 


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!