Andrea Olivieri
(2 comments, 3 posts)
This user hasn't shared any profile information
Posts by Andrea Olivieri
How many lines of custom ABAP code are inside your system? Part2
1Intro
This is the continuation of the previous blog How many lines of custom ABAP code are inside your system? published at the beginning of 2009 by Sergio Ferrari, my colleague and SAP Mentor.
The SLOC, the number of line of ABAP code of custom objects, is one of the most interesting indicators provided during a software assessment as described here.
In this new weblog I am going to share with the great SDN community the new version of the ABAP ZSDN_SIMPLE_ABAP_SLOC_COUNT, developed at night, during the few hours of free time.
Let me summarize briefly the improvements and extensions that this new version introduces.
SPIDERMAN is working in my system or a bug in the debugger?
0The Beginning…
The blog posted by Kevin Wilson a few days ago about the chance to modify the content of SAP tables using the SE16N transaction reminded me the importance of properly managing these tasks in a productive environment:
- System settings (e.g. SCC4/SE06)
- Permissions to perform certain actions and / or transactions.
Just to stay on the subject, I would like to share with the great SDN community a pearl which is based upon one of the peculiarities introduced by the new ABAP debugger.
My colleague Sandro Garofano (he’s really a PI Guru) asked me: <<Hey Andrea, can you change the variable SY-UNAME while debugging?>>
Knowing the classic debugger and imagining to have the same behavior even with the new one, I answered with no doubt: <<Absolutely NOT!>>
Sandro then closed the conversation by adding: <<… Anyway, we did a test; if you change the content of the system variable sy-uname, the new debugger maintains the value … Try it!>>
How many exit routines are active in your SAP ERP system?
2
Let’s check with X-it RAY Eye
In all upgrade projects in which I was involved I prepared a checklist of standard modifications and implemented userexits.
This kind of analysis performed before the upgrade, as well as give an overview of the system complexity, is helpful to prepare the testing sessions and identify a dangerous situations such as the missing call to an exit routine.