Sap Bw 7.4 Practical Guide Pdf 28 Info

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 .

For years, a quiet, dog-eared document circulated among senior BW consultants: a PDF simply titled "SAP BW 7.4 Practical Guide." And within that guide, was the threshold.

To truly clean house, you didn't need a re-org. You needed RSRV analysis (transaction code) to identify "empty requests" and then RSDD_HDB_DROP_DB_INDEX followed by RSDD_HDB_CREATE_DB_INDEX .

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 . sap bw 7.4 practical guide pdf 28

Page 28 would show you the dark art of the — specifically, how to convert your cube to "cube merge" mode and enable INMEMORY_AGGREGATION .

Why? Because HANA’s optimizer relies on fresh statistics. If your stats were from the last system copy three months ago, HANA would generate a brilliant execution plan for a dataset that no longer existed. You’d see a query take 12 seconds that should take 200 milliseconds.

But here is the practical kicker that most blogs missed: Even after conversion, your F table still contained REQUEST_GUID entries for every single data load. That’s right—every DTP request left a forensic trail inside the fact table. Page 28 would have scolded you: "Index maintenance

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.

In older BW releases, the system was brilliant at navigating via SID tables. In 7.4 on HANA, the game changed. The guide would warn you: "Stop forcing HANA to behave like an OLAP processor."

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 . On the other: CompositeProvider

Now go check your RSDD_HDB logs. You’ll probably find an index that hasn’t been rebuilt since 2018.

Run transaction ST04 (DBACOCKPIT). Look for "High Wait Time on Locks." Then, run RSRT with the technical name of your slowest query. Turn on "HANA Execution Details."

Have your own page 28 story from BW 7.4? Share your worst "HANA hangover" tale in the comments below.

It had one foot in the legacy world of transparent tables, aggregate rollups, and process chains that looked like spaghetti. And its other foot was firmly planted in the future—in-memory computing, columnar storage, and the promise of "instant" reporting.