User Specific Break Point

[Former Member]

Hello Experts,

Is there a way to create a break point specific to user?

Thanks.

[former_member194669]

Looking for this???

if sy-uname eq 'XXXXX'.
   break-point.
endif.

a®

[Former Member]

No

[Former Member]

use

BREAK <user id>.

[Former Member]

No sure what version you are on but I suggest using checkpoints - see transaction SAAB. These are activated per user on demand (even in a productive system). There is plenty of documentation on them but for a started look at the help on syntax BREAK-POINT ID <xyz>

Pete

[Former Member]

break-point.

Will work if its a custome ddevlopemnt but for satndard SAP code it wont work. You would need to go for

enhancement impimentaton for standard sap code.

[Former Member]

Thanks for the responses. Sorry for not being eloborative about my requirement. Users have an issue with code in a BADI on transaction MSC2N in PRD System. I don't have access to MSC2N (and should not) in PRD and the users don't have access to that program code/degubber (obviously). As MSC2N is a widely used transaction, I wanted to set up the break point for a user in PRD, so we can debug and find out the issue. Hope this gives clear idea about the issue.

Thanks Again.

PS: I don't want to create a break-point programatically.

Edited by: SAM K on Mar 31, 2009 1:32 PM

[former_member376453]

I think in there are two kind of break point, external and session. External break point is user specific.

KUntal

[former_member194669]

I don't have access to MSC2N (and should not) in PRD and the users don't have access to that program code/degubber (obviously). As MSC2N is a widely used transaction, I wanted to set up the break point for a user in PRD, so we can debug and find out the issue

If users don't debugging access, in that case what will be the point to put a break-point ??? (Obviously u don't have access also)

My suggestion is get a debug (DISPLAY) access in PRD for a day.

or

Recreate the same scenrio in other unit testing enviornement and make debug there

a®

[Former Member]

This message was moderated.

[matt]

External breakpoints can be set for other users - but they have to have debug authority. In order to debug, then either you need authority to run the transaction, or the user needs debug authority. No way round this. If there's a business requirement, and it's cost the company money, eventually someone will authorise it.

matt

[Former Member]

In that case as it is a BADi then do as I suggested and create a checkpoint (activatable break-point) in SAAB and insert the corresponding statement in the BADi (BREAK-POINT ID <xyz>). The checkpoint remains dormant until it is activated for a specific user. Once debugging has finished then de-activate the checkpoint again in SAAB.

I 'litter' all my code with checkpoints as a 'good practice' methodology for this same reason!

Edited by: Pete Devereux on Mar 31, 2009 9:50 PM

[Former Member]

you can user

break <<your user name>>

[Former Member]

Hi Pete,

I am using 46c version and SAAB transaction does not exist in our system. Is there a tcode that is equivalent of this?

Thanks.

[former_member156446]

use [this link |http://help.sap.com/saphelp_nw70/helpdata/EN/b0/940640555ae369e10000000a155106/content.htm]to place a ext. break-point and run the Tr.

[Debanjan_75]

What if the username contains a dot?

[Former Member]

Hi Sam,

Afraid there is nothing like SAAB in your release. I would of suggested memory inspector to try any work it out from the data at runtime but if my memory serves me correct this was only available on a >620 platform.

Therefore the only non-programatic solutions to you have already been discussed:

- Recreate the data in another environment that can be debugged. I know this is often hard or very hard given the data quality in test/qa/training environments. This will largely depend upon each organisation.

- Have a role in production that will give debug access in display mode as mentioned above. To clarify just in case - display mode debugging will not allow you to change any values. This role will can be assigned temorarily when needed. Most organisations that I have worked have taken this sensible approach - even pharma and aerospace industries. It's probably not for you to argue this but the head of SAP support in your organisation.

As someone has mentioned before - something has to give. Either data needs to be re-created (e.g. by regular copies of production into a pre-prod system (v.costly) or access is given in a controled manner for a small period of time). The flip side to this is that if there is a programatic change to correct the error then someone would have to recreated the scenario in a qa environment to approve the transport request to prod!

Pete

[Former Member]

Thanks all for the responses.