SAP Basis Application layer

Direkt zum Seiteninhalt
Application layer
Log in history of users using SAL
Another important example is the reading permission for TemSe objects. The temporary files are often forgotten, because it is often not considered that cached (strictly) sensitive data, which is intended for only one user (owner), can be viewed by another user without permission - and across clients. The examples mentioned show us how important it is to carefully assign permissions for client-independent transactions. Download Transaction tables The transactions that enable the examples above, including certain expressions of the associated permission objects and our recommendations for them, can be found in the file "Critical cross-client permissions" for download. Other client-independent transactions are located in the Cross Clients TCODES file. The criticality of these transactions should be assessed according to the context. I recommend always being careful and keeping these transactions in mind.

Basis includes a client/server architecture and configuration, a relational database management system (DBMS), and a graphical user interface (GUI). In addition to the interfaces between system elements, Basis includes a development environment for R/3 applications, a data directory, and user and system administration and monitoring tools.

On www.sap-corner.de you will also find useful information about SAP basis.
SAP Applications
SAP Basis is responsible for the smooth operation of the SAP Basis system. The SAP Basis system is like an operating system for R/3 as well as S/4. Every operating system, such as Windows, provides an environment in which programs developed for that environment can run, such as MS Office. Likewise, the SAP Basis system provides an environment in which SAP programs can run. In any R/3 or S/4 system, there is a database server, such as HANA, where the database resides. It provides the necessary data to all other applications. The data here is not only data tables, but also applications, system control tables and user data.

The Expert Team Lead leads a group of specialists, e.g. a group of SMEs or a specific technical area such as a group of operators. For example, this role can lead and steer a virtual group of experts with the participation of other IT departments on the topic of print management. The role serves as the interface and contact of the SAP basis to other specialist areas such as memory management or operating systems. In cooperation with other IT departments, the Technical Team Lead leads expert groups. These expert groups are usually virtually organised and their existence limited in time. The role of the Technical Lead functions as (partial) project leader for topics and projects of particular importance to the SAP basis. He takes care of all the activities involved in project management and control.

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

The management of user and permission structures must ensure that, when the roles and responsibilities change, the privileges of the employees concerned in the systems are adjusted.

A note box in which data of all kinds can be quickly filed and retrieved. This is what Scribble Papers promises. At first, the program looks very spartan. But once a small structure is in place, you realise the great flexibility of this little helper.


The first call should automatically open a dialogue to maintain the organisational levels, as they are still empty.
Zurück zum Seiteninhalt