cancel
Showing results for 
Search instead for 
Did you mean: 

EXIT_SAPLRSBBS_001

Former Member
0 Kudos

Hi experts,

Is there a way that i could debug the code I added in

EXIT_SAPLRSBBS_001, Include ZXRSRU05?

Thanks in advance for the help.

Best Regards,

Rose

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Yup, exactly.

Former Member
0 Kudos

Hi,

Would be kind to let me know how? I tried to use rsrt1 but i was unable to.

My situation is that I have a global view.. which when run behaves like

RRI. The problem is it passes a filter value that is based on the an attribute

of an infoobject. I want this filter value removed.

thanks in advance for the help.

Best Regardss,

Rose

Former Member
0 Kudos

You can enter a breakpoint in the ABAP code.

Use BREAK-POINT or BREAK <userid> right where you want to debug.

Former Member
0 Kudos

Hi,

That is exactly what I did.. maybe this is not used anymor in BI 7?

Maybe i should for for BADi instead? Would you know?

Thanks,

Best Regards,

Rose

Former Member
0 Kudos

The old user exits still work.

However, I noticed that when the Badi is activated, the user exit doesn't work anymore.

Can you check this?

Former Member
0 Kudos

Hi,

I created a badi implemenation for SMOD_RSR00004 but still i wasn't

able to debug. when i tried to run report a report interface from RSRT2

I didn't manage to get to the break point.

Regards,

Rose

Former Member
0 Kudos

That would mean the exit/badi isn't called.

Is everything activated?

Former Member
0 Kudos

Hi,

I have made it work now.. thanks.

Rose

Former Member
0 Kudos

That's great.

Would you mind sharing what the problem was?

In case other persons are struggling with the same issue.

Former Member
0 Kudos

Hi,

We cannot debug jumping from query to view... In jumping.. I meant, query in web with a view created on it, then from the main query execute the view. Doing this will trigger an RRI exit but I cannot debug this in RSRT1.

What I did was I created a dummy query just to test the RRI exit to see if it is working. Then I defined a jump to this query. This gave me the possibility to debug the RRI exit in RSRT1. Doing this enabled me to understand how SAP set values to the RRI parameters and I was able to recode my exit accordingly.

This is an SAP issue.. static filters on infobojects in the main query is not applied to the view if the infobject is not included as free characteristics or not part in the view. Instead, what SAP does is it gets an attribute value of the infoobject with static filter and use the attribute value instead, which makes the result in the view incorrect.

I hope you understand what I meant... anyway if you have questions related to this.. don't hesitate ask.

Best Regards,

Rose

Former Member
0 Kudos

Hi,

sorry, I did not quite get that. I also had the problem that my breakpoints did not react when I used the drilldowns (RRI) in my reports in BEx. When doing so in RSRT, debugging is not a problem. An explanation for me is still missing

Can you elaborate again, what you think the cause is?

Thanks,

Andreas

Former Member
0 Kudos

Hello Werner,

curious - I was using the user exit first in my implementation. Since I could not get my breakpoints to react when debugging, I thought I was in the wrong spot (SE80-Function Group-"XRSR"-EXIT_SAPLRSBBS_001/Include ZXRSRU05 respectively). I researched some more and then found the BadI SMOD_RSR00004/EXIT_SAPLRSBBS_001 alternative and activated it. Had the same "breakpoint is being ignored"-effect first, before trying to run my queries in RSRT.

Now the BadI Implementation works ... and I guess I will not find out, if I could have done without

Best regards,

Andreas

Edited by: Andreas Michligk on Nov 26, 2008 6:48 PM