Questions that will be answered in this blog are:
- Which information should I provide when reporting a performance issue to SAP?
- What should I have already checked before submitting performance issue to SAP?
When to report a performance issue to SAP?
You can report a performance issue to SAP when you are sure it is caused by standard SAP.
There are 2 cases:
- Overall system performance
- Specific transaction performance
Validations to be done upfront:
- Issue is system wide: in this case it is most likely a issue with your network, storage, database or all work processes are filled up. See the blog on performance first aid kit. Run also the snapshot monitoring (see blog).
- Database issues: check for example specific notes on Oracle: 1817553 – Checklist for performance problems in SAP Oracle Databases, and HANA: 2000000 – FAQ: SAP HANA Performance Optimization
- Specific transaction performance: check that the issue is not caused by Z code. To analyze if Z code is not the root cause, run the ANST trace for the transaction that is reported as slow. Then check if Z code is involved or not. You can use the SAT tool or ST12 performance trace tool to further analyze the Z code poor performance.
- Check the tools in the PDF document attached to OSS note 2442365 – Survival Guide for performance analysis on SAP system.
- In case of performance issues between systems and users: for example on development transaction is fast, but slow on production, or it is fast for user A, but slow for user B, then first check OSS note 3006447 – Comparing slow transactions, users and reports between systems.
What information to provide in a performance issue to SAP?
In case of specific performance issues, add as much specific information as possible. Try to have a case in a development, test or acceptance system as well. In these systems SAP can replay the performance issue without running the risk of hampering the end users performance. Add trace files (ANST, ST12) to speed up the analysis for SAP. It also makes debugging and running large trace files easier for SAP.
Good checklists are present in OSS notes: