Department performance dependent bonus

Hi,
We have an On premise SAP system. My company has been giving yearly bonuses to managers which are dependent on company and department/line of business performance via excels so far. Employees get their bonus through the usual MSS.
Can anyone please direct me to SAP best practices on how this can be implemented? It is not a simple Matrix Guideline based on dimensions as it involves multiplying performance dependent factors of org units. SF has this functionality but I could not find anything about it for the on-prem system.
Prakash

Hi Dark,
1. Try to make modifications of warranty popup screen using user exit BG000003 : subscreen for Changing Warranty Check Result
regards
pushpa

Similar Messages

Performance depends on hardware for CPU usage below 50%?

I need to assess whether we should move our service to more capable hardware. At present our bandwidth is about 25 megabit out of our gigabit link and typical CPU usage is about 10-40%. I want to know whether FMS will stream with less lag or does that purely depend on client upstream bandwidth?
Cheers.

So there's a couple of pieces you care about here.
1. In your Application.xml your <Live> tag will have settings for queueing aggregate messages (both in size and in time). That will induce delay into your stream (up to a single GOP (keyframe interval)) but will save you oodles of CPU on not having to deliver single messages to clients. However, as mentioned you pay for it in stream latency of about a keyframe interval.
2. The CPU chart from your system is more accurate - FMS historically reported CPU percentage that ONLY FMS is using. I'm not a big fan of that stat since it's deceptive, (only 40% CPU the system must be fine - but only if the other 60% is free) - anyway that can't be changed currently thanks to backward compatability issues . While I can't recommend against it, I will say it's not our most useful stat.
LMK what you find with the live stream queueing, that's more relevant to your performance characteristics on live.
Asa

Performance dependent Warranty Counter

Hi,
Need some clarification with respect to Performance based counters.
I have created an equipment and assigned a master warranty to it with a performance based counter. When i create a notification i get a pop up with the start date mentioned but no end date unlike in Time based counters where start and end dates are mentioned.
Is it posiible to get a pop up mentioning validity remaining for the warranty. For example ( if the validity is for 10000kms and i create a notification at 5000kms then is it possible for the system to generate a pop up that only 5000kms more is left). Or is any special customizing needed.
Thanks in advance
Regards

Hi Dark,
1. Try to make modifications of warranty popup screen using user exit BG000003 : subscreen for Changing Warranty Check Result
regards
pushpa

ECM - Load Bonus information strategy

All,
My client pays bonuses to employees quarterly, the compensation cycle is performed outside of SAP MSS ECM. Thsi is becuase of lot of parameters involved in calculating this Bonus. This bonus is dependant on company performance, department performance personal performance and afew other attributes. This is currently done in excel.
What should be strategy to load thi siinformation abck into SAP. i.e in infotype 759.
Should be load them using BDC ince tghe cycle is completed?
regards
Raj

Hi
How the bonus get paid to employee is it via IT0015, if so howz IT record get updated?
Yes u can upload data in IT759 in planned status. Via your configuration u can still control the effective date of Bonus, review period by setting review item and review item attributes. So that you can upload the data in IT759 within the cycle period and later using standard report "Change compensation process status" you can change the status to approved (once HR is happy with amounts got loaded in planned status) and then you can run report of activation which is standard.
Upon activation its takes care of updating IT0015 as well as IT759 simultenously.
Hope this info helps...

How to write a SQL based on a view can get the best performance ?

Hi ,
I am thinking about performance of sql based on VIEW .For the best performance ,How to do when I create and use a view ? for example , Should i use key in my where clause as select data from table? (of cause ,this key refers to the key of table which structure the view. ) , Could you give me any advice on creating and using view in term of performance ?

Hi Guixin Chen,
Performance depends on various factors. The major key factors are:
1. Result Set should be Small
2. Amount of Data Transferred should be minimum.
3. Number of Data Transfers should be minimum.
4. Search Overhead should be minimum.
5. Database Load should be minimum.
For more details, check the following docs.
Performance Notes
http://help.sap.com/saphelp_nw04s/helpdata/en/fc/eb3b7e358411d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/5b/320c40ac368f5ce10000000a155106/frameset.htm
You can also check Performance by,
1. Transaction code ST05
2. From ABAP Workbench using the menu path Test Performance Trace.
Dont forget to reward pts, if it helps ;>)
Regards,
Rakesh.

Performance impact on the size of the CHM file

Is there any impact on performance depending on the size of a
CHM file?

The main issues people have with help file performance
(regardless of whether it is a CHM file) are related to the number
of images, DHTML hotspots, bookmarks and links they have in a
topic. The number of topics in a CHM should not be an issue. What
exactly are you trying to access the performance impact of?

Performance issue when opening DOCX Word Doc with Excel Links

