6 Kick-Ass Tips to Improve SAP Performance

© Basis Technologies International 2014

kickas


Kick-Ass tips to improve your SAP performance


and you want to

your performance…

STEP UP

the first step is ensuring that you have

high performance code



the SAP code inspector rapidly finds issues within your ABAP code that might not be obvious to the naked eye…

things like selects not

using indexes, and

nested select statements



you might know that you can get

it from

SE80/SE37/SE20

via

Menu>Check>Code Inspector

but have you tried

transaction

SCI?

take a look, it provides some very powerful extra

features

Kick-Ass tips to improve your SAP performance Kick-Ass tips to improve your SAP performance

http://wiki.scn.sap.com/wiki/display/ABAP/Code+Inspector




you should be using Code Inspector as part of your Change Control and QA processes to

prevent issues that might affect performance from getting into your production systems in

the first place…

TEACHER’S PET



Big Data has



meaning that your reports, extracts and interfaces get slower and slower as the data they crunch gets

bigger

bigger and



because ABAP code processes large data volumes

sequentially your ABAP runtimes will

get longer and longer over time



this means that your business users will have to wait longer for their precious information



which means - yep, you guessed it

even more waiting…

and, if multiple users are running the same report, they’re placing extra load on your hardware to run the same reports multiple times



take advantage of parallel processing

spread the workload across

your existing under-utilized

processing power



but parallel processing is complex to develop

control and manage…

and predefining multiple background jobs with variants isn’t really a

scalable solution



and even allow reports to be run once for multiple

users without any performance

overhead

solutions like Mass Data

Runtime simplify parallel

processing


http://basistechnologies.com/Run-SAP-ABAP-Faster-No-Hardware

http://basistechnologies.com/Run-SAP-ABAP-Faster-No-Hardware


sometimes, the fastest way to

make your code run faster is not

to code…



log out of SAP

take a walk to sit with your business users or set up a regular call with your

user community


your business

users know exactly

what they want



sometimes this can be

lost in translation

between

&



it’s only when you spend time really understanding business

requirements that you can write code that elegantly delivers them

many performance issues can be resolved simply by restricting

default values on selections screens, or breaking processing

down into discrete steps


frequent user conversations will improve your understanding of

requirements and open up new ways of working that

save days of unnecessary coding



like making incorrect

tables selections by declaring selections

without full indexes or incorrect indexes

when coding, there are some important points that are easily overlooked but have a

huge impact on performance…



indexes are your

friend



take general ledger table BSEG it contains most of the information required but unless it’s read using the full key, it’s very inefficient as a cluster table leading to slow data retrieval



click on the Indexes button in SE11 to compare the indexes against your WHERE clause and adjust to fit get the exact index for BSEG, AUFM, VBFA, EDIDC or any of the massive cluster tables and you’re well on the way to writing high performance code



these tables have efficient

indexes available to act as the

driving SELECT to then allow a full

key to be used on BSEG

leading to much

improved performance

BSIS/BSAS G/L ITEMS

BSID/BSAD CUSTOMER

OPEN/CLOSE ITEMS

BSIK/BSAK VENDOR

OPEN/CLOSE ITEMS



WRONG…

if you ever attended the BC400 at the SAP Academy you were shown transaction SE30 on day 1…



it provides you with an area where you can test two versions of code against each other. that often overlooked Tips & Tricks button will take you to this very useful sandpit…


you can check if one WHERE clause is more efficient than another… or if an INNER JOIN really does improve things more than a SELECT/FOR ALL ENTRIES combo



a few minutes trying out different data input and SELECT statements will reap rewards later in final processing times and a little online research will reveal plenty of blogs full of performance tips and SCN forums crammed with topics that will help you work out whether method A is faster than method B

you might be surprised…



shared experiences make us all better

programmers so make sure you

pass on your learning for the benefit of

fellow developers

if you solve an SAP performance problem… post the solutions to the SCN forum



become a performance informer and put 10 minutes in your diary each week to share what you’ve learned

if we all help one fellow ABAP developer to improve their SAP system performance, the world will be a better place


kickas

www.basistechnologies.com

http://go.basistechnologies.com/l/44792/2014-09-17/mtp1



6 Kick-Ass Tips to Improve SAP Performance

Software

Transcript of 6 Kick-Ass Tips to Improve SAP Performance