Steps To Stop Debugger at ELM BADI CRM - MKTLIST - BADI From Web UI Screen

This document outlines 9 steps to debug the BADICRM_MKTLIST_BADI from the SAP Web UI screen when developing External List Management (ELM). The steps include checking the number of servers, opening the function module CRM_MKTLIST_WORKFLOW_DEBUG in transaction SE37 on each server and placing external breakpoints, keeping sessions open on each server, adding a debugging parameter, executing the upload from the Web UI screen, and debugging the BADI methods with additional breakpoints. Key points are to place breakpoints on all servers, keep sessions open on all servers, and remove the debugging parameter once complete.

Uploaded by

rajesh98765

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

68 views4 pages

Steps To Stop Debugger at ELM BADI CRM - MKTLIST - BADI From Web UI Screen

Uploaded by

rajesh98765

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

You are on page 1/ 4

Steps to stop debugger at ELM BADI CRM_MKTLIST_BADI from Web UI Screen

In most of the External List Management (ELM) developments, we need to work with BADICRM_MKTLIST_BADI. As
a developer we need to debug the BADI implementation to check the data which flows from Web UI screen at run
time and proceed with the development. Debugging this BADI is bit tricky.

Debugging steps:

1. Execute SAP Transaction SM51 and check the number of servers in your SAP system.

For example, our SAP system has two servers viz dc1-20 and dc1-22.

This is a very important step. We never know which server gets triggered when we execute the Web UI. So we need
to put break point in both servers as shown in steps below.
2. Execute Transaction SE37 and open
FM CRM_MKTLIST_WORKFLOW_DEBUG in one server say dc1-20. Put one External breakpoint(not the normal
breakpoint as we will execute from Web UI).
3. Execute SE37 again and open the same FM
CRM_MKTLIST_WORKFLOW_DEBUG in second server say dc1-22 and put one more External breakpoint in
another line.
4. Please note, you need to keep at least one session
open in each server dc1-20 and dc1-22.

5. Go to your user parameters (Transaction code SU3) and insert a Parameter with
ID CRM_DEBUG_CODE and value as MKTLIST.
6. Please do not open more than 5 sessions in total (1
session you will need for WebUI). The debugger will open one more session. So need to have one extra session to
be available.
7. Now go to Web UI screen. 8. Upload the ELM file and
execute. The debugger will stop at the Function ModuleCRM_MKTLIST_WORKFLOW_DEBUG.

9. Now debug normally or press F8. It will take you to the BADI Methods. Please note, you need to have breakpoint in
the BADI Methods as well.

Points to remember

1) Put External breakpoint in all servers in FM CRM_MKTLIST_WORKFLOW_DEBUG.
2) Keep at least one session open in all the servers.
3) Do not open more than 5 sessions in total.
4) And dont forget to put debugger in the BADI method you want to look and remove the parameter
CRM_DEBUG_CODE in your user setting once your debugging is finished.