Is this a bug or is there a config setting that can prevent Word from needlessly opening Excel repeatedly (upon initial open of a DOCX Word doc) when pre-existing links should NOT be updated. The behavior is good using 2003 formats (DOC & XLS),
but varies significantly (~100:1 range in performance) depending on the test scenario (see below) using DOCX with XLSX.
We can't move our environment to the new XML formats until we can find a fix. We were led to believe Microsoft knew this to be a bug in Office 2007, but it has NOT been corrected in Office 2010. Omitting a detailed explanation for why we need to
do this, here's our test scenarios:
-Currently testing Office 2010 Pro Trial version on WIN XP SP3. (We have found similar results using Office 2007 with Win7 or XP).
-Word Option Deselected/DISABLED: "Update Automatic Links at Open"
-The Word Doc contains 100 linked Excel tables and is 130K in size (DOCX).
-Each link points to the same 10x10 cell range in one Excel Workbook located in same directory as the Word Doc, although other tests using separate directories produced similar results.
-The Excel Links were inserted into Word via Paste Special/Paste Link/MS Excel Worksheet Object.
-The workbook (XLSX) is 15K in size.
-All Links are set for "Manual" update, our testing showed no difference if links are set to "Auto".
-Again, Word is set to NOT update Automatic links when the document is opened.
-Results shown below are for local hard drive test.
-Network response times are slightly greater on 100mb LAN
-Word is completely restarted prior to each test to make sure there's no application caching involved.
LOCAL DRIVE RESPONSE TIMES TO OPEN THE WORD DOC in Docx format:
1. Open the Word Doc from Word with Excel closed - 175 seconds (Excel appears to be opened and closed once per link)
2. Open the Word Doc from Word with Excel open & workbook closed - 33 seconds (Excel appears to be accessed once per link)
3. Open the Word Doc from Word with the linked workbook already open - 7 seconds (Excel appears to be accessed once per link)
4. Rename Excel XLSX workbook so that Word can't find it. Then open Doc the from Word. 1-2 seconds (Excel does not appear to be invoked)
5. Repeat ALL of the above scenarios 1-4 using DOC and XLS files. These files are created with "Save AS" option based on original test files and then re-pasting the links. 1-2 seconds to open the Word Doc (Excel does not appear to be invoked)
Summary
Using DOCX/XLSX, if Word can't find the linked spreadsheet it gives up and performs nicely during file-open. Otherwise, Word performs needless, time-consuming access to Excel, and in the worst case, opens and closes Excel repeatedly in the background.
Testing with DOC/XLS formats gives good performance across all scenarios.

It is a known bug and one for which AFAIK, there has been no fix. The only way that I could get around it in a particular application was to do something like save the linked information as document variables and then on opening the document recreate
all the information. My memory on exactly what I did is a bit hazy, but I can go back and check if you are interested.
-- Hope this helps.
Doug Robbins - Word MVP,
dkr[atsymbol]mvps[dot]org
Posted via the Community Bridge
"galmcrantz" wrote in message news:[email protected]...
Is this a bug or is there a config setting that can prevent Word from needlessly opening Excel repeatedly (upon initial open of a DOCX Word doc) when pre-existing links should NOT be updated. The behavior is good using 2003 formats (DOC & XLS), but varies
significantly (~100:1 range in performance) depending on the test scenario (see below) using DOCX with XLSX.
We can't move our environment to the new XML formats until we can find a fix. We were led to believe Microsoft knew this to be a bug in Office 2007, but it has NOT been corrected in Office 2010. Omitting a detailed explanation for why we need to do this,
here's our test scenarios:
-Currently testing Office 2010 Pro Trial version on WIN XP SP3. (We have found similar results using Office 2007 with Win7 or XP).
-Word Option Deselected/DISABLED: "Update Automatic Links at Open"
-The Word Doc contains 100 linked Excel tables and is 130K in size (DOCX).
-Each link points to the same 10x10 cell range in one Excel Workbook located in same directory as the Word Doc, although other tests using separate directories produced similar results.
-The Excel Links were inserted into Word via Paste Special/Paste Link/MS Excel Worksheet Object.
-The workbook (XLSX) is 15K in size.
-All Links are set for "Manual" update, our testing showed no difference if links are set to "Auto".
-Again, Word is set to NOT update Automatic links when the document is opened.
-Results shown below are for local hard drive test.
-Network response times are slightly greater on 100mb LAN
-Word is completely restarted prior to each test to make sure there's no application caching involved.
LOCAL DRIVE RESPONSE TIMES TO OPEN THE WORD DOC in Docx format:
1. Open the Word Doc from Word with Excel closed - 175 seconds (Excel appears to be opened and closed once per link)
2. Open the Word Doc from Word with Excel open & workbook closed - 33 seconds (Excel appears to be accessed once per link)
3. Open the Word Doc from Word with the linked workbook already open - 7 seconds (Excel appears to be accessed once per link)
4. Rename Excel XLSX workbook so that Word can't find it. Then open Doc the from Word. 1-2 seconds (Excel does not appear to be invoked)
5. Repeat ALL of the above scenarios 1-4 using DOC and XLS files. These files are created with "Save AS" option based on original test files and then re-pasting the links. 1-2 seconds to open the Word Doc (Excel does not appear to be invoked)
Summary
Using DOCX/XLSX, if Word can't find the linked spreadsheet it gives up and performs nicely during file-open. Otherwise, Word performs needless, time-consuming access to Excel, and in the worst case, opens and closes Excel repeatedly in the background.
Testing with DOC/XLS formats gives good performance across all scenarios.
Doug Robbins - Word MVP dkr[atsymbol]mvps[dot]org

