SAP GRPC_API_SESSION_VOLUME Function Module for Define data detail to be read from HR database









GRPC_API_SESSION_VOLUME is a standard grpc api session volume SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Define data detail to be read from HR database 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 session volume FM, simply by entering the name GRPC_API_SESSION_VOLUME into the relevant SAP transaction such as SE37 or SE38.

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



Function GRPC_API_SESSION_VOLUME 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_SESSION_VOLUME'"Define data detail to be read from HR database
  EXPORTING
*  I_SESSION_ID =  "GRPC unique session ID
*  I_SET_NONE =  "Only ID and DESCR
*  I_SET_SHORT =  "NONE + standard attributes
*  I_SET_FULL =  "SHORT + Long text attributes

 IMPORTING
   E_IS_NONE =  "GRPC Flag Char 1
   E_IS_SHORT =  "GRPC Flag Char 1
   E_IS_FULL =  "GRPC Flag Char 1
   E_RETURN_CODE =  "Natural number

TABLES
*  ET_MESSAGE =  "Table with BAPI Return Information
.



IMPORTING Parameters details for GRPC_API_SESSION_VOLUME

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_SET_NONE - Only ID and DESCR

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

I_SET_SHORT - NONE + standard attributes

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

I_SET_FULL - SHORT + Long text attributes

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

EXPORTING Parameters details for GRPC_API_SESSION_VOLUME

E_IS_NONE - GRPC Flag Char 1

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

E_IS_SHORT - GRPC Flag Char 1

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

E_IS_FULL - GRPC Flag Char 1

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

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_SESSION_VOLUME

ET_MESSAGE - Table with BAPI Return Information

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

Copy and paste ABAP code example for GRPC_API_SESSION_VOLUME 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:
lv_e_is_none  TYPE GRPC_FLAG, "   
lt_et_message  TYPE STANDARD TABLE OF BAPIRETTAB, "   
lv_i_session_id  TYPE GRPC_API_SESSION_ID, "   
lv_e_is_short  TYPE GRPC_FLAG, "   
lv_i_set_none  TYPE GRPC_FLAG, "   
lv_e_is_full  TYPE GRPC_FLAG, "   
lv_i_set_short  TYPE GRPC_FLAG, "   
lv_i_set_full  TYPE GRPC_FLAG, "   
lv_e_return_code  TYPE INT4. "   

  CALL FUNCTION 'GRPC_API_SESSION_VOLUME'  "Define data detail to be read from HR database
    EXPORTING
         I_SESSION_ID = lv_i_session_id
         I_SET_NONE = lv_i_set_none
         I_SET_SHORT = lv_i_set_short
         I_SET_FULL = lv_i_set_full
    IMPORTING
         E_IS_NONE = lv_e_is_none
         E_IS_SHORT = lv_e_is_short
         E_IS_FULL = lv_e_is_full
         E_RETURN_CODE = lv_e_return_code
    TABLES
         ET_MESSAGE = lt_et_message
. " GRPC_API_SESSION_VOLUME




ABAP code using 7.40 inline data declarations to call FM GRPC_API_SESSION_VOLUME

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!