SAP CALO_LOG_INIT_MEMORY Function Module for Initialize Log Interface
CALO_LOG_INIT_MEMORY is a standard calo log init memory SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initialize Log Interface 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 calo log init memory FM, simply by entering the name CALO_LOG_INIT_MEMORY into the relevant SAP transaction such as SE37 or SE38.
Function Group: CALO
Program Name: SAPLCALO
Main Program:
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CALO_LOG_INIT_MEMORY 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 'CALO_LOG_INIT_MEMORY'"Initialize Log Interface.
EXPORTING
* ONLY_MESSAGES = ' ' "
* CONTINUE_LOG = ' ' "
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for CALO_LOG_INIT_MEMORY
ONLY_MESSAGES -
Data type: CAPIFLAG-MSG_INITDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CONTINUE_LOG -
Data type: CAPIFLAG-CONT_LOGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR - Error in Application Log
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CALO_LOG_INIT_MEMORY 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_error | TYPE STRING, " | |||
| lv_only_messages | TYPE CAPIFLAG-MSG_INIT, " SPACE | |||
| lv_continue_log | TYPE CAPIFLAG-CONT_LOG. " SPACE |
|   CALL FUNCTION 'CALO_LOG_INIT_MEMORY' "Initialize Log Interface |
| EXPORTING | ||
| ONLY_MESSAGES | = lv_only_messages | |
| CONTINUE_LOG | = lv_continue_log | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " CALO_LOG_INIT_MEMORY | ||
ABAP code using 7.40 inline data declarations to call FM CALO_LOG_INIT_MEMORY
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 MSG_INIT FROM CAPIFLAG INTO @DATA(ld_only_messages). | ||||
| DATA(ld_only_messages) | = ' '. | |||
| "SELECT single CONT_LOG FROM CAPIFLAG INTO @DATA(ld_continue_log). | ||||
| DATA(ld_continue_log) | = ' '. | |||
Search for further information about these or an SAP related objects