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

Function ACID_XI_APPLICATION_LOG 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 'ACID_XI_APPLICATION_LOG'"Application Log.
EXPORTING
LOG_HEADER = "Application Log: Object Name (Application Code)
LOG_MESSAGES = "Table of Structure
IMPORTING Parameters details for ACID_XI_APPLICATION_LOG
LOG_HEADER - Application Log: Object Name (Application Code)
Data type: BAL_S_LOGOptional: No
Call by Reference: Yes
LOG_MESSAGES - Table of Structure
Data type: ACID_MAPPING_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ACID_XI_APPLICATION_LOG 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_log_header | TYPE BAL_S_LOG, " | |||
| lv_log_messages | TYPE ACID_MAPPING_T. " |
|   CALL FUNCTION 'ACID_XI_APPLICATION_LOG' "Application Log |
| EXPORTING | ||
| LOG_HEADER | = lv_log_header | |
| LOG_MESSAGES | = lv_log_messages | |
| . " ACID_XI_APPLICATION_LOG | ||
ABAP code using 7.40 inline data declarations to call FM ACID_XI_APPLICATION_LOG
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