Direkt zum Seiteninhalt
Installation of the SAP system landscape, backup, restore and snapshot routines
For existing solutions, it is necessary to assess to what extent the solution is customised. A modification is the more serious the more time-consuming the maintenance is, including testing, e.g. in the case of upgrades. The fewer customer specifications are available, the more suitable a system or application is for external operation by a service form to be chosen.

In more complex system environments, thousands, if not tens of thousands, of SAP jobs can run per day. Their interdependencies create a high level of complexity. If administrators or admin teams want to maintain an overview, they have to rely on meaningful monitoring. It must be clear at all times which jobs are running and which are not, in order to ensure proper SAP operation. Ideally, one is informed of critical errors by e-mail or SMS. The trend towards internationalization, outsourcing and mixed operation with on-premise and on-demand systems means that SAP landscapes are often widely distributed. This makes monitoring more difficult and, at the same time, clarity must be maintained. Integrating SAP job management and job requests into a central system, such as SAP Solution Manager, therefore makes sense and is useful for supplementing IT service processes in a meaningful way and accelerating process flows.
SAP Script
There was even a case where the SAP environment required a review of the data center power and cooling. At that time, the data center infrastructure had to be upgraded before we could even proceed.

Understanding the structure and functioning of the system is especially important for IT administration. It is not for nothing that "SAP Basis Administrator" is a separate professional field. On the page you will find useful information on this topic.

Especially in larger companies, which also have multiple locations in different countries, it is often necessary to grant different employees the same permissions for different levels of organisation, such as accounting circles. In order to make maintenance and maintenance of the system easy in such a situation, it is useful to set the inheritance principle for SAP permissions. How does SAP Permissions Inheritance work? An inheritance is always about a master object passing certain properties to a derived (sub) object. Therefore, these properties do not need to be maintained several times. Also, changes to the master object are passed directly to the derived objects. This allows easier maintenance and drastically minimises the error rate. In the case of SAP Permission Inheritance, the required permissions are bundled in a Upper or Master role. Only the organisational levels have to be maintained in the roles derived from them. The permissions are automatically pulled from the master role. Create Inheritance for SAP Permissions The following shows how to create and use inheritances for SAP permissions. This requires only two steps: Creating a master role and defining derived roles. Step 1: Create a master role Inheritance always requires a parent role, because all properties are inherited from it. If this role, in which all shared permissions are bundled, is missing, the first step is to create this master role. To do this, open the PFCG transaction and enter the desired name of the master role in the Name field. It is possible to identify master and derived roles by using naming conventions. The "Single Role" button will then be used to create the desired role. In the following example I create the master role "findepartment_r".

"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.

The gw/reg_info parameter must be set to use this file.

SAP Basis Operation manages the IT underlying the SAP system.

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.
Zurück zum Seiteninhalt