AGLEA Blog

For some, SE16 is an unfamiliar transaction code. For SAP administrators, it is part of daily life — and often, unfortunately, for others too. This article covers what SE16 does, how many variants exist, and why access to it needs to be carefully controlled.

"SAP logs everything" — it's a statement heard frequently. But is it actually true? Can you always trace who did what in the system? And are there ways to bypass or delete those logs? This article addresses all of these questions.

Who decided there is a problem? What criteria make a given SAP vulnerability critical and what happens when the red findings become too many to handle? Are they all genuine?

From SAP_BASIS 7.40 SP16 SAP has been release a new tool for trace user authorization "long-term" trace.

What is it and how works? 

What can be done to check whether programs developed in SAP comply with security standards?

There are several workflows that this tool provides.

Some of these are standard and cannot be changed, while others leave ample room for customization.

What are the points of attention when deciding which steps and how many to include in various workflows?

We will discuss about them in this article.

In order to perform a risk analysis in SAP and even non-SAP systems, you can use the SAP GRC Access Control tool.

Through the Access Risk Analysis module.

What does it mean? What is it used for and how can it be done in SAP systems?

Are there only advantages or also disadvantages?

In SAP there may be some language problems. Certainly there may be additional difficulties.

But even this in some situations can turn into a headache. Let's see how and why!

How to search for a Fiori application in your launchpad? How to find it in the SAP Fiori Library?

What are some useful tips? Read this article to find out!