Supported by
Supported by Inetum

Farewell Wordpress, hello Jamstack

images/thumbnail.png - Thumbnail
After over 10 year using Wordpress, the world evolved and Abapinho decided it’s time to evolve with it.

if you love your neighbour, avoid CLEAR

images/thumbnail.jpg - Thumbnail
Please stop. Too many regressions happen because someone forgets to CLEAR or to not CLEAR a variable.

Don't be so negative

images/thumbnail.jpg - Thumbnail
Legibility is very important in all written text. Except, maybe, in concrete poetry. As a follow up to the previous post, here are a couple of rules to help you deal with the negative in boolean expressions.

IF conditions should be simple to read

images/thumbnail.jpg - Thumbnail
Because…why should they be complex to read? It would only make it harder to maintain in the future. Just because an IF condition is complex doesn’t mean it has to be complicated.

SELECT with CASE

images/thumbnail.jpg - Thumbnail
ABAP SQL is becoming more and more interesting and powerful. My latest discovery is the ability to use CASE in SELECT.

I already miss you Sérgio!

images/thumbnail.jpg - Thumbnail
My dear friend Sérgio Fraga passed away. Abapinho also belongs to him. Forever. Thank you my friend for everything you were.

The RANGEs double negatives

images/thumbnail.jpg - Thumbnail
RANGEs have interesting properties.

SELECT WHERE field IN (*, x)

images/thumbnail.jpg - Thumbnail
Ok let’s go slowly on this one. Picture a scenario in which you have a customizing table with several levels of detail which may or may not be defined: BUKRS (empresa) WERKS (plant) LGORT (depósito) When one of the fields is empty, we treat it as a wildcard, meaning all values are valid.

Insert without raising exception in internal table with unique key

images/thumbnail.jpg - Thumbnail
How many times in your ABAP consultant life did you have to deal with dumps happening as a consequence of a program trying to insert duplicate lines into an internal table defined with a UNIQUE KEY? Enough.

Manually populate a LISTBOX

images/thumbnail.jpg - Thumbnail
In 2012 I wondered why LISTBOX is so rarely used. I taught how to use it with standard data elements, which automatically populate it. Today I’ll teach you how you can populate it yourself.

SELECTION-SCREEN FUNCTION KEY N

images/thumbnail.jpg - Thumbnail
There’s so many things you can do on the selection screen. Here’s another one: five buttons in the toolbar.

Send emails to a distribution list

images/thumbnail.jpg - Thumbnail
When you need to send an email to multiple email addresses, the usual approach is to store that list of email addresses in a custom table and then add each one as recipient to the BCS request. But I recently learned a much nicer way to achieve the same result.

Change selection screen texts without hard coding them

images/thumbnail.jpg - Thumbnail
Even though many ABAP programmers tend to forget this, the less texts you hard code in your program the simpler it will be to translate it. Here’s a simple but rather obscure way to manipulate selection screen texts while still being able to translate then. This way you can, for example, prefix them with icons.

Call RFC functions AS SEPARATE UNIT

images/thumbnail.jpg - Thumbnail
Imagine that you are calling an RFC function module several times in a row. Maybe you think that each call is completely independent from the others. It is not. The remote function group remains in memory and so does its global data. That global data will be reused on every call. This is probably irrelevant in most cases. But there will be scenarios in which, for some reason, the function module being called is storing data in global variables which will negatively affect the outcome of the subsequent calls.

Local dummy functions named after remote RFC functions

images/thumbnail.jpg - Thumbnail
I recently started working in a new customer and noticed something they do here which I really liked. Whenever they need to call a remote function module by RFC in another SAP system, they create a local function module with the same name and leave it empty, except for a comment explaining that it is a dummy function for that remote function call. Thanks to this simple trick, one can use the where-used tool to find out where it is being called.