SARE Archive Explorer
Generate and monitor a revision-proof permission concept tool-based: The established processes for entitlement management, role application and assignment are not documented at all or in a central location in your company? In the revision, it was noticed that a written authorisation concept does not exist, is not up to date or that the processes do not meet the requirements?
SAP Basis is responsible for the smooth operation of the SAP Basis system. The SAP Basis system is like an operating system for R/3 as well as S/4. Every operating system, such as Windows, provides an environment in which programs developed for that environment can run, such as MS Office. Likewise, the SAP Basis system provides an environment in which SAP programs can run. In any R/3 or S/4 system, there is a database server, such as HANA, where the database resides. It provides the necessary data to all other applications. The data here is not only data tables, but also applications, system control tables and user data.
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.
SM61 Display control object list
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:
Job scheduling: your system needs to run various automatic background jobs that consume resources. Your administrator must carefully schedule these tasks when user demand is low so they don't impact performance.
The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.
SAP's client concept enables a SAP system to be split into several logical sub-systems - clients.
Due to the increased demands, this role and the associated activities must be professionalised through training and further training.