I’ve been offline and haven’t blogged or responded to comments for quite some time and frankly I don’t have any good excuses:
- I fell asleep
- My dog ate my WordPress login account info (never mind that I don’t have a dog yet)
- I was working (yeah, right)
- I used the TARDIS to back in time to the Byzantine empire and became a Roman soldier…oh wait, that’s me confusing the awesome Doctor Who episode “The Pandorica Opens” with reality again
Okay, no more excuses and back to work! I’ll catch up on the comments eventually too!
So it’s the new year (well….28 days into it) and what’s my first post – PowerPivot and SAP!
The basic gist of the paper is that there are six scenarios for PowerPivot to connect to SAP but none of them are a direct connection between PowerPivot and SAP:
- Importing data into PowerPivot via an Excel PivotTable connected to SAP BW
- Importing data into PowerPivot via SQL Server Reporting Services connected to SAP BW
- Importing data into PowerPivot from a text file generated using SAP BW Open Hub Service
- Importing data into PowerPivot from a SQL Server Analysis Services cube connected to SAP BW created using ERP-Link iNet.BI
- Importing data into PowerPivot using Xtract PPV connected to SAP BW
- Importing data into PowerPivot using Simplement Data Liberator connected to SAP ERP
If you want to review more about how these techniques work, read on to the paper, eh?!
And if you’re looking for me, I’m probably looking to fight the Daleks again… (it’s a Doctor Who reference)
Emergency Temporal Shift! Well done, sir!