Never trust the GUI. Trust M_MVC_TABLES . If the RECORD count in HANA doesn't match the ROWS in SE16 for your fact table, you are already in performance hell. The "Transparent Filter" Lie Another gem likely buried around page 28 of that PDF is the revelation about SID (Surrogate ID) navigation .
Page 28 of a good practical guide would have shown you the exact ABAP report to run: RSDDB_INDEX_ANALYZE and, more importantly, RSDD_HDB_TRANSFER_DBSTATS . sap bw 7.4 practical guide pdf 28
The fix? Rebuild your CompositeProvider as a HANA Calculation View directly in the HANA Studio (or XSA). Then consume it in BW via an External View. Never trust the GUI
Have your own page 28 story from BW 7.4? Share your worst "HANA hangover" tale in the comments below. The "Transparent Filter" Lie Another gem likely buried
Page 28 would have scolded you: "Index maintenance is not a monthly job. It is a post-load job." The practical guide’s 28th page probably had a flowchart. On one side: Advanced DSO . On the other: CompositeProvider . In the middle: Open ODS Views .
Beyond the GUI: Unearthing the Raw Performance Secrets of SAP BW 7.4 (A Deep Dive into the ‘Practical Guide’ Ethos)
In BW 3.5 and 7.0, your fact tables (F-fact tables and E-fact tables) were designed to minimize disk I/O for row-based databases like Oracle or DB6. But on HANA, row storage is poison. It destroys parallelization.