Home > Articles

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

9.5 Identifying Key Transactions and Business Processes

As I said before, there are many ways to identify the key transactions and business processes representative of a particular condition, event, or state. The opinions and experience of the end-user community that actually conducts much of this work is an obvious source of knowledge, albeit an imperfect and not necessarily holistic source. Regardless, I still recommend that you speak with your business representatives and functional experts. Indeed, for systems that have not gone "live" yet, there's really no alternative. But for precise and historically accurate information that reflects the load borne by your production systems day in and day out, week after week, month after month, I strongly encourage you to leverage the abundance of transactional and performance data sitting in CCMS. In this way, you can have insight into the whole picture—the most popular online transactions, the heaviest batch processing jobs and execution windows, visibility into the mundane repetitive tasks collectively responsible for much of the load, and so on. Month-end closes, seasonal peaks, and other high-water loads can be clearly understood in this way, and beyond this, how all of the various functions intertwine and come together to create the lifeblood of an SAP system—its workload—becomes clear as well.

Prior to following the steps outlined in the sections that follow, you need to determine the scope—typically by looking at an entire collection of application servers servicing an SAP system—and then the timeframe you wish to analyze. That is, SAP CCMS will allow you to look at the last "X" minutes or, probably more applicable for our purposes, a particular time period. I often start with analyzing the load of what I'm told is a "typical week" by plugging in start and end dates that reflect 7 full days (usually Sunday at 3 a.m. until the next Sunday at 2:59 a.m., though the timeframe you select may be different). I like somewhere around 3 a.m. because it's often the quietest time of the evening—backups are usually completed, the system is back up and available, but scheduled early-morning batch processes have not yet commenced, and few online users tend to be on the system. I try to avoid capturing only a partial business process or workload—as much as possible, I want to capture the entire week's work the moment it begins, without cutting anything off in the beginning or the end.

From this starting point, I then work to identify peak days within the week, and even peak hours within particular days. The term peak is subjective, of course, but most often involves first uncovering and sorting the quantity of transactions executed. Next, I'll change tack and look at all the transactions sorted by database load, CPU load, and so on. In this way, I can begin to understand the load placed on the various hardware components that underpin SAP. After this detailed analysis, I'll often take a look at an entire month's worth of data as well, just to be sure I didn't miss a particular processing peak not easily seen otherwise. And, in some cases, I might even drill down into a particular application or batch server, especially if capacity planning is one of the goals of the stress testing. In the sections that follow, we will walk through the exact steps necessary to uncover the specifics that come together to create your workload. To help you apply this process to all SAP systems, I will only draw on CCMS, as opposed to SAP Solution Manager or third-party systems-management applications and other tool sets which you may or may not have at your disposal.

9.5.1 Online User Transactions

To determine the mix of your peak online user transactions and how they interplay to create a load on your SAP system's hardware components, log on with a user ID capable of executing core basis transactions to the system being tested, and perform the following steps (if you prefer the newer ST03N, keep in mind that a certain amount of modification to the listed steps will be required. The changes are quite intuitive, fortunately, and for experienced SAP administrators or Basis consultants will present few problems, if any):

  1. Execute transaction /nST03 (the Workload Analysis screen is displayed).

  2. Click the "Performance Database" button.

  3. Select timeframe.

  4. Select the "dialog" button—in this way, only online transactions are analyze.

  5. Select "detailed analysis."

  6. Select a column to sort by, such as CPU, and double-click it. Transactions will now be sorted by those that consume the most CPU time. Record the top 40 transactions.

9.5.2 Batch Processing and Reporting

Follow a process similar to that outlined previously, though changed to reflect batch processes:

  1. Execute transaction /nST03 (the Workload Analysis screen is displayed).

  2. Click the "Performance Database" button.

  3. Select timeframe.

  4. Select the "background" button—in this way, only batch processes are analyzed.

  5. Select "detailed analysis."

  6. Select a column to sort by, such as database response time, and double-click it. Transactions will now be sorted by those that are most disk-intensive. Record the top 40 transactions.

9.5.3 Most Popular Transactions and Other Workloads

Using ST03, the process to identify the most popular transactions (i.e., those that aren't necessarily the hardest hitting but represent the bulk of activities performed on the system) is as follows:

  1. Execute transaction /nST03 (the Workload Analysis screen is displayed).

  2. Click the "Performance Database" button.

  3. Select timeframe.

  4. Select the "total" button—in this way, all transactions are analyzed.

  5. Select "detailed analysis."

  6. Select a column to sort by, such as CPU, and double-click it. Transactions will now be sorted by those that consume the most CPU time. Record the top 40 transactions.

9.5.4 Mixed-Bag Testing

With the step-by-step processes outlined previously, you should now have an understanding of the key online, batch, and noise transactions hosted by your system. At this point, you need to bring this knowledge together to create a "mixed-bag" workload—in effect, your workload to be emulated through scripting. Your workload mix will vary based on the goals of your test. For example, if you wish to test the benefits of a new server platform, you'll probably want to focus on the transactions that drive the heaviest CPU load. Similarly, if an updated disk configuration or brand-new virtual SAN is potentially in your future, you'll probably wish to create a workload that beats up the disk subsystem in the most representative manner.

Refrain from only focusing on a single type of transaction, though, if time and budget allow. Variety should be your mantra. For example, when it comes to disk subsystem testing, I suggest that you combine a number of hard-hitting online transactions and reports along with key batch processes, rather than simply going with easily scripted batch loads (easy because once you do one type, others tend to follow similar patterns or allow for cookie-cutter scripting approaches). In this way, different disk access patterns will be represented, which in the end will also best represent the real world. And I suggest tossing in a few noise scripts as well simply to keep a certain level of constant activity in the background, again representing the real world of most SAP enterprise solutions. At the end of the day, a mix of perhaps 50% batch processes to 25% online transactions and reports and 25% scripted noise activities will serve you well in stress testing and tuning your SAP disk subsystem. And the same argument can be made for testing other subsystems or technology stack layers, too—variety is desirable as long as your budget can absorb the incremental time necessary to perform the requisite business process scripting.

  • + 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.

Overview


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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


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.

Links


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