What to use to measure performance improvement
You know of ST05, ST01 and SE30. But do you know why you would use one transaction code and not the other? What are the main purposes of each one when it comes to performance improvement and measurement?
To measure and improve performance of ABAP programs – Use SE30 to measure:
- Excessive or unnecessary use of modularization units
- CPU-intensive program functions
- User-specific functions that could be replaced with ABAP statements
- Inefficient or redundant database access.
In addition you may want to analyze or fine-tune a program’s database accesses – Use ST05 to measure:
- Database accesses (SQL trace)
- Table buffers
- RFC calls
- Lock operations (client side)
If you wishto fine tune the system – use ST01 to measure:
- Authorization checks
- Kernel functions
- Kernel module
In addition ST01 encompasses the majority of the functionality of ST05.
How to find the IP address of a SAP system
Scenario – You wish to connect to your SAP system from a remote connection, you require your SAP system IP address and port.
Option 1 – There are a few methods to discover the IP address of a system the easiest being to simply use the menu path:
System–>Status–> then press (SHIFT+F5) –> You will see your current systems IP address under the System Information.
Option 2 – Alternativly you may use SM59 then select R/3 connections and double click on the system (RFC destination), then select the menu path:
System Information–>Target System –> You will see the target systems IP address under the “Network address”.
So which system is connected?
I work on a large landscape of 110 SAP systems (not clients). Every now and then someone asks if a specific system is connected to another, there is no way I can remember which systems are connected. Depending on what system they are referring to one may be able to execute a system specific transaction. However as a dependable alternative one may simply use SM59 and view the connected systems.
Here you can view the following connections:
- R/3 connections
- HTTP Connections to R/3 System
- Internal connections
- Logical destinations
- TCP/IP connections
- Connections via ABAP/4 driver
Tip – Depending on your settings (If the logon data is saved on the Logon/security tab) you may even be able to login to a connected system remotely from within SM59, simply select the R/3 connection and selecting “Remote logon” button.
SM12 – Lock Entries Tips
If you check SM12 you may find some lock entries – this is not a problem. Locked entries are required in standard SAP processing. In most instances the entry will remain in SM12 for a few seconds milliseconds, however they could remain in SM12 for a lot longer depending on the logical unit of work.
Factors which can impact the entry in SM12:
- Sizing and performance of the enqueue server.
- Sizing and performance of the application server/number of available processing sessions. (indirectly related)
- Program logic being executed on the application server.
What you may not know is that there is a hidden menu path for SM12 analysis. To activate this menu path you can do the following:
Run SM12, then enter OK code “test”. You will now see the top menu path has included a new Menu Option labelled “Error Handling”.
This menu option has many parameters and test functions which you can use to analyse the enqueue and dequeue processes.
If you require advice on how to use this new functionality you can refer to OSS note 5424 which is the SM12 FAQ! Success!
External Send – email Output and Transaction SCOT
Question: How does the external sending of email for output messages for example standard Order Confirmation occur with SAPconnect?
Answer: The format of the output must be adjusted to be used by the SMTP email server as used in SAPconnect (transaction SCOT). Here is a quick guideline for email outbound processing only:
1) You have to adjust the profile of the SAP Web Application Server if you want to use the SMTP function. The SAPconnect send job can only be scheduled for servers on which SMTP has been activated. For this reason, you must activate SMTP for all of the SAP system’s application servers. – Use transaction RZ10.
2) You maintain the SAPconnect settings for the SMTP node. For more information on SCOT see standard SAP help: Here
3) Next the original format of your standard output,for example order confirmation output could be in SCR (Standard SAPscript). In this case the SD messages are transferred to SAPconnect in SCR format (SAPscript) these are then converted to OTF format and may be converted to PDF format in accordance with the conversion rules in the IMG.
The configuration for the system is done in “SAP Customizing Implementation Guide–> SAPNetWeaver –>SAP Web Application Server -> Basis Services -> Communication Interfaces -> SAPconnect Client-Wide Settings -> General Settings -> Conversion Rules”.
4) Lastly the emails from the SAP spplication are stored in a queue. A background job needs to be created to collect the emails from the queue and process/send them. You can schedul ethe job in SAPconnect with SCOT as follows:
- From the user menu in SCOT select View–>Jobs
- Select Create
- Enter a job name and confirm it.
- Select the variant SAP&CONNECTALL Sending requests
- Schedule the job to run periodically for example every 10 mins.
For more information, refer to the online documentation for SAPconnect (component BC-SRV-COM).
Understanding the Application Server
ERP/ R/3 system architecture consists of amongst others:
- Presentation Server
- Application Server
- Database Server
- You can display a list of application servers that have registered themselves with the SAP message server by executing Transaction SM51, or by choosing Administration –> System Administration –>Monitor –>System Monitoring –>Servers.
The application server may have the following Message Types: Services provided by the application server This contains the configured SAP Work Process types (Dialog, update (Update and Upd2), Enqueue, Batch and Spool) as well as the following services:
SMQ1 – Outbound Queue Statuses
Outbound Queue
The following statuses may be displayed in transaction
SMQ1:
MDM and Netweaver
SAP NetWeaver is an integration and application platform that helps unify and align, information and business processes across technologies and organizations.
SAP Master Data Management (MDM) is a building block of SAP NetWeaver to enable information integrity across the business network and to facilitate a better communication of information across multiple systems.
Does MDM replace the existing master data distribution techniques for example between mySAP CRM and SAP ERP or SAP ERP and mySAP SCM? Read more 
