cancel
Showing results for 
Search instead for 
Did you mean: 

Breakpoints are ignored in BAdi /SAPAPO/CDPS_MATGEN

Former Member
0 Kudos

Dear all,

We try to use BAdi /SAPAPO/CDPS_MATGEN to influence the creation of Setup Group/Setup Matrix.

We activated an implementation of the BAdi and set breakpoints (also hard in the coding).

But the Debugger does not stop in this BAdi at all. We are using transaction /SAPAPO/CDPS_MATGEN for testing.

What should We take care about concerning this BAdi?

Should we use some other transaction to reach that debugging starts at the breakpoints?

We also found some problem which sounds quite similar: http://scn.sap.com/thread/3275780

Thank you very much and kindest regards,

Eva

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Eva,

I have experienced the same pbm while trying to debug the same BADI, I was able to reach the BADI using the classic debugger. Did you tried the classic debugging ?

Also Please make sure you have all the prerequisties maintained for this BADI . Below are the t.code where you need to make the required settings.

And most importantly you have to make sure you select the generation method as via BADI as shown below

Hope this helps. and for more information u can find in below links

http://help.sap.com/saphelp_scm50/helpdata/en/bd/505f42076c6255e10000000a155106/content.htm

http://help.sap.com/saphelp_ewm70/helpdata/en/35/6f5a42091de32ce10000000a1550b0/content.htm

Rgds,

Kiru

Former Member
0 Kudos

Hi Kuru, Hi Babu,

Thank you both very much for your helful answers 😉

Kindest regards,

Eva

Answers (1)

Answers (1)

babu_kilari4
Active Contributor
0 Kudos

Hello Eva,

Usually in these cases, I do a where used list for the method where the code has been written and I set an "external break-point" in the parent Function Module or include that is calling this BADI. This will tell me whether the component is getting triggered and the problem is only with the BADI trigger.


Please try it out.

Babu Kilari