SAP Basis Analyses Proactive measures for optimization - SAP Basis

Direkt zum Seiteninhalt
Analyses Proactive measures for optimization
The administration of SAP Basis
This enhances the capabilities of SAP HANA base administrators and increases the level of service they should provide. Your Basis team can more easily fine-tune your data replication strategy to meet demanding disaster recovery and high availability standards.

The SAP Patch Manager offers two scenarios for inserting support packages or queues: Test Scenario Use the test scenario to determine whether conflicts or problems occur (e.g., unreleased repairs) or whether a modification match is necessary before the actual insertion. This scenario allows you to estimate and minimise the time and effort required to load support packages. In this scenario, no data is imported into the system, and you can continue to play in the event of an error without the error being corrected. You must select the test scenario explicitly. Note that once the test scenario has passed, the queue is empty and needs to be redefined. You must also explicitly choose the default scenario.
System monitoring and management tools
SAP Basis is the foundation of every SAP system. On this page you can find out what is behind the term and what SAP Basis is responsible for in detail.

Some useful tips about SAP basis can be found on

You would like to know more about what is happening on your SAP systems - then I recommend that you take a closer look at the Solution Manager Usage Procedure Logging (UPL) functionality. What code is often executed? Which database tables are accessed regularly? What unused developments exist? - The UPL provides answers to these questions. You can implement the functionality into your existing SAP landscape without additional licence costs and with moderate effort. What information does the UPL provide? Usage Procedure Logging is used to log and record user behaviour data roughly comparable to the ST03N workload statistics. UPL is able to record the call and execution of the following ABAP objects: Reports Functional Blocks Classes Methods Subroutines SQL Calls In addition, UPL is able to detect dynamic programme calls and generate transparency about the modifications used. All usage data is recorded in detail and automated and, if desired, made available centrally in the SAP Solution Manager. Benefits 1) Hardly measurable Performance Impact 2) Central collection of data of all systems in the SAP Solution Manager's BW 3) No complex setup 4) Once activated, the collector and extractor jobs run regularly and without further manual activities Possible usage scenario If you have Solution Manager 7.2 in use, you can use UPL within the framework of "Custom Code Lifecycle Management" (in German: management of customer developments). After one activation of the BW content and some standard jobs, you select one or more systems for which you want to activate UPL. If you already have the SP05 installed, there is a separate "Guided Procedure" for configuring the UPL in SOLMAN_SETUP.

"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.

As in the previous blog post Identifying all transactions of multiple roles, the roles Test_Schmidt1 and Test_Schmidt2 are used for this.

Many customers are currently faced with the question of whether or not to migrate your SAP system.

So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
Zurück zum Seiteninhalt