SAP Basis Consulting regarding the use of hardware, database as well as operating systems and their installation type (physical or virtual) - SAP Stuff

Direkt zum Seiteninhalt
Consulting regarding the use of hardware, database as well as operating systems and their installation type (physical or virtual)
Preparation of documentation
The basis of every SAP system is the SAP NetWeaver Application Server. Everything depends on this "SAP Basis" to keep SAP systems running. In the area of SAP Basis Operations, we handle all technical tasks for our customers that arise during the installation, operation and maintenance of SAP systems. We install, administer, configure, troubleshoot and optimize your SAP system.

Basis comprises a number of middleware programs and tools from SAP. Basis is responsible for the smooth operation of the SAP Basis system and thus for R/3 and SAP ERP, for example. SAP thus provides the underlying basis (hence the name) that enables various SAP applications to be interoperable and portable across operating systems and databases.
Why have a SAP-BASIS department in the companies? Our history
In the area of SAP Basic Administration there are many tasks that occur at long but irregular intervals, such as adjusting the system modifiability. As a result, the know-how is often lacking and it is quickly taken to the next search engine, where long and partially incomplete forum entries make finding the right approach even more difficult. For this reason, I will regularly record recurring tasks from the SAP basis Administration for you in simple tutorials. This blog post will start with the topic system modifiability and client control. If you want to jump directly to a step-by-step guide, just scroll down to the bottom, where I summarised everything once. System Modifiability - What Is It? The system modifiability allows you to set which objects of the repository and the client-independent customisation are modifiable or not. Repository objects can also be customised even further, with respect to the software component and the namespace. You can choose whether an object should be modifiable, restricted, or non-modifiable. In this context, restrictively modifiable means that repository objects can only be created as non-originals (small note: for packages the setting "restricted modifiable" and "modifiable" is identical in the function). Let us now turn to the direct approach to the changeover to system variability. Change system modifiability As a preparation, you should clarify how long the modifiability should take place in your system. I have learned from my clients that it is often desired to set the system to "changeable" for certain tasks from the specialist areas only temporarily. If you have organised this, call the transaction SE06 in the 000 client and click on the button "System Modification". If you do not have permissions for this transaction, you can try either the transaction SE03 —> System Modifiability or the transaction SE09 -> Jump -> Transport Organiser Tools -> System Modifiability (under "Administration"). The following screenshot shows the way across the SE03: Here you can change the desired namespaces and software components depending on your request.

This possibility is particularly advantageous when it is a new topic and there is not yet a lot of know-how in the company. Instead of buying an expensive coach to teach employees the basics of a new topic, this means that the knowledge can be made available more cheaply and in a longer term, for example, through an online course.

With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.

SAP delivers it together with the SAP R/3 Plug-In.

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

You can reduce the Queue selection.
SAP Stuff
Zurück zum Seiteninhalt