Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

ST20 - Capturing F-codes

Go to solution
Former Member

‎2006 Feb 24 2:05 PM

0 Likes
1,505

Hello,

Some of our equipments do not capture certain f-codes as valid. Therefore, I need to trace transaction screens to determine if the f-codes pressed are captured. I thought of using transaction st20. But have a few questions:

1. Does anyone have some documentation on how to read the analysis report from ST20?

2. Does anyone know if where in ST20 analysis report determines the action of pressing an fcode key? and where in the PAI, the fcode key is processed?

3. Does anyone have other suggest as to how to determine/capture whether the FCODES are recognized when pressed?

Thanks for your help.

Regards,

Anna-Liza

1 ACCEPTED SOLUTION
Read only

Go to solution
former_member181966
Active Contributor

‎2006 Feb 24 3:44 PM

0 Likes
1,028

A graphical tool has now been delivered with Transaction ST20 to simplify evaluation of the screen trace. This tool reduces the recording of the trace file while also displaying the structure of the programs recorded in the trace in a navigation tree that you can configure.

You can select the trace level in the ST20 initial screen using

'Record trace'. The only logical level for further evaluation with ST20 is the default 'Level 3'. The 'Trace on' button or Ctrl+F1 both activates trace recording and stops the current work process.

If you also wish to activate the trace for other components besides the screen processor, you can select this function using the 'Components' tab as of Release 6.10.

Once you have activated the trace, you must start the application to be recorded in the same window. You can do this either by directly starting the application using the OK code field or by specifying a

report or transaction in the 'Analysis target' frame. (This frame is displayed on the initial screen of ST20 when the trace is activated.)

When you have run the application as far as you want, switch to Transaction ST20 and end trace recording using the 'Trace off' button or Ctrl+ F2.

In the 'Work process', you should now be able to see the number of the work process and a time stamp that enables you to find the recorded trace in the dev_w-file of the work process.

Evaluation of a previously recorded trace file can now take place.

One option is to display the data as a raw list (Ctrl+F8). This makes sense if you wish to save the trace recording as a local file to be analyzed later.

You can also load a trace file that has been saved in this way in the ST20 using the 'Local file' tab.

The ST20 is mainly used for the graphical evaluation and display of screen trace recordings. This function is described in more detail below.

Graphical evaluation of a trace file is carried out by selecting the 'Evaluation' button (F8 for a file on the application server or F9 for a local file). The main navigation aid is a tree that appears to the left of the trace display. This tree shows the most important steps involved in screen processing.

You can use the key events displayed in this navigation tree, such as transaction or subscreen calls, to jump directly to the corresponding entries in the actual trace file (by double-clicking on the node in the tree).

The tree is set by default to display only the essential screen processing steps required to structure the trace information.

Before starting the evaluation, you can select additional events to be displayed in the navigation tree using the 'Navigation aid' frame. Depending on the type of problem present, you can display, for example, dynamic field modifications or module calls etc. Usually, a detailed evaluation is only required for particular sections of the trace file. For this reason, the ST20 allows you to display these additional nodes in the navigation tree at a later stage for particular trace sections (see below).

Using context menus in the navigation tree, you can select the following actions:

Jump to the Screen Painter

In the navigation tree, you can execute this function on an entry for a main screen or a subscreen.

Analyze the subscreen call hierarchy (Subscreen Tree)

This function is particularly useful for giving an overview of the call sequence of subscreens in the case of complex transactions. To call this function, you must have selected the display for the 'Subscreen Tree' in the navigation tree (by displaying it via the detail evaluation, if necessary).

In the following tree display of the subscreen hierarchy, you can also load the screen source texts and run a fast display of the flow logic and the field list. In this way, you can quickly see whether, for example, you can scroll through a subscreen area and what its minimum or maximum size is. As an alternative to the fast display in the ST20, you can also jump from the tree display of the subscreen hierarchy to the screen painter. Of course, a prerequisite for loading the source text is that the trace was evaluated in the same system as it was recorded.

The subscreen hierarchy check can be supported by a SAPBUI function

described in Note 324687 which allows the subscreen boundaries to be displayed on the frontend. This is particulary useful if you want to check problems with overlapping screens or similar character fields.

Detailed evaluation of individual sections of the trace file

Searching the trace files for entries that should be displayed in the navigation tree is a difficult and time-consuming task. For this reason, some key entries are displayed as options only. If you wish, you can also search the trace files for these at a later stage.

To do this, first evaluate the trace file without selecting optional entries for the navigation aid. By using the context menu to call entries in the navigation tree, you can repeat the evaluation for internal modes or screens only (with or without subnodes).

Displaying legends

The ST20 uses several icons to display the trace entries. As the meaning of the icons is not always self-explanatory, a 'Legend' button or corresponding hyperlink is provided in some areas. Here, you can access a list of the icons currently displayed, together with a short description of their meaning.

