SAP Basis SAP HANA

Direkt zum Seiteninhalt
SAP HANA
SWPC Continue workflows after system crash
Standardisation of SAP operations as well as SAP systems can be seen as a preparation for automation as well as for cloud, outtasking and outsourcing service forms. Therefore, in the whole context of standardisation and automation, a sequence of tasks and systems needs to be followed. To do this, it is necessary to first make a detailed documentation of the respective object, which also describes the IST state in detail. A standardisation strategy can then be developed, defined and implemented. Only then can we consider automation, outtasking, cloud, and outsourcing.

Daily checks are still commonplace for many SAP customers today; with Avantra, they are a thing of the past. These are manual checks that a bot can perform hundreds of times each day. Similarly, a bot can create incidents or notifications when something goes wrong.
Objectives of the training SAP HANA - Installation and Administration:
In order for the stored business logic of an application to be executed correctly, the executing user must also have the necessary permission objects in the flow logic of the OData services in his role. If Authority Checks are performed here, e.g. to query or change data on the backend server, the corresponding role must be authorised. These permissions are expressed in a role by permission objects, as in any ABAP report. If you follow these steps, your Launchpad users should have the Fiori permissions necessary to launch the launchpad, view all relevant tiles, and run the specific apps with their business logic.

Another major topic is the migration of SAP systems, both locally from one data center to another and from one operating system to another or from one database type to another. As a rule, the SWPM tool is used here again.

The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.

This allows us to focus on optimizing your SAP systems, not only reactively in the event of an error, but also proactively to avoid possible errors before they occur.

This means that only the tables or table permission groups for which the corresponding values in the aforementioned permission objects are assigned can be accessed.
SAP Corner
Zurück zum Seiteninhalt