Monthly Reporting / Reviews
SE24 Class Builder
This is where all the system's data resides. These are composed of the actual database and the DBMS, the "database management system". In earlier versions, the database here came from different manufacturers. For example, Microsoft SQL or Oracle. Since SAP HANA, a lot has changed for IT in this data layer. This is because the database comes from SAP itself and is automatically monitored by the system. There is more to this database layer than just the working data. Important elements such as the configuration tables and system data for control and application content are also stored here. This is the repository data used by applications.
Mentioning the SUM tool leads us to another part of SAP Basis: system updates and upgrades. Since SAP software receives updates from SAP at regular intervals - in the case of R/3 in the form of SPS (Support Package Stacks) and in the case of S/4HANA in the form of FPS (Feature Pack Stacks) - a large part of an SAP Basis administrator's job is to import these packages into the SAP system.
CLOUDABILITY, OUTSOURCING AND OUTTASKING
Sound up-to-date know-how: With SAP Basis support, you can save time and money on training that would be needed in-house to keep your employees up to date. An SAP expert is always familiar with the latest technologies.
Only one transaction code can be entered here, otherwise a single role would always be searched, which includes all transactions searched for and is assigned to the respective user. However, since the transactions can also be assigned to the user via different roles, this would not be useful. If you use the above Input variants are also only considered transactions that have been maintained in the role menu. If it is not certain whether the transaction was entered in the menu or in the S_TCODE privilege object of the role, up to four transactions can also be checked by searching through the S_TCODE permission object. Important is the attention and appropriate use of the AND/OR relationship. After the query is executed, the roles that contain the requested transaction and are associated with the user are now displayed. If you use the search through the S_TCODE permission object, the following result page appears. When looking at the result, in addition to limiting the number of transactions that can be entered, another drawback of this variant becomes apparent: Although both associated roles are displayed, at first glance it is not possible to see which transaction is contained in which role. To do this, the roles would have to be considered individually. If more transactions with user assignment are to be identified at the same time and the role assignment is to be seen directly, the use of the transaction SE16N is recommended.
The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.
If you want to get more information about SAP basis, visit the website www.sap-corner.de.
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.
Do you have any further questions or suggestions concerning this topic? Would you like us to go further on the subject? I look forward to your feedback!