SAP Basis High Availability ( HA/DR ) concepts - SAP Stuff

Direkt zum Seiteninhalt
High Availability ( HA/DR ) concepts
A simpler option is to output the transactions used by the expert as a list and to obtain an overview of the task areas. The function block SWNC_COLLECTOR_GET_AGGREGATES is very suitable for exporting the used transactions in a list. As an alternative, one can directly use the workload monitor in the transaction code ST03N.

This is where all the system's data resides. These are composed of the actual database and the DBMS, the "database management system". In earlier versions, the database here came from different manufacturers. For example, Microsoft SQL or Oracle. Since SAP HANA, a lot has changed for IT in this data layer. This is because the database comes from SAP itself and is automatically monitored by the system. There is more to this database layer than just the working data. Important elements such as the configuration tables and system data for control and application content are also stored here. This is the repository data used by applications.
Why does your company need an SAP Basis admin?
For the authorisation requirement of a user, the transactions with user assignment already awarded should be determined accordingly, in order to be able to exclude them when selecting a suitable role. How does this work? There are various ways to identify specific user-assigned transactions, with varying degrees of result. The following article presents two variants. The first section first describes how to use SUIM to address the problem and what problems are encountered. It then explains how the task can be solved by using the transaction SE16N. As in the previous blog post Identifying all transactions of multiple roles, the roles Test_Schmidt1 and Test_Schmidt2 are used for this. Two of the transactions MM01, MM02, MM03 and MM04 were assigned to these roles in different ways. In the Test_Schmidt1 role, the transactions MM01 and MM02 were entered in the Role menu. In the Test_Schmidt2 role, the transaction MM03 was maintained in the menu of the role, but the transaction MM04 was maintained only in the S_TCODE permission object of the role. Both roles have been assigned to the user SCHMIDT_TEST. Identification of certain transactions with user assignment using SUIM This option is useful if only one transaction is to be checked for its existing assignment to a particular user. The audit is carried out here by means of the transaction SUIM. For this purpose, the variant "Roles according to complex selection criteria" has to be executed in the SUIM. After activating the option "With valid assignment of", the corresponding user and the transaction to be checked will be entered here. It is also recommended to hide the display of the collection roles in the search results.

The presentation layer is used to visualize the applications and data for the user. The presentation is done with the help of a graphical user interface (GUI). Furthermore, the presentation view consists of several modules, which are also summarized as SAP GUI. SAP Fiori is the presentation layer of the next generation and is therefore particularly user-friendly.

"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.

However, there are a few things to keep in mind: A process for granting special rights should be defined.

SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page:

If the queue is not yet fully defined, you must define the queue from the available support packages.
SAP Stuff
Zurück zum Seiteninhalt