Skip to main content

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS

Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again.

From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column.

Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel.

You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue.

By Default :- You see data of current day as default view , you can change the default view.


Source of the image : sap-perf.ca

Let's discuss the WORKLOAD MONITOR

By Default : Expert mode needs to be used

As you can see in the picture you have all the data in second or millisecond as unit.

The common way to start analyze the issue is looking into workload monitor ,

So you need to check the overview in this flow , Check for Today , Last Minutes Load, Transaction profile and the response time duration, Total workload option , gets data from the whole SAP System.

Now Lets understand the different monitors that are used and their uses,


 So we need to check in expert mode , because hey we are the basis guys!

WORKLOAD : Two levels of analysis : Individual (Only one Application server) or Total/ALL (All Application server)

All configured Application servers of the SAP System are listed , even when application server is temporarily shutdown.

The other sub views are Day, Week and Month. So that we can check the performance problem of the past easily.


DETAILED ANALYSIS : Business transaction analysis is STAD , this is the successor of STAT which is no longer supported .

This displays workload statistics for every step executed in ABAP based system

As we can see in the below mentioned image we have 3 display mode :-

1. Sorted by time : Display Single records.

2. Grouped by business transaction : Shows all record , grouped by business transaction.

3. Show Business transaction tots : Display single records grouped by business transaction or jobs.


We can set the Read Interval if we want it displayed for a specific time interval.

We have different filter parameter , you can select a user , business transaction or different parameter can be used.

We can use different filter parameters as per our goals.

All records are read but only selective are displayed.  

Usually you will be working using the view , Show all stats records, Sorted by time.

Now [*] the option include statistics from memory , The System Analyzes that are not yet written in stats file but which are stored in the stats of buffer. This is must when you need to analyze the recent periods i.e. buffer records is included in this case. 

Server Selection allows you to analyze the stats of selected servers of the SAP System.

With AS ABAP 7.02 the transaction STADWD became available. STADWD implements the functionality of STAD using web Dynpro of ABAP.

If you did not receive data from a server that was called as a result of RFC problem or busy AS that increases 

Adding here is Another option Last minute's Load again you can either choose a an individual application server or a total summary.















You have Analysis Interval : Read interval [Date, Time]

You can also have data restriction : Filter Parameter [Client, Username and Work process number ]

The granularity of the time interval is determined. This granularity is used in the analysis view Time Profile.

LOAD HISTORY AND DISTRIBUTION : 

In this also you will have two views : Individual and Total application server, which can be displayed by date , week or month or any time period i.e. different time interval can be analyzed. 

By default only DIA (Dialog task types) are listed but obviously others can also be seen.

You can also check users per instance along with a cumulative view.

BI WORKLOAD :

Business Warehouse capabilities of Netweaver is checked here.

Schedule corresponding collector that gathers respective information about the workload caused by Business Warehouse functions in SAP System.

COLLECTOR AND PERFORMANCE DB :

1. Performance Database

2. Performance Monitor Collector

    - access to log files of report RSCOLL00 that collects the data as per scheduling mentioned in table TCOLL

3. Workload Collector 

    - Customize the workload collector , for example how many records to collect during a run.

4. Statistics records and files : Here you can look up and change SAP System Parameters relevant for collecting statistics data.


Let's understand the ANALYSIS VIEW 

We can see different Analysis views present in ST03 that is present in  the left pane.



So as you see the second half Analysis View :

Workload View : By Default it shows for today you can customize this setting. This gives you a rough idea what is the issue with performance in normal scenario.

Transaction Profile :  This helps you find the most used transaction , Sort as per the total response time , number of steps.

As an admin , we need to focus on transactions that have the largest total response time as we need to tune these . We need to understand that these transaction will have the major impact on SAP System performance.

We need to inspect the average response time for transactions.

Two categories : Standard and Early watch.

In this we need to analyze the transactions that are affected and that needs to be changed 

Standard : All available aggregation types and analysis views.

Early Watch : Only offers a sub-set function 












Source - sap-pref.ca

Time Profile : Statistical data of chosen task is displayed segmented according to granularity level and time interval you specified.

source : saptechnicalguru.com


Ranking Lists : You can find the top 40 executed steps executed within the SAP System , according to task types and differentiated between 

1. Response time

2. Number of database calls 

