SAP GRPC_CLM_EXPORT Function Module for Export data to CLM
GRPC_CLM_EXPORT is a standard grpc clm export SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Export data to CLM 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 clm export FM, simply by entering the name GRPC_CLM_EXPORT into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPC_CLM_API
Program Name: SAPLGRPC_CLM_API
Main Program: SAPLGRPC_CLM_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function GRPC_CLM_EXPORT 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_CLM_EXPORT'"Export data to CLM.
EXPORTING
IV_JOB_ID = "Job ID
IMPORTING
EV_CONTENT = "
EV_HAS_MORE = "Boolean Variable (X=True, Space=False)
ET_BAPIRET = "Return parameter table
IMPORTING Parameters details for GRPC_CLM_EXPORT
IV_JOB_ID - Job ID
Data type: CHAR32Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GRPC_CLM_EXPORT
EV_CONTENT -
Data type: XSTRINGOptional: No
Call by Reference: No ( called with pass by value option)
EV_HAS_MORE - Boolean Variable (X=True, Space=False)
Data type: SAP_BOOLOptional: No
Call by Reference: No ( called with pass by value option)
ET_BAPIRET - Return parameter table
Data type: BAPIRET2_TOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GRPC_CLM_EXPORT 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_iv_job_id | TYPE CHAR32, " | |||
| lv_ev_content | TYPE XSTRING, " | |||
| lv_ev_has_more | TYPE SAP_BOOL, " | |||
| lv_et_bapiret | TYPE BAPIRET2_T. " |
|   CALL FUNCTION 'GRPC_CLM_EXPORT' "Export data to CLM |
| EXPORTING | ||
| IV_JOB_ID | = lv_iv_job_id | |
| IMPORTING | ||
| EV_CONTENT | = lv_ev_content | |
| EV_HAS_MORE | = lv_ev_has_more | |
| ET_BAPIRET | = lv_et_bapiret | |
| . " GRPC_CLM_EXPORT | ||
ABAP code using 7.40 inline data declarations to call FM GRPC_CLM_EXPORT
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