Regarding Performance tunning...

HI Experts,
can you suggest me, how exactly performance is checked.
what is the measure we considered for performance check.
what are ideals status of the performance check for a certain program.
that is, how much should be database use, abap use and the system
use in the program.
i checked my program in t-code SE30, and it is showing almost
above 90% use of database and very less use of abap and
almost no use of system.
so please tell me exactly how much it should be...
Thanks in advance.
Regard,
vijay chavan

Hi
these are the ways of checking performance of a report
Tools for Performance Analysis
Run time analysis transaction SE30
SQL Trace transaction ST05
Extended Program Check (SLIN)
Code Inspector ( SCI)
Run time analysis transaction SE30 :This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing.
SQL Trace transaction ST05: The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.
The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on a particular database table of the ABAP program would be mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.
The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.
To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.
Extended Program Check
This can be called in through transaction SE38 or through transaction SLIN. This indicates possible problems that may cause performance problems.
Code Inspector (SCI)
You can call the Code Inspector from the ABAP Editor (SE38), the Function Builder (SE37), the Class Builder (SE24), or as a separate transaction (SCI).
The Code Inspector indicates possible problems. However, note that, especially with performance issues: There is no rule without exception. If a program passes an inspection, it does not necessarily mean that this program will have no performance problems.
Run time analysis transaction SE30
steps
In Transaction SE30, fill in the transaction name or the program name which needs to be analyzed for performance tuning.
For our case, let this be ZABAP_PERF_TUNING
Run time analysis transaction SE30
After giving the required inputs to the program, execute it. After the final output list has been displayed, PRESS the BACK button.
On the original SE30 screen, now click on ANALYZE button.
The percentage across each of the areas ABAP/ Database/System shows the percentage of total time used for those areas and load on these areas while running the program . The lesser the database load faster the program runs.
SQL Trace ST05
steps
Starting the Trace:
To analyze a trace file, do the following:
Choose the menu path Test  Performance Trace in the ABAP Workbench or go to Transaction ST05. The initial screen of the test tool appears. In the lower part of the screen, the status of the Performance Trace is displayed. This provides you with information as to whether any of the Performance Traces are switched on and the users for which they are enabled. It also tells you which user has switched the trace on.
Using the selection buttons provided, set which trace functions you wish to have switched on (SWL trace, enqueue trace, RFC trace, table buffer trace).
If you want to switch on the trace under your user name, choose Trace on. If you want to pass on values for one or several filter criteria, choose Trace with Filter. Typical filter criteria are: the name of the user, transaction name, process name, and program name.
Now run the program to be analyzed.
Stopping the Trace:
To deactivate the trace:
Choose Test Performance Trace in the ABAP Workbench. The initial screen of the test tool appears. It contains a status line displaying the traces that are active, the users for whom they are active, and the user who activated them.
Select the trace functions that you want to switch off.
Choose Deactivate Trace. If you started the trace yourself, you can now switch it off immediately. If the performance trace was started by a different user, a confirmation prompt appears before deactivation-
Analyzing a Sample trace data:
PREPARE: Prepares the OPEN statement for use and determines the access method.
OPEN: Opens the cursor and specifies the selection result by filling the selection fields with concrete values.
FETCH: Moves the cursor through the dataset created by the OPEN operation. The array size displayed beside the fetch data means that the system can transfer a maximum package size of 392 records at one time into the buffered area.
Reward if useful

Tools in Performance Tunning

What are the tools in performance Tunning in ABAP/4
Thanks Regards,
Kumar

