SAP Basis is structured in the form of a three-layer model and consists of the following components:
Authorization management: Preparation and follow-up of audits as well as ongoing or selective support
In order for the stored business logic of an application to be executed correctly, the executing user must also have the necessary permission objects in the flow logic of the OData services in his role. If Authority Checks are performed here, e.g. to query or change data on the backend server, the corresponding role must be authorised. These permissions are expressed in a role by permission objects, as in any ABAP report. If you follow these steps, your Launchpad users should have the Fiori permissions necessary to launch the launchpad, view all relevant tiles, and run the specific apps with their business logic.
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.
Advice on hardware, database, operating system, type of installation (physical or virtual)
SAP Basis usually takes care of the administration of the SAP system. The most important SAP Basis transactions are listed in this article.
An important area of SAP Security is the analysis of the customer's own SAP programs, which are classically written in the proprietary SAP language ABAP. Here, too, as in all programming languages, security vulnerabilities can be programmed - whether consciously or unconsciously. However, the patterns of security vulnerabilities in ABAP code differ from those in Java stacks or Windows programs. The goal of these conventional programs is usually to either crash the program (buffer overflow) or to artificially execute the program's own code (code injection). Both is not possible in ABAP, since a crash of a process causes nothing else than the creation of an entry in the log database (Dump ST22) and a subsequent termination of the report with return to the menu starting point. So a direct manipulation as in other high level languages or servers is not possible. However, there are other manipulation possibilities.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
However, migration is expected to be required for the changeover.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
NEXUS / ENTERPRISE SOLUTIONS is now focusing more strongly on this business area and is strengthening its service portfolio in the basic operation of SAP Basis services (Application Management Services / ongoing support) with optional extensions and project services of SAP Basis operation, for example, in the course of migrations.