SAP Basis How relevant is SAP Basis? - SAP Admin

Direkt zum Seiteninhalt
How relevant is SAP Basis?
NEW TECHNOLOGIES & INNOVATION
Instead of data maintenance and application development, SAP Basis is more about providing and maintaining the software environment on which the data resides and is processed. Therefore, SAP Basis is an important core of any SAP infrastructure and is required in both previous versions such as R/3, as well as current versions such as S/4HANA 2021.

Before SAP HANA was released, there was no SAP database - you had to install SAP ERP (or the application you were using) on a third-party database, such as Oracle or SQL Server. SAP developed the HANA database to fully leverage the power of SAP's next-generation S/4 software.

The website www.sap-corner.de offers many useful information about SAP basis.
Solutions for production environments and as proof of concept (PoC)
Entry-level employees earn just under 40,000 euros per year. An employee with significant professional experience can look forward to around 90,000 euros. The average salary is 60,000 euros. However, these sums can vary depending on the company and location. The size of the respective company is also essential.

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.

Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.

Both ABAP and Java stack can be monitored from one platform.

So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.


This behaviour is controlled with the abap/heaplimit parameter.
Zurück zum Seiteninhalt