Browse Prior Art Database

SAP Trace Analyze Tool

IP.com Disclosure Number: IPCOM000015829D
Original Publication Date: 2002-Apr-07
Included in the Prior Art Database: 2003-Jun-21
Document File: 2 page(s) / 54K

Publishing Venue

IBM

Abstract

Description : The Trace Analyze Tool is intended for SAP-Developers and provides opportunities to extract subsets from a SAP-Trace focused on certain aspects for a quick and efficient Analysis. A SAP-Trace can be created with the Tco SE30 and calling a certain transaction like VA01 ‘Create Order’. A trace for a transaction like “Create Order” easily achieves more than 20 Megabyte and therefore an analysis is very difficult and time consuming

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 63% of the total text.

Page 1 of 2

SAP Trace Analyze Tool

Description : The Trace Analyze Tool is intended for SAP-Developers and provides opportunities to extract subsets from a SAP-Trace focused on certain aspects for a quick and efficient Analysis. A SAP-Trace can be created with the Tco SE30 and calling a certain transaction like VA01 'Create Order'. A trace for a transaction like "Create Order" easily achieves more than 20 Megabyte and therefore an analysis is very difficult and time consuming !

Using the Advantages of a Trace :

The Trace is created in time with very special data or/and a special way of using the transaction (eg.: creating, changing certain fields). Only the effective processed source code is traced according to the used data und used (business) functions.

Dynamic calls are resolved. Loops are serialized.

What's new for a developer:

To get a logical flow overview of the entire process, the developer extracts a skeleton of the trace showing the processed screens, called modules and main routines in a manageable size. This can be achieved by limiting the Nesting Level. For a subject of interest ( eg. a certain user exit) the developer gets a detailed view within the subset of the trace to see where within the entire process and how often a subroutine is processed . Additionally a line number will be provided, which enables the developer to know how several filtered subsets of the trace fits into the entire process, eg. to see the order of appearance of a special subroutine, cal...