Hope this`ll help you ..

Pl Awars the points

Thanks

Hello,

Some of our equipments do not capture certain f-codes as valid. Therefore, I need to trace transaction screens to determine if the f-codes pressed are captured. I thought of using transaction st20. But have a few questions:

1. Does anyone have some documentation on how to read the analysis report from ST20?

2. Does anyone know if where in ST20 analysis report determines the action of pressing an fcode key? and where in the PAI, the fcode key is processed?

3. Does anyone have other suggest as to how to determine/capture whether the FCODES are recognized when pressed?

Thanks for your help.

Regards,

Anna-Liza

Reply
2 REPLIES 2
Read only

Go to solution
Former Member

‎2006 Feb 24 2:13 PM

0 Likes
1,028

Hi,

You can try captruting Ok codes using Recording also..

SHDB is the transaction code to record.

Regards

vijay

Read only

Go to solution
former_member181966
Active Contributor

‎2006 Feb 24 3:44 PM

0 Likes
1,029

A graphical tool has now been delivered with Transaction ST20 to simplify evaluation of the screen trace. This tool reduces the recording of the trace file while also displaying the structure of the programs recorded in the trace in a navigation tree that you can configure.

You can select the trace level in the ST20 initial screen using

'Record trace'. The only logical level for further evaluation with ST20 is the default 'Level 3'. The 'Trace on' button or Ctrl+F1 both activates trace recording and stops the current work process.

If you also wish to activate the trace for other components besides the screen processor, you can select this function using the 'Components' tab as of Release 6.10.

Once you have activated the trace, you must start the application to be recorded in the same window. You can do this either by directly starting the application using the OK code field or by specifying a

report or transaction in the 'Analysis target' frame. (This frame is displayed on the initial screen of ST20 when the trace is activated.)

When you have run the application as far as you want, switch to Transaction ST20 and end trace recording using the 'Trace off' button or Ctrl+ F2.

In the 'Work process', you should now be able to see the number of the work process and a time stamp that enables you to find the recorded trace in the dev_w-file of the work process.

Evaluation of a previously recorded trace file can now take place.

One option is to display the data as a raw list (Ctrl+F8). This makes sense if you wish to save the trace recording as a local file to be analyzed later.

You can also load a trace file that has been saved in this way in the ST20 using the 'Local file' tab.

The ST20 is mainly used for the graphical evaluation and display of screen trace recordings. This function is described in more detail below.

Graphical evaluation of a trace file is carried out by selecting the 'Evaluation' button (F8 for a file on the application server or F9 for a local file). The main navigation aid is a tree that appears to the left of the trace display. This tree shows the most important steps involved in screen processing.

You can use the key events displayed in this navigation tree, such as transaction or subscreen calls, to jump directly to the corresponding entries in the actual trace file (by double-clicking on the node in the tree).

The tree is set by default to display only the essential screen processing steps required to structure the trace information.

Before starting the evaluation, you can select additional events to be displayed in the navigation tree using the 'Navigation aid' frame. Depending on the type of problem present, you can display, for example, dynamic field modifications or module calls etc. Usually, a detailed evaluation is only required for particular sections of the trace file. For this reason, the ST20 allows you to display these additional nodes in the navigation tree at a later stage for particular trace sections (see below).

Using context menus in the navigation tree, you can select the following actions:

Jump to the Screen Painter

In the navigation tree, you can execute this function on an entry for a main screen or a subscreen.

Analyze the subscreen call hierarchy (Subscreen Tree)

This function is particularly useful for giving an overview of the call sequence of subscreens in the case of complex transactions. To call this function, you must have selected the display for the 'Subscreen Tree' in the navigation tree (by displaying it via the detail evaluation, if necessary).

In the following tree display of the subscreen hierarchy, you can also load the screen source texts and run a fast display of the flow logic and the field list. In this way, you can quickly see whether, for example, you can scroll through a subscreen area and what its minimum or maximum size is. As an alternative to the fast display in the ST20, you can also jump from the tree display of the subscreen hierarchy to the screen painter. Of course, a prerequisite for loading the source text is that the trace was evaluated in the same system as it was recorded.

The subscreen hierarchy check can be supported by a SAPBUI function

described in Note 324687 which allows the subscreen boundaries to be displayed on the frontend. This is particulary useful if you want to check problems with overlapping screens or similar character fields.

Detailed evaluation of individual sections of the trace file

Searching the trace files for entries that should be displayed in the navigation tree is a difficult and time-consuming task. For this reason, some key entries are displayed as options only. If you wish, you can also search the trace files for these at a later stage.

To do this, first evaluate the trace file without selecting optional entries for the navigation aid. By using the context menu to call entries in the navigation tree, you can repeat the evaluation for internal modes or screens only (with or without subnodes).

Displaying legends

The ST20 uses several icons to display the trace entries. As the meaning of the icons is not always self-explanatory, a 'Legend' button or corresponding hyperlink is provided in some areas. Here, you can access a list of the icons currently displayed, together with a short description of their meaning.

Hope this`ll help you ..

Pl Awars the points

Thanks