Data Migration
Maintenance of SAP licenses
The tasks of a company's own SAP Basis department are currently undergoing enormous change, as SAP is also increasingly relying on cloud services. Strategically, completely self-hosted SAP systems are becoming rarer and the proportion of customers using an SAP system from the cloud is increasing. The new roles of SAP Basis employees tend to be "enablers" and coordinators between the cloud provider and internal IT and the business departments. Until that time comes, companies can also rely on external service providers to offer expert know-how as well as operational support for the transition period.
Due to the technology diversity, including in the SAP product portfolio, the support by a single silo unit SAP basis is almost impossible. Likewise, there are many activities that are located for historical reasons in the SAP basis and in parallel in the non-SAP area. In this respect, the separation between SAP and Non-SAP must be examined and, if possible, eliminated by standardisation, integration and centralisation. For example, the issue of output management can be set up in a team that has knowledge in the SAP printing area as well as in the non-SAP printing area and has contact points in the SAP basis. From the SAP basis, tools must be made available to the non-SAP areas to support them in their work in the SAP environment.
Hard skills and soft skills
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.
After installing the GUI, the GUI patches should be applied as far as available. This includes the hotfixes after the patches, which are necessarily installed after the patches. BI Addon Patch A new service package and patch may need to be installed. It may also be that can be patched directly if another SP exists. The process takes about 30 minutes. The progress of the installation pauses at a certain percentage, as already mentioned above, so you do not have to cancel the installation prematurely. If the installation is not possible, the latest version will be included in another setup. Installation of the Precalculation Server The Precalculation Server is installed. You can also install any patches here. Service The installations create a service. This can be called under Services. Set the Startup Type of the service to "Automatic" (Standard Manual) Enter Login Credentials Recovery for First and Second Failure to "Restart the Service" Start Service Logon SAP Login to the SAP system with the appropriate client from the Precalculation Server. You can use the SAP system's own login. Warning: There must be permissions for the transaction RSPRECALCADMIN and SM51. The transaction SM51 will then be called. Before creating the instances, it must be ensured that the correct application server is selected, otherwise problems with the instances in the user's application may occur later. The transaction RSPRECALCADMIN is then called. A certain number of instances are displayed. They should all be marked and deleted until the view is empty again. They are then re-created with a continuous numbering in order to distinguish them later. Only the ID and description must be entered. The rest will be awarded automatically. The service will now restart and all instances should be green. This may take 2-3 minutes. Important: In the end, all instances must be green. This completes the creation and configuration.
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
Server-side scripting in ABAP and Javascript.
SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis: www.sap-corner.de.
This blog post will start with the topic system modifiability and client control.