I'd like to get the call stack of an exception which were caught in a try block to identify the location were the exception was thrown. So basically, I want to get the same information which would be visible for a short dump in ST22 under section "Ac...
I'm facing today the similar problem what occured one year ago for the ASE instance, now with the NPL instance (downloaded developer edition). The Sybase license expired on 2016-10-31: % RUN_NPL
00:0000:00000:00000:2016/11/02 08:27:50.97 kernel SySA...
Hi all, Is there a way to also handle deleted (or renamed) objects within a transport of copies?I'd like to create a transport of copies of a new version of a small tool which should replace the previous versions. The works fine for all changed and n...
Hi all, after an upgrade from AS ABAP 7.40 to 7.50 I just encountered that - as usual - some of the Code Inspector tests and extended program checks changed with this upgrade. My question: Is there any detailed change log on what changed at the check...
During the last years, I was a lot working with static analysis for ABAP. However, since SAP is introducing many new programming technologies, more and more SAP users are confronted with new languages besides ABAP. One of these is SAP HANA SQLScript,...
Hi Sandra, invoking the debugger (or any other SAP tool) does not work for my use case. My intend is to pass the call stack information when executing an RFC function module from outside of the SAP system and I'd like to have these information in th...
I fully agree - the call to the standard code should be already wrapped in an exception. But I'm exactly interested in debugging possibility (other than ST22) for a situation where this exception chaining is missing.
HI Sandra, thanks for your answer, but I'd be indeed be interested in the complete stack. Source position would be a starting point, but when the exception e.g. occurs in standard code, I won't be able to identify the last step in our custom code whi...
Yes, I'm aware of this, but I'd like to also see the Code Inspector results (from the BAdI call) when I release a task automatically in Eclipse (without separately executing ATC) - or at least a message displaying that errors / warnings did occur. Th...