DEBUGGING_IMPOSSIBLE

There is a main transaction (let's call it AA). I have a transaction that can be called from within this transaction (BB). When a button is pushed within BB, it calls another transaction (CC) that can also be called from AA. BB sends a BDCDATA table to CC so that it feeds data to screens the user doesn't need to see. The problem is however many times I call CC through BB, when I exit AA, it goes back to BB that many times before it finally exits the entire program. Also, when I try to debug to figure out what is happening, when I push the button that calls CC from BB, I get this error: "Runtime error DEBUGGING_IMPOSSIBLE has occurred." Can anyone make sense of this?

How do you leave from a transaction? Do you use LEAVE PROGRAM or Exit? How you call a transaction in your program when Debugging Impossible occurs?
"AA" uses PERFORM DESTROY_OBJECTS USING SY-DYNNR.
          LEAVE PROGRAM.
"BB" uses LEAVE PROGRAM.
"CC" uses PERFORM DESTROY_OBJECTS USING SY-DYNNR.
          LEAVE TO SCREEN 0.
The Debugging_Impossible occurs at this command:
CALL TRANSACTION 'AA' USING BDCDATA MODE 'E'.
I forgot to mention that to get to transaction CC, I have to call AA and go through a few screens and fill them with data.

Similar Messages

Dump -- DEBUGGING_IMPOSSIBLE

Hi,
In our ECC6.0 system, We are receing dump:
Runtime Errors         DEBUGGING_IMPOSSIBLE
Short text
    ABAP programs cannot currently be debugged.
What happened?
    The running program is supposed to be debugged by the ABAP Debugger (for
     example, by a BREAK-POINT statement).
    Since you are in a production system or client (table T000), you can
    only jump to the ABAP Debugger if the work process is able to switch to
    debugging mode.
    The maximum number or work processes in debugging mode has already been
    reached, however, which means that debugging is not currently possible.
I checked in system only one work process is running in debug mode.Still I am getting this dump.
Please suggest root cause of this error and how can we come out of this issue, Do we have any parameter which defines maximim number of work process for debugging mode.
Please suggest.
Regards,
Shivam Mittal

Hi,
By default only one workprocess will allow to debug . if you want you can increase with the following parameter.
rdisp/wpdbug_max_no
Read this note
Note 726719 - ABAP debugging in production system / DEBUGGING_IMPOSSIBLE
Thanks
Siva

DEBUGGING_IMPOSSIBLE in ECC IDES EhP4

Hello All,
I would like to ask for your expert opinions on how i should set up my parameter rdisp/wpdbug_max_no in the sandbox client of my newly installed ECC IDES EhP4.
I am currently encountering a lot of ABAP Runtime error DEBUGGING_IMPOSSIBLE. This system is used as a playground as well as a training environment, so there are a lot of ABAPers that usually use this system simultaneously.
I 've read from SAP Note 726719 - ABAP debugging in production system / DEBUGGING_IMPOSSIBLE that in a prod client, the number of work processes reserved for the debugging is half the number of dialog processes. But since this is a sandbox client, the number of workprocess for debugging is controlled and limited by the parameter rdisp/wpdbug_max_no.
Its current value in my system is 1 (which is the default). I am thinking of setting this to half og my dialog processes but I'm a bit hesitant of what its impact is going to be once I do this and a lot of users simulataneously use the debugger.
I have the following work processes:
Dialog: 15
Background: 7
Update (V1): 3
Update (V2): 1
Enqueue: 1
Spool: 3
Please advise. I am using Oracle10g as my database and Windows Server 2003 as operating system.
Thanks a lot!
Cha Cha
Moderator message: not directly related to ABAP development, please have a look in the SAP Netweaver Admin or Performance forums.
Edited by: Thomas Zloch on May 31, 2011 9:30 AM

Hi friends,
now the error is comming as below.
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(DB) ERROR: DDL statement failed
(DROP VIEW "/ISDFPS/V_BI_TGT")
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE VIEW "/ISDFPS/V_BI_TGT" ( "OTYPE" , "TASK" , "LANGU" , "SHORT" , "STEXT" ) AS SELECT T0001."OTYPE", T0001."OBJID", T0001."LANGU", T0001."SHORT", T0001."STEXT" FROM "HRS1000" T0001 WHERE ( T0001."OTYPE" = 'TS' OR T0001."OTYPE" = 'WS' OR T0001."OTYPE" = 'TG' ))
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(DB) INFO: disconnected from DB
D:\usr\sap\IDS\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\IDS\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20111116181302
regards
Ganesh Datt Tiwari

Runtime error while opeinig window in Web Dynport- ABAP

Hello,
We are having a strange scenario in abap web Dynpro. we are using POWL and users are getting run time error while opening a pop up window for enter some information with the message "nstance of the view W_POP_UP already exists in component". The issue is, this run time error is giving for only users. We tried to debug the issue in their system as well but it is giving run time error with "Debugging_impossible". We alredy tried by clearing the widow instance, but o luck
Could you please help me out in this situation, its really critical and also I did browse before posting this thread, but no use.
Appreciate your <priority normalized by moderator> response......
Regards,
Kumar
Edited by: Vinod Kumar on Jul 25, 2011 12:11 PM

Hi Lakshman,
From the above, I think you are creating an instance of a view. But this instance is already available.
Check your code where this error is occurring while calling lo_window_manager->create_window( ) method?
if so check for the initialness of the view 'W_POP_UP' before this method.
if W_POP_UP is not bound.
W_POP_UP = lo_window_manager->create_window( ).
endif.
Regards,
Ravi

DEBUGGING_IMPOSSIBLE

Similar Messages

Maybe you are looking for