SAP Basis Connection of cloud services - SAP Admin

Direkt zum Seiteninhalt
Connection of cloud services
Basis administration in the age of SAP HANA
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.

Depending on whether the user should edit or display the table, either "UPDATE" or "SHOW" can be used here. Enter an X as the value. It is important to use either"'SHOW" or "UPDATE" because a combination will cause an error when calling the parameter transaction. In addition, the table must set the view to be called. Use the "VIEW" field. Finally, the parameter transaction can be created using the "Save" button. As usual, it must be assigned to a package and a workbench order to become available. If a person's role is now assigned permission for this parameter transaction, it can open the specified view above it and does not have the ability to enter all possible views in the SM30.

Understanding the structure and functioning of the system is especially important for IT administration. It is not for nothing that "SAP Basis Administrator" is a separate professional field. On the page you will find useful information on this topic.
The typical tasks of system support and administration of an SAP landscape include, among others:
Therefore, there can also be critical permissions, profiles, and roles that do not fit in the naming scheme defined by SAP. Manual identification of critical SAP permissions is difficult overall. However, tools are available that automatically check for critical permissions. In this case, the critical SAP permissions are usually predefined by special verification software. If the critical permissions, profiles, and roles are identified, they should be adjusted according to the permission planning. The system will then be checked to see if the desired system behaviour has been achieved or if malfunctions occur. This adjustment process may be complex in the event of major changes and should not be carried out on the production system.

For the authorisation requirement of a user, the transactions with user assignment already awarded should be determined accordingly, in order to be able to exclude them when selecting a suitable role. How does this work? There are various ways to identify specific user-assigned transactions, with varying degrees of result. The following article presents two variants. The first section first describes how to use SUIM to address the problem and what problems are encountered. It then explains how the task can be solved by using the transaction SE16N. As in the previous blog post Identifying all transactions of multiple roles, the roles Test_Schmidt1 and Test_Schmidt2 are used for this. Two of the transactions MM01, MM02, MM03 and MM04 were assigned to these roles in different ways. In the Test_Schmidt1 role, the transactions MM01 and MM02 were entered in the Role menu. In the Test_Schmidt2 role, the transaction MM03 was maintained in the menu of the role, but the transaction MM04 was maintained only in the S_TCODE permission object of the role. Both roles have been assigned to the user SCHMIDT_TEST. Identification of certain transactions with user assignment using SUIM This option is useful if only one transaction is to be checked for its existing assignment to a particular user. The audit is carried out here by means of the transaction SUIM. For this purpose, the variant "Roles according to complex selection criteria" has to be executed in the SUIM. After activating the option "With valid assignment of", the corresponding user and the transaction to be checked will be entered here. It is also recommended to hide the display of the collection roles in the search results.

With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.

In the area of SAP Basic Administration there are many tasks that occur at long but irregular intervals, such as adjusting the system modifiability.

So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.

There are also some points to consider when managing print jobs.
Zurück zum Seiteninhalt