SM61 Display control object list
It should be mentioned here that it only makes sense to access the tables by reading the SELECT statement to get a quick view of the results. Using the DBACOCKPIT, it is not possible to create entire table structures using Create Table. For such applications, SAP provides other, better options. Another important point is that once a user has the necessary permissions to use the transaction DBACOCKPIT, it can potentially (with appropriate permissions on the tables) access the entire SAP system. For example, a query can be used to read the entire user table. Therefore, the transaction should always be treated with caution and only awarded to administrators. DBACOCKPIT handles the call control permissions similar to the SE16 / SE16N transaction. When the table is called, the S_TABU_DIS or S_TABU_NAM permission object is checked with a specific activity. This means that only the tables or table permission groups for which the corresponding values in the aforementioned permission objects are assigned can be accessed. You can read more about assigning permissions to individual tables here. In addition, you can save SQL statements that you run once, and run them again at any time to recognise changes in the result set without having to reformulate the SQL statement each time. The editor also allows you to start the query for SQL statements in the background. The result is obtained by calling the transaction SM37, in which the result is output in a spool file.
Verify that the data file was generated. If it was not created, make sure that the [Page 10] Recreate Data File settings in SPAM settings are enabled. For more information, see Note 70752. ADD_TO_BUFFER In this step, the queue is placed in the transport buffer of your system.
Do you know how to execute SQL commands on the tables in your SAP system? In the past, I asked myself the same question when I wanted to run prepared Querys on a table without converting it to a query over the SE16N with appropriate filters. After my research, I came across a simple way to have your SQL statements resolved transaction-based by an editor. This is the approach I'll describe to you in the following post. You may know the situation that you want to quickly put a short SQL statement on your SAP system without having to invest much effort in ABAP programming. You may not have the ABAP knowledge to extract data from a table, but you are familiar with SQL.
All of the above tasks have been part of SAP Basis Administration for decades. However, SAP software has changed a lot since the introduction of HANA in 2010, and with that, the SAP system administrator's job has changed as well. Here are some of the key differences:
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
SAP HANA has been one of the major topics in the SAP environment for the last few years.
Settings Securing the system also means securing the underlying infrastructure.