cancel
Showing results for 
Search instead for 
Did you mean: 

Debug BSP in ICF tree /default_host/sap/public/bsp/sap/...

Former Member
0 Kudos
414

Hi,

does anyone know, how to debug a public bsp application?

I'd like to debug my own login bsp, but I'm not able to activate debugging for the system user.

thanks a lot,

Claudia

Accepted Solutions (1)

Accepted Solutions (1)

RieSe
Contributor
0 Kudos

Hello Claudia,

i know this problem, debugging the login application.

You have forgotten something. The application runs under user SAPSYS in client 00, You have to log on in client 00, setting the break-point for user SAPSYS. If it doesn't exist, your system administrator has to create one.

There is no other chance.

Best regards,

Stefan

former_member181879
Active Contributor
0 Kudos

Yes, Stefan is right for the SYSTEM application. Specifically this application is one of the most difficult ones to understand or debug. You must set all break-points twice.

The complete public tree runs as SAPSYS user <b>only in</b> client 000.

brian

Claudia_Dangers
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

the system administrator now has created the user SAPSYS in client 000, but it's not possible to log on with this user. The error message is: wrong user name or password. Any ideas?

thanks, Claudia

Answers (2)

Answers (2)

BernhardSiewert
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Claudia,

the user SAPSYS is not a dialog user. What you need is a "normal" dialog user for client 000. Then you have to logon with this user in client 000 and set the breakpoint for user SAPSYS.

Hth, Bernhard

former_member181879
Active Contributor
0 Kudos

Hallo Claudia,

There is one of two techniques/ideas:

(1) set the break-points in name of the public user. When on a BSP page in SE80, use menu Help>Settings (Hilfsmittel>Einstellungen). You are interested in the tab ABAP-Editor and then Debugging. There you can configure the user for which the breakpoints must be set. Only problem with this is that everyone now runs into your breakpoints.

(2) Run the "public" application under your name. It will only run public if you supply no authentication information. So you close all browsers. Start browser new, and add ?sap-user=X&sap-password=Y onto the URL. Do this only for testing.

Do not forget to assign points. Still <b>today</b>! We need them to pay for a ! Maybe you want also to participate?

brian

Claudia_Dangers
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Brian,

I've already tried out both idea:

(1) It is not possible to activate debugging for the system user "sapsys". The system says, that it does not know this user.

(2) If I run the application under my name, I'm already logged in and therefore the login application behaves in a different way.

Any other ideas?

Former Member
0 Kudos

Hi,

You might try setting a user in transaction SICF under path sap->bc->bsp->sap-><name of your bsp app>.

Then set the debug settings according to Brian's info:

>(1) set the break-points in name of the public user.

> When on a BSP page in SE80, use menu Help-->Settings

>(Hilfsmittel-->Einstellungen). You are interested in the

> tab ABAP-Editor and then Debugging. There you can

> configure the user for which the breakpoints must be

> set.

> <b>Only problem with this is that everyone now runs</b>

> <b>into your breakpoints.</b>

Set the checkbox for IP matching, this will prevent others to run into the breakpoint.

Greetings,

Vincent

Claudia_Dangers
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Vincent,

thanks for the idea, but it's not possible to set a breakpoint for user sapsys.

Regards,

Claudia

Former Member
0 Kudos

Aaargh stupid, if you set a user in SICF then you are logged in as well... sorry for that.

Hmmm I read a little about the custom login pages, but I won't be able to help you further.

Good luck.

Vincent

Former Member
0 Kudos

Hi Claudia,

You can try to create a loop in your application like:


DO.
  IF l_flag EQ 'X'.
    EXIT.
  ENDIF.
ENDDO.

and obtaining program debug from SM50.

It isn't a clean solution, but it should work...

Dany