Show TOC

Maintenance of Trace PropertiesLocate this document in the navigation structure

Use

The Trace Attribute screen displays information on a selected trace.

In change mode, you can change certain properties, for example to enter a description for the trace, change the name or trace (ID), or execute the trace up to a certain program object.

Integration

You can access the maintenance of trace properties for a particular trace, using the Trace and Trace Collection areas of the trace tool.

Prerequisites

The required user activities have been logged and the corresponding trace determined. More information:Logging User Actions andDetermining a Logged Trace.

Features

In the upper screen area, the system displays the trace GUID, trace (ID) and description of the chosen trace (seeDetermining a Logged Trace).

You can change the trace (ID) and description in change mode:

Changing trace (ID) and description

Property Description

Trace (ID)

Key with name that the system generates using the following pattern: systemname/xxxxxx (xxxxxx represents a 6-digit sequence number).

You can change the generated trace ID to any 20-digit term.

Note that the trace (ID) must be unique in the system.

You can reuse the trace (ID)s of deleted traces.

Description

Free Text

Basis Attributes Tab Page

The Basis Attributes tab page shows different default values:

Default values of a trace

Property Description

Trace type

Type of trace

  • Standard trace
  • CATT trace: Special standard trace used to generate automatic tests
  • OLAP trace: CATT trace in the Reporting, Planning and OLAP Technology application area

Application area

Isolated process area where you can log user actions.

This setting is determined, depending on the user, in the global settings (seeAdministration).

Application layer

Clearly definable call layer during process editing, within an application area.

Tip

In the Reporting, Planning and OLAP Technology application area there are the following application layers:

  • BW BEx Request
  • BW Business Explorer
  • BW Open Analysis Interfaces
  • BW Aggregation Layer
  • BW Core Calculation Layer
  • BW Data Access Layer
  • BW Planning Layer
  • BW BPS Layer

Author

User who logged the trace

Date of creation, time of creation

Date and time of first logging

SAP system ID

Technical name of the BW system

Current release

 

Patch level

 

Last changed by

Last user to change the trace

Date of modification, time of modification

Date and time of last change

In the change mode you can choose the application layer here.

The following image illustrates the process of executing a trace using an example from the Reporting, Planning and OLAP Technology application area:

While executing a trace, selecting a certain application layer allows the extent of the execution to be controlled by logged program objects.

Tip

If an upper application layer, BW Business Explorer for example, is not interesting because executing the logged program objects requires a great deal of time or certain authorizations, you can hide this layer and let the trace run on a lower application layer, for example BW Core Calculation Layer, with the logged input parameters.

Logged Program Objects Tab Page

The Logged Program Objects tab page displays all the important information about all of the program objects whose interface parameters (in the Reporting, Planning and OLAP Technology application area while a query was executed) were logged and lets them be played again.

In this sense, program objects are:

  • Function modules
  • Static methods
  • Instance methods

In the default setting, the system only displays program objects in the call table that belong to the application layer set for the trace (see Basis Attributes tab page).

Change Call View gives you the option of displaying all of the logged program objects for this trace.

Using Parameters, the system displays the values of the parameters for each program object as XML.

Double-click on a table entry to start the Trace Execution:

  • If the program object of this table entry is in the application layer chosen on the Basis Attributes tab page, the ABAP Debugger appears. The system stops directly before calling the program object.
  • If the program object is in a different application layer, the system executes the entire trace. The run is documented in corresponding messages.

The information in the table includes:

Special information on the Logged Program Objects tab page

Column Description

Sequence number

In the Reporting, Planning and OLAP Technology application area, the sequence number specifies the sequence regarding the query navigation. See the Sequence Descriptions tab page.

Item

Sequential number of program objects together with the ID for the call.

Program type

Type of logged program object.

Program module

Technical name of the program object.

Framework program

 

Runtime

 

Layer depth

Application layer depth: Current position (nesting depth) within an application layer.

Layer depth = 0 is the entry point for playing on the respective application layer.

Stack depth

Stack depth: Current position (depth) in the call list, relating to the highest call module.

Application layer

See Basis Attributes tab page

Test object

See Test Objects tab page

The following image illustrates the determining of layer and stack depths for the function modules FU1, FU2 and FU3 using an example from the Reporting, Planning and OLAP Technology application area:

Testable Program Objects Tab Page

The Testable Program Objects tab page displays all of the program objects, whose parameters or variables were recorded, that can be checked in a regression test.

Note

This tab page only applies to CATT traces (not standard traces).

It is a prerequisite that the user is not only activated for logging the trace, but also for generating the test, seeLogging User Actions.

In addition to the information on the Logged Program Objects, tab page, the table includes the following:

Special information on the Testable Program Objects tab page

Column Description

Check-position type

Developer information:

  • I for Interface After Input
  • O for Interface Before Output
  • S for Special Parameters: You can query a parameter up to ten times. You can use this, for example, to check the intermediate status of a local or interface parameter of a program object.

Check alias

Explanatory name that the developer assigns to a check position

Test Objects Tab Page

The Test Objects tab page provides you with an overview of the logical objects that were logged using this trace.

Tip

In the Reporting, Planning and OLAP Technology application area, this could be one BW query or - for Web applications - several BW queries.

Sequence Descriptions Tab Page

The Sequence Descriptions tab page provides you with an overview of all of the logged sequences for this trace run.

Tip

In the Reporting, Planning and OLAP Technology application area, a sequence corresponds to a navigation step in the BW query.

In change mode you have the option of entering a descriptive text for the sequences.