topic Re: ECATT problems with abap objects. in Application Development and Automation Discussions

ECATT problems with abap objects.

Former Member — Fri, 31 Jan 2014 13:45:07 GMT

Hello!

There is a limit in 36 abap blocks in ECATT. After reaching this limit it implicitly executing "rescon" command which erases all abap blocks shared memory and Im loosing my created abap objects (references). Even if Im using option "target system = NONE", Im facing with this problem.

I tried to use "Abap objects" pattens to create my objects, but they are erased too (suppose it is the same inline abap).

Is there any way to save references after recon in ECATT?

Regards,

Sergey.

Re: ECATT problems with abap objects.

AjayHS — Thu, 06 Feb 2014 10:21:57 GMT

Hello,

To the best of my knowledge there is no limit, however would like to understand are you using all the 36 abap blocks in a single ecatt script ? if so try to modularize your script.

Also you can store the connection id's into a variable which you can pass to different script so as to execute your scripts in a single session.

Thanks,

Re: ECATT problems with abap objects.

Former Member — Wed, 12 Feb 2014 07:00:26 GMT

Hello.

My single script consists of several (quite lot actually) subscripts, which called by REF command.

The script is executed locally. And yes, Im using more than 36 abap subpools, but they are spread around subscripts.

Re: ECATT problems with abap objects.

AjayHS — Thu, 13 Feb 2014 06:22:41 GMT

Hello,

As mentioned in your other post i am assuming your issue is resolved post upgrade of SAPGUI from 7.2 to 7.3 , please let me know if not to further analyze the issue.

Thanks,

Re: ECATT problems with abap objects.

Former Member — Thu, 13 Feb 2014 06:29:26 GMT

Well, this is a strange advice. I don't think that upgrading a frontend application would lead to increasing limit of abap subpools or somehow.

Re: ECATT problems with abap objects.

AjayHS — Thu, 13 Feb 2014 06:40:10 GMT

Ok, i mistoke it for your other issue Random screen refresh during ECATT replay which you mentioned was resolved due to GUI upgrade.

Coming back to this issue, execute your script by including break points to reach that REF where your script fails.

Appreciate if you could include screen shot or details of the error message in your log, little more details will help to identify the root cause.

Re: ECATT problems with abap objects.

Former Member — Thu, 13 Feb 2014 06:49:47 GMT

Previous problem was with 'sapgui' command in different script.

References become initial after reaching 36th abap subpool, as I mentioned before. Error message is about that.

What details can I include more?