Hi kumar,
Tools provided for Performance Analysis
Following are the different tools provided by SAP for performance analysis of an ABAP object
Run time analysis transaction SE30
This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing.
SQL Trace transaction ST05
The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.
The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on the SPFLI table in our test program is mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.
The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.
To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.
how to perform sql trace:
Poorly written SQL statements have the greatest impact on application performance. An SQL
statement using which an Oracle database system reads and/or sorts thousands or even millions of
rows of data can bring the database to a standstill. Indexes should be used properly to prevent such
situations from occurring. To analyze such problems you should use the SQL Trace (TCode ST05) to
with database access operations.
CAUTION
Only one person can perform an SQL trace at a time. Remember to turn off the
trace when you are finished. SQL trace slows the system down.
1. Using SQL Trace
1. Open a program that you want to analyze, in the editor, so that it is ready and waiting to be
executed.
2. Open a new session using the menu path System   Create session.
3. Run transaction ST05 (enter /nst05-zero-five, not oh-five in the Command field, or choose
the menu path System Utilities Performance Trace).
4. Then the initial screen of the test tool appears.
The status of the Performance Trace is displayed in the lower part of the screen. This status tells you
three things namely
Whether any of the Performance Traces are switched on
The users for whom Performance Trace is enabled
The user that switched the Performance Trace on
If the trace is switched on you must switch it off before you can proceed. There are two cases in
which the trace needs to be switched off. They are
If the trace was started within the past hour, it is possible that it is still being used. Contact the
indicated user or try again later
If the trace was started hours or days ago, the user probably left it on by mistake and it can be
safely turned off
To turn off the trace, press the Trace Off pushbutton.
5. The initial screen has various trace functions such as SQL Trace, Enqueue Trace, RFC
Trace
6. Select SQL Trace.
7. There are various options under which trace can be switched on. They are
If you want to switch on the trace under your user name, choose Trace on.
If you want to switch on the trace for another user or user group, choose Trace on for user.
To enter a single user, specify the user name.
To enter a user group, specify a search pattern (you can use the normal wildcards).
If you want to change the user or user group, switch off the Performance Trace and then restart it,
entering the new users or user group.
8. Now switch back to the window containing your editor session (the one with your program
waiting to be executed).
9. Press F8 to run your program.
Note Just press F8 and do nothing. Do not even press the Back button.
10. When your program has run and the hourglass is no longer displayed, switch back to the trace
window.
11. Press the Trace Off pushbutton.
12. Once Performance Trace is switched off, you can analyze the data
Using Runtime Analysis Tool (SE30)
1. You can open the Runtime Analysis tool as follows:
To start from Choose
Any screen System   Utilities   Runtime Analysis   Execute
Initial screen of ABAP
Workbench
Test   Runtime Analysis
Initial screen of ABAP Editor Program   Execute Runtime Analysis
ABAP Editor Utilities   More utilities   Runtime Analysis
2. In the simplest case, you would enter a short description and a measurement object
(transaction, program, or function module) to run the analysis in the current session.
3. In the Measurement restrictions group box, you can make more specific restrictions for the
measurement. For example, you may want to include only certain statements or time periods.
(For further information refer section 3. 0).
4. To start the measurement, choose Measure runtime. From the initial screen, you can
specify whether the analysis should run in the same session or in a parallel session using the
Enable/Disable button in the In parallel session group box.
5. Run the transaction, program, or function module as normal.
6. Return to the initial screen of the Runtime Analysis transaction. To do so, either leave
transaction, program, or function module as normal, or start the runtime analysis again.
7. The name of the performance data file that has just been created is displayed at the bottom of
the initial screen. The file created by the system is added to the list of performance data files.
You can now analyze, print, or delete the file, or save it locally. The Performance file group
box contains options for analyzing performance files. (For further information refer sections 4.
0 and 5. 0)
regards,
keerthi

BOM Performance Analysis using SAT or SE30 t-code?

Hi,
Currently I'm doing performance analysis of BOM to find out the bottlenecks. I'm doing the analysis using SAT or SE30 t-code.
From my understanding, BOM performance depends upon
1. no. of BOM items
2. BOM Level
3. BOM Evolution over time
Can anyone provide me a hint to find out the bottlenecks in BOM performance. Thanks!!
Regards,
Saravana

I have done the BOM Performance Analysis. Based on the most execution time and top performance consumers, please find my observations…
Functionally, Performance of BOM execution depends upon
Number of BOM items available in the BOM
Number of Assemblies present in the BOM
BOM Levels
BOM Evolution over time
Technically, BOM execution time is purely depends upon
fetching the data from the SAP tables
hitting the same table again and again when goes down the level
loop at the tables / Nested functions used in SAP Program
Hence, I'm closing this thread.....

Performance Analysis Notes

Hi,
I want some "Performance Analysis Notes or material"..
Plz give me some links or send me on my id: [email protected]
Thanks...

