topic Re: SAP Console Debugging in Application Development and Automation Discussions

SAP Console Debugging

Former Member — Wed, 22 Aug 2007 14:10:51 GMT

Hi.

Is it possible to debug the program while running the transaction under SAP Console?

Set External Breakpoint don't work.

Darley.

Re: SAP Console Debugging

RichHeilman — Wed, 22 Aug 2007 14:17:38 GMT

No it isn't. You would need to debug your program using SAPgui, I do understand that the problem may not be visible on the SAPgui, which is why you want to do it from sapconsole, but this is not possible. What exactly is the problem that you are having which is leading you to debug from console.

Regards,

Rich Heilman

Re: SAP Console Debugging

Former Member — Wed, 22 Aug 2007 14:32:20 GMT

I got a exception raized by standard program

In ST22:

<i>Exception condition "CNTL_ERROR" raised.

Termination occurred in the ABAP program "CL_GUI_DOCKING_CONTAINER======CP" -

in "CONSTRUCTOR".

The main program was "SAPMV50A ".

In the source code you have the termination point in line 90

of the (Include) program "CL_GUI_DOCKING_CONTAINER======CM001".

</i>


CALL METHOD DOCK_AT_internal
  EXPORTING
    SIDE   = SIDE
    notify = space
  EXCEPTIONS
    CNTL_SYSTEM_ERROR = 1
    CNTL_ERROR = 2.

CASE SY-SUBRC.
  WHEN 0.
  WHEN 1.
    RAISE CNTL_SYSTEM_ERROR.
  WHEN 2.
>>>>>    RAISE CNTL_ERROR.
  WHEN OTHERS.
    RAISE CNTL_ERROR.
ENDCASE.

In Sap gui works fine.

Re: SAP Console Debugging

RichHeilman — Wed, 22 Aug 2007 14:47:02 GMT

Yes, please remember that when running sapconsole, it is a stripped down version of the SAPgui, which means all none essential controls are stripped off, including all of the enjoy control stuff that we love so much. A docking container is part of this control framework, and any transaction which uses these controls can not be ran in sapconsole. This is the reason for your error. The only solution is to of course use the non-enjoy transaction instead. So say if you are using ME22N, you would simply use ME22. What transaction are you using?

Regards,

Rich Heilman

Re: SAP Console Debugging

Former Member — Wed, 22 Aug 2007 14:56:55 GMT

VL02N.

Tanks Rich.

Re: SAP Console Debugging

RichHeilman — Wed, 22 Aug 2007 15:00:25 GMT

Right, so try using VL02.

Regards,

Rich Heilman

Re: SAP Console Debugging

Former Member — Wed, 08 Jul 2009 13:12:34 GMT

Hi,

we are facing a problem that seems to have many common points with this one described in the thread:

We have created a web service based on a function module that modify an

entry sheet using a call transaction based on the transaction ML81.

Executing the web service by web service navigator it has a different

behavior (failure) against executing the relative function module by the

transaction ECC SE37 (success).

In detail:

TEST 1: Web Service navigator execution:

we fill some fields of the web service navigator screen interface with

our test data. When we exceed 22 services in the entry sheet adding the

23th service and saving, the service doesn't insert the last one neither the others

we would like to be added (24th, 25th..... etc.).

we get an error related to the call transaction of the ML81:

As follows is the the MESSTAB structure returned by ML81:

messtabMsgnr[1] = 343

messtabMsgtyp[1] = S

messtabMsgv1[1] = cursor field ESLL-TBTWR1(17)2 not in dynpro.

messtabTcode[1] = ML81

messtabMsgnr[2] = 349

messtabMsgtyp[2] = S

messtabMsgv1[2] = the field ESLL-MENGE1(17)2 not in dynpro SAPLMLSP3 02104.

messtabTcode[2] = ML81

TEST 2: Funtion module execution by transaction SE37:

in this case, using same test data and adding the 23th service, the

function module have a correct behavior updating the entry sheet.

it seem to be an error related to the batch input procedure, but the question is; why does the error is showed only using web service navigator?

Thanks in advance

Luca