Transaction SAAB

[Former Member]

Hi.

I created a check-point group in one client of dev system.

I specified "To break" for Break-points.

It is working correctly in that client.

But in the other client, it is not being triggered. I went into SAAB and saw that status there is "Inactive".

When it is a workbench object, it should behave in the same fashion in all clients, isn't it?

If not, how am i supposed to activate the check-group in the other client? We cannot change workbench objects in that client.

Thanks in adv.

[Former Member]

Hi,

Update to the update: Okay, I think I found the evidence that supports my original answer below. The online <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/96/2997420722d26ae10000000a155106/frameset.htm">help</a> states that "The context limits the validity of the activation setting either to a particular user or a particular application server... The context specification is <b>client-dependent</b>." By the way, the complete authorization path can be found in class CL_AAB_ID method AUTHORITY_CHECK.

<b>Disregard this paragraph (see above for the most recent update and see below for the orginal answer):</b> <i>Updated answer: I'm second guessing myself now... Table AAB_ID_ACT is not client-dependent. But the evidence still makes me think my answer may still hold true. Anyone else have a more definitive answer out there?</i>

<u>My Original Answer</u>:

I don't think the checkpoint activation <u>settings</u> are considered to be workbench objects. Probably the only way you will be able to activate in your other client is to get the proper authorization for changing the checkpoint activation settings in that client via transaction SAAB (authorization object S_DEVELOP, object type ACID for checkpoint group, activity 02... verify with your security folks).

This is not exactly related to your question, but the following information from the online help for SAAB gives a clue to the nature of the activation settings vs. the checkpoint group:

<i>"Unlike the checkpoint group itself, the activation settings for a checkpoint group cannot be transported. When a newly created group is transported, it is inactive in the target system by default. If an existing group is changed, the activation status in the target system remains unchanged."</i>

Best Regards,

James Gaddis

Message was edited by: James Gaddis