Differentiation from SAP ABAP
Design of applications
In the case of client settings, you should ensure that the production client is protected against overwriting and that changes are only approved via the transport management system (TMS) to ensure traceability. In the interests of system security, changes to repository and client-independent objects should also not be permitted. The use of eCATT and CATT should also be at least restricted, as allowing them can lead to significant database changes.
SAP HANA (SAP High-Performance Analytic Appliance) is an SAP platform based on in-memory technology. With SAP HANA, you can achieve huge performance increases over traditional databases that were previously unthinkable. This enables you to analyze and evaluate mass data almost in real time without the need for data aggregation.
Planning and design of the system landscape, system layout, hardware sizing, system monitoring
New risks in SAP HANA: In addition to the known risks, there are also new risks from the use of SAP HANA. A very good example are frequently used web applications that represent something new in the SAP area. In contrast to an SAP ERP system, HANA systems consist mainly of web applications, which were considered optional in the previous versions. These web applications can be found by various search engines on the Internet. This also applies to SAP Portal or Netweaver. There are URL schemes that help locate the system. This also applies to other SAP systems that use Web applications. This makes the new technology vulnerable to typical web attacks. SQL Injection, ABAP Code Injection, or XSS are all included. All risks known for a normal SAP system also apply to a SAP-HANA system. The data is stored unencrypted in RAM. Only then does the system gain this speed advantage. This results in risks such as a read-out by memory scraping malware. These pick up data in memory. Encryption costs performance, so it is not used by default. Especially during a migration HANA runs in a parallel system, therefore at least one new system comes to your landscape. Also note: HANA has its own tools and settings that need to be known and configured. The bottom line is that the system simply needs more attention when operating. Many settings often result in more errors. Three - points - HANA Security Plan 1) Roles and permissions In a previous SAP system, roles and permissions are certainly one of the main pillars of a secure system. Roles and permissions work differently in a HANA system. There are two types of users: 1) Default (limited): With this type of user, there are different access methods to the database. For example, the JDBC or HTTP technologies are used to give two examples.
Soft skills also play an important role in this profession. In everyday life, communication skills are in demand, because SAP administrators are often in close contact with customers and have to respond to their wishes and questions. They also need to be able to work in a structured manner and find creative solutions and decisions. In order not to lose touch, continuous training in this area is advisable.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
Therefore, the customising/workbench developments must be transported to the appropriate system.
Today, "SAP Basis" often does not mean (only) the software architecture.