I am also receiving the same issue! I think it's the way Power BI is calling the data or something that is maxing out our memory in SAP BW since I could see the entire InfoProvider when I looked at it in BEx Analyzer. Has anyone come up with a solution or work around?
no... so far, the best option is to adjust SAP BW in small cubes, this way the conversion is faster and does not run out of available memory and resources.
or use direct query in Power BI, but then you can only create measures. you cannot se data or relationship.
In direct query mode, it doesn't load the whole cube, but it do many small request with few axes, one by graph or visualisation.
Same thing with analysis for office for exemple.
In import mode, it try to load one big set of data with many axes so it use a lot more memory on SAP application server side.
I think it's not a Power BI bug or a bad SAP configuration but more a concept weakness. Responsiveness of import mode come at a price...