topic Re: debugging SAP ABAP have problem in Application Development and Automation Discussions

debugging SAP ABAP have problem

Former Member — Wed, 03 Jul 2019 10:39:24 GMT

Dear Team

I have issue, i can not using debugging in SAP ABAP when i run it alway call to default program is RADSHPBOSTATUS ( incorrect with my program). who can support me what problem how to fix it.

as attachment file my program is item 1(ZBILL_PROGRAM) ,how to i switch and call it ??

need-move-item-1.jpg sap-debugging.jpg

Re: debugging SAP ABAP have problem

Sandra_Rossi — Wed, 03 Jul 2019 12:33:07 GMT

I'm not sure to understand, maybe you'd like to debug ZBILL_PROGRAM but the debugger doesn't stop in it?

In the debugger, all programs in blue are "system programs" (i.e. they can be debugged only if you activate the "system debug" cf menu Settings. You may also start the system debug with /hs) or programs executing a not-debuggable system event, like "EVENT SYSTEM-EXIT".

RADSHPBOSTATUS is a program which is used for the type-ahead search, and it should be a system program as explained in note 2003858 - Report RADSHPBOSTATUS is not a system program, so just apply this note.

Re: debugging SAP ABAP have problem

Former Member — Wed, 03 Jul 2019 14:08:53 GMT

Hi daivu2001 ,

Please explain in detail

Regards,

Chandrashekhar

Re: debugging SAP ABAP have problem

Former Member — Thu, 04 Jul 2019 02:48:22 GMT

when I debuging any program example (ZBILL_PROGRAM) press Shift+F5 to debugging , it not call to ZBILL_PROGRAM and call to one stranger program (RADSHPBOSTATUS), I re-installed SAP Guide problem still occur .Kindly solution to fix.

let's me know if you need any thing for this case.

Re: debugging SAP ABAP have problem

Former Member — Thu, 04 Jul 2019 02:54:48 GMT

Are you any solution to call correct my program while debugging.I only open one session.Why it call other stranger program ?session-of-sap.jpg

Re: debugging SAP ABAP have problem

Sandra_Rossi — Thu, 04 Jul 2019 06:24:47 GMT

Nguyen Dai Vu some ABAP statements sometimes call code from system programs implicitly (dynpro/screen statements, write ... to ..., logical database statements, commit work, etc.), just ignore them while debugging. Note: your case corresponds to an issue that SAP has corrected, please apply the patch I mentioned.

Re: debugging SAP ABAP have problem

matt — Thu, 04 Jul 2019 06:56:28 GMT

I find if a parameter has a conversion exit it, I start debugging within the conversion function module. Just go back up a layer until you find you are in your program.

Re: debugging SAP ABAP have problem

matt — Thu, 04 Jul 2019 06:57:40 GMT

Next to where you typed your answer is a bit of text titled "Before answering". It says:

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead,

Next time, use the comment button to reply to an answer or comment.

Re: debugging SAP ABAP have problem

Former Member — Thu, 04 Jul 2019 07:20:14 GMT

The reports RADSHPBOSTATUS, RADSHPBOSWITCH and RADSHUPGRADE are not classified as system programs and may show up while debugging and as sandra has suggested , implement the note 2003858 and it should solve your problem.

Functions from RADSHPBOSWITCH and RADSHUPGRADE are called from RADSHPBOSTATUS and program RADSHPBOPREFLIGHT calls a function from RADSHPBOSTATUS.

Its advised not to remove or change this check else syntax and runtime errors will lead to a unstable system and it would be best advised to implement the note mention.