SAP BAL_LOG_EXCEPTION_ADD Function Module for Application Log: Log: Add Exception

Search SAP Function Modules

BAL_LOG_EXCEPTION_ADD is a standard bal log exception add 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: Add Exception 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 exception add FM, simply by entering the name BAL_LOG_EXCEPTION_ADD into the relevant SAP transaction such as SE37 or SE38.

Function Group: SBAL
Program Name: SAPLSBAL
Main Program: SAPLSBAL
Appliation area:
Release date: 27-Jun-2002
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BAL_LOG_EXCEPTION_ADD 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_EXCEPTION_ADD'"Application Log: Log: Add Exception
  EXPORTING
*  I_LOG_HANDLE =  "Log handle
   I_S_EXC =  "Exception data

 IMPORTING
   E_S_MSG_HANDLE =  "Message handle
   E_MSG_WAS_LOGGED =  "Message collected
   E_MSG_WAS_DISPLAYED =  "Message output

EXCEPTIONS
   LOG_NOT_FOUND = 1    MSG_INCONSISTENT = 2    LOG_IS_FULL = 3 

.

IMPORTING Parameters details for BAL_LOG_EXCEPTION_ADD

I_LOG_HANDLE - Log handle

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

I_S_EXC - Exception data

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

EXPORTING Parameters details for BAL_LOG_EXCEPTION_ADD

E_S_MSG_HANDLE - Message handle

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

E_MSG_WAS_LOGGED - Message collected

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

E_MSG_WAS_DISPLAYED - Message output

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

EXCEPTIONS details

LOG_NOT_FOUND - Log not found

Data type:
Optional: No
Call by Reference: Yes

MSG_INCONSISTENT - Message inconsistent

Data type:
Optional: No
Call by Reference: Yes

LOG_IS_FULL - Message number 999999 reached. Log is full

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BAL_LOG_EXCEPTION_ADD 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.

ABAP code using 7.40 inline data declarations to call FM BAL_LOG_EXCEPTION_ADD

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