Big4Guy

Welcome to Big4Guy.com. Big4Guy is an online resource where I will share with you the latest news, insights, knowledge and some experiences as a Big 4 consultant. We will discuss some of the important issues which organisations are facing today in the areas of information security, security and controls in SAP R/3, Oracle Applications, J.D.Edwards, Peoplesoft and various other ERP's. You will also find information on latest complaince regulations like Sarbanes Oxley, Basel II and so on. Big4guy will also attempt to provide valuable resources for individuals interested in examinations the CISA, CISM, CISSP, PMP and various other security certifications considered essential for entry in any Big 4 accounting, auditing and consulting firms. You are invited to post your comments and viewpoints to posts here. I sincerely hope this online journal will be useful to everyone from a budding student to a professional in the accounting, auditing, management and consultancy professions.

Post details: ABAP Runtime Analysis - How to Perform ABAP Runtime Analysis SE30

09/30/09

Permalink 07:59:00 am, Categories: SAP R/3, ABAP, 351 words   English (US)

ABAP Runtime Analysis - How to Perform ABAP Runtime Analysis SE30

The ABAP runtime analysis can be used to analyze the total run time required for individual SAP transaction codes, sap programs or even SAP function modules. Individual ABAP objects can put a heavy load on the system resources such as CPU and memory, ABAP runtime analysis is especially useful in such case to perform analysis and find the root cause of the problem.

ABAP runtime analysis can be performed using transaction code SE30 or via the menu path: SAP Menu >> Tools >> ABAP Workbench >> Test >> RunTime Analysis SE30. Runtime analysis is performed in three steps which are:

1. Deciding on the data to be measured - As a first step in runtime analysis, the ABAPPER needs to decide which object needs to be analysed. Other important criteria at this stage includes which aggregation should be used whether to use full aggregation, aggregation based in calling position, or no aggregation. Similarly, filters can be used based on modularization and commands. Deciding the data to be ameasured upfront is key to successful runtime analysis.

2. Measuring the Data - The next important step is the measurement of the runtime data. This can be performed in the same user session in which the ABAP runtime analysis is getting completed or can be performed in a new user session using tcode /OSE30. Analysis can also be performed to measure the runtime data for an object that is processed by that work process.

3. Analyzing the Data - In case of data aggregation, the runtime analysis can be seen in the hitlist and in case of aggregation on calling position, this can be seen via call hierarchy or modularization units. Once the runtime analysis is complete, this can be saved on the application server or it can also be sent to the front end. For further analysis, SAP R/3 provides the option to the abapper to saved the data to a specified path and also allocate the memory that the system will use for saving the file.

Related Posts

SAP Function Groups - Finance ABAP
ABAP Authority Check in SAP ECC
ABAP Programming Basic Concepts
SAP WebDynpro ABAP User Interface

Comments:

No Comments for this post yet...

Official Websites

Search

Google

Web Big4Guy.com

October 2009
Mon Tue Wed Thu Fri Sat Sun
<<  <   >  >>
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  

Misc

Syndicate this blog XML

What is RSS?