SAP To Acquire Business Objects In $6.8-Billion Friendly Takeover ...old 2007 news. The integration process is well into its final phases. How has the integration impacted you?
One of the things SAP does not do is to keep duplicate competing products. An initial product roadmap has been announced for the Business Objects and SAP product lines. The immediate impact is on the front end tools targeting the business user community
BEx bye bye!
The plan is to
The latest Business Objects Enterprise release available is XIR3.1. An SAP Integration kit is available as a separate package which enables SAP and Business Objects Systems to communicate.
There were quite a few questions in Infodays. I was intrigued by two in particular
The field eagerly awaits details. The current BEx tools are tightly coupled with SAP. Crystal provides the widest range of options for connecting to SAP presently. It can connect to Tables Clusters and Functions via the OpenSQL driver, talk to Infosets, Queries, cubes and the ODS and seems to be front runner. The OLAP/BAPI driver is used by Webi and Voyager and does not require the transports. Web Intelligence and Voyager is much easier to use than Crystal and puts the power of adhoc analysis in the hands of the Business User.
SAP product set is considered strong when it comes to heirarchies, ragged - unbalanced and the kind while this has been a traditional weakness on the Business Objects front end...expect more synergies here.
( I plan to post my journey on working with the Integration kit, complete with links so that it can be retravelled, progressing to the specific toolsets of Voyager, Web Intelligence, Xcelsius in the near term...so keep checking. comments welcome).