Hi, this may help you.
1) Dont use nested select statements
2) If possible use for all entries in addition
3) In the where addition make sure you give all the primary key
4) Use Index for the selection criteria.
5) You can also use inner joins
6) You can try to put the data from the first select statement into an Itab and then in order to select the data from the second table use for all entries in.
7) Use the runtime analysis SE30 and SQL Trace (ST05) to identify the performance and also to identify where the load is heavy, so that you can change the code accordingly
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d0db4c9-0e01-0010-b68f-9b1408d5f234
ABAP performance depends upon various factors and in devicded in three parts:
1. Database
2. ABAP
3. System
Run Any program using SE30 (performance analys) to improve performance refer to tips and trics section of SE30, Always remember that ABAP perfirmance is improved when there is least load on Database.
u can get an interactive grap in SE30 regarding this with a file.
also if u find runtime of parts of codes then use :
Switch on RTA Dynamically within ABAP Code
*To turn runtim analysis on within ABAP code insert the following code
SET RUN TIME ANALYZER ON.
*To turn runtim analysis off within ABAP code insert the following code
SET RUN TIME ANALYZER OFF.
Always check the driver internal tables is not empty, while using FOR ALL ENTRIES
Avoid for all entries in JOINS
Try to avoid joins and use FOR ALL ENTRIES.
Try to restrict the joins to 1 level only ie only for tables
Avoid using Select *.
Avoid having multiple Selects from the same table in the same object.
Try to minimize the number of variables to save memory.
The sequence of fields in 'where clause' must be as per primary/secondary index ( if any)
Avoid creation of index as far as possible
Avoid operators like <>, > , < & like % in where clause conditions
Avoid select/select single statements in loops.
Try to use 'binary search' in READ internal table. Ensure table is sorted before using BINARY SEARCH.
Avoid using aggregate functions (SUM, MAX etc) in selects ( GROUP BY , HAVING,)
Avoid using ORDER BY in selects
Avoid Nested Selects
Avoid Nested Loops of Internal Tables
Try to use FIELD SYMBOLS.
Try to avoid into Corresponding Fields of
Avoid using Select Distinct, Use DELETE ADJACENT
Check the following Links
Re: performance tuning
Re: Performance tuning of program
http://www.sapgenie.com/abap/performance.htm
http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_PerformanceAnalysisTools.asp
check the below link
http://www.sap-img.com/abap/performance-tuning-for-data-selection-statement.htm
See the following link if it's any help:
http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_PerformanceAnalysisTools.asp
Check also http://service.sap.com/performance
and
books like
http://www.sap-press.com/product.cfm?account=&product=H951
http://www.sap-press.com/product.cfm?account=&product=H973
http://www.sap-img.com/abap/more-than-100-abap-interview-faqs.htm
http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_PerformanceAnalysisTools.asp
Performance tuning for Data Selection Statement
http://www.sap-img.com/abap/performance-tuning-for-data-selection-statement.htm
Debugger
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
Run Time Analyser
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617cafe68c11d2b2ab080009b43351/content.htm
SQL trace
http://help.sap.com/saphelp_47x200/helpdata/en/d1/801f7c454211d189710000e8322d00/content.htm
CATT - Computer Aided Testing Too
http://help.sap.com/saphelp_47x200/helpdata/en/b3/410b37233f7c6fe10000009b38f936/frameset.htm
Test Workbench
http://help.sap.com/saphelp_47x200/helpdata/en/a8/157235d0fa8742e10000009b38f889/frameset.htm
Coverage Analyser
http://help.sap.com/saphelp_47x200/helpdata/en/c7/af9a79061a11d4b3d4080009b43351/content.htm
Runtime Monitor
http://help.sap.com/saphelp_47x200/helpdata/en/b5/fa121cc15911d5993d00508b6b8b11/content.htm
Memory Inspector
http://help.sap.com/saphelp_47x200/helpdata/en/a2/e5fc84cc87964cb2c29f584152d74e/content.htm
ECATT - Extended Computer Aided testing tool.
http://help.sap.com/saphelp_47x200/helpdata/en/20/e81c3b84e65e7be10000000a11402f/frameset.htm
Just refer to these links...
performance
Performance
Performance Guide
performance issues...
Performance Tuning
Performance issues
performance tuning
performance tuning
You can go to the transaction SE30 to have the runtime analysis of your program.Also try the transaction SCI , which is SAP Code Inspector.
1 Always check the driver internal tables is not empty, while using FOR ALL ENTRIES
2 Avoid for all entries in JOINS
3 Try to avoid joins and use FOR ALL ENTRIES.
4 Try to restrict the joins to 1 level only ie only for 2 tables
5 Avoid using Select *.
6 Avoid having multiple Selects from the same table in the same object.
7 Try to minimize the number of variables to save memory.
8 The sequence of fields in 'where clause' must be as per primary/secondary index ( if any)
9 Avoid creation of index as far as possible
10 Avoid operators like <>, > , < & like % in where clause conditions
11 Avoid select/select single statements in loops.
12 Try to use 'binary search' in READ internal table. Ensure table is sorted before using BINARY SEARCH.
13 Avoid using aggregate functions (SUM, MAX etc) in selects ( GROUP BY , HAVING,)
14 Avoid using ORDER BY in selects
15 Avoid Nested Selects
16 Avoid Nested Loops of Internal Tables
17 Try to use FIELD SYMBOLS.
18 Try to avoid into Corresponding Fields of
19 Avoid using Select Distinct, Use DELETE ADJACENT.
Regards
Madhu

Function Based Indexes - negative performance

Has anyone run across any cases where they have had issues with Function Based Indexes negatively impacting performance??
We are trying to use function based indexes in 9i (NLS_SORT=GENERIC_BASELETTER) and 10g (NLS_SORT=BINARY_CI) for case insensitivity.
We thought this was a decent solution until recently when testing with larger datasets. Any info is appreciated.
Thanks,

Just to clarify rreynoldson's first point:
All indexes will negatively impact inserts. Indexes, including function-based indexes, may or may not improve update and delete performance depending on whether the overhead of maintaining the index outweighs the benefit of being able to use the index to find the row(s) to update relatively quickly.
For user564260:
Assuming those parameters are set, make sure that you've gathered statistics on the function based index. If that doesn't resolve the problem, can you post a small test case that demonstrates the problem where you
- Create the table
- Create the indexes
- Populate it with data
- Run the query that you'd expect to use the FBI
- Post the explain plan
that would help us immensely.
Justin

Performance analysis

Hello All,
I have been asigned to improve my system performance,
as Initial analysis I found that there were so many loops in our project, and there were so many routines involved infact in every update rules,
Iam not that much good in ABAP, hope you understand my problem, I need some steps how to analyse the loads and find a way how to improve my system performance.
Suggest some important performance issues while writing ABAP code so that I can check in my routines.
Regards,
Pavan.

