SM14 Update administration
Documentation
The basic operation of SAP Basis 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 execution and frequency depends on the existing system environment and which can be optionally booked (client copies, execution 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.
The tasks described above, which occur at rather irregular intervals and involve a certain degree of complexity due to the lack of routine or process know-how, should be examined in order to determine whether they can be performed more efficiently by an external service provider. One question to be answered is whether it is necessary to keep the necessary knowledge in the company in order to be able to react faster than the external service provider. For example, for business critical systems. Security aspects should also be considered, as external persons gain access to the system. From now on, outtasking performance must be regularly monitored and checked for quality and documentation. A complete dependence on the external partner must not arise.
Provision of Web Dynpro so that all users have access to the Web Dynpro applications via an Internet browser
In order to reduce the complexity of the SAP basis operation and to accelerate and simplify the tasks of the SAPBasis and to create free capacities, standardisation and automation of the existing activities is required. Details can be found in chapters 7.7 and 9.5 of the Master's thesis.
Another important example is the reading permission for TemSe objects. The temporary files are often forgotten, because it is often not considered that cached (strictly) sensitive data, which is intended for only one user (owner), can be viewed by another user without permission - and across clients. The examples mentioned show us how important it is to carefully assign permissions for client-independent transactions. Download Transaction tables The transactions that enable the examples above, including certain expressions of the associated permission objects and our recommendations for them, can be found in the file "Critical cross-client permissions" for download. Other client-independent transactions are located in the Cross Clients TCODES file. The criticality of these transactions should be assessed according to the context. I recommend always being careful and keeping these transactions in mind.
For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.
SAP Basis is built in the form of a three-layer model and consists of the following components: Database layer, Application layer, Presentation layer.
If you want to get more information about SAP basis, visit the website www.sap-corner.de.
After you have created the role, you must then enter the master role in the Derive from Role field in the Description tab.