3. Memory use statistics "Average total memory usage [kB]"

and you can again differentiate between task type.


RFC Profile : Statistics of separate client side and server side RFC activities of the SAP System, you can look up for :-

1. client and server destination

2. users

3. called function blocks

and more 



User and Settlement Statistics : User and client activity

Front end statistics : Activity statistics by front end

Spool Statistics : for print related loads.

Response time duration : Response time in the SAP Application server are distributed . Used for monitoring SLAs. For instance someone guarantees an average response time of DIA as 3s or better.

Load from External System : For External System Activities.

Web Statistics : related to web reporting caused by Business Intelligence Activities.

DB Connection Statistics : Stats regarding DB access , differentiated by DB user . Major load is caused by connection "Default" 


In the next blog we will dive deep in how we analyze the workload.

Labels:

Comments

  1. Anonymous28 June 2022 at 17:49

    Great

    ReplyDelete
  2. Anonymous12 December 2022 at 06:15

    Great post! I found ST03.net quite useful as well.

    ReplyDelete
  3. Anonymous26 March 2023 at 12:10

    Where can we found next blog?

    ReplyDelete
  4. Ziya2 September 2023 at 02:49

    Great blog!. Looking forward to post more blog like this . custom erp development in chennai

    ReplyDelete

Post a Comment

You might find these interesting

8 Must-Know Questions About Object Store on SAP Business Technology Platform

What is the problem that Object Store solves ? Modern enterprise systems increasingly deal with massive volumes of unstructured data such as documents, logs, media files, and backups. Traditional relational databases are not optimized for such workloads. What is Object Store ? Object storage—commonly referred to as blob storage—addresses this gap by providing scalable, durable, and cost-efficient storage for unstructured data. Object storage is a storage architecture designed to manage unstructured data as discrete units called objects.  Each object consists of: Binary data (file content) : Image , File etc Metadata (descriptive attributes) : File size, Content type, Last modified timestamp, Storage class (hot, cool, archive) Unique identifier (key or URL) : unique path-like string used to locate a blob inside a bucket Unlike file systems or relational databases, object storage does not rely on hierarchical file structures or schemas. The SAP BTP Object Store service is a managed, ...
Post a Comment
Read more

Understanding SAP BTP Global Accounts, Directories, Subaccounts, and Entitlements

In SAP Business Technology Platform (BTP), organizing your resources effectively is crucial for efficient management and scalability. This blog provides a comprehensive overview of global accounts, directories, subaccounts, and entitlements within SAP BTP. What is a Global Account in SAP BTP? A global account in SAP BTP represents the contractual agreement you have with SAP. It serves as the top-level container for managing various resources, including directories, subaccounts, members, entitlements, and quotas. Within a global account, you receive entitlements and quotas for platform resources, which can be allocated to subaccounts for actual consumption. How Do Directories Function in SAP BTP? Directories in SAP BTP allow you to organize and manage your subaccounts based on your technical and business requirements. A directory can contain other directories and subaccounts, enabling you to create a hierarchical structure. This hierarchy can be up to 7 levels deep, with the global ac...
Post a Comment
Read more

Deploying SAP on Google Cloud : Part 1

 Connect to Google  Connection Method To be Used for Speed Explanation Example Uses Cloud VPN Proof of Concept Variable, up to 3 Gbps Connects on-premises network to Google Cloud securely over the internet using IPsec VPN tunnels. Creating a Cloud VPN tunnel between on-premises and Google Cloud. Encrypted IPsec tunnels Dedicated Interconnect For Enterprise level connect 10 Gbps to 100 Gbps Provides a dedicated, private connection between on-premises and Google Cloud through Google's network. Provisioning a dedicated interconnect connection. Direct physical connection between on-premises and Google Cloud network infrastructure Partner Connect If you have a data center which cannot be reached to Dedicated Google facility. Variable, up to 100 Gbps Allows connecting to Google Cloud through supported service providers. Establishing a connection with a supported service provider. Utilizes service provider's network infrastructure. Configure Tunnels with Google Cloud Platform IPsec
Post a Comment
Read more

KPIs for Recovery in HANA Database Administration