Hi.......
Look there r many factores...........like Query performance,Load performance............
Now Load performance depends on the overall System performance......
Now if u r using Routines..............1
1)then u should try to avoid nested Loops...........also we shoud'nt use many Loops .......
2) using innerjoin is a very bad programming practice.
Check this ......
http://www.sap-img.com/abap/performance-tuning-for-data-selection-statement.htm
Query Performance Improvement Tools
BW Performance Tuning and Analysis:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1955ba90-0201-0010-d3aa-8b2a4ef6bbb2
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4c0ab590-0201-0010-bd9a-8332d8b4f09c
Data Load Performance:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3a699d90-0201-0010-bc99-d5c0e3a2c87b
To improve query performance..............
1) Create aggregates
2)Create partitions
3) Limited use of Navigational attributes.........
4) Create index(it will effect load performance)
5) Compression........
Regards,
Debjani.....

Performance analyzation

Hi every body,
                 Could any one explain me the following things regarding ABAP RUN TIME ANALYSIS..
1. what can we analyze by checking Tcode SE30.
2. what is abap load and what is database load and what is system load there?
3. For a good performance of a ABAP program, what should be the abap load and data base load?
4. If database load is more what to do to improve performance and if ABAP load is more what to do to improve performance?
          thanks in advance,
           santosh.

Hi
Tools for Performance Analysis
Run time analysis transaction SE30 :This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing.
SQL Trace transaction ST05: The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.
The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on a particular database table of the ABAP program would be mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.
The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.
To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.
Extended Program Check
This can be called in through transaction SE38 or through transaction SLIN. This indicates possible problems that may cause performance problems.
Code Inspector (SCI)
You can call the Code Inspector from the ABAP Editor (SE38), the Function Builder (SE37), the Class Builder (SE24), or as a separate transaction (SCI).
The Code Inspector indicates possible problems. However, note that, especially with performance issues: There is no rule without exception. If a program passes an inspection, it does not necessarily mean that this program will have no performance problems.
the percentage of LOAD
The percentage across each of the areas ABAP/ Database/System shows the percentage of total time used for those areas and load on these areas while running the program . The lesser the database load faster the program runs.
Ways of Performance Tuning
Ways of Performance Tuning
1.     Selection Criteria
2.     Select Statements
     Select Queries
     SQL Interface
     Aggregate Functions
     For all Entries
Select Over more than one internal table
Selection Criteria
1.     Restrict the data to the selection criteria itself, rather than filtering it out using the ABAP code using CHECK statement.
2.     Select with selection list.
SELECT * FROM SBOOK INTO SBOOK_WA.
CHECK: SBOOK_WA-CARRID = 'LH' AND
         SBOOK_WA-CONNID = '0400'.
ENDSELECT.
The above code can be much more optimized by the code written below which avoids CHECK, selects with selection list
SELECT CARRID CONNID FLDATE BOOKID FROM SBOOK INTO TABLE T_SBOOK
WHERE SBOOK_WA-CARRID = 'LH' AND
              SBOOK_WA-CONNID = '0400'.
Select Statements   Select Queries
1.     Avoid nested selects
SELECT * FROM EKKO INTO EKKO_WA.
SELECT * FROM EKAN INTO EKAN_WA
      WHERE EBELN = EKKO_WA-EBELN.
ENDSELECT.
ENDSELECT.
The above code can be much more optimized by the code written below.
SELECT PF1 PF2 FF3 FF4 INTO TABLE ITAB
    FROM EKKO AS P INNER JOIN EKAN AS F
      ON PEBELN = FEBELN.
Note: A simple SELECT loop is a single database access whose result is passed to the ABAP program line by line. Nested SELECT loops mean that the number of accesses in the inner loop is multiplied by the number of accesses in the outer loop. One should therefore use nested SELECT loops only if the selection in the outer loop contains very few lines or the outer loop is a SELECT SINGLE statement.
2.     Select all the records in a single shot using into table clause of select statement rather than to use Append statements.
SELECT * FROM SBOOK INTO SBOOK_WA.
CHECK: SBOOK_WA-CARRID = 'LH' AND
         SBOOK_WA-CONNID = '0400'.
ENDSELECT.
The above code can be much more optimized by the code written below which avoids CHECK, selects with selection list and puts the data in one shot using into table
SELECT CARRID CONNID FLDATE BOOKID FROM SBOOK INTO TABLE T_SBOOK
WHERE SBOOK_WA-CARRID = 'LH' AND
              SBOOK_WA-CONNID = '0400'.
3.     When a base table has multiple indices, the where clause should be in the order of the index, either a primary or a secondary index.
To choose an index, the optimizer checks the field names specified in the where clause and then uses an index that has the same order of the fields. In certain scenarios, it is advisable to check whether a new index can speed up the performance of a program. This will come handy in programs that access data from the finance tables.
4.     For testing existence, use Select.. Up to 1 rows statement instead of a Select-Endselect-loop with an Exit.
SELECT * FROM SBOOK INTO SBOOK_WA
UP TO 1 ROWS
WHERE CARRID = 'LH'.
ENDSELECT.
The above code is more optimized as compared to the code mentioned below for testing existence of a record.
SELECT * FROM SBOOK INTO SBOOK_WA
    WHERE CARRID = 'LH'.
