Home > Articles

  • Print
  • + Share This
This chapter is from the book

9.8 SAP Component and Other Cross-Application Test Mix Challenges

For each particular SAP application, component, or solution, there tends to be a special set of circumstances or limiting factors that complicates creating a repeatable, consistent, or adequate test mix. The following list identifies key problem areas I've run into in the past, and what I did to work around these issues:

  • R/3 business processes range from one-offs to multicomponent, highly complex sets of transactions. But, for most companies, R/3 activities tend to focus on discrete transactions run repeatedly by many users throughout the day, alongside a subset of core batch processes. I suggest focusing on a few key business processes, like order-to-cash, to take advantage of the input/output nature of the underlying transactions. In this way, obtaining input data is a simple matter of leveraging the previous transaction's output. And the first transaction—a sales order—can originate in any number of other systems and be easily completed if core customer, material, and plant data are available and abundant.

  • APO includes both online users and batch-oriented business processes. The real load borne by the system is represented by the latter, though, especially with regard to demand or production planning runs, or Available to Promise (ATP) processing. Online user activity is negligible in comparison. From an input data perspective, the number of key figures that reside in your liveCache server, the number of characteristic combinations (properties) that describe an object, the number of periods (measured in weeks) against which these processes will run, and of course the number of sales, purchase, planned, and other orders transferred from R/3 to APO are all important.

  • BW and SEM activities range tremendously, so it's no surprise that input data ranges are equally wide. In the past, I've started a BW stress test by kicking off an R/3 data extraction process, or simply by pulling data from the ODS to create and populate a cube. These are certainly important functions, but may not represent your most important goals. Instead, you may wish to run queries against one or more standard or custom InfoCubes. The key will therefore be the cubes themselves—if it matters little how the data move through your SAP system landscape, make it easy on yourself and start with a fully populated set of cubes.

  • CRM data hail from a number of systems within the CRM system landscape, including the TRex Server, Multi-Channel Interface Server, InQMy Application Server, and potentially a Workgroup Server and Communication Station, not to mention the CRM server itself. As such, it can be one of the more complex SAP solutions to stress test. As a starting point, I suggest that you concentrate on the core user type your system hosts (probably a Mobile Sales or CIC user, though others exist), and determine the input necessary to support the top five or so key user transactions. For your Mobile Sales users, you might focus on managing opportunities or activities, creating customer orders, performing service-related transactions, or managing customer, product, or project-specific data, for instance. If you host CIC users, you might instead go with the transactions and activities outlined in the SAP CRM benchmark kit, for example, and focus on transactions relevant to managing incoming and outgoing CIC calls

  • EBP (the core component of SRM) is quite complex, especially from an input perspective—data originating from Requisite BugsEye (an online catalog), R/3, BW, and EP complicate executing core EBP business processes. But that's not all! There are other SRM components that need to be considered as well, like the SAP Bidding Engine and SAP Supplier Self Services. Given all of this, a seemingly straightforward shopping-cart–driven procurement business process will have many touch points, will pull data from many sources, and will generally represent a whole lot of scripting and coordination effort.

  • EP has evolved significantly over the last few years and today represents one of the fastest growing products in SAP's line-up. It's also potentially one of the most important products a company will implement, in that all users could conceivably (and, it is hoped, will) leverage its single sign on capabilities to gain access to all other SAP systems and many third-party resources, creating a potential high-availability and performance nightmare should the EP technology stack lack scalability. Thus, stress testing EP will only grow in importance as it continues to be deployed across the globe. Fortunately, stress testing can be conducted quite easily. Sure, many systems represent potential integration points, but an effective load test could very well consist of accessing only local resources.

  • PLM supports users responsible for managing product, asset, and process information at any point in the product lifecycle, from selection and purchasing through production ramp-up, installation, operation, engineering changes, maintenance/repair, retirement, and more. From a data input perspective, then, you need to understand the precise functionality being implemented and what then needs to be tested—everything from Life-cycle Data Management and Asset Lifecycle Management to core functionality like Program and Project Management, Quality Management, and Environment, Health, and Safety (or EHS) can come into play. Plus, because PLM is implemented as an enterprise portal solution and is tied closely with CRM and likely APO, the business processes that can result may be complex indeed. I therefore suggest going after either the biggest couple of functional areas to be implemented (in terms of transaction counts or user counts), or instead the most critical functional areas, and script core transactions rather than full-blown business processes.

The world of SAP has grown considerably over the last year, though—well beyond the components and solutions just highlighted. The SAP XI, xApps, and other products represent additional systems that may be tested individually or as part of a larger SAP solution. For example, simulating the number and size of the messages that the XI Integration Server processes represents an excellent method of testing XI without all of the integration points necessarily in the picture.

XI offers some exciting capabilities when it comes to viewing collaborative cross-application SAP business processes. For example, business processes that span your R/3, APO, and CRM systems can be tied together via synchronous and asynchronous messaging defined by and maintained within XI. You may then leverage XI to enable true cross-application business process stress testing, regardless of whether heterogeneous system landscapes have been deployed—test cases would initiate from one of the core SAP systems tied together in this manner, of course. And test execution would be seamless, because XI would handle moving the output from one transaction into the proper component, where it becomes input for the next transaction in a business process. Beyond this awesome timesaving by-product of XI integration, XI also allows you to visually depict and manage SAP components as well as other enterprise applications from Baan, Broadvision, JDE World Software, Oracle, PeopleSoft, Siebel, and more. In this way, the inclusion of SAP and third-party enterprise applications may all be tied together into a cohesive virtual system. More to the point, these complex systems may be managed as a single entity rather than as a bunch of individual systems, which further simplifies testing.

Mainstays like SAP's ITS also continue to thrive. From a data input perspective, I suggest you focus on common transactions supported by back-end systems like R/3. Because all (or nearly all, in the case of older releases of R/3) SAP screen content is maintained in HTML on the ITS server, testing ITS amounts to testing the speed and throughput of Web connections. Fortunately, tools abound that support this input type, as we reviewed in Chapter 6, and scripts of this nature are fairly easy to write and maintain. And the best news of all is that you'll find that your ITS users tend to execute the same transactions as their SAPGUI-enabled colleagues (though exceptions exist—I've got a customer that has pushed the bulk of its HR and ESS workload on ITS, for instance, whereas other modules and functional areas are accessed via the traditional SAPGUI). So once you've established the core transactions executed by a particular SAP product or component, you're well on your way to using this information in support of ITS testing, too.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020