Troubleshooting Crystal Reports off BW

http://wiki.sdn.sap.com/wiki/display/BOBJ/Troubleshooting+Crystal+Reports+off+BW#TroubleshootingCrystalReportsoffBW-TracingBOE

 

Quite useful, especially this part:

SAP BW connectivity

For the SAP BW connectivity you can also look at the following items as part of the troubleshooting process:

• Use transaction MDXTEST to verify the MDX statement used by Crystal Reports and to verify the data. You can find the MDX statement by selecting Show SQL query in the Database menu.
  Please refer to the following documentation for more details:
  http://www.sdn.sap.com/irj/scn/events?rid=/library/uuid/b0320722-741c-2c10-afab-93b5c0fc7e96
  http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f0b98a32-f10d-2b10-7282-da9ee1a85b3f&overridelayout=true
• With transaction RSFLAT you can emulate exactly the same query and verify the datastream you woulg get in Crystal Reports. This transaction is useful when you want to see what data a BEx query will return.
• Use transaction SE37 to call the OLAP BAPI function manually so that you can verify the metadata retrieved by Crystal Reports. You can see OLAP BAPI calls in SAP integration trace.
  Please refer to section 8.3.1 of [Web Intelligence on SAP implementation best practices]
• Use transaction RSRTRACE to create an OLAP trace on the SAP BW server.
  Please refer to section 8.3.2 of [Web Intelligence on SAP implementation best practices]