Symptom
- After refreshing a long-running Crystal Report in Infoview, it returns 'empty data', and a blank page is shown in the viewer.
- In the BW MDX.log, the trace ends with:
- SAP BW MDX: Metadata tables are empty. There will be no result set either.
- SAP: Unable to create binding handle for field ... as the field was not found in the resultset metadata
- In BW transaction MDXTEST, running the query with flattening throws error: << MDX result contains too many cells (more than 1 million) BRAINOLAPAPI121 >>
Environment
SAP BW 7.01 SP6
Crystal Reports 2008 SP1
BusinessObjects XI3.1 SP1
Reproducing the Issue
- Connecting to a BW BEx query
- Report created using BW MDX Driver in Crystal
- Published to BW
- Report opened and Refreshed via WebI Infoview
Cause
This is a storage problem, due to accessing mass data
- By implementing Enhancement Pack 1 (EhP1) for BW, the “1-Million cell” restriction has been removed from the MDX Interface (new RSR_MDX_ function modules, listed in Note 1232751).
- However, the Crystal Reports component on SP1/SP2 (crdb_bwmdx.dll) does not yet leverage these enhancements (i.e. the reporting framework still uses the old BAPI_MDDATASET_ functions).
Resolution
- For full interoperability, please implement fix ADAPT01370921, as delivered FixPack2.7 / FixPack3.1
- If the BEx selection parameters cannot be restricted for the query, then the BusinessObjects Enterprise, Crystal, and SAP Integration Kit components need to be upgraded to level FP2.7 or FP3.1
Keywords
KBA , BI-RA-CR , Crystal Reports designer or Business View Manager , BI-RA-ODA , OLAP Data Access Components , Problem
Product
SAP Crystal Reports all versions