SAP APPL_LOG_WRITE_MESSAGE_PARAMS Function Module for Application log: Enter message with parameters









APPL_LOG_WRITE_MESSAGE_PARAMS is a standard appl log write message params 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: Enter message with parameters 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 appl log write message params FM, simply by entering the name APPL_LOG_WRITE_MESSAGE_PARAMS into the relevant SAP transaction such as SE37 or SE38.

Function Group: SLG0
Program Name: SAPLSLG0
Main Program: SAPLSLG0
Appliation area: S
Release date: 22-Dec-1994
Mode(Normal, Remote etc): Normal Function Module
Update:



Function APPL_LOG_WRITE_MESSAGE_PARAMS 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 'APPL_LOG_WRITE_MESSAGE_PARAMS'"Application log: Enter message with parameters
EXPORTING
* OBJECT = ' ' "Object name
* SUBOBJECT = ' ' "Sub-object name
* LOG_HANDLE = ' ' "
MESSAGE = "Message
* UPDATE_OR_INSERT = 'U' "Change (U) or insert (I) message flag

IMPORTING
E_MSG_HANDLE = "

TABLES
PARAMETERS = "Parameters and corresponding values

EXCEPTIONS
OBJECT_NOT_FOUND = 1 SUBOBJECT_NOT_FOUND = 2 NO_TEXT_AND_NO_USEREXIT = 3
.



IMPORTING Parameters details for APPL_LOG_WRITE_MESSAGE_PARAMS

OBJECT - Object name

Data type: BALHDR-OBJECT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SUBOBJECT - Sub-object name

Data type: BALHDR-SUBOBJECT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

LOG_HANDLE -

Data type: BALHDR-LOG_HANDLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

MESSAGE - Message

Data type: BALMI
Optional: No
Call by Reference: No ( called with pass by value option)

UPDATE_OR_INSERT - Change (U) or insert (I) message flag

Data type:
Default: 'U'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for APPL_LOG_WRITE_MESSAGE_PARAMS

E_MSG_HANDLE -

Data type: BALMSGHNDL
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for APPL_LOG_WRITE_MESSAGE_PARAMS

PARAMETERS - Parameters and corresponding values

Data type: SPAR
Optional: No
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)

NO_TEXT_AND_NO_USEREXIT - neither text module nor user exit specified

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for APPL_LOG_WRITE_MESSAGE_PARAMS 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, "   SPACE
lt_parameters  TYPE STANDARD TABLE OF SPAR, "   
lv_e_msg_handle  TYPE BALMSGHNDL, "   
lv_object_not_found  TYPE BALMSGHNDL, "   
lv_subobject  TYPE BALHDR-SUBOBJECT, "   SPACE
lv_subobject_not_found  TYPE BALHDR, "   
lv_log_handle  TYPE BALHDR-LOG_HANDLE, "   SPACE
lv_no_text_and_no_userexit  TYPE BALHDR, "   
lv_message  TYPE BALMI, "   
lv_update_or_insert  TYPE BALMI. "   'U'

  CALL FUNCTION 'APPL_LOG_WRITE_MESSAGE_PARAMS'  "Application log: Enter message with parameters
    EXPORTING
         OBJECT = lv_object
         SUBOBJECT = lv_subobject
         LOG_HANDLE = lv_log_handle
         MESSAGE = lv_message
         UPDATE_OR_INSERT = lv_update_or_insert
    IMPORTING
         E_MSG_HANDLE = lv_e_msg_handle
    TABLES
         PARAMETERS = lt_parameters
    EXCEPTIONS
        OBJECT_NOT_FOUND = 1
        SUBOBJECT_NOT_FOUND = 2
        NO_TEXT_AND_NO_USEREXIT = 3
. " APPL_LOG_WRITE_MESSAGE_PARAMS




ABAP code using 7.40 inline data declarations to call FM APPL_LOG_WRITE_MESSAGE_PARAMS

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).
DATA(ld_object) = ' '.
 
 
 
 
"SELECT single SUBOBJECT FROM BALHDR INTO @DATA(ld_subobject).
DATA(ld_subobject) = ' '.
 
 
"SELECT single LOG_HANDLE FROM BALHDR INTO @DATA(ld_log_handle).
DATA(ld_log_handle) = ' '.
 
 
 
DATA(ld_update_or_insert) = 'U'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!