The purpose of this task is to confirm that the system can carry the full volume of your company’s crucial SAP business processes, enabling you to identify potential improvements to system performance before going live. Determine the transaction volume, data volume, and required levels of performance for each critical SAP business process. As each test procedure is set up in this activity, the necessary volume of transactions and functions is generated. Once the test has been run, review the results and make any changes to fine tune system performance.
1. Evaluation – Check Expected Results
In practice, in the course of implementing the Business Blueprint, changes are made that affect data volumes in the core transactions. Working with the application owner, review the central business processes and core transactions. Check the expected print volumes, and the archiving strategy in the core processes. Check that the user department has conducted the functional test, and that the workflow for the business process will not be changed.
Record:
- How frequently the business process is used in productive operation
- How many users work with the business process
- What crucial business processes there are upstream, or downstream
- Does the business procedure requires its own volume test or stress test, and if so:
· What are the critical parameters for the business procedure (for example, a two-second average processing time to create a sales order)
2. Testing – Reporting Results
Check whether suitable data has become available during the test process for the identified crucial business procedure.
Consider also what you can learn from the technical monitors in the SAP system.
Pay particular attention to:
- Measuring procedures for the test
- The clarity of the test procedure
- Incorporating the test in the software logistics infrastructure
Conduct the volume test and use the logged results to create useful documentation for the business procedure.
SAP system carries full volumes for all critical SAP business processes.