The analysis process of ABAP™ programs:
in future with visual illustration
The conventional methods used until now
The conventional analysis of the source code (e.g. ABAP™ programs) to determine the process flow of the program, fault finding or quality control has always been a large-scale strenuous task requiring a great deal of concentration.
Quite often the program process can only be determined through a debugging session - provided the suitable test data are at hand.
Our solution: the visual process analysis
From the trace data pool of a recorded debugging-session (ABAP™ program process) or from the data of a performance analysis (transaction SE30), information is gathered in order to generate dynamic diagrams.
These generated control data form the basis for the visualizing of the program process. The graphic representations ensures imediate recognition of the essential processed program events (FORM, FUNCTION, METHOD, DYNPRO, MODULE, CALL SCREEN, etc.).
A trace control panel allows browsing forwards or backwards through the program; thus the program process can quite easily be visually analyzed .
Within the diagrams you will find extensive functions for the analysis of the program and documentation. Double click on a graph element to navigate through the appropriate section of the source code, for example .
By clicking through a mouse click in the source code you can go to the respective graph element. It is also possible to find out further information about a graph element (call hierarchy, input parameter, output parameter, runtime, etc.).
Graph elements which are not of immediate relevance can be compressed in order to call up more important processed parts of the program.
In this screenshot the CT-Test & Optimizer shows a graph based on the runtime analysis (SAP transaction SE30).
Enlarge screenshot
In which IT areas do I profit from the graphic process analysis?
The graphic representation of the processed ABAP™ program events ensures a transparent overall view of the program process and thus supports the following task areas considerably:
 |
Optimizing the business process at the program level
- Which coding parts are assigned to which process?
- Are processed coding parts comparable for the called process?
- Can processed program parts deliver the necessary information?
- Is program control still correct after customizing?
|
 |
Process documentation
- Spread documentation of connected program flows
- Documentation of dynamically called external programs
|
 |
Modification (assigned form compatible USER-Exits)
- Which data is available and when?
|
 |
Control over test data completeness
- Which program parts are not called by the test data ?
|
 |
Graphic documentation of the program flow
- Quick over all view of the function of the program parts
|
 |
Quality control
- Easy to comprehend overview of the processed program structure
- Does a clear call hierarchy exist?
- Are single program events involved conspicuously often?
|
 |
Performance testing
-
Which program parts block subsequent routines?
-
Which program parts hinder the time-critical transaction process?
|
 |
Computing revision
- automatic documentation of the processed program areas
- control at different times where program sequences are identical
|
 |
Maintenance and program changes
- automatic registration of the process, before and after maintenance
- control of program execution before and after program alterations
|
 |
2nd Level Support
|
 |
Training and education
|
The CT add-on is suitable for the following SAP® systems: R/3® from release 3.1x up to 4.7 (Enterprise), mySAP™ ERP, mySAP™ CRM, SAP® BW, SAP® APO and SAP NetWeaver™ (up to 6.4).
The CT-Test & Optimizer uses a modern GUI library, which can be fully customized. More than 10 GUI elements (display windows, trees, control elements, etc.) can be individually arranged to build your individual environment.
The installation process depends on the release and takes about 5-10 minutes. Information about the system requirements can be found here.
Technical diagram

[Please click here to enlarge the diagram]
|