SAP GRPC_API_PERS_PRINT_SET Function Module for Report personalization - store general setting
GRPC_API_PERS_PRINT_SET is a standard grpc api pers print set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Report personalization - store general setting 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 pers print set FM, simply by entering the name GRPC_API_PERS_PRINT_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPC_API_REPORT
Program Name: SAPLGRPC_API_REPORT
Main Program: SAPLGRPC_API_REPORT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function GRPC_API_PERS_PRINT_SET 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_PERS_PRINT_SET'"Report personalization - store general setting.
EXPORTING
IS_PRINT = "Printer settings
* I_USER = SY-UNAME "User Name
TABLES
* ET_MESSAGE = "Table with BAPI Return Information
IMPORTING Parameters details for GRPC_API_PERS_PRINT_SET
IS_PRINT - Printer settings
Data type: GRPC_S_REP_PRINT_SETTINGSOptional: No
Call by Reference: No ( called with pass by value option)
I_USER - User Name
Data type: SY-UNAMEDefault: SY-UNAME
Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for GRPC_API_PERS_PRINT_SET
ET_MESSAGE - Table with BAPI Return Information
Data type: BAPIRETTABOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GRPC_API_PERS_PRINT_SET 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_is_print | TYPE GRPC_S_REP_PRINT_SETTINGS, " | |||
| lt_et_message | TYPE STANDARD TABLE OF BAPIRETTAB, " | |||
| lv_i_user | TYPE SY-UNAME. " SY-UNAME |
|   CALL FUNCTION 'GRPC_API_PERS_PRINT_SET' "Report personalization - store general setting |
| EXPORTING | ||
| IS_PRINT | = lv_is_print | |
| I_USER | = lv_i_user | |
| TABLES | ||
| ET_MESSAGE | = lt_et_message | |
| . " GRPC_API_PERS_PRINT_SET | ||
ABAP code using 7.40 inline data declarations to call FM GRPC_API_PERS_PRINT_SET
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.| "SELECT single UNAME FROM SY INTO @DATA(ld_i_user). | ||||
| DATA(ld_i_user) | = SY-UNAME. | |||
Search for further information about these or an SAP related objects