Supported by
Supported by Inetum

The transaction who wanted to call another and couldn't

images/thumbnail.jpg - Thumbnail

John created transaction ZFB01 and associated it with program ZFB01 which, after doing some stuff, does a CALL TRANSACTION on FB01. Then came his friend Mike and ran transaction ZFB01.

He managed to start running it because he had permissions to do it. But half way through he got an error because he doesn’t have permissions to run transaction FB01.

Both John and Mike knew that the system administrators would never ever give Mike permission to run FB01.

And that’s when they remembered about SE97,

Transaction SE97 allows you to say that, when you’re running a given transaction, the authorization checks for a list of other transactions can be skipped when you submit them using CALL TRANSACTION.

So first they chose transaction ZFB01:


Then they added transaction FB01 and said they didn’t want any authorization checks on it:


As you can infer by the columns you can even configure it to show a warning instead of halting with an error:


John and Mike never told this to anyone and lived happily ever after.

Greetings from Abapinho.