SAP Performance Testing


What is SAP Performance Testing? 

SAP performance testing helps IT teams ensure that their SAP software landscapes are consistently high-performing, reliable, and support business demands. 

The criticality of performance testing SAP software has only increased with today’s SAP system landscape. Multiple systems integrate with business processes, spanning different business functions, and involving multiple SAP applications, third-party products, and middleware.  

Testing modern SAP applications powered by SAP S/4HANA and SAP Fiori 2.0, which involve many highly distributed components, is especially important.  

What is SAP Performance Testing? 

SAP performance testing helps IT teams ensure that their SAP software landscapes are consistently high-performing, reliable, and support business demands. 

The criticality of performance testing SAP software has only increased with today’s SAP system landscape. Multiple systems integrate with business processes, spanning different business functions, and involving multiple SAP applications, third-party products, and middleware.  

Testing modern SAP applications powered by SAP S/4HANA and SAP Fiori 2.0, which involve many highly distributed components, is especially important.  

Key Performance and Scalability Indicators 

Before testing performance it is important to understand two fundamental characteristics.  

  1. Response time. Defined as the time between when a user triggers an interaction and the user sees a UI that is ready for the next input, expected response time can vary depending on the perceived complexity of the task. “Users make assumptions about the complexity of each request and, based on these assumptions, they grant the system a corresponding amount of time to process their request,” writes the author of an SAPinsider article. “The time users allow for the system depends strongly on their perception of the complexity of the task. Achieving sub-second average end-to-end response times is a target for interactive applications that process business data of normal volumes. Sub-second response times are standard and in line with studies on perceived performance conducted by our usability team.” 
  1. High throughput. More relevant for background processes, high throughput is generally expected to result in systems running in an optimized and predictable manner — even in high-load situations. “The precondition for high throughput is having software and hardware that are scalable. A scalable software system can predictably handle increasing amounts of work and should be easily extendible to process more tasks,” writes the author. 

Case Study: McKesson Ensures Business Continuity with Automated Testing 

McKesson runs one of the largest SAP environments in healthcare. Its complex landscape, the nature of its business, and a goal of updating its software on a daily and sometimes hourly basis required the company to implement rapid and rigorous testing. It undertook a testing transformation in 2019 working with Tricentis, implementing its enterprise continuous testing platform, and preparing for an SAP S/4HANA roll out.  

At the time of the case study’s publication McKesson was well on its way to reaching 90% test automation with a 35% reduction of testing costs. And, McKesson is able to prevent unexpected, adverse effects on the processes its clients depend on. 

SAP Performance Testing Tools 

SAP provides solutions for performance testing, including SAP Enterprise Performance Testing by Tricentis, formerly named SAP Load Testing by Tricentis. It offers cloud-based testing.  

And, SAP LoadRunner by Micro Focus. It can be used to validate software performance, virtualize your network, simulate workloads, benchmark production system performance, and optimize your deployment of SAP HANA software. 

Tricentis and Panaya are considered leaders in SAP software testing, including performance testing. 

6920 results

  1. Extending and Modifying SAP Standard with Business Add-Ins and the New Modification Assistant

    Published: 15/October/1999

    Reading time: 1 mins

    Up until now, Customer Exits and Modifications were the only development techniques available for extending and modifying standard SAP applications. Release 4 introduces two new techniques – Business Add-Ins and the Modification Assistant. Business Add-Ins are predefined exit points in a source that allow developers to either insert their own logic during implementation or simply…...…
  2. Real-Time, Outbound Interfaces to Non-R/3 Systems Made Simple with Change Pointers, Message Control, and Workflow

    Published: 15/October/1999

    Reading time: 1 mins

    Developers often struggle with custom ABAP/4 code or database logging to devise ways to track changes to data and then to trigger output of that changed data across outbound interfaces to non-R/3 systems. The onus of creating a way to track changes as they occur rests squarely on the shoulders of these developers, but it…...…
  3. Size Does Matter – Strategies for Successful SAP R/3 Capacity Planning

    Published: 15/October/1999

    Reading time: 2 mins

    Capacity planning is not a trivial task. Choose your hardware vendor and equipment carefully, and upgrades will pose few problems. Choose the wrong vendor-model combination, and you will be forced to make extensive changes to your hardware and operating system that will entail extensive planning and testing, and could ultimately require all new equipment. So…...…
  4. An Introduction to SAP’s New and Improved Frontend Printing

    Published: 01/December/1999

    Reading time: 1 mins

    Dr. Stefan Fuchs describes a new spool access method that allows the transfer of print data from the application server to the current location of the SAPGUI. From there the data is sent to the local spooler on the user’s particular frontend. That new spool access method — method “F” — is what SAP calls…...…
  5. Achieving a More Manageable and Reliable R/3 Spool Server Landscape Using Release 4 Output Classifications, Logical Servers, and Alternate Servers

    Published: 15/December/1999

    Reading time: 2 mins

    Three new output features give rise to a more manageable, more reliable R/3 spool server environment — classifications, logical servers, and alternate servers. With Release 4, classifications of output devices and spool servers (along the lines of production, high-volume, desktop, and test printing) are now made possible within R/3 itself. This helps you ensure that…...…
  6. ABAP Programming – An Integrated Overview

    Published: 15/January/2000

    Reading time: 2 mins

    With Release 4.0 and the debut of ABAP Objects, SAP is replacing the classical distinction between reporting and transaction programming with an integrated view, recognizing the simple fact that all application logic is programmed in ABAP and that the application can communicate with the user via screens and with the database via a common interface…....…
  7. A Beginner’s Guide to Accessing BAPIs with the SAP DCOM Connector

    Published: 15/January/2000

    Reading time: 2 mins

    This article will introduce you to the basic design principles behind SAP DCOM Connector (SDC), show you how to build BAPI-enabled applications with SDC in Visual Basic, and discuss some advanced concepts for SDC-based applications. In order to keep things simple, we will assume that our applications are built without MTS. So I will not…...…
  8. Extending SAP Business Workflow with Web Forms

    Published: 15/January/2000

    Reading time: 1 mins

    Web forms are the means by which developers can create applications that enable users to start workflows and execute work items from the comfort of a Web browser. A Web form is a simple, intuitive interface, which is made up of a relatively short list of fields and a “Submit” button. This interface obviates the…...…
  9. Lessons in Logon Load Balancing

    Published: 15/January/2000

    Reading time: 2 mins

    In large SAP R/3 environments that require multiple application instances, you can achieve intelligent, automated distribution of workload across multiple application instances, with minimal impact to end users, through logon groups. This article explains how logon groups work and how to use them to establish a logon load balancing strategy that can improve system performance,…...…
  10. Leveraging the R/3 Warehouse Management Structure with the MM-MOB and WM-LSR Interfaces

    Published: 15/January/2000

    Reading time: 2 mins

    /Project ManagementIntegrating the R/3 Warehouse Management (WM) module with mobile data entry devices and external warehouse management systems is made possible by two interfaces — Mobile Data Entry (MM-MOB), which enables mobile entry and transfer of data to and from SAP, and Warehouse Control Unit (WM-LSR), which enables the sending and receiving of information between…...…