Solution : https://service.sap.com/sap/support/notes/1232751 (SAP Service marketplace login required)
Summary :
When executing an MDX statement in SAP systems, users may encounter an error indicating that the result is too large, specifically outlined by error CX_RSR_MDX_RESULT_TOO_LARGE. This issue stems from a limitation wherein field numberings for TUPLE_ORDINAL, COORDINATES, and CELL_ORDINAL can only accommodate up to 999,999 cells due to their NUMC data type and length constraints. Additionally, the existing MDX interface is not optimized for handling large data volumes. To address this, SAP note introduces two new RFC interfaces to extend functionality: RSR_MDX_CREATE_OBJECT, RSR_MDX_GET_AXIS_INFO, RSR_MDX_GET_AXIS_DATA, RSR_MDX_GET_CELL_DATA, RSR_MDX_GET_FLAT_DATA, and RSR_MDX_GET_FS_DATA. These interfaces are aligned with existing OLAP BAPIs but should be used sparingly when dealing with over 1 million cells. Users are advised to update to the relevant Support Packages in SAP NetWeaver BI for enhanced performance and compatibility.
Key words :
software component sap_bw business inform, business application programming interface, 01 bi abap support package 02, sap netweaver bi 7, component type rrtcellordinal, component type rrttupleordinal, component type rrtcoordinates, online analytical processing, accessing mass data, manual pre-implement
Related Notes :
| 1572018 | MDX: Ausführungsarten in Transaktion MDXTEST - BW 7.00-7.11 |
| 1480454 | MDX: RSTT: Runtime error OBJECTS_TABLES_NOT_COMPATIBLE |
| 1381821 | Memory and Performance Analysis for MDX |
| 1252370 | MDX: Runtime error GETWA_NOT_ASSIGNED for cell properties |
| 931479 | MDX: More than 1,000,000 instances per axis |
| 841635 | RSCRM - overcome the 1'000'000 cell limit |