Introduction: In the dynamic landscape of database administration, ensuring the robustness of a system is paramount. One crucial aspect that demands meticulous attention is the recovery process following a system failure. Two key performance indicators (KPIs) stand out in this realm – Recovery Point Objective (RPO) and Recovery Time Objective (RTO) . In this technical blog, we will delve into the significance of these KPIs for HANA database administrators and explore strategies to optimize them. Recovery Point Objective (RPO): RPO is a critical metric that defines the maximum acceptable data loss in the event of a system failure . For HANA database administrators, establishing an RPO involves a careful balance between data consistency and the overhead of continuous data replication. Continuous Data Backups: To meet stringent RPO requirements, implementing continuous data backups is imperative. Utilizing HANA's native backup capabilities and integrating them with a robust backup s...
Post a Comment
Read more

Notes for Build Resilient Applications on SAP BTP with Amazon Web Services [ Week 1]

Welcome back to the next chapter in our ongoing series dedicated to unraveling the dynamic interplay between SAP Business Technology Platform (BTP) and Amazon Web Services (AWS). For those just joining us, this blog serves as an invaluable resource for individuals delving into the world of SAP BTP or seeking a comprehensive reference guide. SAP BTP, or SAP Business Technology Platform, is a comprehensive platform that brings together various essential capabilities for application development, automation, data management, analytics, planning, integration, and AI. These features are all integrated into a unified environment, making it user-friendly for both professional IT developers and citizen developers. Image Credit  Key Features of SAP BTP: Application Development: SAP BTP offers a range of tools for development. For instance, SAP Build enables low-code development, while the SAP Business Application Studio caters to core developers, providing services like document management a...
1 comment
Read more

Execute HANASitter for hang situation analysis

The SAP HANAsitter is configured to perform default checks once every hour to ascertain the online and primary status of SAP HANA. Upon confirmation, it initiates tracking procedures, which involve regular responsiveness assessments (typically every minute). If SAP HANA becomes unresponsive, the HANAsitter commences recording activities, potentially capturing call stacks of active threads, run-time dumps, index server gstacks, and/or kernel profiler traces, although, by default, no recording occurs. When SAP HANA is responsive, the script scrutinizes critical features, including a standard check for more than 30 active threads. If this threshold is exceeded, the script triggers recording. Upon completing the recording process, the script exits, with an option to be configured for restart using the command line. Setup Steps Overview: Begin by creating an SAP HANA user with the desired name (e.g., HANASITTER) and assign the CATALOG READ privilege to it. Establish a user key in the hdbuse...
Post a Comment
Read more

Huge Multiversion Concurrency Control (MVCC) Versions in HANA

What is MVCC? MVCC is a database concurrency control method that allows multiple transactions to occur concurrently without conflicting with each other. In a nutshell, it ensures that each transaction sees a snapshot of the database at a specific point in time, even if other transactions are making changes concurrently. MVCC in SAP HANA: SAP HANA uses MVCC to manage concurrent access to data. Each transaction in HANA sees a consistent snapshot of the data at the time the transaction began. This is achieved by maintaining multiple versions of a data row, each associated with a specific transaction or point in time. The Issue of Huge MVCC Versions: Now, the term "Huge MVCC Versions" indicates a situation where there is a significant number of these versions for a particular set of data. Here's why this might become a problem: Increased Memory Usage: Each version of a data row consumes memory. As the number of versions increases, the overall memory consumption by the databas...
Post a Comment
Read more

Building the Foundation of the PO System: Architecture and some terminologies

1. Loosely Coupled and Tightly Coupled Services : Loosely Coupled Services : These services interact with each other with minimal dependencies. Changes in one service don't significantly impact others. Pros include flexibility, easier updates, and better scalability. A common example in PO is when a shipping service communicates with an inventory service. Changes in the inventory service won't necessarily disrupt shipping. Tightly Coupled Services : These services are interdependent, so changes in one service can affect others. While they might provide faster communication, they can be less flexible and harder to maintain. For example, tightly coupling an order processing service with a payment service means any change in payment could ripple to order processing. 2. SOA - Service-Oriented Architecture : SOA is an architectural approach where everything is treated as a service, encapsulating specific functionality. Service Orchestration Example (Banking Transaction) : Consider ...
2 comments
Read more

STONITH : I maintain your servers integrity. Part 1

Hello Fellow Administrators , Today we will be discussing about STONITH 
Post a Comment
Read more