EXIT.
ENDSELECT.
5.     Use Select Single if all primary key fields are supplied in the Where condition .
If all primary key fields are supplied in the Where conditions you can even use Select Single.
Select Single requires one communication with the database system, whereas Select-Endselect needs two.
Select Statements SQL Interface
1.     Use column updates instead of single-row updates
to update your database tables.
SELECT * FROM SFLIGHT INTO SFLIGHT_WA.
SFLIGHT_WA-SEATSOCC =
    SFLIGHT_WA-SEATSOCC - 1.
UPDATE SFLIGHT FROM SFLIGHT_WA.
ENDSELECT.
The above mentioned code can be more optimized by using the following code
UPDATE SFLIGHT
       SET SEATSOCC = SEATSOCC - 1.
2.     For all frequently used Select statements, try to use an index.
SELECT * FROM SBOOK CLIENT SPECIFIED INTO SBOOK_WA
WHERE CARRID = 'LH'
    AND CONNID = '0400'.
ENDSELECT.
The above mentioned code can be more optimized by using the following code
SELECT * FROM SBOOK CLIENT SPECIFIED INTO SBOOK_WA
WHERE MANDT IN ( SELECT MANDT FROM T000 )
    AND CARRID = 'LH'
    AND CONNID = '0400'.
ENDSELECT.
3.     Using buffered tables improves the performance considerably.
Bypassing the buffer increases the network considerably
SELECT SINGLE * FROM T100 INTO T100_WA
BYPASSING BUFFER
WHERE     SPRSL = 'D'
        AND ARBGB = '00'
        AND MSGNR = '999'.
The above mentioned code can be more optimized by using the following code
SELECT SINGLE * FROM T100 INTO T100_WA
WHERE     SPRSL = 'D'
        AND ARBGB = '00'
        AND MSGNR = '999'.
Select Statements Aggregate Functions
     If you want to find the maximum, minimum, sum and average value or the count of a database column, use a select list with aggregate functions instead of computing the aggregates yourself.
Some of the Aggregate functions allowed in SAP are MAX, MIN, AVG, SUM, COUNT, COUNT( * )
Consider the following extract.
            Maxno = 0.
            Select * from zflight where airln = LF and cntry = IN.
             Check zflight-fligh > maxno.
             Maxno = zflight-fligh.
            Endselect.
The above mentioned code can be much more optimized by using the following code.
Select max( fligh ) from zflight into maxno where airln = LF and cntry = IN.
Select Statements For All Entries
     The for all entries creates a where clause, where all the entries in the driver table are combined with OR. If the number of entries in the driver table is larger than rsdb/max_blocking_factor, several similar SQL statements are executed to limit the length of the WHERE clause.
     The plus
     Large amount of data
     Mixing processing and reading of data
     Fast internal reprocessing of data
     Fast
     The Minus
     Difficult to program/understand
     Memory could be critical (use FREE or PACKAGE size)
Points to be must considered FOR ALL ENTRIES
     Check that data is present in the driver table
     Sorting the driver table
     Removing duplicates from the driver table
Consider the following piece of extract
          Loop at int_cntry.
Select single * from zfligh into int_fligh
where cntry = int_cntry-cntry.
Append int_fligh.
                      Endloop.
The above mentioned can be more optimized by using the following code.
Sort int_cntry by cntry.
Delete adjacent duplicates from int_cntry.
If NOT int_cntry[] is INITIAL.
            Select * from zfligh appending table int_fligh
            For all entries in int_cntry
            Where cntry = int_cntry-cntry.
Endif.
Select Statements Select Over more than one Internal table
1.     Its better to use a views instead of nested Select statements.
SELECT * FROM DD01L INTO DD01L_WA
WHERE DOMNAME LIKE 'CHAR%'
        AND AS4LOCAL = 'A'.
SELECT SINGLE * FROM DD01T INTO DD01T_WA
    WHERE   DOMNAME    = DD01L_WA-DOMNAME
        AND AS4LOCAL   = 'A'
        AND AS4VERS    = DD01L_WA-AS4VERS
        AND DDLANGUAGE = SY-LANGU.
ENDSELECT.
The above code can be more optimized by extracting all the data from view DD01V_WA
SELECT * FROM DD01V INTO DD01V_WA
WHERE DOMNAME LIKE 'CHAR%'
        AND DDLANGUAGE = SY-LANGU.
ENDSELECT
2.     To read data from several logically connected tables use a join instead of nested Select statements. Joins are preferred only if all the primary key are available in WHERE clause for the tables that are joined. If the primary keys are not provided in join the Joining of tables itself takes time.
SELECT * FROM EKKO INTO EKKO_WA.
SELECT * FROM EKAN INTO EKAN_WA
      WHERE EBELN = EKKO_WA-EBELN.
ENDSELECT.
ENDSELECT.
The above code can be much more optimized by the code written below.
SELECT PF1 PF2 FF3 FF4 INTO TABLE ITAB
    FROM EKKO AS P INNER JOIN EKAN AS F
      ON PEBELN = FEBELN.
3.     Instead of using nested Select loops it is often better to use subqueries.
SELECT * FROM SPFLI
INTO TABLE T_SPFLI
WHERE CITYFROM = 'FRANKFURT'
    AND CITYTO = 'NEW YORK'.
