SAP BAL_LOG_MSG_CHANGE Function Module for Application Log: Log: Message: Change









BAL_LOG_MSG_CHANGE is a standard bal log msg change 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: Log: Message: Change 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 bal log msg change FM, simply by entering the name BAL_LOG_MSG_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SBAL
Program Name: SAPLSBAL
Main Program: SAPLSBAL
Appliation area: S
Release date: 26-Apr-1999
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BAL_LOG_MSG_CHANGE 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 'BAL_LOG_MSG_CHANGE'"Application Log: Log: Message: Change
EXPORTING
I_S_MSG_HANDLE = "Message handle
I_S_MSG = "Message data

EXCEPTIONS
LOG_NOT_FOUND = 1 MSG_INCONSISTENT = 2 MSG_NOT_FOUND = 3
.



IMPORTING Parameters details for BAL_LOG_MSG_CHANGE

I_S_MSG_HANDLE - Message handle

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

I_S_MSG - Message data

Data type: BAL_S_MSG
Optional: No
Call by Reference: Yes

EXCEPTIONS details

LOG_NOT_FOUND - Log not found

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

MSG_INCONSISTENT - Message inconsistent

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

MSG_NOT_FOUND - Message not found

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

Copy and paste ABAP code example for BAL_LOG_MSG_CHANGE 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_not_found  TYPE STRING, "   
lv_i_s_msg_handle  TYPE BALMSGHNDL, "   
lv_i_s_msg  TYPE BAL_S_MSG, "   
lv_msg_inconsistent  TYPE BAL_S_MSG, "   
lv_msg_not_found  TYPE BAL_S_MSG. "   

  CALL FUNCTION 'BAL_LOG_MSG_CHANGE'  "Application Log: Log: Message: Change
    EXPORTING
         I_S_MSG_HANDLE = lv_i_s_msg_handle
         I_S_MSG = lv_i_s_msg
    EXCEPTIONS
        LOG_NOT_FOUND = 1
        MSG_INCONSISTENT = 2
        MSG_NOT_FOUND = 3
. " BAL_LOG_MSG_CHANGE




ABAP code using 7.40 inline data declarations to call FM BAL_LOG_MSG_CHANGE

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



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!