Installation of the SAP system landscape, backup, restore and snapshot routines
FAQ on SAP Basis
The master's thesis identified and examined in detail influencing factors such as technological trends and the SAP product strategy as well as the company-specific conditions. Several empirical studies were also carried out in the course of the work. If you are interested in the entire Master's thesis and are a DSAG member, you can read the document at info@dsag.de, headword: Master thesis SAP-Basis of Tomorrow, request.
Only one transaction code can be entered here, otherwise a single role would always be searched, which includes all transactions searched for and is assigned to the respective user. However, since the transactions can also be assigned to the user via different roles, this would not be useful. If you use the above Input variants are also only considered transactions that have been maintained in the role menu. If it is not certain whether the transaction was entered in the menu or in the S_TCODE privilege object of the role, up to four transactions can also be checked by searching through the S_TCODE permission object. Important is the attention and appropriate use of the AND/OR relationship. After the query is executed, the roles that contain the requested transaction and are associated with the user are now displayed. If you use the search through the S_TCODE permission object, the following result page appears. When looking at the result, in addition to limiting the number of transactions that can be entered, another drawback of this variant becomes apparent: Although both associated roles are displayed, at first glance it is not possible to see which transaction is contained in which role. To do this, the roles would have to be considered individually. If more transactions with user assignment are to be identified at the same time and the role assignment is to be seen directly, the use of the transaction SE16N is recommended.
Creating a basis for the SAP landscape
In the ERP environment, SAP has created a separate module for each business task area over the course of time. Companies have the option of putting together a suitable system from these modules, depending on their individual needs.
However, the system modifiability has no influence on customising changes that are customised by the client. If you want to set the customising changes to customise, you must go to the client control. You can achieve this either by pressing the button "Client Control" when changing the system or by calling the table T000 via the transaction SM30. If you are now in the list of clients, you can double-click on the respective row to jump into the settings of the respective client. Here you can also make the desired settings and save them. Step-by-Step Tutorials System Modifiability (Customising Settings and Repository Objects that are independent of the client) Call the SE06 and click on "System Modifiability". Adjust the desired objects and global setting, depending on your request. Save the changes. Client control (custom customising settings) Call the T000 table in the SM30. Double click on the desired client. Change the settings here depending on your request. Save your changes.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
This method displays the result in the GUI shortly after the query is sent.
The website www.sap-corner.de offers many useful information about SAP basis.
If you have unsigned SAP hints, there is a risk that the notice has been changed unnoticed and malicious code will be added to your SAP system when you install the notice.