SAP BAL_GLB_MSG_CURRENT_HANDLE_GET Function Module for Application Log: Global: Get current message handle
BAL_GLB_MSG_CURRENT_HANDLE_GET is a standard bal glb msg current handle get 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: Global: Get current message handle 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 glb msg current handle get FM, simply by entering the name BAL_GLB_MSG_CURRENT_HANDLE_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SBAL_TOOLBOX
Program Name: SAPLSBAL_TOOLBOX
Main Program:
Appliation area: S
Release date: 26-Apr-1999
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BAL_GLB_MSG_CURRENT_HANDLE_GET 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_GLB_MSG_CURRENT_HANDLE_GET'"Application Log: Global: Get current message handle.
IMPORTING
E_S_MSG_HANDLE = "Message handle
EXCEPTIONS
NO_CURRENT_MSG = 1
EXPORTING Parameters details for BAL_GLB_MSG_CURRENT_HANDLE_GET
E_S_MSG_HANDLE - Message handle
Data type: BALMSGHNDLOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_CURRENT_MSG - There is no current message
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAL_GLB_MSG_CURRENT_HANDLE_GET 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_s_msg_handle | TYPE BALMSGHNDL, " | |||
| lv_no_current_msg | TYPE BALMSGHNDL. " |
|   CALL FUNCTION 'BAL_GLB_MSG_CURRENT_HANDLE_GET' "Application Log: Global: Get current message handle |
| IMPORTING | ||
| E_S_MSG_HANDLE | = lv_e_s_msg_handle | |
| EXCEPTIONS | ||
| NO_CURRENT_MSG = 1 | ||
| . " BAL_GLB_MSG_CURRENT_HANDLE_GET | ||
ABAP code using 7.40 inline data declarations to call FM BAL_GLB_MSG_CURRENT_HANDLE_GET
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