SAP CACS_LOG_SET_DATA Function Module for Commission: Supplying Application Log Subscreen with Data
CACS_LOG_SET_DATA is a standard cacs log set data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Commission: Supplying Application Log Subscreen with Data 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 cacs log set data FM, simply by entering the name CACS_LOG_SET_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS_BUFFERLOG
Program Name: SAPLCACS_BUFFERLOG
Main Program: SAPLCACS_BUFFERLOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CACS_LOG_SET_DATA 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 'CACS_LOG_SET_DATA'"Commission: Supplying Application Log Subscreen with Data.
EXPORTING
I_LOG_HANDLE = "Application Log: Log Handle Table
IMPORTING
E_PROGRAM = "Calling Program
E_DYNNR = "Calling Screen
EXCEPTIONS
NO_LOGS_SPECIFIED = 1 LOG_NOT_FOUND = 2 SEVERE_ERROR = 3 INTERNAL_ERROR = 4 PROFILE_INCONSISTENT = 5
IMPORTING Parameters details for CACS_LOG_SET_DATA
I_LOG_HANDLE - Application Log: Log Handle Table
Data type: BAL_T_LOGHOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CACS_LOG_SET_DATA
E_PROGRAM - Calling Program
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_DYNNR - Calling Screen
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_LOGS_SPECIFIED - No Log Specified
Data type:Optional: No
Call by Reference: Yes
LOG_NOT_FOUND - Log not found
Data type:Optional: No
Call by Reference: Yes
SEVERE_ERROR - Critical Error
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR - Internal Error
Data type:Optional: No
Call by Reference: Yes
PROFILE_INCONSISTENT - Profile Inconsistent
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CACS_LOG_SET_DATA 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_e_program | TYPE STRING, " | |||
| lv_i_log_handle | TYPE BAL_T_LOGH, " | |||
| lv_no_logs_specified | TYPE BAL_T_LOGH, " | |||
| lv_e_dynnr | TYPE BAL_T_LOGH, " | |||
| lv_log_not_found | TYPE BAL_T_LOGH, " | |||
| lv_severe_error | TYPE BAL_T_LOGH, " | |||
| lv_internal_error | TYPE BAL_T_LOGH, " | |||
| lv_profile_inconsistent | TYPE BAL_T_LOGH. " |
|   CALL FUNCTION 'CACS_LOG_SET_DATA' "Commission: Supplying Application Log Subscreen with Data |
| EXPORTING | ||
| I_LOG_HANDLE | = lv_i_log_handle | |
| IMPORTING | ||
| E_PROGRAM | = lv_e_program | |
| E_DYNNR | = lv_e_dynnr | |
| EXCEPTIONS | ||
| NO_LOGS_SPECIFIED = 1 | ||
| LOG_NOT_FOUND = 2 | ||
| SEVERE_ERROR = 3 | ||
| INTERNAL_ERROR = 4 | ||
| PROFILE_INCONSISTENT = 5 | ||
| . " CACS_LOG_SET_DATA | ||
ABAP code using 7.40 inline data declarations to call FM CACS_LOG_SET_DATA
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