Smart Form Trace


Using the Smart Form trace, you can trace how a Smart Form was processed during printing. You can then see, for example, the sequence in which the nodes were run or the point at which processing terminated due to an error.


The trace is activated in transaction SFTRACE or by the user. When the trace is activated, Smart Forms stores a trace on the database for each output, using the generated function module. You can set the degree of detail for this trace. The Smart Form trace is automatically deactivated again after a day. The stored trace files are, however, retained.

In deliveries before SAP Web AS 6.10, the trace can be started in transaction SMARTFORM_TRACE.


The trace output is user-specific. The trace is therefore only recorded with the user who activated it. For traces to be recorded for batch input, the batch therefore has to be run under the user who activated the trace. This is automatically the case if you do not specify an explicit batch user when scheduling a batch.


Trace Settings




Degree of detail in trace output (see below)

logical page (Name)

Restriction of trace output to a specific page, only useful as of trace level 30.


Restriction of trace output to a specific window on a page (if you have also specified a logical page) or on all pages on which the window exists.

ABAP break points

Both these check fields (warning and error) are only used internally

The level of the trace determines how detailed the trace is. Trace level 5 contains general information only and trace level 80 is the most detailed. The next highest trace level contains all the information from the last level and supplements this with additional data:

Trace Level


Content of Trace Output

Warning or error (5)

Trace level, trace version, system date and time, system information (SAP Release, local operating system, database system, SAP system name, user name) If warnings or errors occur during processing, they are output in the trace.

Document information (15)

Also contains additional specifications on:

·        The output channel (for example, the short name for the printer)

·        Static form attributes

·        The structure of the form - corresponds to the structure of pages and windows in the Form Builder navigation tree

·        Output results (spool ID, number of forms and number of pages)

Pages (30)

Also contains the names of the processed pages (without the name of the start page).

Window (40)

Also contains the names of the processed windows (including address and graphic nodes if they are output from a separate output area).

Output area (45)

Also contains specifications as to when table output areas (header area, main area, and footer area) are processed.

Cell change (table) (47)

Also contains outputs on line types and cells processed in tables.

Text information (50)

Also contains the attribute values of processed output nodes (text elements, text modules, include texts, graphics, addresses), for example, language, style used, technical name of the included text module, and so on.

Fields (60)

Also contains the names and values of fields in text outputs. (Found in the trace as symbol).

Scanner token (80)

Also contains the scanner outputs when analyzing the texts in text nodes.

If you change the trace settings, confirm by pressing the Enter key so that the new settings are copied for the next trace run.



       1.      Activate and configure the trace.

       2.      Call a form - if the trace is activated, Smart Forms automatically stores a trace on the database.

       3.      Analyze the trace.

       4.      Deactivate the trace if you no longer require it. You can deactivate the trace using the Deactivatepushbutton in Trace management (transaction SFTRACE).