SAP LOG_WRITE_COLLECTED_MESSAGES Function Module for NOTRANSL: Gesammelte Meldungen in Anwendungslog übernehmen
LOG_WRITE_COLLECTED_MESSAGES is a standard log write collected messages SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Gesammelte Meldungen in Anwendungslog übernehmen 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 log write collected messages FM, simply by entering the name LOG_WRITE_COLLECTED_MESSAGES into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMX_PM_LOG
Program Name: SAPLCMX_PM_LOG
Main Program:
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LOG_WRITE_COLLECTED_MESSAGES 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 'LOG_WRITE_COLLECTED_MESSAGES'"NOTRANSL: Gesammelte Meldungen in Anwendungslog übernehmen.
EXPORTING
OBJECT = "
* SUBOBJECT = ' ' "Name of application log subobject
EXCEPTIONS
OBJECT_NOT_FOUND = 1 SUBOBJECT_NOT_FOUND = 2
IMPORTING Parameters details for LOG_WRITE_COLLECTED_MESSAGES
OBJECT -
Data type: BALHDR-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
SUBOBJECT - Name of application log subobject
Data type: BALHDR-SUBOBJECTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJECT_NOT_FOUND - Object not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SUBOBJECT_NOT_FOUND - Subobject not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LOG_WRITE_COLLECTED_MESSAGES 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_object | TYPE BALHDR-OBJECT, " | |||
| lv_object_not_found | TYPE BALHDR, " | |||
| lv_subobject | TYPE BALHDR-SUBOBJECT, " SPACE | |||
| lv_subobject_not_found | TYPE BALHDR. " |
|   CALL FUNCTION 'LOG_WRITE_COLLECTED_MESSAGES' "NOTRANSL: Gesammelte Meldungen in Anwendungslog übernehmen |
| EXPORTING | ||
| OBJECT | = lv_object | |
| SUBOBJECT | = lv_subobject | |
| EXCEPTIONS | ||
| OBJECT_NOT_FOUND = 1 | ||
| SUBOBJECT_NOT_FOUND = 2 | ||
| . " LOG_WRITE_COLLECTED_MESSAGES | ||
ABAP code using 7.40 inline data declarations to call FM LOG_WRITE_COLLECTED_MESSAGES
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 OBJECT FROM BALHDR INTO @DATA(ld_object). | ||||
| "SELECT single SUBOBJECT FROM BALHDR INTO @DATA(ld_subobject). | ||||
| DATA(ld_subobject) | = ' '. | |||
Search for further information about these or an SAP related objects