3021428 - Why to check if the issue is reproducible in RSRT transaction?

There is an issue occurring in Analysis Office tool and a BW data source is involved (e.g. BEx Query, CDS view, etc) in the scenario.

Why it is important to check if the issue/scenario is reproducible when running the BW data source directly in RSRT transaction?

This document aims to explain the reasons behind this test.

In many cases, if a BW data source is involved and there is an issue occurring in Analysis Office tool, the scenario can be (and should be) checked by executing the BW data source directly in RSRT transaction in ABAP BICS mode in the BW system.

Below are some examples:

• Wrong/unexpected data in the report;
• Issues related to the variables;
• Issues related to Value Help (aka F4 Help), like e.g. wrong/unexpected/missing members in the list of values;
• Errors/exceptions when executing the data source or after a specific navigation (e.g. filter, drilldown, sorting, etc);
• Bad performance;
• Issue related to hierarchies (e.g. wrong/unexpected/missing nodes, etc);
• Unexpected behavior; 

Whenever possible, check if the issue is also reproducible in RSRT transaction in ABAP BICS mode. If the issue also occurs in RSRT transaction, it means that the issue is not related to a bug in Analysis Office tool and should be checked by the backend team. In this case, it will not be necessary to upgrade and check the scenario in the latest version of Analysis Office.
Raising an case directly in a closer and more suitable area will help to speed up the resolution process.

The following table can be used as a guide of where to raise the case in SAP, if the issue also occurs in RSRT:

This wiki page can also help to determine the correct area in the backend.

rsrt, analysis office, afo, a4o, olap engine , KBA , BI-RA-AO-XLA , Excel Addin , Problem