SE51 Screen Painter
Recommended gateway settings for RFC system protection
The integration of the SAP basis enables solutions to be introduced faster and better integrated into the existing system landscape. This is partly because the solutions are already known in advance and the necessary knowledge exists or is already planned. This will make it easier to implement the roadmap. It should also be noted that a clear strategy on digitisation and also on cloud products in general, as well as their possible uses, sets out a framework for action that all parties can follow. The participants thus know where the company wants to develop or orientate itself, what is possible and what is not possible or permitted. Thus, both companies and the parties have a valid point of reference at all times. This also leads to an increased acceptance within the SAP basis and a more practical implementation for the SAP basis, as the mentioned expertise is already present in the strategy. As a result, this makes it easier and cheaper to ensure operation in a manageable system landscape.
The lifecycle of an SAP system begins with the installation of the database platform. This is installed by an SAP Basis administrator and can consist of one of the following databases: HANA, Sybase, DB2, Oracle, MSSQL and MaxDB.
Migration from SAP ERP to SAP S/4HANA
Understanding the structure and functioning of the system is particularly important for IT administration. It is not for nothing that "SAP Basis Administrator" is a career field in its own right. Instead of data and application development, the focus here is on providing the software environment on which the company's tools are created. SAP Basis is therefore comparable to the server and platform infrastructure and its administration in companies - as distinct from application and web development.
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.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
SPAM/SAINT updates (SPAM update) provide updates and improvements to SAP Patch Manager and SAP Add-On Installation Tool.
This presentation layer exchanges data with the application layer.