Support Settings

To activate the SAP NetWeaver BW trace tool environment, select the Enable BW Server Tracing check box.

You can also activate the BW server tracing with the file system setting AbapTrace in the Ao_app.config file.

The trace tool environment (transaction code RSTT in the connected BW system) has special tools to log and play back traces and process automatic regression tests.

For more information about the trace tool environment, see SAP Help Portal at http://help.sap.com   SAP NetWeaver   SAP NetWeaver by Key Capability  Information Integration by Key Capability  Business Intelligence  BI Platform  OLAP  Performance Optimization  BEx Monitor  Trace Tool Environment .

To activate the SAP NetWeaver BW query runtime statistics, select the Enable Profiling check box.

You can also activate the workbook profiling with the file system setting Profiling in the Ao_app.config file.

Using the query runtime statistics, you can find out how much time it takes to execute certain user actions in Analysis and the BW analytic engine. The system records the performance-critical parts of the processing (statistics events). It calculates the net times by calculating the runtime of an event using the difference between the start and end times (minus the times for other events called from within the event).

You can check the statistics in theAnalysis ribbon Actions group under  Messages  Show Workbook Profiling Statistics... . The Messages entry is enabled only if statistics are available.

For more information about the query runtime statistics, see section Query runtime statistics in the Analysis Administrator guide.

To activate the Analysis client profiling, select the Enable Profiling check box.

You can also activate the client profiling with the file system setting clientProfiling in the Ao_app.config file.

If the setting is activated, Analysis will capture every interaction.

You can check the statistics in the Analysis ribbon Actions group under  Messages  Show Client Profiling Statistics... . The Messages entry is enabled only if statistics are available.

In the Client Profiling Statistics dialog, the captured interactions are displayed as steps in a tree view and you can navigate to each interaction. You can see the overall processing time per step (in ms), the time the user spent in dialogs, the number of RFC calls per step and the time that was spent for RFC. In section Update UI, you can see if a navigation step has caused (unexpected) RFC calls.

At the bottom of the Client Profiling Statistics dialog, you find a summary containing the time that was used on client side for processing (in ms), the number of RFC calls (count) and the time that was used for that (in ms) and the time the user spent in dialogs (in ms).

To activate the technical names of the dimensions in your Analysis workbook, select the Display Technical Names check box. The dimensions are displayed with technical name and text.

This setting may be used for SAP error handling.

Analysis uses the .Net connector (NCO) for calling ABAP RFCs from client. NCO supports logging of RFC traces. You can activate the tracing by selecting Enable NCO Tracing and choosing the desired level (usually 4).

If you now work with Analysis, log files will be created in the %temp% folder of windows. There you can find a dev_nco_rfc.log file and a number of files "nco_rfc_XXXX_Y.trc". Additionally, there are the Analysis log files of type .glf, for example AO_Log_<processID>.glf.. You can zip all of them to attach them to the message.

Select this check box you want the suppressed messages to be shown.