SAP best practices · LessonReviewed by Anitha M, SAP Trainer, 13 yrs · Updated · Published · SAP S/4HANA 2023 · all levels
SAP Best Practice Performance
Performance best practice is mostly about efficient database access and code, plus proper sizing, applied consistently so the system stays fast at scale.
Quick answer
SAP performance best practice is a short list applied from the start: no SELECT in a loop, read data once into internal tables; select only the rows and columns needed with an indexed WHERE; aggregate and join in Open SQL or CDS, especially on HANA; use sorted or hashed tables for large data; and measure with ST03 and ST05 first.
Key takeaways
- Watch out: a test against development data volumes proves nothing about production.
Key practices
- No SELECTs in loops; read data once into internal tables.
- Select only needed rows/columns; use indexed WHERE clauses.
- Aggregate/join in the database (Open SQL, CDS), especially on HANA.
- Use sorted/hashed internal tables and field-symbols for large data.
- Size the database, buffers and work processes for the workload; measure with ST03/ST05.
Why it matters
Most performance problems are preventable custom-code or database issues. Applying these rules from the start, and measuring before tuning, keeps the system responsive as data and users grow, avoiding the slow programs that plague poorly-built systems.
Common pitfalls
- Skipping the discipline under delivery pressure.
- Not documenting decisions.
- Ignoring the clean-core principle.