SELECT * FROM SFLIGHT AS F
    INTO SFLIGHT_WA
    FOR ALL ENTRIES IN T_SPFLI
    WHERE SEATSOCC -FLAG = 'X'.
ENDIF.
ENDLOOP.
The above code works faster as compared to
LOOP AT ITAB INTO WA.
I = SY-TABIX MOD 2.
IF I = 0.
    WA-FLAG = 'X'.
    MODIFY ITAB FROM WA.
ENDIF.
ENDLOOP.
8.    If collect semantics is required, it is always better to use to COLLECT rather than READ BINARY and then ADD.
LOOP AT ITAB1 INTO WA1.
READ TABLE ITAB2 INTO WA2 WITH KEY K = WA1-K BINARY SEARCH.
IF SY-SUBRC = 0.
    ADD: WA1-VAL1 TO WA2-VAL1,
         WA1-VAL2 TO WA2-VAL2.
    MODIFY ITAB2 FROM WA2 INDEX SY-TABIX TRANSPORTING VAL1 VAL2.
ELSE.
    INSERT WA1 INTO ITAB2 INDEX SY-TABIX.
ENDIF.
ENDLOOP.
The above code uses BINARY SEARCH for collect semantics. READ BINARY runs in O( log2(n) ) time. The above piece of code can be more optimized by
LOOP AT ITAB1 INTO WA.
COLLECT WA INTO ITAB2.
ENDLOOP.
SORT ITAB2 BY K.
COLLECT, however, uses a hash algorithm and is therefore independent
of the number of entries (i.e. O(1)) .
9.    "APPEND LINES OF itab1 TO itab2" accelerates the task of appending a table to another table considerably as compared to LOOP-APPEND-ENDLOOP.
APPEND LINES OF ITAB1 TO ITAB2.
This is more optimized as compared to
LOOP AT ITAB1 INTO WA.
APPEND WA TO ITAB2.
ENDLOOP.
10.   DELETE ADJACENT DUPLICATES accelerates the task of deleting duplicate entries considerably as compared to READ-LOOP-DELETE-ENDLOOP.
DELETE ADJACENT DUPLICATES FROM ITAB COMPARING K.
This is much more optimized as compared to
READ TABLE ITAB INDEX 1 INTO PREV_LINE.
LOOP AT ITAB FROM 2 INTO WA.
IF WA = PREV_LINE.
    DELETE ITAB.
ELSE.
    PREV_LINE = WA.
ENDIF.
ENDLOOP.
11.   "DELETE itab FROM ... TO ..." accelerates the task of deleting a sequence of lines considerably as compared to DO -DELETE-ENDDO.
DELETE ITAB FROM 450 TO 550.
This is much more optimized as compared to
DO 101 TIMES.
DELETE ITAB INDEX 450.
ENDDO.
12.   Copying internal tables by using ITAB2[ ] = ITAB1[ ] as compared to LOOP-APPEND-ENDLOOP.
ITAB2[] = ITAB1[].
This is much more optimized as compared to
REFRESH ITAB2.
LOOP AT ITAB1 INTO WA.
APPEND WA TO ITAB2.
ENDLOOP.
13.   Specify the sort key as restrictively as possible to run the program faster.
SORT ITAB BY K. makes the program runs faster as compared to SORT ITAB.
Internal Tables         contd
Hashed and Sorted tables
1.     For single read access hashed tables are more optimized as compared to sorted tables.
2.      For partial sequential access sorted tables are more optimized as compared to hashed tables
Hashed And Sorted Tables
Point # 1
Consider the following example where HTAB is a hashed table and STAB is a sorted table
DO 250 TIMES.
N = 4 * SY-INDEX.
READ TABLE HTAB INTO WA WITH TABLE KEY K = N.
IF SY-SUBRC = 0.
ENDIF.
ENDDO.
This runs faster for single read access as compared to the following same code for sorted table
DO 250 TIMES.
N = 4 * SY-INDEX.
READ TABLE STAB INTO WA WITH TABLE KEY K = N.
IF SY-SUBRC = 0.
ENDIF.
ENDDO.
Point # 2
Similarly for Partial Sequential access the STAB runs faster as compared to HTAB
LOOP AT STAB INTO WA WHERE K = SUBKEY.
ENDLOOP.
This runs faster as compared to
LOOP AT HTAB INTO WA WHERE K = SUBKEY.
ENDLOOP.

Performance of the transaction RBT_ENH_vb7

Is there any standard report through which i can know that i have to
enter that much of rebate agreements to run transaction RBT_ENH_VB7 for
April-2011 (We are running RBT_ENH_VB7 tocde at the end of the every
month).
That's why i want to check how to exclude those rebate agreements
initially which are not valid anymore. Now system fetch all the rebate
agreement even not valid anymore and how to
exclude invalid agreement at the first beginning?
Could you please suggest some report or program through which we can
know that.
Regards,
Chirag

1.Run time analysis transaction SE30
This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing.
2.SQL Trace transaction ST05
The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.
The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on the SPFLI table in our test program is mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.
The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.
To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.
Or can use load balancing servers for user over load.

Department performance dependent bonus

Similar Messages

Maybe you are looking for