SAP BAL_DB_DELETE Function Module for Application Log: Database: Delete Logs from Database

Search SAP Function Modules

BAL_DB_DELETE is a standard bal db delete 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: Database: Delete Logs from Database 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 db delete FM, simply by entering the name BAL_DB_DELETE into the relevant SAP transaction such as SE37 or SE38.

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

Function BAL_DB_DELETE 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_DB_DELETE'"Application Log: Database: Delete Logs from Database
  EXPORTING
*  I_T_LOGS_TO_DELETE =  "Alternative 1: Table of log headers
*  I_T_LOG_HANDLE =  "Alternative 2: Table of log handles
*  I_T_LOGNUMBER =  "Alternative 3: Table of log numbers
*  I_CLIENT = SY-MANDT "Client for I_T_LOGNUMBER
*  I_IN_UPDATE_TASK = ' ' "In UPDATE TASK?
*  I_WITH_COMMIT_WORK = ' ' "DB_COMMIT after 100 logs
*  I_PACKAGE_SIZE = 100 "Package Size for DB_COMMIT

EXCEPTIONS
   NO_LOGS_SPECIFIED = 1 

.

IMPORTING Parameters details for BAL_DB_DELETE

I_T_LOGS_TO_DELETE - Alternative 1: Table of log headers

Data type: BALHDR_T
Optional: Yes
Call by Reference: Yes

I_T_LOG_HANDLE - Alternative 2: Table of log handles

Data type: BAL_T_LOGH
Optional: Yes
Call by Reference: Yes

I_T_LOGNUMBER - Alternative 3: Table of log numbers

Data type: BAL_T_LOGN
Optional: Yes
Call by Reference: Yes

I_CLIENT - Client for I_T_LOGNUMBER

Data type: SY-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_IN_UPDATE_TASK - In UPDATE TASK?

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

I_WITH_COMMIT_WORK - DB_COMMIT after 100 logs

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

I_PACKAGE_SIZE - Package Size for DB_COMMIT

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

EXCEPTIONS details

NO_LOGS_SPECIFIED - No logs specified

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

Copy and paste ABAP code example for BAL_DB_DELETE 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_DB_DELETE

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