Picture a company where hundreds of people begin their workday at approximately 9 a.m.Visualize a business where hundreds of staff members begin their workday at some time around 9 a.m. The sales staff logs into SAP to verify customer orders, employees in the warehouse update inventory information, and finance staff start processing transactions. Everything runs as expected for a couple of minutes. Then complaints arise that the screens aren’t loading quickly enough, reports are slow, and a few transactions won’t respond.
Initial response is to look for a problem with either the internet or the specific computers. But it might have to do with the SAP system itself.
This is an important aspect of system administration in SAP systems. An understanding of how the system resources are being utilized, where the bottlenecks are and what monitoring tools will be able to help determine the cause.
This is a helpful real-life scenario for students studying SAP BASIS Training in Mumbai, as it provides a link between SAP architecture, workload management, and system performance.
What is causing the slow performance of SAP during peak hours?
SAP systems enable multiple users and multiple business processes to work at the same time. The system resources are utilized for each user action to process a request.
If there are lots of users executing operations at the same time, the system needs to deal with their requests by utilizing the resources of the application server.
Common causes of poor performance are:
- High CPU or memory utilisation.
- Heavy database activity.
- Long-running transactions.
- Few available work processes.
- Many resource heavy reports being executed at the same time.
- Imbalanced application server request distribution.
Slow response doesn’t necessarily indicate that the server is overloaded. A few times, a single poorly written report, or database problem impacts a lot of people.
The role of the administrator is to understand what is really going on, so as to make changes to the configuration.
you will understand what is going on in an SAP Application Server.
When users make requests, they are handled by an SAP application server, and when the database needs to be accessed to get or modify information, the application server does so.
The work process is an important concept that students need to be aware of.
Work process is the one that performs various types of tasks in the SAP system. Common types include:
Dialog Work Processes: Respond to requests made from a user, such as opening transactions and showing information.
Background Work Processes: Run jobs scheduled for a specified time without user interaction.
Update Work Processes: Any work process database changes due to application activities.
Spool Work Processes: Process output requests (print related processes).
Enqueue Work Processes: Control logical locking in order to ensure consistency of data when multiple users access the same business objects.
Other users could also experience delays if the dialog work processes that are available are being used for longer durations.
This is why it is important for a BASIS administrator to be aware of work process utilisation.
A hands-on troubleshooting scenario.
Suppose you have a manufacturing company and you hear from employees that the transactions are slow every morning in SAP.
A BASIS administrator looks at the problem incrementally, rather than proactively adding more resources to servers.
Step 1: Identify active work process.
A transaction code is available (SM50) for the administrator to track work processes on an application server.
This allows the identification of processes that are active, waiting, or running for an unusually long time.
In systems with several application servers, SM66 offers you a global perspective of the work process activity.
The administrator can dive into the remaining occupied dialog processes and determine which operations are consuming the available capacity when there are multiple dialog processes that are occupied by long running tasks.
Step 2: you review Workload Information.
Transaction code ST03N is used to analyse workload statistics.
It offers valuable information regarding system performance, response times and workload distribution.
For instance, if users complain that a specific transaction slows down in the morning, the workload analysis can be used to compare its behaviour in the morning time compared to other times.
This will help you know when a delay is just a one-time matter or if it is a repeated problem in performance.
Step 3: use the necessary resources.
This can make the SAP application slow, as you may be experiencing resource constraints on the server.
Depending on the system configuration and the set-up for monitoring, administrators can access information about the operating system using transaction code ST06.
Operating system metrics such as CPU usage, memory utilisation, or other metrics can be used to determine if it is a problem related to the infrastructure.
Step 4: Store the Data in a Database
Not all performance problem is at the application server level.
Database queries, constraints on the database’s resources, or inefficient data access can cause a transaction to take longer.
BASIS administrators will usually collaborate with database administrators and development teams to diagnose these situations.
The key is knowing where to find and how to gather useful technical information prior to escalation.
Report this to the teacher.Report this to the teacher.
Administrators should not rely on users’ complaints as the only means of coping with issues in a production environment.
Through regular monitoring it is possible for abnormal behaviour to be detected in time before it becomes a significant operational problem.
For instance, a background job can use a lot of resources during the business hours. This is because a large report could take longer than anticipated. The workload on an application server can differ from that of other servers.
These can be early signs of potential performance issues.
SAP administrators can monitor the health of the system with various monitoring transactions, system alerts, and infrastructure monitoring solutions.
But monitoring can only be beneficial if administrators are aware of what the information gathered means. If you see a high CPU percentage, but don’t look into what it is doing, you might come to the wrong conclusion.
During SAP BASIS training what should students be practicing?
Students will learn more than just transaction code names. They should know the meaning of each tool and when it’s helpful.
This sequence can be followed with a practical learning exercise:
- Teach and practice using SM50 to access work process information.
- Know the details of the work process overview for the global context (SM66).
- Use ST03N to review workload statistics.
- Discuss operating system monitoring with ST06.
- Recognize examples of long running transactions and the potential consequences of these transactions.
- Understand the process and practice of documenting findings before meeting with the appropriate technical team to discuss the issue.
In these exercises students are introduced to the kind of investigation that goes on in real SAP support environments.
They should also be educated about the need to handle production systems carefully. Administrators should adhere to approved procedures and ensure that they are aware of the consequences before altering the settings of work processes and/or other system parameters.
Where’s SAP BASIS Knowledge in an IT career?
SAP BASIS professionals are responsible for the technical business context in which SAP applications run. Typically, they have to monitor the system, handle user administration, manage transport, monitor background jobs, coordinate with databases, analyze performance, and maintain the system.
The advantage of performance troubleshooting is that it involves knowledge of several technical aspects as opposed to one isolated transaction.
The following are some of the basic concepts that students interested in this field should learn: SAP architecture, application servers, database concept, operating systems, and monitoring tools.
Develop hands-on SAP Administration Skills in Version IT.
Enhanced learning is the key approach adopted at Version IT for SAP BASIS Training in Mumbai, where students are given the opportunity to learn and implement major concepts in administration.
Students will develop an understanding of how an SAP system will behave when it is heavily loaded, which will help them appreciate what the BASIS professionals are undertaking. It also enables them to get acquainted with the monitoring and troubleshooting tasks performed in business setting.
Students must read about the syllabus, how to get access to systems for practical, the experience of the trainer and topics for the troubleshooting sessions before attending a training.
Final Takeaway
In times of high usage, the answer to a sluggish SAP system is not necessarily more servers. The actual reason may be an occupied work process, database activity, an inefficient transaction or limited resources on the operating system.
A good SAP BASIS administrator will systematically research these areas rather than make guesses.
By learning how to monitor work processes, analyze workload statistics, and understand system resources, students will have more of a basis to address actual SAP administration issues.
