SAP SQLM_UI_DLP_MAINTAIN Function Module for Create or change a dynamic logpoint

Search SAP Function Modules

SQLM_UI_DLP_MAINTAIN is a standard sqlm ui dlp maintain SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create or change a dynamic logpoint 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 sqlm ui dlp maintain FM, simply by entering the name SQLM_UI_DLP_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.

Function Group: SQLM_UI_LOGPOINT
Program Name: SAPLSQLM_UI_LOGPOINT
Main Program: SAPLSQLM_UI_LOGPOINT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SQLM_UI_DLP_MAINTAIN 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 'SQLM_UI_DLP_MAINTAIN'"Create or change a dynamic logpoint
  EXPORTING
*  IS_ALV_LINE =  "Display structure for dynamic logpoints
*  I_DLP_KEY =  "
*  I_REQ_TYPE =  "SQL Monitor: Request Type
*  I_ROOT_ID =  "SQL Monitor: Request Entry Point (Transaction, etc.)

 IMPORTING
   DIALOGUE_WAS_CANCELED =  "
   LOGPOINT =  "Dynamic logpoint
   NEW_LOGPOINT_CREATED =  "
   LOGPOINT_ALREADY_EXISTED =  "

.

IMPORTING Parameters details for SQLM_UI_DLP_MAINTAIN

IS_ALV_LINE - Display structure for dynamic logpoints

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

I_DLP_KEY -

Data type: CL_DLP_DYNAMIC_LOGPOINT=>TY_KEY
Optional: Yes
Call by Reference: Yes

I_REQ_TYPE - SQL Monitor: Request Type

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

I_ROOT_ID - SQL Monitor: Request Entry Point (Transaction, etc.)

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

EXPORTING Parameters details for SQLM_UI_DLP_MAINTAIN

DIALOGUE_WAS_CANCELED -

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

LOGPOINT - Dynamic logpoint

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

NEW_LOGPOINT_CREATED -

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

LOGPOINT_ALREADY_EXISTED -

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

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

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