Direkt zum Seiteninhalt
ST03N Workload monitor
Administrators often need to replicate part or all of a database, for example, to create a system backup or test an upgrade before putting it into production. In the past, this was surprisingly difficult to do with most databases. With HANA, replication works instantly and provides richer functionality and better control than previous databases.

It is essential to define the role to be played within the company. STEP 4: DETERMINATION OF THE TARGET GROUP In this step, the target group of the service is defined and described in detail, e.g. by means of a letter. It will also discuss future target groups which may be of interest in the future. By defining a target group within a company, the SAP basis decides for whom the services and IT products should be delivered. It also makes sense to identify and describe future target groups (e.g. specialist areas) within the framework of a transformation of the SAP basis. STEP 5: POSITIONING This step will position the service on the market and also position the competitors in the relevant segment.
In addition, the SAP Basis team can easily implement new functionality in the new system - without compromising the security, stability or quality of the previous function, which would be the case with non-certified and inexperienced people. Smooth implementation is enabled by project experience, training and certificates.

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.

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

SPAM ensures that support packages are only played in the order specified.

The miners then forward this information to other miners, who in turn do the same.
Zurück zum Seiteninhalt