SAP Basis Requirements - SAP Basis

Direkt zum Seiteninhalt
Requirements
TRANSPORT MANAGEMENT
There is no way around containers, and even SAP will soon have to reorient itself here and allow the NetWeaver stack to be run in containers. There are many indications that Kubernetes will win the battle for supremacy among container management tools. SAP has also already invested in Gardener and is also intensifying its partnerships with IBM and Red Hat Openshift.

SAP Basis is the foundation of every SAP system. On this page you can find out what is behind the term and what SAP Basis is responsible for in detail.
Optimization of the SAP infrastructure
In the past, when we deployed SAP environments, we first had to work out a detailed sizing and architecture and pass it on to the procurement team, which then ordered the systems and installed them in the data center. From there, it went on to the network team, the storage team, the operating system team, and the database team. So it was not uncommon for three to six months to pass between the architecture design and the installation of a new SAP system.

From a purely technical point of view, each generated authorization role contains a profile from which a user receives the actual authorization objects and authorization characteristics. If this profile is outdated or not assigned at all, the user will not have all the authorization objects contained in the authorization role. Incidentally, the problem arises particularly frequently after role transports: If an authorization role is changed in the development system and then transported to the production system, the current profile is not automatically assigned to the users with the respective role. A user comparison must therefore be performed here.

Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.

Now you can import this transport into the system just like any ordinary transport order.

The size of the respective company is also important.
SAP BASIS
Zurück zum Seiteninhalt