SCC7 Client import - postprocessing
You implement - we support!
SAP Basis or system administrators work with SAP Basis in a company. They are responsible for the correct installation, configuration and maintenance of the SAP application servers and applications, and in some companies also for the operating system and the SAP database if no administrators are available. Using SAP's own programming language ABAP, developers and programmers design SAP applications that run on the ABAP stack of the SAP NetWeaver Application Server as the only publicly accessible ABAP runtime environment. In some cases, the boundaries between ABAP developers and SAP Basis administrators are permeable, and each of the two groups of specialists has a basic knowledge of the other. As a rule, however, the competencies remain separate.
To evaluate the log files, please use transaction RSAU_READ_LOG. If you archive the security audit log files you can read them using transaction RSAU_READ_ARC.
The database layer
The Technical Lead functions as the work package leader or sub-project manager within the SAP basis when the project is the focus of the SAP basis. The Technical Lead will become more important in the future as the SAP basis acts as a technology consultant and more projects and project activities are expected in the future. This role must be filled more and more often. Due to the increased demands, this role and the associated activities must be professionalised through training and further training.
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).
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
Logging of the results The results of the tests are logged via the application log and can be viewed both by SAP standard means and directly by the tool.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
Various tools can be used for this purpose, which take over the maintenance, care, configuration and monitoring of the SAP system.