SAP GRPC_API_USERNAME_QUERY Function Module for to get the list of the users from the system

Search SAP Function Modules

GRPC_API_USERNAME_QUERY is a standard grpc api username query SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for to get the list of the users from the system 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 username query FM, simply by entering the name GRPC_API_USERNAME_QUERY into the relevant SAP transaction such as SE37 or SE38.

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

Function GRPC_API_USERNAME_QUERY 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_USERNAME_QUERY'"to get the list of the users from the system
  EXPORTING
*  I_SEARCH_PATTERN =  "Search pattern
*  I_FULL =  "Boolean
*  IV_SESSION_ID =  "GRPC unique session ID

 IMPORTING
   E_RETURN_CODE =  "Natural number

TABLES
*  ET_USERNAME =  "The list of the users in the system
*  ET_MESSAGE =  "Error Messages

.

IMPORTING Parameters details for GRPC_API_USERNAME_QUERY

I_SEARCH_PATTERN - Search pattern

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

I_FULL - Boolean

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

IV_SESSION_ID - GRPC unique session ID

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

EXPORTING Parameters details for GRPC_API_USERNAME_QUERY

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_USERNAME_QUERY

ET_USERNAME - The list of the users in the system

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

ET_MESSAGE - Error Messages

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

Copy and paste ABAP code example for GRPC_API_USERNAME_QUERY 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.

ABAP code using 7.40 inline data declarations to call FM GRPC_API_USERNAME_QUERY

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