Scribd
Upload
123 views

CRM Middle Ware Debugging

This document provides instructions for setting breakpoints in order to debug a BADI that populates a structure after a code change. It outlines the following steps: 1) Set the user profile CRM_USER_LEVEL parameter to "9" to enable debugging. 2) Create a follow-up transaction in CRMD_ORDER and make changes to trigger the BADI. 3) Set breakpoints at specific function modules and classes to stop program execution for debugging when the BADI is called.

Uploaded by

souban7-1
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
123 views

CRM Middle Ware Debugging

This document provides instructions for setting breakpoints in order to debug a BADI that populates a structure after a code change. It outlines the following steps: 1) Set the user profile CRM_USER_LEVEL parameter to "9" to enable debugging. 2) Create a follow-up transaction in CRMD_ORDER and make changes to trigger the BADI. 3) Set breakpoints at specific function modules and classes to stop program execution for debugging when the BADI is called.

Uploaded by

souban7-1
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 11

After activating and implementing the BADI and adding the code to populate the structure.

The following document below, describe the technique to set the break-points so that you can
stop the BDoc so that we can debug the BADI.

The following pages will be very helpful to debug the process after the code as been added.

1) First set the user profile. If you do not have the CRM_USER_LEVEL parameter, add it to
your profile with a value of 9..

To summarize the note here are the print screens showing the steps:
1)

Execute CRMD_ORDER and open an existing transaction.

2)

Create the follow-up transaction:

Choose Service Confirmation.

Selecting Service Confirmation gets you the following screen

Next select a doc line number and hit copy

After hitting copy you get the following screen:

Next Choose fast entry tab get the following screen:

After this screen displays, change the Service employee field and employee responsible
fields: See next screen shot.

Next click the service tab get the next screen:

On this screen change the start of work date and the end of work date. The times must differ.
See next screen.

After hitting enter. Click on the in process tab and choose complete:

After choosing complete you get the next screen:

Now before we hit save, to debug the BADI type in /h and hit enter.
After hitting enter and clicking on save and get the following screen:

Next set a break point at function module CRM_UPLOAD_BTMBDOC_START_FLOW. Then


run the transaction by pressing the 'F8' button.
Now set a break point for the class method call:
CL_SMW_MFLOW=> PROCESS_OUTBOUND and enter into the class method.
Now change the value of _dbgmode from space to X.

After setting the value to 'X', hit execute takes you back to the service order.

Now choose the doc flow icon get you the next screen:

Here you should see the outbound BDOC. It is from here were the real debugging starts for
the BADI. To start the debugging double click on the outbound BDOC get you the next
screen:

Now select the line and after selecting the line do a /h.
Next after the /h and hitting enter click on the BDOCMESSAGE and choose reprocess:

After choosing reprocess you get the following screen:

Next set a breakpoint at function module CRM_R3_SERVICECONF_UPLOAD.


After setting this breakpoint click on execute and we will get next screen.

Choosing 'Yes'.
This is the place from where the BADI is called:

Bring the execution to line 309

Set gv_synchronous_call to X..

Now you can enter the ECC through here.


Make sure update debugging is on as it is needed sometimes

You might also like