SAP SBLM_DELETE_LOGS Function Module for Blocklist Monitor: Delete Log Tables









SBLM_DELETE_LOGS is a standard sblm delete logs SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Blocklist Monitor: Delete Log Tables 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 sblm delete logs FM, simply by entering the name SBLM_DELETE_LOGS into the relevant SAP transaction such as SE37 or SE38.

Function Group: SBLM_REMOTE_API
Program Name: SAPLSBLM_REMOTE_API
Main Program: SAPLSBLM_REMOTE_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SBLM_DELETE_LOGS 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 'SBLM_DELETE_LOGS'"Blocklist Monitor: Delete Log Tables
EXPORTING
I_CLIENT_ID = "Blacklist Monitor: Enable Concurrent Usages of IF_SBLM_API
I_TIMESTAMP = "UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun)

IMPORTING
E_STATE = "Blacklist Monitor: State on Server

EXCEPTIONS
NO_AUTHORIZATION = 1 LOCK_ERROR = 2 BAD_PARAMETER = 3
.



IMPORTING Parameters details for SBLM_DELETE_LOGS

I_CLIENT_ID - Blacklist Monitor: Enable Concurrent Usages of IF_SBLM_API

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

I_TIMESTAMP - UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun)

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

EXPORTING Parameters details for SBLM_DELETE_LOGS

E_STATE - Blacklist Monitor: State on Server

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

EXCEPTIONS details

NO_AUTHORIZATION -

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

LOCK_ERROR -

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

BAD_PARAMETER -

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

Copy and paste ABAP code example for SBLM_DELETE_LOGS 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_state  TYPE SBLM_S_SYSTEM_STATE, "   
lv_i_client_id  TYPE SBLM_CLIENT_ID, "   
lv_no_authorization  TYPE SBLM_CLIENT_ID, "   
lv_lock_error  TYPE SBLM_CLIENT_ID, "   
lv_i_timestamp  TYPE TIMESTAMPL, "   
lv_bad_parameter  TYPE TIMESTAMPL. "   

  CALL FUNCTION 'SBLM_DELETE_LOGS'  "Blocklist Monitor: Delete Log Tables
    EXPORTING
         I_CLIENT_ID = lv_i_client_id
         I_TIMESTAMP = lv_i_timestamp
    IMPORTING
         E_STATE = lv_e_state
    EXCEPTIONS
        NO_AUTHORIZATION = 1
        LOCK_ERROR = 2
        BAD_PARAMETER = 3
. " SBLM_DELETE_LOGS




ABAP code using 7.40 inline data declarations to call FM SBLM_DELETE_LOGS

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!