Supported by
Supported by Inetum

SAAB activation variants

images/thumbnail.jpg - Thumbnail

Some time ago we spoke about SAAB and its advantages as a tool to analyse, debug and find problems in our code. In that article we didn’t explore an important aspect of it: Activation variants.

A given project may be crowded with BREAK-POINTs, LOG-POINTs and ASSERTs, making it overwhelming to analyse if we are to activate them all. But, if we already have an idea of where our problem may be, we can create an activation variant listing only the objects we intend to analyse. Just like in transaction SAT, these activation varants can be local (only visible to the current user) or global (visible to everyone in that system). Global variants must start with Z or Y like any other custom object.

Once we have created and populated or variant, it can be activated at any moment and in any system using SAAB itself. It will be active for a given period of time or a specific date.

SAAB activation variant

Thank you Diane Duane for the photo.

Greetings from Abapinho.