Configuration & operation of the SAP Solution Manager
How CodeProfiler for ABAP works
SAP Basis ensures smooth operation of the SAP Basis system. The SAP Basis system is a kind of operating system of the R/3 system or SAP ERP. It includes three layers: database, application and presentation. In addition, Basis includes many SAP middleware programs and administration tools. With Basis SAP applications can be used compatible and independent of operating system and database and can be enriched with the necessary data.
In the case of distributed or local SAP systems, it can also be helpful if departments or decentralized IT units can schedule their own jobs themselves. It is important that the associated approval processes can also be mapped and easily tracked. This brings convenience, flexibility and a degree of freedom without neglecting operational security. The integration of the business departments can relieve the IT administrator and turn background processing into an end-to-end process integrated into the organization.
SM20 Evaluation of the Security Auditlog
This point may sound a little trivial at first. Who tests, surely documents this? Experience shows: Yes, but often patchy. In the case of unsuccessful tests, where subsequent or additional developments are due and the cause of the error is not directly apparent at first glance, good result documentation often pays off. This saves developers time in communication and effort by re-imagining the scenario. At this point, the SAP Solution Manager offers extensive opportunities to manage templates and result documents centrally and in the individual test plans. Automated testing only Automated testing offers many advantages, whether it is a higher software quality through more comprehensive test coverage or reusability of test cases. However, it does not always make sense to use only automated test scripts. A less good choice is the test automation for frequently changing software or processes, because the maintenance effort can be enormous. At this point, it is often more effective to run manual test runs instead of spending a lot of time customising test scripts. Poor test preparation The relevant processes have been defined, the test plans have been created and the test period has begun - so can testing begin? Not always. Lack of test preparation often leads to unplanned additional time costs. Sometimes the testers were not familiar with the test environment or no one thought about taking care of a sufficient and current test data set (master data, movement data). Make sure you have thought of everything you need! (missing test data, unrepresentative test environment, unstable).
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.
Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.
This is because a user is assigned the correct authorization role - but the profile associated with the role is not up to date.
Compared to a classic ERP / R3 scenario, the normal DB is replaced by HANA.