Database management
System changeability and client settings
The presentation view is used to visualize the applications and data for the user. The presentation is done with the help of a graphical user interface (GUI). Furthermore, the presentation view consists of several modules, which are also summarized as SAP GUI. SAP Fiori is the presentation layer of the next generation and is therefore particularly user-friendly.
For these cases, you should take a closer look at the DBACOCKPIT transaction. This transaction provides you with many other database management features, an editor that allows you to easily execute your SQL queries against your SAP system. This method displays the result in the GUI shortly after the query is sent. How to execute a SQL query To call the editor for SQL queries in DBACOCKPIT, the user must: The user needs corresponding rights to execute the transactions SM49 and SM69. STOR and SMSS must be cultivated in the S_ADMI_FCD permission object. SQL queries must maintain the database connection. To get the current status of a database connection, see the DBCONT table. Rights for calling the table(s) to be retrieved must be assigned. For more details, see the section "Further information on DBACOCKPIT" in this blog post.
Database Management
This access method depends solely on the rights assigned to the user. System users: Users of this user group are comparable to SAP*. They act as administrator in the system. Therefore, they should be deactivated / set to inactive as soon as possible, as soon as the system operation is ensured. You should still be aware of the SAP ERP environment to address this security risk. In a HANA system, there are privileges instead of permissions. The difference is first of all in terms of terminology. Nevertheless, the permissions are assigned differently (directly / indirectly) via the assignment of roles. These are thus accumulations of privileges. As in older SAP systems, system users must be disabled and certain roles that already exist must be restricted. Compared to an SAP ERP system, small apps are allowed instead of large applications. In this case, attention should be paid to an individual authorisation. It should be a matter of course for users to have implemented secure password rules. Settings Securing the system also means securing the underlying infrastructure. Everything from the network to the host's operating system must be secured. When looking at the system landscape, it is striking that the new technology brings many connections that need to be secured. The SAP Gateway, which is responsible for the connection between backend and frontend, is also a security risk and must be considered. All security settings of existing and future components must be validated to HANA compatibility. Secure communication of connections is obtained when you restrict access where possible. Encryption of the data of a HANA system is disabled by default. Be sure to encrypt sensitive data anyway. Especially data that is archived. If an attack is made on your system, you should be able to run forensic analysis, so you should enable the audit log. Moreover, few users should have access to it.
Together with our SAP development team, our SAP Basis experts develop programs and transaction processes using Web Dynpro technology. This includes, for example, our SAP AddOn "SAP Password Reset". We would be happy to develop your solution.
Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.
If you want to skip the backgrounds and prefer a direct step-by-step guide, you can jump directly into the last section.
If you generate the role, the permission tab will also appear green.