I recently found a program which was generating an SQL statement by concatenating several variables with fixed SQL parts. But, either by not paying attention or simple ignorance, the person who did it, thought it would make sense to associate a text-symbol to each of these variables with. Something like this:
Sometimes a SALV has inconsistencies which can go unnoticed. For example, if its structure has an amount field which doesn’t have an associated currency field:
Once again SAPGui surprises me with yet another obscure shortcut I didn’t know about.
Let’s use the customer display transaction XD03 as an example:
Go into the transaction’s selection screen with /NXD03
Fill in the customer number an press ENTER to display its details
Do whatever it is you want to do there and get out of it
Suddenly… you remember that you needed to do something else there
Instead of /NXD03 type /*XD03
In my current customer, I have three development systems. There used to be only one. And that’s where I customized and fine tuned the Code Inspector_ variant I use to run Abap Test Cockpit.
When the other two appeared, before manually copying the variant into them, I decided to investigate a little bit. Much to my surprise, I found in GitHun project upDOWNci which does exactly what I needed: export and import Code Inspector Now, copying the variant was a piece of cake.
If in your report called APP1 you need to save a file in a server folder (ex.: /export/app1/) and you don’t want it to be a selection screen parameter, how do you do it?
You’re in the editor. You type ( or [ or { or ’ and SAP is dumb and doesn’t close it right away like a proper IDE would.
Well,
Click on the lower right corner icon which gives you access to the SAPGui options where you configure code templates.
In the formatting option, activate Enable Auto Brackets and voilá, SAP will now automatically close any doors you open.
I don’t see why this isn’t set by default.
If you read Abapinho you already know how much I like exception classes. But this is not the only ABAP mechanism for dealing with errors.
There is another one, called ASSERT, which should be used more often.
The other day a very strange thing happened to me. I was sending SY-TABIX as a parameter into a method. Before the call it contained 1 but, once inside, the parameter’s value was 0. Weird.
o_thingalizer->very_strange_thing(sy-tabix).
I was hearing “Why?! Why?!” repeatedly inside my head.
But suddenly I understood it!
When you send some field of the SYST as a by parameter you have to pass it by value and not by reference. I was passing it by reference. But, inside the method, ABAP automatically cleaned the SY-TABIX because there it was no longer inside a loop.
Some time ago I wrote an article explaining a way to automatically convert classic exceptions to exception classes. Today I use this technique in almost all the exception classes that I create (and I’ve even improved it, but I’ll leave that for another post).
This tip explains the exact opposite.