SAP Basis - operation, structure and definition
The basic SAP Basis operation includes the operational readiness of the SAP system, management of system changeability, configuration and administration of system profiles, analysis of system failures, operation and monitoring of technical interfaces, scheduling and monitoring of SAP standard jobs, and much more. The optional services as an extension include activities whose implementation and frequency depends on the existing system environment and which can be optionally booked (client copies, implementation of client transports and homogeneous/heterogeneous system copies, etc.). These include performing release upgrades, installing enhancement packages, adapting new printer types, device drivers or character sets, and much more.
In the case of client settings, you should ensure that the production client is protected against overwriting and that changes are only approved via the transport management system (TMS) to ensure traceability. In the interests of system security, changes to repository and client-independent objects should also not be permitted. The use of eCATT and CATT should also be at least restricted, as allowing them can lead to significant database changes.
SAP Basis refers to the IT underlying the SAP system. It includes various middleware programs and tools and is responsible for the smooth operation of the SAP system.
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).
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
It is therefore not unusual for the authorisation allocations to be regularly reviewed in the course of a revision or by external auditors.
The activities with the emergency user are logged in a revision-proof manner.