SAP Basis SPRO Implementation Guide - SAP Basis

Direkt zum Seiteninhalt
SPRO Implementation Guide
DOCUMENTATION / ARCHIVING
In order to cope with the digital transformation in general, but also to cope with the changing demands on the SAP basis and its scope of responsibility, it is necessary to revise existing roles and define and establish new roles. These include the roles of the technology architect, new features of the Subject Matter Expert (SME), and the role of the Expert Team Lead in leading a group of experts. Further information can be found in chapter 7.1 and 9.3 of the Master's thesis.

SAP Basis is also known as module BC or application Basis. In this regard, SAP Basis refers to all transactions, programs and objects that control the functions of the overall system. This includes, among other things, user and authorization management as well as the configuration of interfaces via RFC.
Creation of quick reference guides for end users and administrators
SAP's client concept enables a SAP system to be split into several logical sub-systems - clients. These subsystems can be used independently and in isolation as separate systems. But how should non-client transactions be treated? How can you prevent one client from accessing the other and why should you want to prevent that? In this blog post, I will answer these questions and discuss some negative examples. Why is it important to consider independent transactions separately? Imagine that every one of your employees is allowed to create or change a client in the production system, or worse, both. Creating and modifying a client in the production system is authorised and documented - you wonder what could possibly go wrong? The risk in this case is a loss of integrity of system and data, loss of confidentiality: With each new client, Superuser SAP* lives up to its comprehensive, cross-client rights and the assigned standard password.

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

"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.

Site Reliability Engineering(SRE) is the equivalent of SAP Basis in the Google world.

Read how to find out if a parameter is static or dynamic and how to use the RSMEMORY report to dynamically adjust the memory allocation parameters.
SAP BASIS
Zurück zum Seiteninhalt