{"id":2193,"date":"2020-04-15T15:41:23","date_gmt":"2020-04-15T15:41:23","guid":{"rendered":"https:\/\/www.biconnector.com\/blog\/?p=2193"},"modified":"2020-12-22T12:32:42","modified_gmt":"2020-12-22T12:32:42","slug":"how-to-connect-power-bi-to-obiee-and-oac-without-costly-re-engineering","status":"publish","type":"post","link":"https:\/\/www.biconnector.com\/blog\/how-to-connect-power-bi-to-obiee-and-oac-without-costly-re-engineering\/","title":{"rendered":"How to Connect Power BI to OBIEE and OAC [Without Costly Re-engineering]"},"content":{"rendered":"\n
When visualizing OBIEE\/Oracle Analytics Cloud (OAC) Subject Areas and Reports in Power BI, the users most often experience hiccups in establishing a seamless connectivity from Power BI to OBIEE\/Oracle Analytics Cloud (OAC).<\/p>\n\n\n\n
The manual process of exporting and importing data from OBIEE to Power BI is cumbersome. On top of that, the users also spend a huge amount of time again in blending OBIEE data with data from other data sources. <\/p>\n\n\n\n
The users typically end up spending an average of 4 to 5 hours every week in the overhead activities (export\/import and mash-up), which when monetized roughly estimates to a productivity loss of $10000\/user\/year.<\/p>\n\n\n\n
On the other hand, the re-engineering option to create the complex schema, joins, aggregations and reports (created with years of efforts in OBIEE) in Power BI from the scratch roughly costs more than $250,000 in new investment, and takes about 5 months\/Subject Area.<\/p>\n\n\n