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

Function DPICB_LOG_SAVE_ALL 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 'DPICB_LOG_SAVE_ALL'"Save all logs.
EXPORTING
IV_LOG_HANDLE = "Application Log: Log Handle
* IT_REMOVE_MSG_CLASS = "Message Classes not to be added
IMPORTING Parameters details for DPICB_LOG_SAVE_ALL
IV_LOG_HANDLE - Application Log: Log Handle
Data type: BALLOGHNDLOptional: No
Call by Reference: Yes
IT_REMOVE_MSG_CLASS - Message Classes not to be added
Data type: RSDSSELOPT_TOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for DPICB_LOG_SAVE_ALL 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_log_handle | TYPE BALLOGHNDL, " | |||
| lv_it_remove_msg_class | TYPE RSDSSELOPT_T. " |
|   CALL FUNCTION 'DPICB_LOG_SAVE_ALL' "Save all logs |
| EXPORTING | ||
| IV_LOG_HANDLE | = lv_iv_log_handle | |
| IT_REMOVE_MSG_CLASS | = lv_it_remove_msg_class | |
| . " DPICB_LOG_SAVE_ALL | ||
ABAP code using 7.40 inline data declarations to call FM DPICB_LOG_SAVE_ALL
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