SAP Basis Prerequisites - SAP Admin

Direkt zum Seiteninhalt
SAP Basis business benefits
The SAP basis as an organisational unit within a growing IT organisation is facing far-reaching changes. The growing number of technologies and the growing need for integration and collaboration with upstream and downstream IT departments means that the SAP basis is constantly growing. Examples of organisational concepts and further information can be found in chapters 7.6 and 9.4 of the Master's thesis.

As a user of the group, you cannot see tabs either. Now select the applications / tabs to which the group should be accessed (with CTRL you can select several) and select the Grant button. Note: Select the Grant drop-down menu using the button and not the drop-down menu! Use the drop-down menu to determine if and how far users of the group you are currently editing can make CMC tab configurations to other groups / users! Select Grant for the desired tabs. If you still do not see any applications/tabs, it is because the group/user lacks the generic display right at the top level of the respective tab. To do this, go to the desired tab (in the example is the universe), select Manage —> Top-Level Security —> All Universes (the last point differs depending on the tab). Confirm the hint that appears and assign at least the following right for the groups you want: General —> General —> Objects View. Once this right is granted, the tab will also appear on the CMC home page. You can then see the tabs on the CMC home page.

SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page:
Database maintenance, scheduling and restoring database backups
The 5 most common errors in SAP test management In this blog post I would like to discuss the 5 most common errors in SAP test management, which in my experience occur regularly in this area. I hope that with this I can give you some guidance so that you can avoid these mistakes. No test management Quite simple. You have complex SAP software in use or are just introducing a new module tailored to your company, but the test process plays a subordinate role and tests take place only sporadically and unstructured? Then you have already made the first mistake. To ensure high software quality, avoid hidden consequential error costs and consciously plan for a test period instead of the risk of time bottlenecks, a methodical approach should be planned. Too much testing If you have decided to introduce test management, you need to weigh up the resources required for this. A large amount of testing quickly pushes the cost-benefit ratio into the realm of inefficiency, because the time required for testing drives up costs. On the other hand, the test quality should of course be high. Therefore, a structured and comprehensive approach is of high importance. Basically, you should make sure that the costs for the test effort do not exceed the average of the consequential failure costs.

Since jobs and backups should run at set times for organizational or technical reasons, automating them is a good idea. In simple, clear system environments, many SAP Basis administrators help themselves with SAP CPS (Central Process Scheduling) and simple ABAP batch jobs that start operations or other jobs. Since the desires and the system environments usually grow continuously, this approach becomes complex and confusing over time and troubleshooting often becomes difficult. As a result, maintainability often falls by the wayside and error-proneness can increase. If different jobs are strung together to form chains, further problems arise.

"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.

He is considered a reliable and conscientious developer from the IT department.

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 simplification and bundling of the product portfolios should also reduce the administrative burden when ordering, activating, changing, terminating and, of course, invoicing.
Zurück zum Seiteninhalt