SAP RSDS_LOAD_LOGGING Function Module for Central log module data loading
RSDS_LOAD_LOGGING is a standard rsds load logging SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Central log module data loading 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 rsds load logging FM, simply by entering the name RSDS_LOAD_LOGGING into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSDS_BACKEND
Program Name: SAPLRSDS_BACKEND
Main Program: SAPLRSDS_BACKEND
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSDS_LOAD_LOGGING 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 'RSDS_LOAD_LOGGING'"Central log module data loading.
EXPORTING
* I_REQUEST = "Request ID (Data Package)
* I_ERROR = "Error
* I_R_DTPLOG = "DTP: Log and Error Object
* I_NO_MORE_DATA = " no more data
* I_EXTERNAL = "Parallel Logging: Derive Idocnummern from DP
* I_NO_MONITOR = "Don't write standard monitoring entries
* I_CRT_LOG = "Write into CRT-Log
* I_IDOC = "Log as Idoc
* I_S_MSG = "Message (ONLY message without anything else)
* I_RQSTATE = "Status of the data selection
* I_AUFRUFER = "Callers
* I_DATAPAKID = "Data Package Number
* I_RECORDS = "Number of selected data records (absolute)
IMPORTING Parameters details for RSDS_LOAD_LOGGING
I_REQUEST - Request ID (Data Package)
Data type: RSREQUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ERROR - Error
Data type: RS_BOOLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_R_DTPLOG - DTP: Log and Error Object
Data type: CL_RSBM_LOG_CURSOR_STEPOptional: Yes
Call by Reference: Yes
I_NO_MORE_DATA - no more data
Data type: RS_BOOLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_EXTERNAL - Parallel Logging: Derive Idocnummern from DP
Data type: RS_BOOLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_NO_MONITOR - Don't write standard monitoring entries
Data type: RS_BOOLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CRT_LOG - Write into CRT-Log
Data type: RS_BOOLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_IDOC - Log as Idoc
Data type: RS_BOOLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_S_MSG - Message (ONLY message without anything else)
Data type: RSPC_S_MSGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RQSTATE - Status of the data selection
Data type: RSRQSTATEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_AUFRUFER - Callers
Data type: RSCALLEROptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATAPAKID - Data Package Number
Data type: RSDATAPIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RECORDS - Number of selected data records (absolute)
Data type: RSNUMRECORDOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSDS_LOAD_LOGGING 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_i_request | TYPE RSREQUID, " | |||
| lv_i_error | TYPE RS_BOOL, " | |||
| lv_i_r_dtplog | TYPE CL_RSBM_LOG_CURSOR_STEP, " | |||
| lv_i_no_more_data | TYPE RS_BOOL, " | |||
| lv_i_external | TYPE RS_BOOL, " | |||
| lv_i_no_monitor | TYPE RS_BOOL, " | |||
| lv_i_crt_log | TYPE RS_BOOL, " | |||
| lv_i_idoc | TYPE RS_BOOL, " | |||
| lv_i_s_msg | TYPE RSPC_S_MSG, " | |||
| lv_i_rqstate | TYPE RSRQSTATE, " | |||
| lv_i_aufrufer | TYPE RSCALLER, " | |||
| lv_i_datapakid | TYPE RSDATAPID, " | |||
| lv_i_records | TYPE RSNUMRECORD. " |
|   CALL FUNCTION 'RSDS_LOAD_LOGGING' "Central log module data loading |
| EXPORTING | ||
| I_REQUEST | = lv_i_request | |
| I_ERROR | = lv_i_error | |
| I_R_DTPLOG | = lv_i_r_dtplog | |
| I_NO_MORE_DATA | = lv_i_no_more_data | |
| I_EXTERNAL | = lv_i_external | |
| I_NO_MONITOR | = lv_i_no_monitor | |
| I_CRT_LOG | = lv_i_crt_log | |
| I_IDOC | = lv_i_idoc | |
| I_S_MSG | = lv_i_s_msg | |
| I_RQSTATE | = lv_i_rqstate | |
| I_AUFRUFER | = lv_i_aufrufer | |
| I_DATAPAKID | = lv_i_datapakid | |
| I_RECORDS | = lv_i_records | |
| . " RSDS_LOAD_LOGGING | ||
ABAP code using 7.40 inline data declarations to call FM RSDS_LOAD_LOGGING
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